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
Architecture review: Failback after recovery and Recovery point objective. Requirement A: A team has documented failover to a secondary region but no controlled return to primary. Requirement B: A business may lose at most five minutes of writes during failover. Which complete two-part proposal satisfies both constraints?
For requirement A, failback is a separate operational sequence after workloads run in the recovery site. For requirement B, RPO measures the maximum tolerated data loss period at a recovery point. Verify both independently: A controlled failback returns traffic and state to the primary without unplanned data loss; Failover comparison shows the latest committed recoverable write is within five minutes.
The option covers one requirement but substitutes Cosmos continuous backup for Recovery point objective. The missing acceptance result is: Failover comparison shows the latest committed recoverable write is within five minutes.
RPO measures the maximum tolerated data loss period at a recovery point. The other proposed action (protect the VM with Azure Backup using a supported vault and retention policy) does not implement the first control. Failback is a separate operational sequence after workloads run in the recovery site.
This combines Azure VM backup policy and Cosmos continuous backup, which do not satisfy the distinct requirements for Failback after recovery and Recovery point objective.
A business process requires approvals plus connectors for Microsoft 365 and a SaaS ticketing system. An architecture board will approve a solution only if this outcome is demonstrated: An approved request creates the expected ticket and notifies the right mailbox. What should be selected?
Logic Apps offers managed integration workflows and prebuilt service connectors. The selected architecture is choose Logic Apps workflows with supported connector authentication; confirm the result by checking that an approved request creates the expected ticket and notifies the right mailbox.
An API gateway can broker external requests to private backends without direct public backend access. That is useful for API private backends (An internet-facing API gateway must call a private service not directly exposed to the internet). It does not meet the current Logic Apps connector workflow requirement: A business process requires approvals plus connectors for Microsoft 365 and a SaaS ticketing system.
Topics fan out a message to independently managed subscriptions with durable handling. Its design target is Publish subscribe topics. The stated requirement instead concerns: A business process requires approvals plus connectors for Microsoft 365 and a SaaS ticketing system.
APIM can enforce per-client API consumption controls before requests reach backends. It does not solve the specified Logic Apps connector workflow condition.
Backup workloads in restricted networks must avoid general public service access where supported. An engineer must deliver the following acceptance evidence: Protected workload backup succeeds through the approved private networking arrangement. What design choice is defensible?
Backup private connectivity has service and workload prerequisites distinct from ordinary storage private endpoints. The selected architecture is use approved private endpoint configuration for the supported backup scenario; confirm the result by checking that protected workload backup succeeds through the approved private networking arrangement.
Managed PostgreSQL backups support rebuilding a server at a selected valid recovery time. It does not solve the specified Backup private endpoints condition.
Backup-specific RBAC roles separate operational restore tasks from vault administration. The relevant requirement is: Backup workloads in restricted networks must avoid general public service access where supported.
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 Backup private endpoints requirement: Backup workloads in restricted networks must avoid general public service access where supported.
A backend API should expose delegated scopes to a client on behalf of a signed-in user. An architecture board will approve a solution only if this outcome is demonstrated: The API token contains the required scope and access without that scope is rejected. What should be selected?
Delegated permissions represent what an application can do on behalf of an authenticated user. The selected architecture is define exposed API permissions in the app registration and require consent as appropriate; confirm the result by checking that the API token contains the required scope and access without that scope is rejected.
Azure SQL supports Entra authentication and compatible managed identities can eliminate stored SQL secrets. The relevant requirement is: A backend API should expose delegated scopes to a client on behalf of a signed-in user.
App-only permissions grant service principal operations without a delegated signed-in user. It does not solve the specified App registration API scopes condition.
Administrative units scope eligible directory management roles to selected objects, not data visibility. Its design target is Delegation with admin units. The stated requirement instead concerns: A backend API should expose delegated scopes to a client on behalf of a signed-in user.
Architecture rationale review—On-prem AD federation: Design supported hybrid identity integration for the existing Active Directory dependency. Which explanation accurately distinguishes this capability?
Hybrid identity connects on-prem directories and cloud identity but legacy protocols may need separate infrastructure. It is material here because legacy apps require on-premises Active Directory-integrated authentication while using Azure for modern services.
Administrative units scope eligible directory management roles to selected objects, not data visibility. Hybrid identity connects on-prem directories and cloud identity but legacy protocols may need separate infrastructure.
External ID consumer capabilities support customer journeys distinct from employee workforce governance. It belongs to Consumer sign-in. The stated architecture instead relies on: Hybrid identity connects on-prem directories and cloud identity but legacy protocols may need separate infrastructure.
Management locks guard against accidental resource deletes and operate separately from authorization roles. Hybrid identity connects on-prem directories and cloud identity but legacy protocols may need separate infrastructure.
A legacy Windows service requires full OS control and custom drivers but has moderate CPU and memory needs. Identify the most suitable implementation for an outcome where the workload runs its required driver within the provisioned compute budget.
General-purpose VMs balance CPU and memory while retaining OS-level control. The selected architecture is choose an appropriately sized general-purpose Azure VM with supporting disks and network; confirm the result by checking that the workload runs its required driver within the provisioned compute budget.
AKS provides managed Kubernetes control-plane hosting with configurable worker clusters. That is useful for AKS full Kubernetes (A platform team needs custom Kubernetes network policies controllers and cluster API access). It does not meet the current General purpose VM requirement: A legacy Windows service requires full OS control and custom drivers but has moderate CPU and memory needs.
ACR stores OCI images and supports Azure identity-based authorization to the registry. It does not solve the specified General purpose VM condition.
Spot instances offer lower-priced spare capacity without guaranteed availability. The relevant requirement is: A legacy Windows service requires full OS control and custom drivers but has moderate CPU and memory needs.
A downstream service stays unhealthy and unlimited client retries exhaust all front-end worker threads. A deployment must satisfy this operational criterion: Unhealthy requests fail quickly and the service resumes calls after recovery. Which plan is appropriate?
Circuit breakers stop futile downstream calls temporarily and permit controlled re-entry. The selected architecture is use an application circuit breaker with timeout and recovery probing; confirm the result by checking that unhealthy requests fail quickly and the service resumes calls after recovery.
PDBs constrain voluntary disruptions but do not prevent all involuntary failures. The relevant requirement is: A downstream service stays unhealthy and unlimited client retries exhaust all front-end worker threads.
Failover-group listeners abstract the primary location during regional failover. It does not solve the specified Circuit breaker behavior condition.
Availability sets spread VM instances across host-related fault and update domains within a datacenter. That is useful for Availability set (A legacy VM workload runs in a region without required availability zones but needs protection from host maintenance faults). It does not meet the current Circuit breaker behavior requirement: A downstream service stays unhealthy and unlimited client retries exhaust all front-end worker threads.
Architecture review: Cosmos conflict handling and Premium SSD v2. Requirement A: A multi-write-region Cosmos account can update the same logical item concurrently. Requirement B: A VM workload needs independently adjustable provisioned IOPS and throughput with SSD latency. Which complete two-part proposal satisfies both constraints?
For requirement A, concurrent writes require a conflict resolution policy to prevent unintended last-writer outcomes. For requirement B, premium SSD v2 decouples some provisioned performance settings from disk capacity. Verify both independently: A controlled simultaneous update resolves according to the documented business rule; The disk achieves its provisioned IOPS and throughput under a supported VM configuration.
The first step implements Storage service endpoints instead of Cosmos conflict handling. The necessary change is to define supported multi-region conflict resolution strategy and concurrency controls.
Both proposed halves address other use cases: Storage service endpoints and Cosmos DB NoSQL. The requested pair is Cosmos conflict handling and Premium SSD v2.
The mismatched half is Cosmos DB NoSQL; Premium SSD v2 instead needs: Evaluate Premium SSD v2 managed disks where region and VM support permit.
Architecture review: Application Gateway zone redundancy and Zone-redundant load balancer. Requirement A: A web workload requires HTTP routing and WAF across availability zones. Requirement B: A regional application needs one L4 frontend distributing traffic to healthy VMs across zones. Which complete two-part proposal satisfies both constraints?
For requirement A, application Gateway offers L7 proxy capabilities with WAF unlike a basic L4 load balancer. For requirement B, load Balancer routes TCP/UDP flows to healthy backends without terminating HTTP requests. Verify both independently: The gateway keeps HTTP traffic flowing when a backend zone is unavailable; Failed backend probes remove one instance and healthy zonal instances continue serving.
Both proposed halves address other use cases: VM scale set autoscaling and Cosmos multi-write availability. The requested pair is Application Gateway zone redundancy and Zone-redundant load balancer.
One action is correct. The other targets Cosmos multi-write availability, leaving Zone-redundant load balancer unsolved. Its necessary action is: Use a supported zone-redundant Standard Load Balancer deployment with health probes.
Load Balancer routes TCP/UDP flows to healthy backends without terminating HTTP requests. The other proposed action (use Virtual Machine Scale Sets with autoscale rules and a stateless design) does not implement the first control. Application Gateway offers L7 proxy capabilities with WAF unlike a basic L4 load balancer.
The design team completed work on Peering nontransitivity. Its governing requirement was: Spoke A peers with the hub and spoke B peers with the same hub but cannot communicate directly. Identify the conclusive verification result.
VNet peering alone is not transitive and forwarding needs explicit architecture. Confirm using the measurable result: Permitted spoke-to-spoke traffic follows inspected hub path and denied traffic fails.
VPN Gateway can establish encrypted IPsec tunnels over public networks. The distinguishing check is: Permitted spoke-to-spoke traffic follows inspected hub path and denied traffic fails.
Private endpoints attach supported PaaS access to a private IP and require DNS resolution. The offered observation would demonstrate Private endpoint: The data source resolves to a VNet private address and public access is denied. The current validation is different: Permitted spoke-to-spoke traffic follows inspected hub path and denied traffic fails.
Route Server enables BGP exchange with NVAs without custom per-prefix UDR maintenance. Those observations validate Route Server dynamic routing. They do not establish the required Peering nontransitivity result: Permitted spoke-to-spoke traffic follows inspected hub path and denied traffic fails.
Compliance requires offsite protected copies of blob data separate from only operational object versioning. The acceptance test is: An eligible blob recovery point is restored using the protected vault workflow. Which design recommendation best satisfies both?
Vaulted blob backup supplies protected backup storage with different capabilities than operational backups. The selected architecture is evaluate supported vaulted backup for blobs with documented feature and region limits; confirm the result by checking that an eligible blob recovery point is restored using the protected vault workflow.
A non-disruptive DR test validates recovery sequences and dependencies before a real disaster. The relevant requirement is: Compliance requires offsite protected copies of blob data separate from only operational object versioning.
Failback is a separate operational sequence after workloads run in the recovery site. It does not solve the specified Blob vaulted backup condition.
Share snapshots preserve file-share point-in-time state for supported restoration. That is useful for Azure Files snapshots (An Azure Files SMB share needs hourly recovery of files accidentally overwritten by users). It does not meet the current Blob vaulted backup requirement: Compliance requires offsite protected copies of blob data separate from only operational object versioning.
Please check your mailbox for a message from support@examlabs.com and follow the directions.