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
To validate the SQL offline migration deployment, reviewers revisit this operational need: A small SQL database can tolerate a planned maintenance outage for cutover. What result confirms it was met?
Offline migration can simplify cutover when application downtime is acceptable. Confirm using the measurable result: The migrated database passes consistency checks before reopening writes.
Replatforming changes hosting characteristics while preserving most app behavior. Those observations validate Replatform database. They do not establish the required SQL offline migration result: The migrated database passes consistency checks before reopening writes.
Rebuild replaces the application rather than merely moving its binaries. The distinguishing check is: The migrated database passes consistency checks before reopening writes.
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: The migrated database passes consistency checks before reopening writes.
Before approving Azure VM image standard, the reviewer assesses this requirement: A fleet needs consistent hardened VM images recreated every week from an approved source. Which of the reported outcomes is decisive?
Compute Gallery distributes managed image versions for repeatable VM deployments. Confirm using the measurable result: New VMs deploy from the approved version and report the expected security baseline.
VMSS automates management and scaling of similar VMs in the same workload. The distinguishing check is: New VMs deploy from the approved version and report the expected security baseline.
Durable Functions manages stateful workflows over serverless function executions. The Azure Functions durable workflow test checks a resumed orchestration continues from saved state after a worker restart; the relevant outcome is New VMs deploy from the approved version and report the expected security baseline.
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: New VMs deploy from the approved version and report the expected security baseline.
A solution must address both Blob archive rehydration and Blob hot/cool/cold. First requirement: A seven-year archive is rarely read and recovery can wait hours. Second requirement: A log archive sees frequent access for a month and rare access afterward. Select TWO recommendations that meet these independent needs.
For the Blob hot/cool/cold half of this design, tiering trades storage price against access and retrieval cost based on usage. Check: Old eligible blobs transition to the intended tier and remain retrievable. The other half concerns Blob archive rehydration.
For the Blob archive rehydration half of this two-part design, archive tier minimizes long-term storage cost but archived objects must be rehydrated before reading. Verify: An archived test object is restored to an online tier within the acceptable window. The other half concerns Blob hot/cool/cold.
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 Blob archive rehydration and Blob hot/cool/cold.
ADLS Gen2 adds directory semantics and access ACLs to blob-backed storage. That plan is appropriate for Blob HNS namespace. The two controls sought here are Blob archive rehydration and Blob hot/cool/cold.
Bounded staleness constrains replication read lag according to allowed versions/time. Its own validation would be: A test secondary read remains within the documented staleness bound. The current paired requirement is Blob archive rehydration and Blob hot/cool/cold.
A public site sometimes fails before user telemetry is received and operations need outside-in availability tests. Identify the most suitable implementation for an outcome where a deliberate endpoint outage is detected from multiple test locations before users file reports.
Synthetic tests independently probe URL availability and latency even when no real customer transaction occurs. The selected architecture is configure Application Insights availability tests at suitable geographic test locations; confirm the result by checking that a deliberate endpoint outage is detected from multiple test locations before users file reports.
Container insights exposes Kubernetes workload health and container logs beyond generic virtual-machine statistics. It does not solve the specified Synthetic uptime condition.
AMPLS provides private connectivity to supported Azure Monitor ingestion and query endpoints. That is useful for Private observability (A regulated environment must ingest monitoring data from isolated private networks without exposing public workspace ingestion endpoints). It does not meet the current Synthetic uptime requirement: A public site sometimes fails before user telemetry is received and operations need outside-in availability tests.
A log search alert can evaluate aggregated matching records instead of only raw metric time series. Its design target is Log anomaly alert. The stated requirement instead concerns: A public site sometimes fails before user telemetry is received and operations need outside-in availability tests.
Architecture review: Retry transient failures and Circuit breaker behavior. Requirement A: An application sends one request and crashes on transient 429 and 503 responses during scale events. Requirement B: A downstream service stays unhealthy and unlimited client retries exhaust all front-end worker threads. Which complete two-part proposal satisfies both constraints?
For requirement A, transient-failure handling reduces unnecessary outages while preventing retry storms. For requirement B, circuit breakers stop futile downstream calls temporarily and permit controlled re-entry. Verify both independently: A simulated 503 triggers spaced retries and a successful response without duplicate writes; Unhealthy requests fail quickly and the service resumes calls after recovery.
Both proposed halves address other use cases: App Service zone redundancy and Front Door global failover. The requested pair is Retry transient failures and Circuit breaker behavior.
One action is correct. The other targets Front Door global failover, leaving Circuit breaker behavior unsolved. Its necessary action is: Use an application circuit breaker with timeout and recovery probing.
The first step implements App Service zone redundancy instead of Retry transient failures. The necessary change is to implement bounded exponential backoff retries with jitter and idempotency protections.
Architecture review: Hub-spoke topology and Private inbound App Service. Requirement A: Many app VNets need shared DNS firewall and on-prem connectivity without each owning a gateway. 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, a hub centralizes connectivity services while spoke VNets isolate applications. For requirement B, private endpoints provide a private inbound path for supported App Service access. Verify both independently: A spoke accesses approved hub services and another spoke only through authorized routing; Corporate users connect using private DNS and public clients are rejected.
A hub centralizes connectivity services while spoke VNets isolate applications. Private endpoints provide a private inbound path for supported App Service access. The proposed steps (evaluate Azure Virtual WAN secured virtual hubs and routing intent; attach a NAT Gateway to the worker subnet with the approved public IP resources) address other capabilities instead of this required pair.
The first step implements Virtual WAN global hubs instead of Hub-spoke topology. The necessary change is to use a hub-and-spoke network topology with shared service governance.
The option covers one requirement but substitutes NAT Gateway outbound for Private inbound App Service. The missing acceptance result is: Corporate users connect using private DNS and public clients are rejected.
The design team completed work on SQL serverless idle cost. Its governing requirement was: A dev/test SQL database is idle for long periods but bursts during a short daily test window. Identify the conclusive verification result.
Serverless compute can scale usage and pause eligible databases to reduce idle cost. Confirm using the measurable result: Compute charges drop during idle periods and the test workload resumes within tolerated delay.
Ledger records cryptographically verifiable tamper-evidence for supported relational tables. The SQL ledger immutability test checks verification detects an altered historical ledger record during an audit; the relevant outcome is Compute charges drop during idle periods and the test workload resumes within tolerated delay.
Always Encrypted supports encryption and decryption in capable clients to reduce exposure to the database engine. The offered observation would demonstrate SQL Always Encrypted: The client retrieves authorized plaintext while a privileged server-side query sees encrypted values. The current validation is different: Compute charges drop during idle periods and the test workload resumes within tolerated delay.
Active geo-replication creates readable asynchronously updated secondary databases while primary remains writable. The distinguishing check is: Compute charges drop during idle periods and the test workload resumes within tolerated delay.
For NSG subnet filtering, operations are closing a change that addressed: A team must restrict a VM subnet to TCP 443 from a management prefix without deploying a full firewall. Which post-change signal belongs in the acceptance record?
NSGs provide stateful Layer 3/4 access rules rather than application-layer inspection. Confirm using the measurable result: The approved source reaches TCP 443 and another source is denied.
A hub centralizes connectivity services while spoke VNets isolate applications. The offered observation would demonstrate Hub-spoke topology: A spoke accesses approved hub services and another spoke only through authorized routing. The current validation is different: The approved source reaches TCP 443 and another source is denied.
VNet integration is principally an outbound feature; inbound private access requires other controls. Those observations validate VNet integration App Service. They do not establish the required NSG subnet filtering result: The approved source reaches TCP 443 and another source is denied.
Azure Load Balancer routes Layer 4 traffic inside a VNet without parsing HTTP URLs. The distinguishing check is: The approved source reaches TCP 443 and another source is denied.
A workflow waits hours between steps while retaining orchestration state through restarts. An architecture board will approve a solution only if this outcome is demonstrated: A resumed orchestration continues from saved state after a worker restart. What should be selected?
Durable Functions manages stateful workflows over serverless function executions. The selected architecture is use Durable Functions orchestration with proper idempotent activity design; confirm the result by checking that a resumed orchestration continues from saved state after a worker restart.
Confidential VMs use hardware-backed protection for sensitive guest execution environments. It does not solve the specified Azure Functions durable workflow condition.
General-purpose VMs balance CPU and memory while retaining OS-level control. Its design target is General purpose VM. The stated requirement instead concerns: A workflow waits hours between steps while retaining orchestration state through restarts.
GPU instances provide accelerators not present on standard CPU-only VMs. The relevant requirement is: A workflow waits hours between steps while retaining orchestration state through restarts.
Architecture review: Graceful scale-in and Zone-redundant load balancer. Requirement A: A stateless API behind a load balancer loses in-flight requests when autoscale removes instances mid-response. Requirement B: A regional application needs one L4 frontend distributing traffic to healthy VMs across zones. Which complete two-part proposal satisfies both constraints?
For requirement A, graceful scale-in lets existing requests finish while the removed instance stops taking new traffic. For requirement B, load Balancer routes TCP/UDP flows to healthy backends without terminating HTTP requests. Verify both independently: The scale-in test completes active requests while newly arriving calls use surviving workers; Failed backend probes remove one instance and healthy zonal instances continue serving.
The mismatched half is Retry transient failures; Zone-redundant load balancer instead needs: Use a supported zone-redundant Standard Load Balancer deployment with health probes.
This combines PostgreSQL zone redundant HA and Retry transient failures, which do not satisfy the distinct requirements for Graceful scale-in and Zone-redundant load balancer.
The option covers one requirement but substitutes PostgreSQL zone redundant HA for Graceful scale-in. The missing acceptance result is: The scale-in test completes active requests while newly arriving calls use surviving workers.
The acceptance criterion for SQL compute scaling comes from this issue: A database must grow compute during a seasonal sales period but not during idle months. Which measured outcome is the strongest proof?
Managed SQL compute tiers can scale resources but scaling may have operational consequences. Confirm using the measurable result: A scheduled scale-up meets throughput and a later scale-down reduces cost.
Read-only replicas can offload reporting from the primary where the tier provides the capability. The SQL read scaling test checks reporting connections route to a readable replica while transactions remain on primary; the relevant outcome is A scheduled scale-up meets throughput and a later scale-down reduces cost.
Hyperscale decouples storage scale from compute and supports large database sizes. The offered observation would demonstrate SQL Hyperscale growth: A growth test reaches the required storage target with the expected compute and backup architecture. The current validation is different: A scheduled scale-up meets throughput and a later scale-down reduces cost.
Partition elimination and aligned indexes can reduce scans when predicates match partition keys. Those observations validate SQL database partitioning. They do not establish the required SQL compute scaling result: A scheduled scale-up meets throughput and a later scale-down reduces cost.
Please check your mailbox for a message from support@examlabs.com and follow the directions.