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
A solution must address both Azure-to-Azure ASR networking and Failback after recovery. First requirement: Replicated VMs boot in the secondary region but application private DNS and subnets are unavailable. Second requirement: A team has documented failover to a secondary region but no controlled return to primary. Select TWO recommendations that meet these independent needs.
For the Azure-to-Azure ASR networking half of this two-part design, compute replication does not automatically guarantee complete application network reachability. Verify: A test failover can reach the recovered app through the intended private routes. The other half concerns Failback after recovery.
For the Failback after recovery half of this design, failback is a separate operational sequence after workloads run in the recovery site. Check: A controlled failback returns traffic and state to the primary without unplanned data loss. The other half concerns Azure-to-Azure ASR networking.
Azure Backup creates managed recovery points distinct from continuously replicating a running VM. The corresponding task is Azure VM backup policy: A production Azure VM must be recoverable to an earlier day after accidental deletion of application files. It is not one of the two requested controls (Azure-to-Azure ASR networking and Failback after recovery).
Soft delete retains recoverable protected backup data after deletion for a configured interval. Its own validation would be: The deleted item is recoverable within the protected deletion window. The current paired requirement is Azure-to-Azure ASR networking and Failback after recovery.
RTO is the maximum acceptable restoration duration, not the amount of lost data. This alternative solves Recovery time objective, while the question separately requires Azure-to-Azure ASR networking and Failback after recovery.
An architect must sign off on Container Registry. The business problem is: Build pipelines need a private managed Docker image repository with vulnerability scanning and managed identity access. What observed test result provides valid evidence?
ACR stores OCI images and supports Azure identity-based authorization to the registry. Confirm using the measurable result: A pipeline pushes a signed image and production pulls it without shared registry passwords.
Redundancy prevents a single host maintenance event from removing the only serving instance. The VM maintenance handling test checks maintenance on one node leaves other healthy nodes serving the API; the relevant outcome is A pipeline pushes a signed image and production pulls it without shared registry passwords.
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 pipeline pushes a signed image and production pulls it without shared registry passwords.
GPU instances provide accelerators not present on standard CPU-only VMs. Those observations validate GPU VM. They do not establish the required Container Registry result: A pipeline pushes a signed image and production pulls it without shared registry passwords.
A SQL database writes audit and performance diagnostics but the central workspace has only platform activity records. Identify the most suitable implementation for an outcome where sQL diagnostic records appear in the target workspace and can be filtered by database name.
Resource diagnostic settings forward selected resource logs whereas subscription Activity Log tracks management operations. The selected architecture is enable the supported SQL resource diagnostic categories to a Log Analytics workspace; confirm the result by checking that SQL diagnostic records appear in the target workspace and can be filtered by database name.
AMPLS provides private connectivity to supported Azure Monitor ingestion and query endpoints. Its design target is Private observability. The stated requirement instead concerns: A SQL database writes audit and performance diagnostics but the central workspace has only platform activity records.
Event Hubs provides durable high-throughput event ingestion for downstream stream consumers. It does not solve the specified Database resource diagnostics condition.
WAF rule and access diagnostics identify rule IDs and request outcomes that aggregate health metrics miss. That is useful for WAF decision logs (The application firewall blocks legitimate requests but developers cannot see the matching rule). It does not meet the current Database resource diagnostics requirement: A SQL database writes audit and performance diagnostics but the central workspace has only platform activity records.
Analytics engines require directory-aware ACLs and atomic directory rename semantics over object storage. The acceptance test is: A Spark user renames an eligible directory atomically and directory ACLs are enforced. Which design recommendation best satisfies both?
ADLS Gen2 adds directory semantics and access ACLs to blob-backed storage. The selected architecture is enable hierarchical namespace and use Azure Data Lake Storage Gen2 capabilities; confirm the result by checking that a Spark user renames an eligible directory atomically and directory ACLs are enforced.
A user-delegation SAS is authorized through Entra credentials and avoids distributing account keys. The relevant requirement is: Analytics engines require directory-aware ACLs and atomic directory rename semantics over object storage.
Blob Inventory produces scheduled object inventories without crawling each object individually. That is useful for Blob inventory (Operations needs a weekly manifest of millions of blobs with properties and access tiers). It does not meet the current Blob HNS namespace requirement: Analytics engines require directory-aware ACLs and atomic directory rename semantics over object storage.
Blob change feed records changes to blob objects for downstream processing. It does not solve the specified Blob HNS namespace condition.
A collaboration app must send real-time server-to-client notifications to many concurrent browsers. An engineer must deliver the following acceptance evidence: Two connected clients immediately receive the authorized published event. What design choice is defensible?
Web PubSub provides managed WebSocket connection fan-out so application servers need not hold all client sessions. The selected architecture is use Azure Web PubSub with authenticated WebSocket clients and appropriate hub design; confirm the result by checking that two connected clients immediately receive the authorized published event.
Application Gateway provides application-aware path routing rather than basic L4 forwarding. That is useful for Application Gateway path routing (One regional HTTPS endpoint needs /api requests routed to API pods and /shop to a web tier). It does not meet the current Web PubSub real time requirement: A collaboration app must send real-time server-to-client notifications to many concurrent browsers.
APIM can enforce per-client API consumption controls before requests reach backends. Its design target is APIM rate limiting. The stated requirement instead concerns: A collaboration app must send real-time server-to-client notifications to many concurrent browsers.
Event Grid distributes discrete source events to configured subscribers. It does not solve the specified Web PubSub real time condition.
Architecture review: PostgreSQL flexible server and Azure SQL Database single database. Requirement A: An application depends on PostgreSQL extensions and wants managed PostgreSQL without a VM. Requirement B: A SaaS app runs a standalone transactional SQL Server-compatible database and must avoid managing operating systems. Which complete two-part proposal satisfies both constraints?
For requirement A, flexible Server offers managed open-source PostgreSQL with supported extensions and deployment options. For requirement B, Azure SQL Database offers fully managed relational database operations with automated backups. Verify both independently: The required extension is available and the app connects without an OS-managed database host; The application connects through its supported driver without patching database VMs.
Flexible Server offers managed open-source PostgreSQL with supported extensions and deployment options. Azure SQL Database offers fully managed relational database operations with automated backups. The proposed steps (use appropriate application-side connection pooling with database tier capacity planning; use SQL Always Encrypted with appropriate key management and compatible client drivers) address other capabilities instead of this required pair.
The mismatched half is SQL Always Encrypted; Azure SQL Database single database instead needs: Select Azure SQL Database for the managed individual database.
The first step implements SQL connection pooling instead of PostgreSQL flexible server. The necessary change is to select Azure Database for PostgreSQL Flexible Server and verify extension availability.
A database application depends on a third-party kernel-level driver installed alongside SQL Server. An architecture board will approve a solution only if this outcome is demonstrated: The vendor driver runs on the VM while maintenance responsibilities are explicitly assigned. What should be selected?
IaaS retains operating-system and SQL instance control that PaaS databases do not provide. The selected architecture is keep SQL Server on an Azure virtual machine with appropriate HA and backup architecture; confirm the result by checking that the vendor driver runs on the VM while maintenance responsibilities are explicitly assigned.
Always Encrypted supports encryption and decryption in capable clients to reduce exposure to the database engine. It does not solve the specified SQL Server on Azure VM condition.
Database-per-tenant provides a distinct security and backup boundary versus one shared schema. The current need is: A database application depends on a third-party kernel-level driver installed alongside SQL Server.
Flexible Server offers managed open-source PostgreSQL with supported extensions and deployment options. That is useful for PostgreSQL flexible server (An application depends on PostgreSQL extensions and wants managed PostgreSQL without a VM). It does not meet the current SQL Server on Azure VM requirement: A database application depends on a third-party kernel-level driver installed alongside SQL Server.
An architect must sign off on ADLS ACLs. The business problem is: A Spark job has storage RBAC access at container level but must isolate sensitive folders. What observed test result provides valid evidence?
Directory ACLs provide path-level data authorization when hierarchical namespace is enabled. Confirm using the measurable result: A test identity reads its assigned folder but is denied a sibling folder.
Service endpoints secure selected Azure service traffic from VNets but do not create a private IP for the PaaS service. Those observations validate Storage service endpoints. They do not establish the required ADLS ACLs result: A test identity reads its assigned folder but is denied a sibling folder.
Partition key distribution governs data/throughput placement and query efficiency. The distinguishing check is: A test identity reads its assigned folder but is denied a sibling folder.
Managed disks provide block storage to Azure VMs rather than object or SMB interfaces. The Azure managed disks test checks the disk attaches to the VM and meets measured random IO latency; the relevant outcome is A test identity reads its assigned folder but is denied a sibling folder.
For SQL migration assessment, operations are closing a change that addressed: A legacy SQL database contains unsupported features and the team wants a target tier before moving. Which post-change signal belongs in the acceptance record?
Migration assessment identifies blockers and target-fit issues before a cutover. Confirm using the measurable result: The compatibility report has no unmitigated blocking features for the chosen target.
Temporal tables retain row history and support as-of queries independently of whole-database backups. Those observations validate SQL temporal tables. They do not establish the required SQL migration assessment result: The compatibility report has no unmitigated blocking features for the chosen target.
Active geo-replication creates readable asynchronously updated secondary databases while primary remains writable. The distinguishing check is: The compatibility report has no unmitigated blocking features for the chosen target.
Read replicas offload eligible read-only queries but are asynchronously updated from the writer. The offered observation would demonstrate PostgreSQL read replica: The reports run on a replica while primary transaction performance improves. The current validation is different: The compatibility report has no unmitigated blocking features for the chosen target.
An obsolete application codebase has no maintainable runtime and must use current cloud services. An architecture board will approve a solution only if this outcome is demonstrated: The new app meets functional acceptance while retiring the unsupported runtime. What should be selected?
Rebuild replaces the application rather than merely moving its binaries. The selected architecture is choose a rebuild approach where business requirements justify new architecture; confirm the result by checking that the new app meets functional acceptance while retiring the unsupported runtime.
Offline migration can simplify cutover when application downtime is acceptable. That is useful for SQL offline migration (A small SQL database can tolerate a planned maintenance outage for cutover). It does not meet the current Rebuild cloud native requirement: An obsolete application codebase has no maintainable runtime and must use current cloud services.
Azure Migrate inventories servers and supports readiness and sizing assessments. It does not solve the specified Rebuild cloud native condition.
Hybrid reachability depends on both routing and security decisions in the destination VNet. The current need is: An obsolete application codebase has no maintainable runtime and must use current cloud services.
The VM resource health review proposes: Use Azure Resource Health and resource health alerts for the VM. Which Azure behavior is the technical justification for this decision?
Resource Health reports the platform-side availability history of individual Azure resources. It is material here because a single VM becomes unavailable but the Azure region itself is healthy.
Dynamic thresholds adapt alert boundaries to historical metric patterns after sufficient data exists. That statement describes Dynamic baseline alerts, while the question asks how VM resource health works: Resource Health reports the platform-side availability history of individual Azure resources.
Resource diagnostic settings forward selected resource logs whereas subscription Activity Log tracks management operations. Resource Health reports the platform-side availability history of individual Azure resources.
Metrics are low-latency numeric series and alert evaluation can trigger actions independently of a log query. It belongs to CPU threshold alerts. The stated architecture instead relies on: Resource Health reports the platform-side availability history of individual Azure resources.
Please check your mailbox for a message from support@examlabs.com and follow the directions.