LPI 305-300 Exam Actual Questions
LPIC-3: Virtualization and Containerization - 305, version 3.0 (Page 2 )

• What D means: In Security Command Center (SCC), a posture combines both preventative controls (predefined and custom organization policies) and detective controls (predefined and custom Security Health Analytics [SHA] modules). Scope this posture to the business unit folder to enforce those controls across the Vertex AI environment.

• Why this is correct: You need both preventative guardrails (policies) and detective guardrails (SHA findings) to meet internal security requirements. A posture provides a unified, scalable way to apply and monitor these controls to a specific organizational unit.

• Why the other options are weaker:

• If you want, I can break down the exact components of a SCC posture and how to apply it to a Vertex AI project.

• Create Power Query parameters for the Azure SQL server/database—or at least the database name.
• Use the parameter in the PBIX connection.
• Publish the same PBIX separately to the relevant development, test, and production workspaces.
• Set each dataset’s parameter value in the Power BI service so it points to the corresponding Azure SQL database.

• Development dataset ? DevelopmentDB
• Test dataset ? TestDB
• Production dataset ? ProductionDB

• The same PBIX is used for every lifecycle stage.
• Each stage consumes data from its matching database.
• Deployment pipelines are not required.
• Azure SQL is a cloud source, so gateway administration is generally avoided.
• Only the parameter value differs between published datasets, reducing maintenance.

• Users retain their existing usernames and passwords.
• Existing accounts can be used to access Azure-based resources.
• Administrators avoid manually recreating thousands of accounts.
• The transition is less disruptive before the on-premises data center is retired.

• A (training data, hyperparameters, stakeholder feedback) focuses on training provenance; these details are important but are typically part of pre-deployment/training records, not the primary post-deployment documentation.
• B (encountered issues, monitoring process, risks) relates to governance and monitoring rather than the core documentation you’d publish about the deployed model itself.
• C (licensing information, the team, business goals) covers governance context but not the technical traceability and performance-based record needed for ongoing maintenance.

• Co to znaczy: transakcje zachowuja sie tak, jakby byly wykonywane jeden po drugim. Dzieki temu nie ma brudnych odczytów, niepowtarzalnych odczytów ani phantom reads.

• Implementacja: PostgreSQL uzywa SSI (Serializable Snapshot Isolation). W praktyce oznacza to, ze jesli wykryje konflikt miedzy transakcjami, jedna z nich zostanie zakonczona bledem “serialization failure” i trzeba ja ponowic.

• Zalózmy tabele orders(customer_id int, amount int).

• Transakcja T1:

• Transakcja T2, równoczesnie:

• T1 ponownie wykonuje to zapytanie:

• Strongest encryption algorithms: Choose the strongest available encryption and integrity options, typically AES with the largest key size and a secure integrity algorithm.
• Encrypt all traffic: Select tunnel mode rather than transport mode. Tunnel mode encrypts the entire original IP packet, which is appropriate for a site-to-site VPN between branch networks.
• Secret-password authentication: Configure a pre-shared key (PSK) on both VPN concentrators. The key must match at both ends.

• A: True. You can change the size of a Virtual Warehouse after creation (via UI or ALTER WAREHOUSE).

• B: True. A warehouse can be resized while it’s running; the resize will take effect without needing to stop queries.

• C: True. A warehouse can be configured to suspend after a period of inactivity (AUTO_SUSPEND).

• D: True. A warehouse can be configured to auto-resume when new queries are submitted (AUTO_RESUME).

• Equipment and hardware
• Facilities
• Inventory
• Backup media
• Supplies stored at an alternate or remote location

• Personal belongings of staff: Usually not organizational assets.
• DR line-item revenues: Revenue is a financial impact, not a physical asset.
• Cloud-based applications: These are primarily logical or information-processing assets, even though they depend on physical infrastructure.

• Enable the owner dimension
• Allocate a standard costing inventory model

• Owner dimension (B): This dimension Lets you track who owns the stock. By enabling the owner dimension, items can be configured as either company owned or consignment (vendor-owned) when you create or edit items. Without enabling this dimension, you can’t designate ownership per item.
• Standard costing inventory model (D): Selecting a costing model determines how item costs are calculated and posted. Standard costing provides a fixed cost per unit, which is commonly used for agreed pricing scenarios like consignment arrangements for easier accounting and valuation. It helps ensure consistent cost treatment across transactions for items that can be owned by the company or on consignment.

