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: 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.
A solution must address both Azure service health and VM resource health. First requirement: A regional Azure platform incident affects databases but project teams have no subscription-specific warning. Second requirement: A single VM becomes unavailable but the Azure region itself is healthy. Select TWO recommendations that meet these independent needs.
For the Azure service health half of this two-part design, service Health reports Azure platform incidents and planned maintenance relevant to a subscription. Verify: A platform health incident produces the configured subscription-scoped notification. The other half concerns VM resource health.
For the VM resource health half of this design, resource Health reports the platform-side availability history of individual Azure resources. Check: The specific VM shows an unavailable health state while the regional Service Health feed remains normal. The other half concerns Azure service health.
VM insights and the agent collect supported guest operating-system counters and process data. This alternative solves VM guest performance, while the question separately requires Azure service health and VM resource health.
DCRs specify collected streams destinations and transformations for supported agent sources. That plan is appropriate for Agent collection rules. The two controls sought here are Azure service health and VM resource health.
Metrics are low-latency numeric series and alert evaluation can trigger actions independently of a log query. This alternative solves CPU threshold alerts, while the question separately requires Azure service health and VM resource health.
To validate the PIM on-demand roles deployment, reviewers revisit this operational need: Cloud operations needs eligible administrators to activate subscription Owner only during approved maintenance. What result confirms it was met?
PIM can time-bound eligible role activation with approvals MFA and justification. Confirm using the measurable result: An eligible operator activates access for the window and loses elevation after expiry.
Management-plane Azure RBAC Reader does not automatically authorize blob data-plane reads. Those observations validate Resource RBAC versus data access. They do not establish the required PIM on-demand roles result: An eligible operator activates access for the window and loses elevation after expiry.
App-only permissions grant service principal operations without a delegated signed-in user. The distinguishing check is: An eligible operator activates access for the window and loses elevation after expiry.
Managed identities provide Entra tokens to supported workloads while data-plane RBAC grants the actual blob permissions. The offered observation would demonstrate Managed identity for App Service: A token-based read works and the app has no stored storage-account key. The current validation is different: An eligible operator activates access for the window and loses elevation after expiry.
An architect must sign off on App Service zone redundancy. The business problem is: A production App Service must resist a zone failure without managing VM instances. What observed test result provides valid evidence?
Eligible App Service plans distribute app workers across availability zones with sufficient capacity. Confirm using the measurable result: A zonal disruption leaves the application reachable via surviving workers.
Traffic Manager is DNS-based and clients connect directly to the returned service endpoint. The distinguishing check is: A zonal disruption leaves the application reachable via surviving workers.
Load Balancer routes TCP/UDP flows to healthy backends without terminating HTTP requests. The offered observation would demonstrate Zone-redundant load balancer: Failed backend probes remove one instance and healthy zonal instances continue serving. The current validation is different: A zonal disruption leaves the application reachable via surviving workers.
Multi-region writes allow eligible regions to accept writes but require handling conflicts. Those observations validate Cosmos multi-write availability. They do not establish the required App Service zone redundancy result: A zonal disruption leaves the application reachable via surviving workers.
A subnet must send internet-bound flows through a centrally managed inspection firewall. An engineer must deliver the following acceptance evidence: Traceroute and firewall logs show the intended inspected egress path. What design choice is defensible?
User-defined routes can override platform routing to steer approved subnets through an NVA/firewall. The selected architecture is configure a route table with default route next hop to the firewall and enable required forwarding; confirm the result by checking that traceroute and firewall logs show the intended inspected egress path.
NAT Gateway provides outbound SNAT for supported subnet internet traffic. Its design target is NAT Gateway outbound. The stated requirement instead concerns: A subnet must send internet-bound flows through a centrally managed inspection firewall.
NSGs provide stateful Layer 3/4 access rules rather than application-layer inspection. The current need is: A subnet must send internet-bound flows through a centrally managed inspection firewall.
Application Gateway provides regional Layer 7 reverse proxy and routing for private backends. It does not solve the specified UDR firewall inspection condition.
An architect must sign off on Application resilience timeout. The business problem is: An API waits indefinitely for a failing inventory service and exhausts its worker threads. What observed test result provides valid evidence?
Failure handling isolates unhealthy dependencies and avoids request pileups. Confirm using the measurable result: Simulated downstream failure produces prompt controlled errors while healthy requests remain available.
Edge content distribution can cache static resources near users. Those observations validate CDN static content. They do not establish the required Application resilience timeout result: Simulated downstream failure produces prompt controlled errors while healthy requests remain available.
Asynchronous projections can lag writes and need clear read-after-write expectations. The distinguishing check is: Simulated downstream failure produces prompt controlled errors while healthy requests remain available.
Front Door rule sets change eligible request and response behavior at the edge according to match conditions. The Front Door rules engine test checks requests to the deprecated path redirect and supported responses include the configured header; the relevant outcome is Simulated downstream failure produces prompt controlled errors while healthy requests remain available.
The design team completed work on SQL Always Encrypted. Its governing requirement was: A database handles patient identifiers that should stay encrypted from database administrators during normal access. Identify the conclusive verification result.
Always Encrypted supports encryption and decryption in capable clients to reduce exposure to the database engine. Confirm using the measurable result: The client retrieves authorized plaintext while a privileged server-side query sees encrypted values.
SQL auditing captures database events as configured separately from application request telemetry. Those observations validate SQL auditing. They do not establish the required SQL Always Encrypted result: The client retrieves authorized plaintext while a privileged server-side query sees encrypted values.
Ledger records cryptographically verifiable tamper-evidence for supported relational tables. The distinguishing check is: The client retrieves authorized plaintext while a privileged server-side query sees encrypted values.
Elastic pools share resources across independent databases with non-synchronized demand. The SQL elastic pool test checks aggregated tenant peaks stay within pool limits at lower cost than individually overprovisioned databases; the relevant outcome is The client retrieves authorized plaintext while a privileged server-side query sees encrypted values.
New storage accounts across many subscriptions often appear with no diagnostic configuration. Identify the most suitable implementation for an outcome where a newly provisioned supported storage account gets the intended diagnostics after policy remediation.
DeployIfNotExists can evaluate related configurations and deploy missing compliant resources with appropriate permissions. The selected architecture is use Azure Policy deployIfNotExists with remediation identity for supported diagnostic settings; confirm the result by checking that a newly provisioned supported storage account gets the intended diagnostics after policy remediation.
A log search alert can evaluate aggregated matching records instead of only raw metric time series. That is useful for Log anomaly alert (Security needs an alert when failed sign-in counts by IP exceed a KQL-defined rule over fifteen minutes). It does not meet the current Automated diagnostics policy requirement: New storage accounts across many subscriptions often appear with no diagnostic configuration.
Dynamic thresholds adapt alert boundaries to historical metric patterns after sufficient data exists. It does not solve the specified Automated diagnostics policy condition.
Action groups define notifications and automated responses and can be reused by alert rules. The current need is: New storage accounts across many subscriptions often appear with no diagnostic configuration.
Architecture review: Immutable evidence archive and Cross-subscription workspace. Requirement A: Auditors require tamper-resistant retention of exported logs that are rarely queried. Requirement B: Four subscriptions must be searched together during incident response with one KQL query and shared retention policy. Which complete two-part proposal satisfies both constraints?
For requirement A, storage-based diagnostic archives and immutability serve compliance preservation rather than interactive KQL search. For requirement B, a workspace can aggregate resource telemetry across subscription boundaries when access and diagnostic routing are configured. Verify both independently: A retained log blob rejects unauthorized deletion during its compliance retention window; The same query returns events labeled with all four source subscription IDs.
Storage-based diagnostic archives and immutability serve compliance preservation rather than interactive KQL search. The other proposed action (use Azure Policy deployIfNotExists with remediation identity for supported diagnostic settings) addresses a different operation. A workspace can aggregate resource telemetry across subscription boundaries when access and diagnostic routing are configured.
The option covers one requirement but substitutes CPU threshold alerts for Immutable evidence archive. The missing acceptance result is: A retained log blob rejects unauthorized deletion during its compliance retention window.
Storage-based diagnostic archives and immutability serve compliance preservation rather than interactive KQL search. A workspace can aggregate resource telemetry across subscription boundaries when access and diagnostic routing are configured. The proposed steps (create Azure Monitor metric alert rules with appropriate evaluation windows and an action group; use Azure Policy deployIfNotExists with remediation identity for supported diagnostic settings) address other capabilities instead of this required pair.
A log archive sees frequent access for a month and rare access afterward. An architecture board will approve a solution only if this outcome is demonstrated: Old eligible blobs transition to the intended tier and remain retrievable. What should be selected?
Tiering trades storage price against access and retrieval cost based on usage. The selected architecture is apply Blob lifecycle management that transitions objects through supported access tiers; confirm the result by checking that old eligible blobs transition to the intended tier and remain retrievable.
Blob change feed records changes to blob objects for downstream processing. The relevant requirement is: A log archive sees frequent access for a month and rare access afterward.
Cosmos DB provides a distributed document database with configurable consistency and throughput. It does not solve the specified Blob hot/cool/cold condition.
Autoscale adjusts provisioned RU/s capacity according to measured load within a maximum. Its design target is Cosmos autoscale. The stated requirement instead concerns: A log archive sees frequent access for a month and rare access afterward.
A solution must address both Azure-to-Azure ASR networking and Failback after recovery. First requirement: Replicated VMs boot in the secondary region but application private DNS and subnets are unavailable. Second requirement: A team has documented failover to a secondary region but no controlled return to primary. Select TWO recommendations that meet these independent needs.
For the Azure-to-Azure ASR networking half of this two-part design, compute replication does not automatically guarantee complete application network reachability. Verify: A test failover can reach the recovered app through the intended private routes. The other half concerns Failback after recovery.
For the Failback after recovery half of this design, failback is a separate operational sequence after workloads run in the recovery site. Check: A controlled failback returns traffic and state to the primary without unplanned data loss. The other half concerns Azure-to-Azure ASR networking.
Azure Backup creates managed recovery points distinct from continuously replicating a running VM. The corresponding task is Azure VM backup policy: A production Azure VM must be recoverable to an earlier day after accidental deletion of application files. It is not one of the two requested controls (Azure-to-Azure ASR networking and Failback after recovery).
Soft delete retains recoverable protected backup data after deletion for a configured interval. Its own validation would be: The deleted item is recoverable within the protected deletion window. The current paired requirement is Azure-to-Azure ASR networking and Failback after recovery.
RTO is the maximum acceptable restoration duration, not the amount of lost data. This alternative solves Recovery time objective, while the question separately requires Azure-to-Azure ASR networking and Failback after recovery.
Please check your mailbox for a message from support@examlabs.com and follow the directions.