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 Recovery time objective, the reviewer assesses this requirement: A payment system must resume in thirty minutes after a regional outage. Which of the reported outcomes is decisive?
RTO is the maximum acceptable restoration duration, not the amount of lost data. Confirm using the measurable result: A regional failover test restores business service in less than the allowed interval.
Azure SQL automatic full differential and log backups support restoring database state at a selected time. The SQL database PITR test checks a restored database contains transactions immediately preceding the truncation; the relevant outcome is A regional failover test restores business service in less than the allowed interval.
Backup private connectivity has service and workload prerequisites distinct from ordinary storage private endpoints. Those observations validate Backup private endpoints. They do not establish the required Recovery time objective result: A regional failover test restores business service in less than the allowed interval.
Soft delete retains recoverable protected backup data after deletion for a configured interval. The distinguishing check is: A regional failover test restores business service in less than the allowed interval.
Projects repeatedly omit the environment tag although the parent resource group has it. The acceptance test is: New supported resources inherit the resource-group environment tag after assignment. Which design recommendation best satisfies both?
Modify effects can update eligible metadata and require the required remediation permissions. The selected architecture is use a Policy modify or inherit-tag pattern with appropriate managed identity; confirm the result by checking that new supported resources inherit the resource-group environment tag after assignment.
Management groups supply governance scope above subscriptions without moving resources into a single subscription. The current need is: Projects repeatedly omit the environment tag although the parent resource group has it.
Policy deny or audit effects can enforce required metadata at supported resource scopes. That is useful for Required tag policy (Cost reporting is missing the billing cost center tag on newly created resources). It does not meet the current Inherited tagging requirement: Projects repeatedly omit the environment tag although the parent resource group has it.
Budgets monitor and notify about spending and do not automatically stop resources. It does not solve the specified Inherited tagging condition.
An architect must sign off on Azure-to-Azure ASR networking. The business problem is: Replicated VMs boot in the secondary region but application private DNS and subnets are unavailable. What observed test result provides valid evidence?
Compute replication does not automatically guarantee complete application network reachability. Confirm using the measurable result: A test failover can reach the recovered app through the intended private routes.
Independent crash-consistent snapshots may not preserve database write ordering across disks. The distinguishing check is: A test failover can reach the recovered app through the intended private routes.
Geo-redundant vault storage can provide recovery copies in a paired region subject to feature settings. The Cross-region backup test checks a supported secondary-region restore yields the expected recovery point; the relevant outcome is A test failover can reach the recovered app through the intended private routes.
RTO is the maximum acceptable restoration duration, not the amount of lost data. The offered observation would demonstrate Recovery time objective: A regional failover test restores business service in less than the allowed interval. The current validation is different: A test failover can reach the recovered app through the intended private routes.
A legacy application runs on a physical Windows server and needs an IaaS move. The acceptance test is: A cutover VM starts in Azure with its application settings preserved. Which design recommendation best satisfies both?
Physical migration requires source capture and replication methods different from VMware agentless VM migration. The selected architecture is use an Azure Migrate-supported physical-server or agent-based migration approach; confirm the result by checking that a cutover VM starts in Azure with its application settings preserved.
Landing-zone foundations provide policy, connectivity and subscription placement for incoming workloads. That is useful for Migration landing zone (A program plans 100 app moves but lacks identity, DNS, governance and network foundations). It does not meet the current Physical server migration requirement: A legacy application runs on a physical Windows server and needs an IaaS move.
Rebuild replaces the application rather than merely moving its binaries. Its design target is Rebuild cloud native. The stated requirement instead concerns: A legacy application runs on a physical Windows server and needs an IaaS move.
Retiring unused assets reduces migration risk and cloud cost rather than copying unnecessary VMs. It does not solve the specified Physical server migration condition.
A geographically distributed app needs a readable secondary SQL database to offload reports without moving the primary write location. An engineer must deliver the following acceptance evidence: Report queries use the designated secondary and replication lag stays within the accepted bound. What design choice is defensible?
Active geo-replication creates readable asynchronously updated secondary databases while primary remains writable. The selected architecture is configure supported Azure SQL active geo-replication and route stale-tolerant reads to the replica; confirm the result by checking that report queries use the designated secondary and replication lag stays within the accepted bound.
Read-only replicas can offload reporting from the primary where the tier provides the capability. Its design target is SQL read scaling. The stated requirement instead concerns: A geographically distributed app needs a readable secondary SQL database to offload reports without moving the primary write location.
Ledger records cryptographically verifiable tamper-evidence for supported relational tables. The relevant requirement is: A geographically distributed app needs a readable secondary SQL database to offload reports without moving the primary write location.
Business Critical uses a local SSD-oriented architecture with high availability replicas. It does not solve the specified SQL geo-replication reporting condition.
A business app appears self-contained but batch jobs communicate with undocumented on-prem systems. An engineer must deliver the following acceptance evidence: A test workload executes its dependent calls from the planned Azure subnet. What design choice is defensible?
Hidden dependencies can break after migration even when VM replication succeeds. The selected architecture is build a dependency map and classify blockers before sequencing migration waves; confirm the result by checking that a test workload executes its dependent calls from the planned Azure subnet.
Refactoring changes application structure and decouples independent workloads. It does not solve the specified Application dependency mapping condition.
Online migration reduces cutover downtime by applying ongoing changes after the baseline copy. That is useful for SQL online migration (A high-volume database allows little cutover downtime and must synchronize changes before switch). It does not meet the current Application dependency mapping requirement: A business app appears self-contained but batch jobs communicate with undocumented on-prem systems.
Server migration replication supports lift-and-shift of eligible VM workloads to Azure. Its design target is VM agentless migration. The stated requirement instead concerns: A business app appears self-contained but batch jobs communicate with undocumented on-prem systems.
A migrated app uses a new Azure IP but clients have a hardcoded old DNS endpoint. Identify the most suitable implementation for an outcome where clients resolve the new endpoint and the rollback procedure returns traffic if needed.
DNS cutover requires propagation and dependency planning independent of VM replication. The selected architecture is plan DNS TTL reduction, cutover updates and rollback before service migration; confirm the result by checking that clients resolve the new endpoint and the rollback procedure returns traffic if needed.
Target compatibility determines whether code changes or a different managed target are required. The current need is: A migrated app uses a new Azure IP but clients have a hardcoded old DNS endpoint.
Server migration replication supports lift-and-shift of eligible VM workloads to Azure. Its design target is VM agentless migration. The stated requirement instead concerns: A migrated app uses a new Azure IP but clients have a hardcoded old DNS endpoint.
Refactoring changes application structure and decouples independent workloads. It does not solve the specified Networking cutover DNS condition.
A solution must address both Storage service endpoints and Blob object storage. First requirement: Virtual network workloads need storage traffic to use Azure backbone but the storage service remains publicly addressable. Second requirement: A media service stores millions of image and video objects accessed through REST without a shared file system. Select TWO recommendations that meet these independent needs.
For the Storage service endpoints half of this two-part design, service endpoints secure selected Azure service traffic from VNets but do not create a private IP for the PaaS service. Verify: Approved subnet access succeeds and other public sources are denied by storage rules. The other half concerns Blob object storage.
For the Blob object storage half of this design, Blob Storage manages massively scalable object data rather than SMB-compatible shared volumes. Check: A client uploads and downloads an object using its scoped authorization. The other half concerns Storage service endpoints.
Premium SSD v2 decouples some provisioned performance settings from disk capacity. That plan is appropriate for Premium SSD v2. The two controls sought here are Storage service endpoints and Blob object storage.
Session consistency offers read-your-writes within a session without strong global consistency. Its own validation would be: The writing session immediately reads its own update while other sessions may lag. The current paired requirement is Storage service endpoints and Blob object storage.
Autoscale adjusts provisioned RU/s capacity according to measured load within a maximum. That plan is appropriate for Cosmos autoscale. The two controls sought here are Storage service endpoints and Blob object storage.
Architecture review: VNet integration App Service and Private inbound App Service. Requirement A: An App Service must make outbound calls to a private SQL server while remaining publicly accessible for inbound requests. Requirement B: An App Service must accept requests only through the corporate private network. Which complete two-part proposal satisfies both constraints?
For requirement A, vNet integration is principally an outbound feature; inbound private access requires other controls. For requirement B, private endpoints provide a private inbound path for supported App Service access. Verify both independently: The app connects to private SQL via VNet while its public frontend remains reachable as intended; Corporate users connect using private DNS and public clients are rejected.
VNet integration is principally an outbound feature; inbound private access requires other controls. Private endpoints provide a private inbound path for supported App Service access. The proposed steps (use Azure Standard Internal Load Balancer with probes and backend pool; deploy Azure VPN Gateway site-to-site tunnels with matching local/remote IPsec settings) address other capabilities instead of this required pair.
VNet integration is principally an outbound feature; inbound private access requires other controls. The other proposed action (deploy Azure VPN Gateway site-to-site tunnels with matching local/remote IPsec settings) addresses a different operation. Private endpoints provide a private inbound path for supported App Service access.
One action is correct. The other targets Load Balancer internal L4, leaving VNet integration App Service unsolved. Its necessary action is: Use App Service regional VNet integration for outbound connectivity and private routing.
A SQL application can move to managed SQL with a few configuration changes but needs no redesign. Which Azure architecture would most directly achieve the required result: Migration validation shows required database features function on the selected managed tier?
Replatforming changes hosting characteristics while preserving most app behavior. The selected architecture is evaluate replatforming to Azure SQL Managed Instance or Database after compatibility tests; confirm the result by checking that migration validation shows required database features function on the selected managed tier.
Physical data transfer can shorten initial bulk migration when network transfer is impractical. The relevant requirement is: A SQL application can move to managed SQL with a few configuration changes but needs no redesign.
Object count alone cannot establish content integrity or ACL preservation. The current need is: A SQL application can move to managed SQL with a few configuration changes but needs no redesign.
DNS cutover requires propagation and dependency planning independent of VM replication. It does not solve the specified Replatform database condition.
Architecture review: AKS cluster autoscaler and AKS availability zones. Requirement A: Node pool capacity becomes insufficient for pending pods during daily traffic peaks. Requirement B: A production AKS cluster requires pods and nodes across three availability zones. Which complete two-part proposal satisfies both constraints?
For requirement A, cluster autoscaler adjusts nodes to schedule eligible pending pods. For requirement B, zone-distributed nodes plus suitable Kubernetes scheduling reduce single-zone concentration. Verify both independently: Pending pods move to new nodes before the measured capacity deadline; After a simulated zone failure, surviving pods maintain API availability and replacement replicas become Ready within the tested recovery window on healthy-zone nodes.
Both proposed halves address other use cases: Azure SQL zone redundancy and VM scale set autoscaling. The requested pair is AKS cluster autoscaler and AKS availability zones.
One action is correct. The other targets VM scale set autoscaling, leaving AKS availability zones unsolved. Its necessary action is: Use zone-aware node pools and workload spread/anti-affinity policies.
The first step implements Azure SQL zone redundancy instead of AKS cluster autoscaler. The necessary change is to enable AKS cluster autoscaler within approved node pool bounds.
Please check your mailbox for a message from support@examlabs.com and follow the directions.