• Batch dimension (A): Batch tracking is unrelated to ownership and isn’t required to support company-owned vs. consignment configurations.
• Moving average costing (C): This is an alternative costing method. It’s not required to enable ownership config, and the exam’s expected choice focuses on standard costing for this scenario.

• Answer: Data enhancement.

• Why: Augmenting gold-layer tables with an additional dataset is enriching or enhancing the existing data to support the ad-hoc analysis. The other options don’t capture the idea of adding external data to improve the dataset (ad-hoc improvements = tweaks, last-mile dashboarding = building dashboards, last-mile ETL = ETL steps at the end of the pipeline). In practice, this is often also called data enrichment.

• SageMaker endpoint: Not required because the model is being used through Amazon Bedrock.
• SageMaker Model Registry: Used for managing SageMaker models, not for making a Bedrock custom model available.
• Grant access in Amazon Bedrock: IAM permissions may still be needed, but granting access alone does not provide the required inference capacity.

• What it’s asking: In an ARM template, for an Availability Set, what value should you set for the property platformFaultDomainCount to maximize availability during fabric failures or maintenance?

• Key concept: Fault domains are groups of hardware that can fail independently. By spreading VMs across more fault domains, you reduce the risk that a single hardware fault takes out many VMs.

• Important detail: For managed Availability Sets, the number of fault domains you can use varies by region — typically 2 or 3.

• What to choose: Set platformFaultDomainCount to the maximum supported in your region. In most regions this is 3, which gives you the best resilience. If your region only supports 2, you’d use 2.

• Answer: 3 (Max Value). In ARM template syntax, this would appear as "platformFaultDomainCount": 3 (within the Availability Set resource).

• A — IDS attack signatures: An IDS generally detects suspicious network activity but does not necessarily scan uploaded PDF files or prevent them from being accepted.
• C — Load balancer: Distributes traffic among servers; it does not inspect files for malware.
• D — WAF command-injection blocking: A WAF can help block web attacks such as command injection, SQL injection, and cross-site scripting, but this option does not specifically address malicious PDF uploads.

• Wiping securely overwrites the drive so the original data cannot reasonably be recovered. It is generally less expensive than physically destroying the device.
• Recycling could expose the data if the drive is not securely erased first.
• Shredding physically destroys the drive and is effective, but usually more costly and prevents reuse.
• Deletion only removes file references; it is not a secure sanitization method.

• Dynamics 365 Remote Assist — used for remote collaboration and mixed-reality scenarios.
• Dynamics 365 Finance — supports financial and operational management.
• Dynamics 365 Business Central — designed primarily for small and medium-sized businesses’ finance and operations.
• Dynamics 365 for Phones — provides mobile access to Dynamics 365 apps, including Sales, through the mobile Unified Interface.

• A — Add a Path for Stage: A Path lets users update the Opportunity’s Stage directly from the record page, without opening the full edit form. It can also display guidance and key fields.
• B — Use a Kanban list view: Users can move Opportunities between stages by dragging records between columns, which is ideal when Stage is the only field they normally change.

• Enable the owner dimension

• Assign a standard costing inventory model

• Batch dimension tracks batches or lots, such as expiration or production batches. It does not identify inventory ownership.
• Moving average is a costing method, but it is not the required choice for this consignment configuration.

• Answer: D: Making business cases for improvement action

• Continual Improvement focuses on identifying and planning improvements and ensuring they’re funded and prioritized. Creating a business case for an improvement action is part of justifying and obtaining support/resources to implement improvements.
• A (Identifying the cause of incidents) aligns with Problem Management.
• B (Authorizing changes) aligns with Change Enablement.
• C (Logging/managing incidents that result in improvement opportunities) aligns with Incident Management, not Continual Improvement.

• App Tag: a label that reflects the app’s enterprise readiness based on its Cloud Confidence Index (CCI) rating. It lets you quickly group apps (e.g., Poor, Average, Good) for policy decisions.
• App Score: a numeric value representing the CCI score. It provides a precise threshold you can use to enforce policies (e.g., block apps with Score below 50).

• You can create policies that block or restrict apps with a Poor App Tag or with an App Score under a chosen threshold.
• These two aspects let you filter cloud apps by CCI ratings during policy evaluation.

• CCL isn’t described as a real-time policy facet in this scenario.
• GDPR Readiness is a separate consideration and not the two CCI aspects used for real-time protection policy in this context.

