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
During technical sign-off for Recovery point objective, the architect selects: Use a replication and write-consistency design verified against the five-minute RPO. Which underlying behavior should be documented?
RPO measures the maximum tolerated data loss period at a recovery point. It is material here because a business may lose at most five minutes of writes during failover.
Immutable backup settings can prevent specified destructive operations against protected backups. That statement describes Vault immutability, while the question asks how Recovery point objective works: RPO measures the maximum tolerated data loss period at a recovery point.
Blob operational backup relies on point-in-time object protection features rather than VM-level backups. RPO measures the maximum tolerated data loss period at a recovery point.
Managed PostgreSQL backups support rebuilding a server at a selected valid recovery time. It belongs to PostgreSQL PITR. The stated architecture instead relies on: RPO measures the maximum tolerated data loss period at a recovery point.
The target environment adopts this approach for Eventual consistency UX: Design an eventual-consistency contract with status tracking and idempotent updates. What property makes it suitable?
Asynchronous projections can lag writes and need clear read-after-write expectations. It is material here because an order service writes asynchronously into a read model and users momentarily see old data.
Durable orchestrations checkpoint progress and coordinate stateful serverless workflows. Asynchronous projections can lag writes and need clear read-after-write expectations.
Event Grid distributes discrete source events to configured subscribers. It belongs to Event Grid notification. The stated architecture instead relies on: Asynchronous projections can lag writes and need clear read-after-write expectations.
Shared session state survives an individual stateless app worker replacement. That statement describes Azure Cache for Redis session, while the question asks how Eventual consistency UX works: Asynchronous projections can lag writes and need clear read-after-write expectations.
The team has justified its VM scale set autoscaling design with: Use Virtual Machine Scale Sets with autoscale rules and a stateless design. Which statement accurately describes why the approach works?
VMSS can add or remove similarly configured VM instances based on supported signals. It is material here because demand for a stateless API swings by 10x and manual provisioning causes downtime.
Eligible App Service plans distribute app workers across availability zones with sufficient capacity. VMSS can add or remove similarly configured VM instances based on supported signals.
ZRS synchronously replicates data across primary-region zones. It belongs to Blob ZRS availability. The stated architecture instead relies on: VMSS can add or remove similarly configured VM instances based on supported signals.
Traffic Manager is DNS-based and clients connect directly to the returned service endpoint. VMSS can add or remove similarly configured VM instances based on supported signals.
Before approving NAT Gateway outbound, the reviewer assesses this requirement: A subnet-based worker fleet needs stable outbound public IPs without per-VM public IP addresses. Which of the reported outcomes is decisive?
NAT Gateway provides outbound SNAT for supported subnet internet traffic. Confirm using the measurable result: External partners observe only the approved outbound IP during simultaneous worker sessions.
A hub centralizes connectivity services while spoke VNets isolate applications. The distinguishing check is: External partners observe only the approved outbound IP during simultaneous worker sessions.
Peering connects VNet address spaces through the Microsoft backbone without creating transitive routing by default. The offered observation would demonstrate VNet peering: Private IP traffic flows between the peered VNets with appropriate NSG permissions. The current validation is different: External partners observe only the approved outbound IP during simultaneous worker sessions.
Network Watcher diagnostic tools identify effective network behavior and filtering decisions. Those observations validate Network Watcher diagnosis. They do not establish the required NAT Gateway outbound result: External partners observe only the approved outbound IP during simultaneous worker sessions.
Spoke A peers with the hub and spoke B peers with the same hub but cannot communicate directly. Choose the architecture that can be validated by this result: Permitted spoke-to-spoke traffic follows inspected hub path and denied traffic fails.
VNet peering alone is not transitive and forwarding needs explicit architecture. The selected architecture is design a routing/transit solution with a supported NVA or Azure Firewall where required; confirm the result by checking that permitted spoke-to-spoke traffic follows inspected hub path and denied traffic fails.
Azure Load Balancer routes Layer 4 traffic inside a VNet without parsing HTTP URLs. Its design target is Load Balancer internal L4. The stated requirement instead concerns: Spoke A peers with the hub and spoke B peers with the same hub but cannot communicate directly.
VNet integration is principally an outbound feature; inbound private access requires other controls. The relevant requirement is: Spoke A peers with the hub and spoke B peers with the same hub but cannot communicate directly.
A hub centralizes connectivity services while spoke VNets isolate applications. It does not solve the specified Peering nontransitivity condition.
To validate the Storage migration validation deployment, reviewers revisit this operational need: After copying storage objects the team assumes file count equality proves complete accuracy. What result confirms it was met?
Object count alone cannot establish content integrity or ACL preservation. Confirm using the measurable result: Checksums, timestamps and access checks reconcile source and destination.
Hidden dependencies can break after migration even when VM replication succeeds. The offered observation would demonstrate Application dependency mapping: A test workload executes its dependent calls from the planned Azure subnet. The current validation is different: Checksums, timestamps and access checks reconcile source and destination.
Rehosting prioritizes speed and minimal code changes over immediate PaaS modernization. The distinguishing check is: Checksums, timestamps and access checks reconcile source and destination.
Retiring unused assets reduces migration risk and cloud cost rather than copying unnecessary VMs. The Retire unused services test checks decommissioned workloads create no application dependency failure; the relevant outcome is Checksums, timestamps and access checks reconcile source and destination.
To validate the AKS full Kubernetes deployment, reviewers revisit this operational need: A platform team needs custom Kubernetes network policies controllers and cluster API access. What result confirms it was met?
AKS provides managed Kubernetes control-plane hosting with configurable worker clusters. Confirm using the measurable result: Custom controllers and policy resources function under the supported cluster configuration.
Compute Gallery distributes managed image versions for repeatable VM deployments. The distinguishing check is: Custom controllers and policy resources function under the supported cluster configuration.
GPU instances provide accelerators not present on standard CPU-only VMs. The GPU VM test checks the model uses available GPU memory and meets measured inference latency; the relevant outcome is Custom controllers and policy resources function under the supported cluster configuration.
Functions supplies event-driven serverless execution with plan-specific scale and timeout limits. The offered observation would demonstrate Azure Functions event: A matching event triggers the function within the required processing window. The current validation is different: Custom controllers and policy resources function under the supported cluster configuration.
One operational SQL database must scale beyond the capacity limits of ordinary General Purpose storage tiers. The acceptance test is: A growth test reaches the required storage target with the expected compute and backup architecture. Which design recommendation best satisfies both?
Hyperscale decouples storage scale from compute and supports large database sizes. The selected architecture is evaluate Azure SQL Database Hyperscale with applicable workload support; confirm the result by checking that a growth test reaches the required storage target with the expected compute and backup architecture.
SQL auditing captures database events as configured separately from application request telemetry. That is useful for SQL auditing (Compliance requires records of login attempts and selected database actions independent of app logs). It does not meet the current SQL Hyperscale growth requirement: One operational SQL database must scale beyond the capacity limits of ordinary General Purpose storage tiers.
Pooling reuses connections and reduces setup overhead relative to per-request creation. Its design target is SQL connection pooling. The stated requirement instead concerns: One operational SQL database must scale beyond the capacity limits of ordinary General Purpose storage tiers.
Business Critical uses a local SSD-oriented architecture with high availability replicas. It does not solve the specified SQL Hyperscale growth condition.
A media service stores millions of image and video objects accessed through REST without a shared file system. The acceptance test is: A client uploads and downloads an object using its scoped authorization. Which design recommendation best satisfies both?
Blob Storage manages massively scalable object data rather than SMB-compatible shared volumes. The selected architecture is use Azure Blob Storage containers with lifecycle policies and scoped access; confirm the result by checking that a client uploads and downloads an object using its scoped authorization.
Cosmos DB provides a distributed document database with configurable consistency and throughput. It does not solve the specified Blob object storage condition.
Partition key distribution governs data/throughput placement and query efficiency. The relevant requirement is: A media service stores millions of image and video objects accessed through REST without a shared file system.
Premium SSD v2 decouples some provisioned performance settings from disk capacity. That is useful for Premium SSD v2 (A VM workload needs independently adjustable provisioned IOPS and throughput with SSD latency). It does not meet the current Blob object storage requirement: A media service stores millions of image and video objects accessed through REST without a shared file system.
A proposed solution for SQL geo-restore is: Plan Azure SQL geo-restore with acceptable recovery objectives and backup redundancy. Select the strongest statement supporting the recommendation.
Geo-restore is backup-based recovery with different RTO/RPO than active geo-replication. It is material here because a SQL database without an active geo-secondary needs disaster recovery from geo-redundant backups.
Compute replication does not automatically guarantee complete application network reachability. Geo-restore is backup-based recovery with different RTO/RPO than active geo-replication.
Nightly backups alone do not provide continuous workload replication or low recovery time. Geo-restore is backup-based recovery with different RTO/RPO than active geo-replication.
RPO measures the maximum tolerated data loss period at a recovery point. That statement describes Recovery point objective, while the question asks how SQL geo-restore works: Geo-restore is backup-based recovery with different RTO/RPO than active geo-replication.
A solution must address both Hybrid route validation and VM agentless migration. First requirement: Migrated VMs can ping local peers but cannot access on-premises databases over ExpressRoute. Second requirement: VMware VMs need replicated migration to Azure with a controlled cutover and minimal app redesign. Select TWO recommendations that meet these independent needs.
For the Hybrid route validation half of this two-part design, hybrid reachability depends on both routing and security decisions in the destination VNet. Verify: The Azure workload connects to on-prem data through the approved private network path. The other half concerns VM agentless migration.
For the VM agentless migration half of this design, server migration replication supports lift-and-shift of eligible VM workloads to Azure. Check: A test migration boots the replicated VM and validates application dependencies. The other half concerns Hybrid route validation.
Rebuild replaces the application rather than merely moving its binaries. That plan is appropriate for Rebuild cloud native. The two controls sought here are Hybrid route validation and VM agentless migration.
Landing-zone foundations provide policy, connectivity and subscription placement for incoming workloads. This alternative solves Migration landing zone, while the question separately requires Hybrid route validation and VM agentless migration.
Online migration reduces cutover downtime by applying ongoing changes after the baseline copy. The corresponding task is SQL online migration: A high-volume database allows little cutover downtime and must synchronize changes before switch. It is not one of the two requested controls (Hybrid route validation and VM agentless migration).
Please check your mailbox for a message from support@examlabs.com and follow the directions.