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: Quotas and limits and Role assignment scope. Requirement A: A proposed subscription hosts many public IPs and compute cores beyond regional quota. Requirement B: An engineer only operates one network resource group but has Contributor for the whole subscription. Which complete two-part proposal satisfies both constraints?
For requirement A, Azure service quotas are often scoped by subscription and region and can constrain deployability. For requirement B, RBAC assignments inherit downward so narrower scope reduces unintended changes. Verify both independently: A capacity forecast and quota decision support the planned deployment without surprise allocation errors; The engineer can change the assigned network group but not another group's resources.
Both proposed halves address other use cases: Defender compliance and Standardized IaC. The requested pair is Quotas and limits and Role assignment scope.
RBAC assignments inherit downward so narrower scope reduces unintended changes. The other proposed action (use Microsoft Defender for Cloud regulatory compliance and security posture assessments) does not implement the first control. Azure service quotas are often scoped by subscription and region and can constrain deployability.
Azure service quotas are often scoped by subscription and region and can constrain deployability. The other proposed action (use Azure Bicep modules and deployment pipelines with approval gates) addresses a different operation. RBAC assignments inherit downward so narrower scope reduces unintended changes.
To validate the Traffic Manager DNS routing deployment, reviewers revisit this operational need: A TCP application requires global endpoint selection using DNS without a global L7 reverse proxy. What result confirms it was met?
Traffic Manager is DNS-based and clients connect directly to the returned service endpoint. Confirm using the measurable result: DNS responses prefer the healthy endpoint as monitoring marks another unavailable.
Multi-region writes allow eligible regions to accept writes but require handling conflicts. The distinguishing check is: DNS responses prefer the healthy endpoint as monitoring marks another unavailable.
GZRS synchronously spreads primary copies across zones and asynchronously replicates to another region. The offered observation would demonstrate Blob GZRS durability: A regional recovery plan uses the secondary while zonal faults leave primary available. The current validation is different: DNS responses prefer the healthy endpoint as monitoring marks another unavailable.
PDBs constrain voluntary disruptions but do not prevent all involuntary failures. Those observations validate AKS pod disruption budget. They do not establish the required Traffic Manager DNS routing result: DNS responses prefer the healthy endpoint as monitoring marks another unavailable.
The Container Registry review proposes: Use Azure Container Registry with controlled image push and pull access. Which Azure behavior is the technical justification for this decision?
ACR stores OCI images and supports Azure identity-based authorization to the registry. It is material here because build pipelines need a private managed Docker image repository with vulnerability scanning and managed identity access.
Durable Functions manages stateful workflows over serverless function executions. That statement describes Azure Functions durable workflow, while the question asks how Container Registry works: ACR stores OCI images and supports Azure identity-based authorization to the registry.
GPU instances provide accelerators not present on standard CPU-only VMs. ACR stores OCI images and supports Azure identity-based authorization to the registry.
Redundancy prevents a single host maintenance event from removing the only serving instance. It belongs to VM maintenance handling. The stated architecture instead relies on: ACR stores OCI images and supports Azure identity-based authorization to the registry.
A VM-based API must survive scheduled host maintenance without customer-visible downtime. The acceptance test is: Maintenance on one node leaves other healthy nodes serving the API. Which design recommendation best satisfies both?
Redundancy prevents a single host maintenance event from removing the only serving instance. The selected architecture is distribute redundant VMs across appropriate zones or fault domains and use health-probed load balancing; confirm the result by checking that maintenance on one node leaves other healthy nodes serving the API.
Durable Functions manages stateful workflows over serverless function executions. The current need is: A VM-based API must survive scheduled host maintenance without customer-visible downtime.
VMSS automates management and scaling of similar VMs in the same workload. That is useful for VMSS dynamic scaling (An autoscaling API needs several identical VMs during peak hours and only a few at night). It does not meet the current VM maintenance handling requirement: A VM-based API must survive scheduled host maintenance without customer-visible downtime.
Queue-length scaling aligns worker count with pending work rather than idle CPU metrics. It does not solve the specified VM maintenance handling condition.
A solution must address both Recovery point objective and Azure Site Recovery failover. First requirement: A business may lose at most five minutes of writes during failover. Second requirement: An enterprise VM workload needs a tested recovery-site boot process after complete primary-region loss. Select TWO recommendations that meet these independent needs.
For the Azure Site Recovery failover half of this design, site Recovery replicates workload state and orchestrates VM failover for supported scenarios. Check: A test failover brings up the application in the recovery region within measured RTO. The other half concerns Recovery point objective.
For the Recovery point objective half of this two-part design, RPO measures the maximum tolerated data loss period at a recovery point. Verify: Failover comparison shows the latest committed recoverable write is within five minutes. The other half concerns Azure Site Recovery failover.
Managed PostgreSQL backups support rebuilding a server at a selected valid recovery time. The corresponding task is PostgreSQL PITR: A managed PostgreSQL server is damaged by a schema update and needs its prior state. It is not one of the two requested controls (Recovery point objective and Azure Site Recovery failover).
Periodic backups produce interval snapshots and are not the same as continuous point-in-time recovery. This alternative solves Cosmos periodic backup, while the question separately requires Recovery point objective and Azure Site Recovery failover.
Continuous backup can support point-in-time restore for supported Cosmos API accounts. The corresponding task is Cosmos continuous backup: A developer deletes Cosmos DB documents and needs to restore the account to an earlier instant. It is not one of the two requested controls (Recovery point objective and Azure Site Recovery failover).
During technical sign-off for Data Factory hybrid copy, the architect selects: Use Azure Data Factory with a self-hosted integration runtime and Copy activity. Which underlying behavior should be documented?
Self-hosted integration runtime initiates supported outbound communications to access private sources. It is material here because a nightly pipeline must copy on-premises SQL data to Azure Data Lake without opening an inbound corporate firewall port.
Service Bus is an enterprise message broker with delivery and dead-letter semantics. It belongs to Service Bus ordering. The stated architecture instead relies on: Self-hosted integration runtime initiates supported outbound communications to access private sources.
Partner event integration routes supported third-party event types without custom polling. Self-hosted integration runtime initiates supported outbound communications to access private sources.
Hybrid/private integration requires a reachable private network path rather than open public DB exposure. Self-hosted integration runtime initiates supported outbound communications to access private sources.
A rollout addressing VM disk encryption has reached acceptance testing. The original problem was: A finance VM needs customer-managed encryption keys for managed disks. Which finding verifies its resolution?
Encryption sets connect managed disk encryption to customer-owned keys. Confirm using the measurable result: Disk configuration shows the designated key and encrypted state before production traffic.
Queue-length scaling aligns worker count with pending work rather than idle CPU metrics. The Autoscaling based on queue test checks the number of workers grows with queue backlog and contracts after processing; the relevant outcome is Disk configuration shows the designated key and encrypted state before production traffic.
Memory-optimized sizes offer higher RAM-to-vCPU ratio for large in-memory working sets. Those observations validate Memory optimized VM. They do not establish the required VM disk encryption result: Disk configuration shows the designated key and encrypted state before production traffic.
Spot instances offer lower-priced spare capacity without guaranteed availability. The distinguishing check is: Disk configuration shows the designated key and encrypted state before production traffic.
To validate the Cosmos conflict handling deployment, reviewers revisit this operational need: A multi-write-region Cosmos account can update the same logical item concurrently. What result confirms it was met?
Concurrent writes require a conflict resolution policy to prevent unintended last-writer outcomes. Confirm using the measurable result: A controlled simultaneous update resolves according to the documented business rule.
Blob Storage manages massively scalable object data rather than SMB-compatible shared volumes. The offered observation would demonstrate Blob object storage: A client uploads and downloads an object using its scoped authorization. The current validation is different: A controlled simultaneous update resolves according to the documented business rule.
Archive tier minimizes long-term storage cost but archived objects must be rehydrated before reading. Those observations validate Blob archive rehydration. They do not establish the required Cosmos conflict handling result: A controlled simultaneous update resolves according to the documented business rule.
ADLS Gen2 adds directory semantics and access ACLs to blob-backed storage. The distinguishing check is: A controlled simultaneous update resolves according to the documented business rule.
The design team completed work on Multifactor critical operations. Its governing requirement was: Ransomware attackers should not disable backup protection with a single compromised admin account. Identify the conclusive verification result.
Multi-user authorization separates approval boundaries for critical backup changes. Confirm using the measurable result: A destructive backup operation requires the independent authorized role.
Nightly backups alone do not provide continuous workload replication or low recovery time. The distinguishing check is: A destructive backup operation requires the independent authorized role.
Periodic backups produce interval snapshots and are not the same as continuous point-in-time recovery. The Cosmos periodic backup test checks the new design demonstrates recovery granularity consistent with the RPO; the relevant outcome is A destructive backup operation requires the independent authorized role.
A non-disruptive DR test validates recovery sequences and dependencies before a real disaster. The offered observation would demonstrate Recovery drill governance: The test network runs recovered workloads and production endpoints remain unaffected. The current validation is different: A destructive backup operation requires the independent authorized role.
A mission-critical PostgreSQL workload requires HA across zones within a region. The acceptance test is: After a zone failure the managed standby serves database connections. Which design recommendation best satisfies both?
A zone-separated standby supports automated failover where offered. The selected architecture is enable zone-redundant HA on eligible Azure PostgreSQL Flexible Server; confirm the result by checking that after a zone failure the managed standby serves database connections.
Availability zones isolate infrastructure failure domains within an enabled region. It does not solve the specified PostgreSQL zone redundant HA condition.
ZRS synchronously replicates data across primary-region zones. Its design target is Blob ZRS availability. The stated requirement instead concerns: A mission-critical PostgreSQL workload requires HA across zones within a region.
Failover-group listeners abstract the primary location during regional failover. The relevant requirement is: A mission-critical PostgreSQL workload requires HA across zones within a region.
A rollout addressing Managed governance dashboards has reached acceptance testing. The original problem was: Auditors need repeatable visual reporting of compliance violations across many subscriptions. Which finding verifies its resolution?
Workbooks provide interactive analytical reports rather than the policy enforcement mechanism itself. Confirm using the measurable result: An auditor filters noncompliant resources by subscription and policy assignment.
Budgets monitor and notify about spending and do not automatically stop resources. The offered observation would demonstrate Cost budgets: A threshold crossing issues notifications while the app remains running. The current validation is different: An auditor filters noncompliant resources by subscription and policy assignment.
Initiatives bundle related policy rules and support shared compliance reporting. Those observations validate Policy initiative. They do not establish the required Managed governance dashboards result: An auditor filters noncompliant resources by subscription and policy assignment.
Landing zones combine platform foundations with repeatable application subscription governance. The distinguishing check is: An auditor filters noncompliant resources by subscription and policy assignment.
Please check your mailbox for a message from support@examlabs.com and follow the directions.