• A. Implement retries with exponential backoff

• C. Reduce the frequency and/or size of requests

• B. Use PutRecord instead of PutRecords — PutRecord sends one record per call and does not remove the underlying throughput limitation. It may increase request overhead.
• D. Use Amazon SNS instead — SNS is not a direct fix for Kinesis shard throttling and changes the required streaming architecture.
• E. Reduce KCL consumers — KCL consumers read from Kinesis; they do not solve producer-side PutRecords throttling.

• The correct answer is Mass Transfer Tool.

• The Mass Transfer Records tool is Salesforce’s built-in way to reassign ownership of existing records in bulk. In this scenario, you need to transfer ownership of the departed rep’s accounts and opportunities to a new rep while keeping the team structure intact.

• Go to Setup > Data Management > Mass Transfer Records.
• Choose the object: Accounts (and then Opportunities, if needed).
• Set “Transfer From” (the leaving rep) and “Transfer To” (the new rep).
• Decide whether to transfer related records as well (e.g., opportunities tied to accounts) and proceed.
• Review and confirm.

• Data Loader / Data Import Wizard are for bulk import/export, not bulk reassigning ownership.
• Dataloader.io is a third-party tool; the built-in Mass Transfer tool is the standard Salesforce method for this task.

• The problem: Guest users can’t create posts in the Monthly Reports channel.
• The recommended fix (answer B): Modify the Guest access settings in the Teams admin center.

• Guest access settings control what guests are allowed to do across Teams (for example, posting, chat, and channel participation). If guests are restricted from posting, enabling the appropriate guest permissions will let them post in channels like Monthly Reports.
• The other options don’t directly change guest permissions in the way that affects posting:

• Active vs passive: Active assessment involves actively scanning targets by sending probes/packets to identify hosts, services, and vulnerabilities. Passive assessment observes traffic without probing.
• External vs internal: External assessment is about testing from outside the network perimeter; the scenario doesn’t specify external vantage, only that tools are identifying hosts/services across the enterprise network.

• What the scenario asks: You have a Power BI semantic model that pulls from multiple sources (Azure SQL Database and SharePoint Online), must support a single dataset for three reports, keep data current (daily refresh by 7 AM PT), and apply RLS to limit sales data by region. You need to choose a storage mode for the tables.

• Correct choice: Dual storage mode.

• Why Dual fits:

• Key concepts:

• Sustainability is not a CAF perspective (it's not one of the CAF perspectives).
• Performance efficiency and Reliability are pillars of the AWS Well-Architected Framework, not CAF.

• A Storage Gateway File Gateway provides an on-premises NFS/SMB file share that's backed by objects in S3. This is exactly what you need to migrate an NFS workload: applications continue using NFS, while the actual data moves to and is stored in S3.
• It can cache frequently accessed data locally for performance, while uploads go to an S3 bucket.
• Why the other options aren’t suitable:

• The problem describes the class updating field-level security on some profiles. To prevent updating fields that are not updateable for the current user, you should check each field’s updateability before making changes. Use DescribeFieldResult.isUpdateable() (e.g., via Field.describe() on each field) to guard updates.

• A and D (With Sharing): Running a class with Sharing affects record visibility, not whether a field can be updated by a user. It doesn’t prevent updates to fields the user shouldn’t modify.
• C (WITH SECURITY_ENFORCED in SOQL): This enforces FLS/FRC during queries, but it doesn’t control whether the Apex code updates fields or modifies permissions. It’s not addressing the update behavior directly.

• The explanation states that Traffic Analytics can be enabled by a user with one of these subscription-level roles:

• Question 34 — Network Contributor: Yes
• Question 35 — Owner: Yes
• Question 36 — Reader: Yes, according to the stated explanation and documentation

• Answer:

• Why:

• Why the other centers aren’t the right fit here:

python 
import azure.cognitiveservices.speech as speechsdk 


speech_config = speechsdk.SpeechConfig( 
    subscription="YOUR_KEY", 
    region="YOUR_REGION" 
)

Important Azure Speech SDK classes

• SpeechConfig

• AudioConfig

python 
  audio_config = speechsdk.audio.AudioConfig( 
      use_default_microphone=True 
  )

• SpeechRecognizer

python 
  recognizer = speechsdk.SpeechRecognizer( 
      speech_config=speech_config, 
      audio_config=audio_config 
  )

• SpeechSynthesizer

• AudioOutputConfig

 Bogotá, Colombia