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 developer accidentally deletes a container and the organization wants short-term recovery. The acceptance test is: An accidentally deleted test object is recovered before retention expires. Which design recommendation best satisfies both?
Soft delete retains recoverable deleted objects or containers during the configured period. The selected architecture is enable appropriate Blob and container soft-delete features within retention; confirm the result by checking that an accidentally deleted test object is recovered before retention expires.
Autoscale adjusts provisioned RU/s capacity according to measured load within a maximum. It does not solve the specified Blob soft delete condition.
Versioning preserves older object versions independently of current content overwrites. That is useful for Blob versioning (A file is frequently overwritten and teams need to restore the value before the last upload). It does not meet the current Blob soft delete requirement: A developer accidentally deletes a container and the organization wants short-term recovery.
Archive tier minimizes long-term storage cost but archived objects must be rehydrated before reading. The relevant requirement is: A developer accidentally deletes a container and the organization wants short-term recovery.
The target environment adopts this approach for Vault immutability: Enable an appropriately configured immutable Azure Backup vault with supporting controls. What property makes it suitable?
Immutable backup settings can prevent specified destructive operations against protected backups. It is material here because a security audit worries a compromised backup administrator could delete protected recovery points.
A non-disruptive DR test validates recovery sequences and dependencies before a real disaster. It belongs to Recovery drill governance. The stated architecture instead relies on: Immutable backup settings can prevent specified destructive operations against protected backups.
RTO is the maximum acceptable restoration duration, not the amount of lost data. That statement describes Recovery time objective, while the question asks how Vault immutability works: Immutable backup settings can prevent specified destructive operations against protected backups.
Periodic backups produce interval snapshots and are not the same as continuous point-in-time recovery. Immutable backup settings can prevent specified destructive operations against protected backups.
An architect must sign off on Hub-spoke topology. The business problem is: Many app VNets need shared DNS firewall and on-prem connectivity without each owning a gateway. What observed test result provides valid evidence?
A hub centralizes connectivity services while spoke VNets isolate applications. Confirm using the measurable result: A spoke accesses approved hub services and another spoke only through authorized routing.
VNet peering alone is not transitive and forwarding needs explicit architecture. The Peering nontransitivity test checks permitted spoke-to-spoke traffic follows inspected hub path and denied traffic fails; the relevant outcome is A spoke accesses approved hub services and another spoke only through authorized routing.
NAT Gateway provides outbound SNAT for supported subnet internet traffic. The offered observation would demonstrate NAT Gateway outbound: External partners observe only the approved outbound IP during simultaneous worker sessions. The current validation is different: A spoke accesses approved hub services and another spoke only through authorized routing.
User-defined routes can override platform routing to steer approved subnets through an NVA/firewall. The distinguishing check is: A spoke accesses approved hub services and another spoke only through authorized routing.
Before approving Backup private endpoints, the reviewer assesses this requirement: Backup workloads in restricted networks must avoid general public service access where supported. Which of the reported outcomes is decisive?
Backup private connectivity has service and workload prerequisites distinct from ordinary storage private endpoints. Confirm using the measurable result: Protected workload backup succeeds through the approved private networking arrangement.
Periodic backups produce interval snapshots and are not the same as continuous point-in-time recovery. Those observations validate Cosmos periodic backup. They do not establish the required Backup private endpoints result: Protected workload backup succeeds through the approved private networking arrangement.
RTO is the maximum acceptable restoration duration, not the amount of lost data. The distinguishing check is: Protected workload backup succeeds through the approved private networking arrangement.
Blob operational backup relies on point-in-time object protection features rather than VM-level backups. The Blob operational backup test checks a deleted supported blob is restored to the requested prior point in the configured interval; the relevant outcome is Protected workload backup succeeds through the approved private networking arrangement.
A serverless order process needs retries and persisted orchestration across multiple long-running steps. A deployment must satisfy this operational criterion: Restarting a worker does not restart already completed business steps. Which plan is appropriate?
Durable orchestrations checkpoint progress and coordinate stateful serverless workflows. The selected architecture is choose Durable Functions with explicit orchestrator and activity functions; confirm the result by checking that restarting a worker does not restart already completed business steps.
Event Hubs provides a replayable ordered stream within partitions for large event volumes. It does not solve the specified Durable Functions orchestration condition.
Queueing decouples front-end latency from downstream worker availability. That is useful for Queue asynchronous processing (Checkout requests should return promptly while invoices are generated asynchronously with retry support). It does not meet the current Durable Functions orchestration requirement: A serverless order process needs retries and persisted orchestration across multiple long-running steps.
Topics fan out a message to independently managed subscriptions with durable handling. The relevant requirement is: A serverless order process needs retries and persisted orchestration across multiple long-running steps.
A solution must address both Cross-region backup and Azure VM backup policy. First requirement: An organization requires VM backup copies surviving the loss of an entire Azure region. Second requirement: A production Azure VM must be recoverable to an earlier day after accidental deletion of application files. Select TWO recommendations that meet these independent needs.
For the Cross-region backup half of this two-part design, geo-redundant vault storage can provide recovery copies in a paired region subject to feature settings. Verify: A supported secondary-region restore yields the expected recovery point. The other half concerns Azure VM backup policy.
For the Azure VM backup policy half of this design, Azure Backup creates managed recovery points distinct from continuously replicating a running VM. Check: A file-level restore recovers the deleted content from the appropriate recovery point. The other half concerns Cross-region backup.
Vaulted blob backup supplies protected backup storage with different capabilities than operational backups. Its own validation would be: An eligible blob recovery point is restored using the protected vault workflow. The current paired requirement is Cross-region backup and Azure VM backup policy.
Soft delete retains recoverable protected backup data after deletion for a configured interval. This alternative solves Backup soft delete, while the question separately requires Cross-region backup and Azure VM backup policy.
Geo-restore is backup-based recovery with different RTO/RPO than active geo-replication. That plan is appropriate for SQL geo-restore. The two controls sought here are Cross-region backup and Azure VM backup policy.
A solution must address both Retire unused services and Refactor monolith. First requirement: An application inventory shows unused servers with no business owner or dependent traffic. Second requirement: An app must separate independent high-scale workloads and use managed messaging. Select TWO recommendations that meet these independent needs.
For the Retire unused services half of this two-part design, retiring unused assets reduces migration risk and cloud cost rather than copying unnecessary VMs. Verify: Decommissioned workloads create no application dependency failure. The other half concerns Refactor monolith.
For the Refactor monolith half of this design, refactoring changes application structure and decouples independent workloads. Check: One service can scale independently and failures are isolated through messaging. The other half concerns Retire unused services.
Sizing, licensing and consumption assumptions materially affect target economics. This alternative solves Modernization cost assessment, while the question separately requires Retire unused services and Refactor monolith.
Hidden dependencies can break after migration even when VM replication succeeds. That plan is appropriate for Application dependency mapping. The two controls sought here are Retire unused services and Refactor monolith.
Replatforming changes hosting characteristics while preserving most app behavior. Its own validation would be: Migration validation shows required database features function on the selected managed tier. The current paired requirement is Retire unused services and Refactor monolith.
A proposed solution for Availability set is: Use an availability set with fault and update domains if suitable. Select the strongest statement supporting the recommendation.
Availability sets spread VM instances across host-related fault and update domains within a datacenter. It is material here because a legacy VM workload runs in a region without required availability zones but needs protection from host maintenance faults.
Fault injection tests whether resilience patterns work under realistic failure conditions. Availability sets spread VM instances across host-related fault and update domains within a datacenter.
Cluster autoscaler adjusts nodes to schedule eligible pending pods. It belongs to AKS cluster autoscaler. The stated architecture instead relies on: Availability sets spread VM instances across host-related fault and update domains within a datacenter.
Circuit breakers stop futile downstream calls temporarily and permit controlled re-entry. That statement describes Circuit breaker behavior, while the question asks how Availability set works: Availability sets spread VM instances across host-related fault and update domains within a datacenter.
The Cosmos multi-region reads review proposes: Add appropriate Cosmos DB read regions and choose the fitting consistency level. Which Azure behavior is the technical justification for this decision?
Read regions bring replicas closer to users without inherently adding multi-write semantics. It is material here because a globally distributed document API needs local low-latency reads near users in multiple regions.
Fault injection tests whether resilience patterns work under realistic failure conditions. Read regions bring replicas closer to users without inherently adding multi-write semantics.
VMSS can add or remove similarly configured VM instances based on supported signals. That statement describes VM scale set autoscaling, while the question asks how Cosmos multi-region reads works: Read regions bring replicas closer to users without inherently adding multi-write semantics.
PDBs constrain voluntary disruptions but do not prevent all involuntary failures. Read regions bring replicas closer to users without inherently adding multi-write semantics.
The acceptance criterion for Compute optimized VM comes from this issue: A stateless batch worker is CPU-bound with little disk IO or memory pressure. Which measured outcome is the strongest proof?
Compute-optimized instances prioritize vCPU capacity over excess memory. Confirm using the measurable result: The same batch finishes within the required CPU time without memory bottlenecks.
AKS provides managed Kubernetes control-plane hosting with configurable worker clusters. The distinguishing check is: The same batch finishes within the required CPU time without memory bottlenecks.
Memory-optimized sizes offer higher RAM-to-vCPU ratio for large in-memory working sets. The Memory optimized VM test checks paging falls and the working data fits within the selected RAM capacity; the relevant outcome is The same batch finishes within the required CPU time without memory bottlenecks.
Azure Batch schedules large-scale parallel workloads across managed compute pools. Those observations validate Azure Batch scheduling. They do not establish the required Compute optimized VM result: The same batch finishes within the required CPU time without memory bottlenecks.
For the RBAC custom role requirement, the proposed architecture uses: Create a least-privilege custom Azure RBAC role and assign it at minimal scope. Why does that design fit?
Custom role actions can grant specific management operations without broad Contributor rights. It is material here because a service team needs a narrow set of resource restart and read operations absent from built-in roles.
Management groups supply governance scope above subscriptions without moving resources into a single subscription. That statement describes Management group hierarchy, while the question asks how RBAC custom role works: Custom role actions can grant specific management operations without broad Contributor rights.
Azure Policy can deny targeted resource types without revoking all contributor operations. Custom role actions can grant specific management operations without broad Contributor rights.
Policy deny or audit effects can enforce required metadata at supported resource scopes. It belongs to Required tag policy. The stated architecture instead relies on: Custom role actions can grant specific management operations without broad Contributor rights.
Please check your mailbox for a message from support@examlabs.com and follow the directions.