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
Two Azure VNets in nearby regions need low-latency private connectivity without VPN gateways. The acceptance test is: Private IP traffic flows between the peered VNets with appropriate NSG permissions. Which design recommendation best satisfies both?
Peering connects VNet address spaces through the Microsoft backbone without creating transitive routing by default. The selected architecture is use VNet peering or global VNet peering under the supported region topology; confirm the result by checking that private IP traffic flows between the peered VNets with appropriate NSG permissions.
NSGs provide stateful Layer 3/4 access rules rather than application-layer inspection. It does not solve the specified VNet peering condition.
Edge WAF can inspect and filter HTTP requests before the proxy forwards them to origins. That is useful for Front Door WAF edge (A public application must block common HTTP attacks before traffic reaches regional origins worldwide). It does not meet the current VNet peering requirement: Two Azure VNets in nearby regions need low-latency private connectivity without VPN gateways.
DDoS protection adds adaptive mitigation and telemetry for supported public resources. The relevant requirement is: Two Azure VNets in nearby regions need low-latency private connectivity without VPN gateways.
Architecture review: Availability zones for VM tier and Zone-redundant load balancer. Requirement A: A web service must survive loss of one data center within an Azure region. 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, availability zones isolate infrastructure failure domains within an enabled region. For requirement B, load Balancer routes TCP/UDP flows to healthy backends without terminating HTTP requests. Verify both independently: A simulated zonal loss leaves healthy VM instances serving requests; Failed backend probes remove one instance and healthy zonal instances continue serving.
Availability zones isolate infrastructure failure domains within an enabled region. Load Balancer routes TCP/UDP flows to healthy backends without terminating HTTP requests. The proposed steps (run controlled fault-injection or chaos tests with clear guardrails and rollback; enable AKS cluster autoscaler within approved node pool bounds) address other capabilities instead of this required pair.
The first step implements Chaos failure testing instead of Availability zones for VM tier. The necessary change is to deploy redundant VMs across availability zones behind an appropriate load balancer.
The option covers one requirement but substitutes AKS cluster autoscaler for Zone-redundant load balancer. The missing acceptance result is: Failed backend probes remove one instance and healthy zonal instances continue serving.
Architecture review: Allowed regions and Policy audit versus deny. Requirement A: Data sovereignty policy forbids new resources outside a small list of approved Azure regions. Requirement B: The platform team needs to measure the impact of a new restriction before blocking deployments. Which complete two-part proposal satisfies both constraints?
For requirement A, policy evaluates resource deployment properties and rejects noncompliant regions. For requirement B, audit effects collect compliance findings without blocking resource creation. Verify both independently: A forbidden-region deployment is denied and an allowed-region deployment succeeds; Noncompliant deployment is logged during pilot but rejected after approved enforcement.
This combines Resource locks and Defender compliance, which do not satisfy the distinct requirements for Allowed regions and Policy audit versus deny.
The option covers one requirement but substitutes Defender compliance for Policy audit versus deny. The missing acceptance result is: Noncompliant deployment is logged during pilot but rejected after approved enforcement.
One action is correct. The other targets Resource locks, leaving Allowed regions unsolved. Its necessary action is: Assign an Azure Policy allowed locations definition with deny enforcement.
To validate the Cost budgets deployment, reviewers revisit this operational need: A department must be notified when cloud spend nears its monthly budget without terminating workloads. What result confirms it was met?
Budgets monitor and notify about spending and do not automatically stop resources. Confirm using the measurable result: A threshold crossing issues notifications while the app remains running.
Policy scope and exclusions should be the smallest feasible exception rather than removing global guardrails. The offered observation would demonstrate Policy exclusion scope: Only the approved application scope avoids the specified policy effect. The current validation is different: A threshold crossing issues notifications while the app remains running.
Policy exemptions record approved exceptions while the policy remains assigned. Those observations validate Policy exemption. They do not establish the required Cost budgets result: A threshold crossing issues notifications while the app remains running.
Resource groups provide a deployment and management boundary and facilitate cohesive cleanup. The distinguishing check is: A threshold crossing issues notifications while the app remains running.
Two Functions apps need the same persistent workload identity even when one app is recreated. An architecture board will approve a solution only if this outcome is demonstrated: Both functions access the approved store and identity remains after one app is replaced. What should be selected?
A user-assigned identity has a lifecycle separate from each consuming Azure resource. The selected architecture is assign a user-assigned managed identity to both apps and scope its data permissions; confirm the result by checking that both functions access the approved store and identity remains after one app is replaced.
Key Vault keys can perform cryptographic operations while restricting private key exposure. It does not solve the specified Shared workload identity condition.
Key Vault secrets support controlled retrieval and rotation separate from packaged application code. That is useful for Key Vault secrets (A service depends on a vendor API password that rotates frequently). It does not meet the current Shared workload identity requirement: Two Functions apps need the same persistent workload identity even when one app is recreated.
Key Vault certificates support managed lifecycle and distribution to compatible Azure integrations. Its design target is Key Vault certificate lifecycle. The stated requirement instead concerns: Two Functions apps need the same persistent workload identity even when one app is recreated.
To validate the PostgreSQL zone redundant HA deployment, reviewers revisit this operational need: A mission-critical PostgreSQL workload requires HA across zones within a region. What result confirms it was met?
A zone-separated standby supports automated failover where offered. Confirm using the measurable result: After a zone failure the managed standby serves database connections.
ZRS synchronously replicates data across primary-region zones. The distinguishing check is: After a zone failure the managed standby serves database connections.
Availability zones isolate infrastructure failure domains within an enabled region. The Availability zones for VM tier test checks a simulated zonal loss leaves healthy VM instances serving requests; the relevant outcome is After a zone failure the managed standby serves database connections.
Failover-group listeners abstract the primary location during regional failover. The offered observation would demonstrate SQL failover groups HA: The app reconnects after an orchestrated failover without endpoint edits. The current validation is different: After a zone failure the managed standby serves database connections.
Architecture rationale review—Private integration access: Use approved private integration runtime and networking features for the chosen data service. Which explanation accurately distinguishes this capability?
Hybrid/private integration requires a reachable private network path rather than open public DB exposure. It is material here because cloud pipelines must access a private database over private routing without publishing its port.
Data Explorer is designed for large-scale append-oriented telemetry exploration with KQL. Hybrid/private integration requires a reachable private network path rather than open public DB exposure.
Service Bus is an enterprise message broker with delivery and dead-letter semantics. Hybrid/private integration requires a reachable private network path rather than open public DB exposure.
Delta Lake transaction logs enable reliable table updates and versioning on cloud object stores. It belongs to Databricks Delta Lake. The stated architecture instead relies on: Hybrid/private integration requires a reachable private network path rather than open public DB exposure.
For Retire unused services, operations are closing a change that addressed: An application inventory shows unused servers with no business owner or dependent traffic. Which post-change signal belongs in the acceptance record?
Retiring unused assets reduces migration risk and cloud cost rather than copying unnecessary VMs. Confirm using the measurable result: Decommissioned workloads create no application dependency failure.
Refactoring changes application structure and decouples independent workloads. The offered observation would demonstrate Refactor monolith: One service can scale independently and failures are isolated through messaging. The current validation is different: Decommissioned workloads create no application dependency failure.
Physical data transfer can shorten initial bulk migration when network transfer is impractical. Those observations validate Storage bulk offline transfer. They do not establish the required Retire unused services result: Decommissioned workloads create no application dependency failure.
PostgreSQL migration requires extension, version and connectivity compatibility checks. The distinguishing check is: Decommissioned workloads create no application dependency failure.
The team has justified its Management group hierarchy design with: Build a management-group hierarchy with appropriate policy and RBAC inheritance. Which statement accurately describes why the approach works?
Management groups supply governance scope above subscriptions without moving resources into a single subscription. It is material here because a global enterprise requires central baseline policies applied to every subscription but autonomous project teams manage resources.
Landing zones combine platform foundations with repeatable application subscription governance. Management groups supply governance scope above subscriptions without moving resources into a single subscription.
RBAC assignments inherit downward so narrower scope reduces unintended changes. It belongs to Role assignment scope. The stated architecture instead relies on: Management groups supply governance scope above subscriptions without moving resources into a single subscription.
Cost exports provide detailed recurring usage data for downstream allocation reporting. That statement describes Cost export, while the question asks how Management group hierarchy works: Management groups supply governance scope above subscriptions without moving resources into a single subscription.
For App deployment blue-green, operations are closing a change that addressed: A mission-critical API needs a low-risk deployment with rapid rollback of application code. Which post-change signal belongs in the acceptance record?
Blue-green deployment preserves a prior known-good instance while testing a replacement. Confirm using the measurable result: A failed health check returns traffic to the prior application version.
Azure Batch schedules large-scale parallel workloads across managed compute pools. The distinguishing check is: A failed health check returns traffic to the prior application version.
Durable Functions manages stateful workflows over serverless function executions. The offered observation would demonstrate Azure Functions durable workflow: A resumed orchestration continues from saved state after a worker restart. The current validation is different: A failed health check returns traffic to the prior application version.
App Service manages web hosting and supports deployment slots on eligible plans. Those observations validate App Service web. They do not establish the required App deployment blue-green result: A failed health check returns traffic to the prior application version.
During technical sign-off for Managed governance dashboards, the architect selects: Build an Azure Workbook over centrally collected compliance and resource data. Which underlying behavior should be documented?
Workbooks provide interactive analytical reports rather than the policy enforcement mechanism itself. It is material here because auditors need repeatable visual reporting of compliance violations across many subscriptions.
Consistent metadata simplifies inventory grouping and cost ownership without changing resources' technical capabilities. Workbooks provide interactive analytical reports rather than the policy enforcement mechanism itself.
DeployIfNotExists requires remediation for already deployed resources where appropriate. Workbooks provide interactive analytical reports rather than the policy enforcement mechanism itself.
Defender for Cloud aggregates recommendations and compliance state for supported frameworks. It belongs to Defender compliance. The stated architecture instead relies on: Workbooks provide interactive analytical reports rather than the policy enforcement mechanism itself.
Please check your mailbox for a message from support@examlabs.com and follow the directions.