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
An API waits indefinitely for a failing inventory service and exhausts its worker threads. Identify the most suitable implementation for an outcome where simulated downstream failure produces prompt controlled errors while healthy requests remain available.
Failure handling isolates unhealthy dependencies and avoids request pileups. The selected architecture is use timeouts, bounded retries and circuit breaking on downstream calls; confirm the result by checking that simulated downstream failure produces prompt controlled errors while healthy requests remain available.
Edge caching reduces origin load and latency for eligible cacheable content. Its design target is Azure Front Door caching. The stated requirement instead concerns: An API waits indefinitely for a failing inventory service and exhausts its worker threads.
Queueing decouples front-end latency from downstream worker availability. The relevant requirement is: An API waits indefinitely for a failing inventory service and exhausts its worker threads.
Web PubSub provides managed WebSocket connection fan-out so application servers need not hold all client sessions. It does not solve the specified Application resilience timeout condition.
Migrated VMs can ping local peers but cannot access on-premises databases over ExpressRoute. Choose the architecture that can be validated by this result: The Azure workload connects to on-prem data through the approved private network path.
Hybrid reachability depends on both routing and security decisions in the destination VNet. The selected architecture is check BGP advertised routes, gateway transit, NSGs and UDRs for the hybrid path; confirm the result by checking that the Azure workload connects to on-prem data through the approved private network path.
Refactoring changes application structure and decouples independent workloads. The relevant requirement is: Migrated VMs can ping local peers but cannot access on-premises databases over ExpressRoute.
DNS cutover requires propagation and dependency planning independent of VM replication. That is useful for Networking cutover DNS (A migrated app uses a new Azure IP but clients have a hardcoded old DNS endpoint). It does not meet the current Hybrid route validation requirement: Migrated VMs can ping local peers but cannot access on-premises databases over ExpressRoute.
Azure Migrate inventories servers and supports readiness and sizing assessments. It does not solve the specified Hybrid route validation condition.
An operator deletes a backup item by mistake and must recover its protected points before permanent purge. Identify the most suitable implementation for an outcome where the deleted item is recoverable within the protected deletion window.
Soft delete retains recoverable protected backup data after deletion for a configured interval. The selected architecture is use Azure Backup soft delete with suitable retention and security settings; confirm the result by checking that the deleted item is recoverable within the protected deletion window.
RPO measures the maximum tolerated data loss period at a recovery point. The current need is: An operator deletes a backup item by mistake and must recover its protected points before permanent purge.
Geo-restore is backup-based recovery with different RTO/RPO than active geo-replication. That is useful for SQL geo-restore (A SQL database without an active geo-secondary needs disaster recovery from geo-redundant backups). It does not meet the current Backup soft delete requirement: An operator deletes a backup item by mistake and must recover its protected points before permanent purge.
Compute replication does not automatically guarantee complete application network reachability. It does not solve the specified Backup soft delete condition.
Two regional web endpoints need internet-edge routing and automatic failover to a healthy region. A deployment must satisfy this operational criterion: Requests shift to healthy origin after simulated regional endpoint failure. Which plan is appropriate?
Front Door provides global application delivery and HTTP(S) origin failover at the edge. The selected architecture is use Azure Front Door with origins and origin health probes; confirm the result by checking that requests shift to healthy origin after simulated regional endpoint failure.
Load Balancer routes TCP/UDP flows to healthy backends without terminating HTTP requests. That is useful for Zone-redundant load balancer (A regional application needs one L4 frontend distributing traffic to healthy VMs across zones). It does not meet the current Front Door global failover requirement: Two regional web endpoints need internet-edge routing and automatic failover to a healthy region.
Circuit breakers stop futile downstream calls temporarily and permit controlled re-entry. Its design target is Circuit breaker behavior. The stated requirement instead concerns: Two regional web endpoints need internet-edge routing and automatic failover to a healthy region.
Cluster autoscaler adjusts nodes to schedule eligible pending pods. It does not solve the specified Front Door global failover condition.
For Application permissions, operations are closing a change that addressed: A scheduled daemon must call Microsoft Graph without an interactive user session. Which post-change signal belongs in the acceptance record?
App-only permissions grant service principal operations without a delegated signed-in user. Confirm using the measurable result: The service obtains an app-only token and performs only the approved Graph actions.
Management locks guard against accidental resource deletes and operate separately from authorization roles. The Resource lock constraints test checks authorized configuration updates succeed but the delete operation is blocked; the relevant outcome is The service obtains an app-only token and performs only the approved Graph actions.
Key Vault secrets support controlled retrieval and rotation separate from packaged application code. The offered observation would demonstrate Key Vault secrets: The service uses the new secret version without an embedded password in deployment artifacts. The current validation is different: The service obtains an app-only token and performs only the approved Graph actions.
B2B collaboration supports guest principals and cross-organization access controls. Those observations validate External B2B partner. They do not establish the required Application permissions result: The service obtains an app-only token and performs only the approved Graph actions.
The ADF tumbling window review proposes: Use Data Factory tumbling-window triggers with dependency and retry design. Which Azure behavior is the technical justification for this decision?
Tumbling-window triggers model contiguous time slices with support for backfill. It is material here because a nightly ingestion job must process every hourly window and backfill missed intervals after outages.
Mapping data flows transform data on managed Spark compute from graphical mappings. Tumbling-window triggers model contiguous time slices with support for backfill.
OneLake offers a common analytics data foundation for supported Fabric workloads. It belongs to Fabric OneLake analytics. The stated architecture instead relies on: Tumbling-window triggers model contiguous time slices with support for backfill.
Serverless SQL queries external lake files with consumption-based query compute. That statement describes Synapse serverless SQL, while the question asks how ADF tumbling window works: Tumbling-window triggers model contiguous time slices with support for backfill.
The Front Door WAF edge review proposes: Attach a supported WAF policy to Azure Front Door routes and validate rule actions. Which Azure behavior is the technical justification for this decision?
Edge WAF can inspect and filter HTTP requests before the proxy forwards them to origins. It is material here because a public application must block common HTTP attacks before traffic reaches regional origins worldwide.
VNet integration is principally an outbound feature; inbound private access requires other controls. It belongs to VNet integration App Service. The stated architecture instead relies on: Edge WAF can inspect and filter HTTP requests before the proxy forwards them to origins.
Virtual WAN provides managed global transit architecture with integrated branch connectivity. That statement describes Virtual WAN global hubs, while the question asks how Front Door WAF edge works: Edge WAF can inspect and filter HTTP requests before the proxy forwards them to origins.
Peering connects VNet address spaces through the Microsoft backbone without creating transitive routing by default. Edge WAF can inspect and filter HTTP requests before the proxy forwards them to origins.
Architecture review: VNet peering and ExpressRoute private circuit. Requirement A: Two Azure VNets in nearby regions need low-latency private connectivity without VPN gateways. Requirement B: A large enterprise needs private reliable WAN connectivity to Azure at scale. Which complete two-part proposal satisfies both constraints?
For requirement A, peering connects VNet address spaces through the Microsoft backbone without creating transitive routing by default. For requirement B, expressRoute links customer WAN to Azure backbone privately through provider connectivity. Verify both independently: Private IP traffic flows between the peered VNets with appropriate NSG permissions; A test workload reaches Azure over advertised private prefixes when one circuit path fails.
One action is correct. The other targets Front Door WAF edge, leaving VNet peering unsolved. Its necessary action is: Use VNet peering or global VNet peering under the supported region topology.
The mismatched half is NAT Gateway outbound; ExpressRoute private circuit instead needs: Use ExpressRoute private peering with redundant circuit/provider design.
This combines Front Door WAF edge and NAT Gateway outbound, which do not satisfy the distinct requirements for VNet peering and ExpressRoute private circuit.
A transactional SQL database must withstand a full zone failure with minimal manual intervention. An architecture board will approve a solution only if this outcome is demonstrated: A zone failure does not permanently interrupt application database access. What should be selected?
Zone redundancy spreads eligible database availability replicas across zones. The selected architecture is choose a supported zone-redundant Azure SQL tier and configuration; confirm the result by checking that a zone failure does not permanently interrupt application database access.
Application Gateway offers L7 proxy capabilities with WAF unlike a basic L4 load balancer. It does not solve the specified Azure SQL zone redundancy condition.
Availability zones isolate infrastructure failure domains within an enabled region. The relevant requirement is: A transactional SQL database must withstand a full zone failure with minimal manual intervention.
Fault injection tests whether resilience patterns work under realistic failure conditions. The current need is: A transactional SQL database must withstand a full zone failure with minimal manual intervention.
Windows clients must access Azure Files using on-premises AD identities and SMB permissions. Identify the most suitable implementation for an outcome where approved domain users mount the share and unauthorized users fail the access test.
Azure Files can integrate with supported directory-based SMB authentication while share and NTFS ACLs govern access. The selected architecture is design supported AD DS-based Azure Files authentication and share/file permission mapping; confirm the result by checking that approved domain users mount the share and unauthorized users fail the access test.
App-only permissions grant service principal operations without a delegated signed-in user. The current need is: Windows clients must access Azure Files using on-premises AD identities and SMB permissions.
Access reviews periodically recertify assigned access and can remove access for denied reviews. It does not solve the specified Azure Files identity access condition.
External ID consumer capabilities support customer journeys distinct from employee workforce governance. Its design target is Consumer sign-in. The stated requirement instead concerns: Windows clients must access Azure Files using on-premises AD identities and SMB permissions.
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.
Please check your mailbox for a message from support@examlabs.com and follow the directions.