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
Before approving Subscription isolation, the reviewer assesses this requirement: A regulated subsidiary needs separate billing and policy boundaries from the parent business unit. Which of the reported outcomes is decisive?
Subscriptions are billing and resource governance boundaries with independent quotas and RBAC assignment scopes. Confirm using the measurable result: The subsidiary's budget and policy reports stay distinct from the parent.
Azure deployment what-if previews resource changes before applying a template. The Deployment drift test checks the change report identifies manual drift and approved deployment restores the intended state; the relevant outcome is The subsidiary's budget and policy reports stay distinct from the parent.
RBAC assignments inherit downward so narrower scope reduces unintended changes. The offered observation would demonstrate Role assignment scope: The engineer can change the assigned network group but not another group's resources. The current validation is different: The subsidiary's budget and policy reports stay distinct from the parent.
Budgets monitor and notify about spending and do not automatically stop resources. Those observations validate Cost budgets. They do not establish the required Subscription isolation result: The subsidiary's budget and policy reports stay distinct from the parent.
A solution must address both Circuit breaker behavior and Blob GZRS durability. First requirement: A downstream service stays unhealthy and unlimited client retries exhaust all front-end worker threads. Second requirement: A critical object store needs zone resilience in primary and a regional recovery copy. Select TWO recommendations that meet these independent needs.
For the Circuit breaker behavior half of this two-part design, circuit breakers stop futile downstream calls temporarily and permit controlled re-entry. Verify: Unhealthy requests fail quickly and the service resumes calls after recovery. The other half concerns Blob GZRS durability.
For the Blob GZRS durability half of this design, GZRS synchronously spreads primary copies across zones and asynchronously replicates to another region. Check: A regional recovery plan uses the secondary while zonal faults leave primary available. The other half concerns Circuit breaker behavior.
Zone-distributed nodes and pod scheduling reduce concentration, but a zone loss can leave pods Pending unless healthy-zone node capacity, quota, volume topology and scheduling constraints permit recovery. This alternative solves AKS availability zones, while the question separately requires Circuit breaker behavior and Blob GZRS durability.
Application Gateway offers L7 proxy capabilities with WAF unlike a basic L4 load balancer. That plan is appropriate for Application Gateway zone redundancy. The two controls sought here are Circuit breaker behavior and Blob GZRS durability.
VMSS can add or remove similarly configured VM instances based on supported signals. Its own validation would be: Traffic spikes scale instances out and scale-in does not lose persistent session state. The current paired requirement is Circuit breaker behavior and Blob GZRS durability.
An architect must sign off on Cosmos multi-region reads. The business problem is: A globally distributed document API needs local low-latency reads near users in multiple regions. What observed test result provides valid evidence?
Read regions bring replicas closer to users without inherently adding multi-write semantics. Confirm using the measurable result: Read latency declines for remote users while sessions observe selected consistency.
VMSS can add or remove similarly configured VM instances based on supported signals. Those observations validate VM scale set autoscaling. They do not establish the required Cosmos multi-region reads result: Read latency declines for remote users while sessions observe selected consistency.
Fault injection tests whether resilience patterns work under realistic failure conditions. The distinguishing check is: Read latency declines for remote users while sessions observe selected consistency.
PDBs constrain voluntary disruptions but do not prevent all involuntary failures. The offered observation would demonstrate AKS pod disruption budget: A planned node drain leaves the minimum healthy pod count running. The current validation is different: Read latency declines for remote users while sessions observe selected consistency.
Architecture review: General purpose VM and Compute optimized VM. Requirement A: A legacy Windows service requires full OS control and custom drivers but has moderate CPU and memory needs. Requirement B: A stateless batch worker is CPU-bound with little disk IO or memory pressure. Which complete two-part proposal satisfies both constraints?
For requirement A, general-purpose VMs balance CPU and memory while retaining OS-level control. For requirement B, compute-optimized instances prioritize vCPU capacity over excess memory. Verify both independently: The workload runs its required driver within the provisioned compute budget; The same batch finishes within the required CPU time without memory bottlenecks.
One action is correct. The other targets Azure Batch scheduling, leaving General purpose VM unsolved. Its necessary action is: Choose an appropriately sized general-purpose Azure VM with supporting disks and network.
The mismatched half is App deployment blue-green; Compute optimized VM instead needs: Choose a compute-optimized VM family sized for sustained CPU throughput.
This combines Azure Batch scheduling and App deployment blue-green, which do not satisfy the distinct requirements for General purpose VM and Compute optimized VM.
Architecture review: VM maintenance handling and VMSS dynamic scaling. Requirement A: A VM-based API must survive scheduled host maintenance without customer-visible downtime. Requirement B: An autoscaling API needs several identical VMs during peak hours and only a few at night. Which complete two-part proposal satisfies both constraints?
For requirement A, redundancy prevents a single host maintenance event from removing the only serving instance. For requirement B, VMSS automates management and scaling of similar VMs in the same workload. Verify both independently: Maintenance on one node leaves other healthy nodes serving the API; The scale set adds instances at load and returns to baseline under low demand.
The first step implements App Service isolation instead of VM maintenance handling. The necessary change is to distribute redundant VMs across appropriate zones or fault domains and use health-probed load balancing.
The option covers one requirement but substitutes App deployment blue-green for VMSS dynamic scaling. The missing acceptance result is: The scale set adds instances at load and returns to baseline under low demand.
Redundancy prevents a single host maintenance event from removing the only serving instance. VMSS automates management and scaling of similar VMs in the same workload. The proposed steps (evaluate App Service Environment v3 with supported isolated-tier plans; use App Service deployment slots or equivalent supported blue-green routing) address other capabilities instead of this required pair.
Data sovereignty policy forbids new resources outside a small list of approved Azure regions. Identify the most suitable implementation for an outcome where a forbidden-region deployment is denied and an allowed-region deployment succeeds.
Policy evaluates resource deployment properties and rejects noncompliant regions. The selected architecture is assign an Azure Policy allowed locations definition with deny enforcement; confirm the result by checking that a forbidden-region deployment is denied and an allowed-region deployment succeeds.
Policy deny or audit effects can enforce required metadata at supported resource scopes. The relevant requirement is: Data sovereignty policy forbids new resources outside a small list of approved Azure regions.
DeployIfNotExists requires remediation for already deployed resources where appropriate. That is useful for Policy remediation (Existing resources are missing diagnostic settings despite new deployments receiving automatic configuration). It does not meet the current Allowed regions requirement: Data sovereignty policy forbids new resources outside a small list of approved Azure regions.
RBAC assignments inherit downward so narrower scope reduces unintended changes. It does not solve the specified Allowed regions condition.
The team has justified its Fabric OneLake analytics design with: Evaluate Microsoft Fabric OneLake with suitable Lakehouse/Warehouse integration. Which statement accurately describes why the approach works?
OneLake offers a common analytics data foundation for supported Fabric workloads. It is material here because a company wants shared analytics data products for Lakehouse and Warehouse consumers in one SaaS environment.
A stored watermark limits reads to changes after the last successful processed interval. OneLake offers a common analytics data foundation for supported Fabric workloads.
Partner event integration routes supported third-party event types without custom polling. It belongs to Event Grid partner events. The stated architecture instead relies on: OneLake offers a common analytics data foundation for supported Fabric workloads.
Pipeline control flow can orchestrate dependent stages instead of independent schedules. That statement describes ADF pipeline dependency, while the question asks how Fabric OneLake analytics works: OneLake offers a common analytics data foundation for supported Fabric workloads.
Compliance requires records of login attempts and selected database actions independent of app logs. An architecture board will approve a solution only if this outcome is demonstrated: A controlled login and database action appear in the configured audit destination. What should be selected?
SQL auditing captures database events as configured separately from application request telemetry. The selected architecture is enable Azure SQL auditing to an approved storage or monitoring destination; confirm the result by checking that a controlled login and database action appear in the configured audit destination.
CMK encryption protects database data at rest while keys are managed under customer control. That is useful for SQL customer-managed keys (Compliance requires the SQL database encryption protector to use customer-controlled key lifecycle in Key Vault). It does not meet the current SQL auditing requirement: Compliance requires records of login attempts and selected database actions independent of app logs.
Azure SQL Database offers fully managed relational database operations with automated backups. Its design target is Azure SQL Database single database. The stated requirement instead concerns: Compliance requires records of login attempts and selected database actions independent of app logs.
Migration assessment identifies blockers and target-fit issues before a cutover. It does not solve the specified SQL auditing condition.
The team has justified its Policy initiative design with: Group relevant definitions into a policy initiative assigned to the correct management scope. Which statement accurately describes why the approach works?
Initiatives bundle related policy rules and support shared compliance reporting. It is material here because security standards require a reusable collection of tagging, encryption and diagnostics policies.
Infrastructure as code declares desired resources and allows review and repeat deployment. That statement describes Standardized IaC, while the question asks how Policy initiative works: Initiatives bundle related policy rules and support shared compliance reporting.
Policy scope and exclusions should be the smallest feasible exception rather than removing global guardrails. Initiatives bundle related policy rules and support shared compliance reporting.
Management groups supply governance scope above subscriptions without moving resources into a single subscription. Initiatives bundle related policy rules and support shared compliance reporting.
An application uses PostgreSQL for writes but analysts overload the writer with complex read-only reports. An engineer must deliver the following acceptance evidence: The reports run on a replica while primary transaction performance improves. What design choice is defensible?
Read replicas offload eligible read-only queries but are asynchronously updated from the writer. The selected architecture is add supported PostgreSQL Flexible Server read replicas with suitable replication-lag expectations; confirm the result by checking that the reports run on a replica while primary transaction performance improves.
Migration assessment identifies blockers and target-fit issues before a cutover. The current need is: An application uses PostgreSQL for writes but analysts overload the writer with complex read-only reports.
SQL auditing captures database events as configured separately from application request telemetry. It does not solve the specified PostgreSQL read replica condition.
Dynamic data masking limits exposure in query results but is not a substitute for database access control. Its design target is SQL dynamic data masking. The stated requirement instead concerns: An application uses PostgreSQL for writes but analysts overload the writer with complex read-only reports.
The team has justified its Network-flow telemetry design with: Configure supported virtual network flow logs with Traffic Analytics where available. Which statement accurately describes why the approach works?
Virtual network flow logs represent observed network flows and Traffic Analytics derives traffic insights. It is material here because network engineers require VNet-level flow visibility for troubleshooting east-west connections without packet capture.
Storage-based diagnostic archives and immutability serve compliance preservation rather than interactive KQL search. Virtual network flow logs represent observed network flows and Traffic Analytics derives traffic insights.
Action groups define notifications and automated responses and can be reused by alert rules. It belongs to Notification routing. The stated architecture instead relies on: Virtual network flow logs represent observed network flows and Traffic Analytics derives traffic insights.
DCRs specify collected streams destinations and transformations for supported agent sources. That statement describes Agent collection rules, while the question asks how Network-flow telemetry works: Virtual network flow logs represent observed network flows and Traffic Analytics derives traffic insights.
Please check your mailbox for a message from support@examlabs.com and follow the directions.