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 rollout addressing Retry transient failures has reached acceptance testing. The original problem was: An application sends one request and crashes on transient 429 and 503 responses during scale events. Which finding verifies its resolution?
Transient-failure handling reduces unnecessary outages while preventing retry storms. Confirm using the measurable result: A simulated 503 triggers spaced retries and a successful response without duplicate writes.
Front Door provides global application delivery and HTTP(S) origin failover at the edge. Those observations validate Front Door global failover. They do not establish the required Retry transient failures result: A simulated 503 triggers spaced retries and a successful response without duplicate writes.
Cluster autoscaler adjusts nodes to schedule eligible pending pods. The distinguishing check is: A simulated 503 triggers spaced retries and a successful response without duplicate writes.
Traffic Manager is DNS-based and clients connect directly to the returned service endpoint. The Traffic Manager DNS routing test checks dNS responses prefer the healthy endpoint as monitoring marks another unavailable; the relevant outcome is A simulated 503 triggers spaced retries and a successful response without duplicate writes.
A SQL database without an active geo-secondary needs disaster recovery from geo-redundant backups. Choose the architecture that can be validated by this result: A region-loss exercise recovers a database from the latest supported geo backup.
Geo-restore is backup-based recovery with different RTO/RPO than active geo-replication. The selected architecture is plan Azure SQL geo-restore with acceptable recovery objectives and backup redundancy; confirm the result by checking that a region-loss exercise recovers a database from the latest supported geo backup.
Azure SQL automatic full differential and log backups support restoring database state at a selected time. That is useful for SQL database PITR (A deployment accidentally truncates a transaction table and the database must be recovered before the change). It does not meet the current SQL geo-restore requirement: A SQL database without an active geo-secondary needs disaster recovery from geo-redundant backups.
Site Recovery replicates workload state and orchestrates VM failover for supported scenarios. It does not solve the specified SQL geo-restore condition.
RTO is the maximum acceptable restoration duration, not the amount of lost data. The relevant requirement is: A SQL database without an active geo-secondary needs disaster recovery from geo-redundant backups.
For Cosmos autoscale, operations are closing a change that addressed: An API's Cosmos traffic varies tenfold through the day and manually fixed throughput is wasteful. Which post-change signal belongs in the acceptance record?
Autoscale adjusts provisioned RU/s capacity according to measured load within a maximum. Confirm using the measurable result: Busy-hour requests meet RU demands and off-peak consumed RU declines.
Tiering trades storage price against access and retrieval cost based on usage. The Blob hot/cool/cold test checks old eligible blobs transition to the intended tier and remain retrievable; the relevant outcome is Busy-hour requests meet RU demands and off-peak consumed RU declines.
Azure Files provides managed SMB file shares whereas Blob Storage is object-oriented. The offered observation would demonstrate Azure Files SMB: The application opens the shared UNC path from authorized machines. The current validation is different: Busy-hour requests meet RU demands and off-peak consumed RU declines.
Blob change feed records changes to blob objects for downstream processing. The distinguishing check is: Busy-hour requests meet RU demands and off-peak consumed RU declines.
An HTTP API needs custom deployment slots and managed PaaS hosting without a Kubernetes operations team. Choose the architecture that can be validated by this result: Traffic swaps to a warmed-up deployment slot without SSH management of app hosts.
App Service manages web hosting and supports deployment slots on eligible plans. The selected architecture is choose Azure App Service on a suitable tier with deployment slots; confirm the result by checking that traffic swaps to a warmed-up deployment slot without SSH management of app hosts.
GPU instances provide accelerators not present on standard CPU-only VMs. The relevant requirement is: An HTTP API needs custom deployment slots and managed PaaS hosting without a Kubernetes operations team.
VMSS automates management and scaling of similar VMs in the same workload. It does not solve the specified App Service web condition.
Encryption sets connect managed disk encryption to customer-owned keys. That is useful for VM disk encryption (A finance VM needs customer-managed encryption keys for managed disks). It does not meet the current App Service web requirement: An HTTP API needs custom deployment slots and managed PaaS hosting without a Kubernetes operations team.
Auditors need repeatable visual reporting of compliance violations across many subscriptions. An architecture board will approve a solution only if this outcome is demonstrated: An auditor filters noncompliant resources by subscription and policy assignment. What should be selected?
Workbooks provide interactive analytical reports rather than the policy enforcement mechanism itself. The selected architecture is build an Azure Workbook over centrally collected compliance and resource data; confirm the result by checking that an auditor filters noncompliant resources by subscription and policy assignment.
Defender for Cloud aggregates recommendations and compliance state for supported frameworks. The current need is: Auditors need repeatable visual reporting of compliance violations across many subscriptions.
Consistent metadata simplifies inventory grouping and cost ownership without changing resources' technical capabilities. It does not solve the specified Managed governance dashboards condition.
DeployIfNotExists requires remediation for already deployed resources where appropriate. The relevant requirement is: Auditors need repeatable visual reporting of compliance violations across many subscriptions.
To validate the Resource lock constraints deployment, reviewers revisit this operational need: An application owner accidentally deletes resources but granting Reader would block legitimate configuration changes. What result confirms it was met?
Management locks guard against accidental resource deletes and operate separately from authorization roles. Confirm using the measurable result: Authorized configuration updates succeed but the delete operation is blocked.
Federated credentials exchange trusted external OIDC assertions for Entra access tokens. The distinguishing check is: Authorized configuration updates succeed but the delete operation is blocked.
External ID consumer capabilities support customer journeys distinct from employee workforce governance. The offered observation would demonstrate Consumer sign-in: The consumer completes the intended registration journey without receiving workforce resource roles. The current validation is different: Authorized configuration updates succeed but the delete operation is blocked.
Administrative units scope eligible directory management roles to selected objects, not data visibility. Those observations validate Delegation with admin units. They do not establish the required Resource lock constraints result: Authorized configuration updates succeed but the delete operation is blocked.
A rollout addressing Azure Cache for Redis session has reached acceptance testing. The original problem was: A scaled-out web app stores user sessions on individual workers and loses sessions on failover. Which finding verifies its resolution?
Shared session state survives an individual stateless app worker replacement. Confirm using the measurable result: The user session persists after a web worker is intentionally removed.
App Configuration centralizes feature settings; secrets should remain in Key Vault. The App Configuration feature flags test checks pilot users see the feature after refresh and others retain the previous behavior; the relevant outcome is The user session persists after a web worker is intentionally removed.
Logic Apps offers managed integration workflows and prebuilt service connectors. The offered observation would demonstrate Logic Apps connector workflow: An approved request creates the expected ticket and notifies the right mailbox. The current validation is different: The user session persists after a web worker is intentionally removed.
At-least-once message delivery requires application logic to deduplicate business side effects. The distinguishing check is: The user session persists after a web worker is intentionally removed.
For Network Watcher diagnosis, operations are closing a change that addressed: A connectivity failure may be caused by either NSG rules, routing or the remote endpoint. Which post-change signal belongs in the acceptance record?
Network Watcher diagnostic tools identify effective network behavior and filtering decisions. Confirm using the measurable result: The test identifies the blocking NSG rule or unreachable next hop before changing production routes.
DDoS protection adds adaptive mitigation and telemetry for supported public resources. The offered observation would demonstrate DDoS protection: Protection coverage reports the eligible public IP and test telemetry is available. The current validation is different: The test identifies the blocking NSG rule or unreachable next hop before changing production routes.
ExpressRoute links customer WAN to Azure backbone privately through provider connectivity. Those observations validate ExpressRoute private circuit. They do not establish the required Network Watcher diagnosis result: The test identifies the blocking NSG rule or unreachable next hop before changing production routes.
VNet peering alone is not transitive and forwarding needs explicit architecture. The distinguishing check is: The test identifies the blocking NSG rule or unreachable next hop before changing production routes.
A rollout addressing Storage service endpoints has reached acceptance testing. The original problem was: Virtual network workloads need storage traffic to use Azure backbone but the storage service remains publicly addressable. Which finding verifies its resolution?
Service endpoints secure selected Azure service traffic from VNets but do not create a private IP for the PaaS service. Confirm using the measurable result: Approved subnet access succeeds and other public sources are denied by storage rules.
Blob Inventory produces scheduled object inventories without crawling each object individually. Those observations validate Blob inventory. They do not establish the required Storage service endpoints result: Approved subnet access succeeds and other public sources are denied by storage rules.
ADLS Gen2 adds directory semantics and access ACLs to blob-backed storage. The distinguishing check is: Approved subnet access succeeds and other public sources are denied by storage rules.
Directory ACLs provide path-level data authorization when hierarchical namespace is enabled. The ADLS ACLs test checks a test identity reads its assigned folder but is denied a sibling folder; the relevant outcome is Approved subnet access succeeds and other public sources are denied by storage rules.
The Azure Files SMB review proposes: Use Azure Files SMB shares with supported identity integration. Which Azure behavior is the technical justification for this decision?
Azure Files provides managed SMB file shares whereas Blob Storage is object-oriented. It is material here because a legacy Windows application needs a shared SMB file path used by multiple virtual machines.
Partition key distribution governs data/throughput placement and query efficiency. It belongs to Cosmos partition key. The stated architecture instead relies on: Azure Files provides managed SMB file shares whereas Blob Storage is object-oriented.
Session consistency offers read-your-writes within a session without strong global consistency. That statement describes Cosmos session consistency, while the question asks how Azure Files SMB works: Azure Files provides managed SMB file shares whereas Blob Storage is object-oriented.
Premium SSD v2 decouples some provisioned performance settings from disk capacity. Azure Files provides managed SMB file shares whereas Blob Storage is object-oriented.
Architecture review: PostgreSQL zone redundant HA and Application Gateway zone redundancy. Requirement A: A mission-critical PostgreSQL workload requires HA across zones within a region. Requirement B: A web workload requires HTTP routing and WAF across availability zones. Which complete two-part proposal satisfies both constraints?
For requirement A, a zone-separated standby supports automated failover where offered. For requirement B, application Gateway offers L7 proxy capabilities with WAF unlike a basic L4 load balancer. Verify both independently: After a zone failure the managed standby serves database connections; The gateway keeps HTTP traffic flowing when a backend zone is unavailable.
A zone-separated standby supports automated failover where offered. The other proposed action (select GZRS or RA-GZRS based on read access needs and service support) addresses a different operation. Application Gateway offers L7 proxy capabilities with WAF unlike a basic L4 load balancer.
The option covers one requirement but substitutes AKS cluster autoscaler for PostgreSQL zone redundant HA. The missing acceptance result is: After a zone failure the managed standby serves database connections.
A zone-separated standby supports automated failover where offered. Application Gateway offers L7 proxy capabilities with WAF unlike a basic L4 load balancer. The proposed steps (enable AKS cluster autoscaler within approved node pool bounds; select GZRS or RA-GZRS based on read access needs and service support) address other capabilities instead of this required pair.
Please check your mailbox for a message from support@examlabs.com and follow the directions.