You save $69.98
AZ-305 Premium Bundle
- Premium File 382 Questions & Answers
- Last Update: Nov 20, 2026
- Training Course 87 Lectures
- Study Guide 933 Pages
You save $69.98
A production Azure VM must be recoverable to an earlier day after accidental deletion of application files. Identify the most suitable implementation for an outcome where a file-level restore recovers the deleted content from the appropriate recovery point.
Azure Backup creates managed recovery points distinct from continuously replicating a running VM. The selected architecture is protect the VM with Azure Backup using a supported vault and retention policy; confirm the result by checking that a file-level restore recovers the deleted content from the appropriate recovery point.
Backup private connectivity has service and workload prerequisites distinct from ordinary storage private endpoints. Its design target is Backup private endpoints. The stated requirement instead concerns: A production Azure VM must be recoverable to an earlier day after accidental deletion of application files.
Continuous backup can support point-in-time restore for supported Cosmos API accounts. It does not solve the specified Azure VM backup policy condition.
Site Recovery replicates workload state and orchestrates VM failover for supported scenarios. That is useful for Azure Site Recovery failover (An enterprise VM workload needs a tested recovery-site boot process after complete primary-region loss). It does not meet the current Azure VM backup policy requirement: A production Azure VM must be recoverable to an earlier day after accidental deletion of application files.
A rollout addressing Cosmos bounded staleness has reached acceptance testing. The original problem was: A globally replicated document store accepts a known upper bound on read lag but not unbounded eventual lag. Which finding verifies its resolution?
Bounded staleness constrains replication read lag according to allowed versions/time. Confirm using the measurable result: A test secondary read remains within the documented staleness bound.
Tiering trades storage price against access and retrieval cost based on usage. The offered observation would demonstrate Blob hot/cool/cold: Old eligible blobs transition to the intended tier and remain retrievable. The current validation is different: A test secondary read remains within the documented staleness bound.
Blob change feed records changes to blob objects for downstream processing. Those observations validate Blob change feed. They do not establish the required Cosmos bounded staleness result: A test secondary read remains within the documented staleness bound.
Blob Storage manages massively scalable object data rather than SMB-compatible shared volumes. The Blob object storage test checks a client uploads and downloads an object using its scoped authorization; the relevant outcome is A test secondary read remains within the documented staleness bound.
The acceptance criterion for Secrets in deployment pipeline comes from this issue: An IaC deployment includes a storage connection string directly in ARM/Bicep parameter files committed to source control. Which measured outcome is the strongest proof?
Secure secret handling removes reusable credentials from source while preserving automation. Confirm using the measurable result: The committed deployment files contain no functional credentials and the deployment still succeeds.
External ID consumer capabilities support customer journeys distinct from employee workforce governance. Those observations validate Consumer sign-in. They do not establish the required Secrets in deployment pipeline result: The committed deployment files contain no functional credentials and the deployment still succeeds.
App-only permissions grant service principal operations without a delegated signed-in user. The distinguishing check is: The committed deployment files contain no functional credentials and the deployment still succeeds.
Delegated permissions represent what an application can do on behalf of an authenticated user. The App registration API scopes test checks the API token contains the required scope and access without that scope is rejected; the relevant outcome is The committed deployment files contain no functional credentials and the deployment still succeeds.
Architecture review: Deployment drift and Standardized IaC. Requirement A: A production app's manually changed resource settings diverge from the approved IaC template. Requirement B: Operations wants reproducible Azure environment deployments from version-controlled definitions. Which complete two-part proposal satisfies both constraints?
For requirement A, Azure deployment what-if previews resource changes before applying a template. For requirement B, infrastructure as code declares desired resources and allows review and repeat deployment. Verify both independently: The change report identifies manual drift and approved deployment restores the intended state; The same versioned module deploys matching compliant resources across test environments.
Infrastructure as code declares desired resources and allows review and repeat deployment. The other proposed action (schedule supported Cost Management exports to an authorized storage destination) does not implement the first control. Azure deployment what-if previews resource changes before applying a template.
This combines Cost export and Quotas and limits, which do not satisfy the distinct requirements for Deployment drift and Standardized IaC.
The option covers one requirement but substitutes Quotas and limits for Standardized IaC. The missing acceptance result is: The same versioned module deploys matching compliant resources across test environments.
An architect must sign off on Availability zones for VM tier. The business problem is: A web service must survive loss of one data center within an Azure region. What observed test result provides valid evidence?
Availability zones isolate infrastructure failure domains within an enabled region. Confirm using the measurable result: A simulated zonal loss leaves healthy VM instances serving requests.
Eligible App Service plans distribute app workers across availability zones with sufficient capacity. The App Service zone redundancy test checks a zonal disruption leaves the application reachable via surviving workers; the relevant outcome is A simulated zonal loss leaves healthy VM instances serving requests.
Fault injection tests whether resilience patterns work under realistic failure conditions. The offered observation would demonstrate Chaos failure testing: The app maintains the defined availability objective during planned dependency failure. The current validation is different: A simulated zonal loss leaves healthy VM instances serving requests.
Circuit breakers stop futile downstream calls temporarily and permit controlled re-entry. The distinguishing check is: A simulated zonal loss leaves healthy VM instances serving requests.
During technical sign-off for Event Grid notification, the architect selects: Use Event Grid as an event routing and notification mechanism. Which underlying behavior should be documented?
Event Grid distributes discrete source events to configured subscribers. It is material here because a storage blob upload should notify multiple Azure Functions through filterable event subscriptions.
App Configuration centralizes feature settings; secrets should remain in Key Vault. Event Grid distributes discrete source events to configured subscribers.
Failure handling isolates unhealthy dependencies and avoids request pileups. It belongs to Application resilience timeout. The stated architecture instead relies on: Event Grid distributes discrete source events to configured subscribers.
Central secret retrieval separates sensitive credentials from source and build artifacts. That statement describes Key Vault app secrets, while the question asks how Event Grid notification works: Event Grid distributes discrete source events to configured subscribers.
Architecture review: Resource RBAC versus data access and Managed identity for App Service. Requirement A: A user can view a storage account resource but cannot download its blobs. Requirement B: A web API on Azure App Service needs to read a storage blob without keeping client secrets in application settings. Which complete two-part proposal satisfies both constraints?
For requirement A, management-plane Azure RBAC Reader does not automatically authorize blob data-plane reads. For requirement B, managed identities provide Entra tokens to supported workloads while data-plane RBAC grants the actual blob permissions. Verify both independently: The user downloads an approved blob without gaining storage management privileges; A token-based read works and the app has no stored storage-account key.
The option covers one requirement but substitutes Key Vault secrets for Resource RBAC versus data access. The missing acceptance result is: The user downloads an approved blob without gaining storage management privileges.
Management-plane Azure RBAC Reader does not automatically authorize blob data-plane reads. Managed identities provide Entra tokens to supported workloads while data-plane RBAC grants the actual blob permissions. The proposed steps (store the password as a versioned Key Vault secret and retrieve it with authorized identity; apply a Conditional Access policy with an appropriate authentication strength to privileged roles) address other capabilities instead of this required pair.
Management-plane Azure RBAC Reader does not automatically authorize blob data-plane reads. The other proposed action (apply a Conditional Access policy with an appropriate authentication strength to privileged roles) addresses a different operation. Managed identities provide Entra tokens to supported workloads while data-plane RBAC grants the actual blob permissions.
Each order event must be processed by billing, shipping and analytics independently. An engineer must deliver the following acceptance evidence: All three subscribers receive an order event without direct calls from checkout. What design choice is defensible?
Topics fan out a message to independently managed subscriptions with durable handling. The selected architecture is use Service Bus topics with subscriptions when reliable broker delivery is needed; confirm the result by checking that all three subscribers receive an order event without direct calls from checkout.
Web PubSub provides managed WebSocket connection fan-out so application servers need not hold all client sessions. That is useful for Web PubSub real time (A collaboration app must send real-time server-to-client notifications to many concurrent browsers). It does not meet the current Publish subscribe topics requirement: Each order event must be processed by billing, shipping and analytics independently.
APIM can enforce per-client API consumption controls before requests reach backends. It does not solve the specified Publish subscribe topics condition.
Durable orchestrations checkpoint progress and coordinate stateful serverless workflows. The current need is: Each order event must be processed by billing, shipping and analytics independently.
Architecture review: Identity lifecycle audits and External B2B partner. Requirement A: Managers need quarterly evidence that external guest access to privileged applications is still justified. Requirement B: A supplier must access a specific application without becoming an employee in the home tenant. Which complete two-part proposal satisfies both constraints?
For requirement A, access reviews periodically recertify assigned access and can remove access for denied reviews. For requirement B, b2B collaboration supports guest principals and cross-organization access controls. Verify both independently: A rejected guest review removes the corresponding app assignment after the review closes; The supplier opens the assigned application but cannot access unrelated tenant resources.
The mismatched half is App registration API scopes; External B2B partner instead needs: Use Microsoft Entra B2B collaboration with scoped application access and appropriate external identities policy.
The first step implements Resource lock constraints instead of Identity lifecycle audits. The necessary change is to run Microsoft Entra access reviews with suitable reviewers and removal actions.
Both proposed halves address other use cases: Resource lock constraints and App registration API scopes. The requested pair is Identity lifecycle audits and External B2B partner.
The acceptance criterion for Web transaction traces comes from this issue: Users report failed checkout requests across a multi-tier web app and only CPU graphs are available. Which measured outcome is the strongest proof?
Application Insights correlates application requests exceptions and downstream dependencies rather than relying only on infrastructure CPU. Confirm using the measurable result: A failed transaction trace identifies its failing dependency and correlated exception.
The Activity Log records Azure Resource Manager control-plane events independent of guest agents. The offered observation would demonstrate Control-plane audit: A denied deployment and a successful resource deletion appear with caller and operation name. The current validation is different: A failed transaction trace identifies its failing dependency and correlated exception.
A log search alert can evaluate aggregated matching records instead of only raw metric time series. Those observations validate Log anomaly alert. They do not establish the required Web transaction traces result: A failed transaction trace identifies its failing dependency and correlated exception.
Action groups define notifications and automated responses and can be reused by alert rules. The Notification routing test checks a simulated critical alert pages the incident team while a capacity warning sends email only; the relevant outcome is A failed transaction trace identifies its failing dependency and correlated exception.
The acceptance criterion for Recovery drill governance comes from this issue: Auditors require evidence that a disaster recovery plan works without disrupting production traffic. Which measured outcome is the strongest proof?
A non-disruptive DR test validates recovery sequences and dependencies before a real disaster. Confirm using the measurable result: The test network runs recovered workloads and production endpoints remain unaffected.
Multi-user authorization separates approval boundaries for critical backup changes. Those observations validate Multifactor critical operations. They do not establish the required Recovery drill governance result: The test network runs recovered workloads and production endpoints remain unaffected.
RPO measures the maximum tolerated data loss period at a recovery point. The distinguishing check is: The test network runs recovered workloads and production endpoints remain unaffected.
Immutable backup settings can prevent specified destructive operations against protected backups. The Vault immutability test checks a forbidden backup deletion or retention reduction is rejected during the configured protection period; the relevant outcome is The test network runs recovered workloads and production endpoints remain unaffected.
Please check your mailbox for a message from support@examlabs.com and follow the directions.