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
For SQL failover groups HA, operations are closing a change that addressed: The database service must recover a read/write endpoint when the primary Azure region fails. Which post-change signal belongs in the acceptance record?
Failover-group listeners abstract the primary location during regional failover. Confirm using the measurable result: The app reconnects after an orchestrated failover without endpoint edits.
Zone redundancy spreads eligible database availability replicas across zones. Those observations validate Azure SQL zone redundancy. They do not establish the required SQL failover groups HA result: The app reconnects after an orchestrated failover without endpoint edits.
A zone-separated standby supports automated failover where offered. The distinguishing check is: The app reconnects after an orchestrated failover without endpoint edits.
Multi-region writes allow eligible regions to accept writes but require handling conflicts. The Cosmos multi-write availability test checks after one region becomes unavailable another authorized region continues to accept writes; the relevant outcome is The app reconnects after an orchestrated failover without endpoint edits.
An architect must sign off on Site-to-site VPN. The business problem is: A small branch needs encrypted connectivity to a VNet over its existing internet link. What observed test result provides valid evidence?
VPN Gateway can establish encrypted IPsec tunnels over public networks. Confirm using the measurable result: Encrypted traffic reaches the approved private Azure subnet from the branch.
Point-to-site VPN authenticates individual clients for private network access. The Point-to-site VPN test checks authorized clients connect privately and revoked clients cannot establish a tunnel; the relevant outcome is Encrypted traffic reaches the approved private Azure subnet from the branch.
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: Encrypted traffic reaches the approved private Azure subnet from the branch.
Virtual WAN provides managed global transit architecture with integrated branch connectivity. Those observations validate Virtual WAN global hubs. They do not establish the required Site-to-site VPN result: Encrypted traffic reaches the approved private Azure subnet from the branch.
An autoscaling API needs several identical VMs during peak hours and only a few at night. Identify the most suitable implementation for an outcome where the scale set adds instances at load and returns to baseline under low demand.
VMSS automates management and scaling of similar VMs in the same workload. The selected architecture is use Virtual Machine Scale Sets with metric-based autoscale and stateless instances; confirm the result by checking that the scale set adds instances at load and returns to baseline under low demand.
Compute-optimized instances prioritize vCPU capacity over excess memory. Its design target is Compute optimized VM. The stated requirement instead concerns: An autoscaling API needs several identical VMs during peak hours and only a few at night.
App Service manages web hosting and supports deployment slots on eligible plans. The relevant requirement is: An autoscaling API needs several identical VMs during peak hours and only a few at night.
Functions supplies event-driven serverless execution with plan-specific scale and timeout limits. It does not solve the specified VMSS dynamic scaling condition.
A solution must address both Agent collection rules and VM guest performance. First requirement: Windows servers send performance counters that should differ by workload and environment. Second requirement: Server owners need guest memory and disk performance for VMs rather than only host-level platform metrics. Select TWO recommendations that meet these independent needs.
For the Agent collection rules half of this two-part design, dCRs specify collected streams destinations and transformations for supported agent sources. Verify: Production servers send approved counters while test servers omit the excluded stream. The other half concerns VM guest performance.
For the VM guest performance half of this design, VM insights and the agent collect supported guest operating-system counters and process data. Check: Per-VM guest memory and disk metrics appear with host identity in Azure Monitor. The other half concerns Agent collection rules.
WAF rule and access diagnostics identify rule IDs and request outcomes that aggregate health metrics miss. This alternative solves WAF decision logs, while the question separately requires Agent collection rules and VM guest performance.
Resource Health reports the platform-side availability history of individual Azure resources. Its own validation would be: The specific VM shows an unavailable health state while the regional Service Health feed remains normal. The current paired requirement is Agent collection rules and VM guest performance.
Metrics are low-latency numeric series and alert evaluation can trigger actions independently of a log query. This alternative solves CPU threshold alerts, while the question separately requires Agent collection rules and VM guest performance.
Architecture review: Blob inventory and Blob object storage. Requirement A: Operations needs a weekly manifest of millions of blobs with properties and access tiers. Requirement B: A media service stores millions of image and video objects accessed through REST without a shared file system. Which complete two-part proposal satisfies both constraints?
For requirement A, blob Inventory produces scheduled object inventories without crawling each object individually. For requirement B, Blob Storage manages massively scalable object data rather than SMB-compatible shared volumes. Verify both independently: The manifest lists the expected blob properties in the configured destination; A client uploads and downloads an object using its scoped authorization.
One action is correct. The other targets Azure Cache for Redis, leaving Blob inventory unsolved. Its necessary action is: Configure Azure Storage Blob Inventory reports.
The mismatched half is Cosmos session consistency; Blob object storage instead needs: Use Azure Blob Storage containers with lifecycle policies and scoped access.
This combines Azure Cache for Redis and Cosmos session consistency, which do not satisfy the distinct requirements for Blob inventory and Blob object storage.
A proposed solution for Dynamic baseline alerts is: Evaluate Azure Monitor dynamic threshold metric alerts for its established behavioral baseline. Select the strongest statement supporting the recommendation.
Dynamic thresholds adapt alert boundaries to historical metric patterns after sufficient data exists. It is material here because a seasonal workload has normal daily peaks and a fixed metric threshold floods the alert queue.
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: Dynamic thresholds adapt alert boundaries to historical metric patterns after sufficient data exists.
AMPLS provides private connectivity to supported Azure Monitor ingestion and query endpoints. That statement describes Private observability, while the question asks how Dynamic baseline alerts works: Dynamic thresholds adapt alert boundaries to historical metric patterns after sufficient data exists.
DCRs specify collected streams destinations and transformations for supported agent sources. Dynamic thresholds adapt alert boundaries to historical metric patterns after sufficient data exists.
The target environment adopts this approach for App Configuration feature flags: Store nonsecret feature flags in Azure App Configuration with app-side refresh. What property makes it suitable?
App Configuration centralizes feature settings; secrets should remain in Key Vault. It is material here because operators must turn a feature on for a pilot group without rebuilding application binaries.
Event Grid distributes discrete source events to configured subscribers. That statement describes Event Grid notification, while the question asks how App Configuration feature flags works: App Configuration centralizes feature settings; secrets should remain in Key Vault.
Front Door rule sets change eligible request and response behavior at the edge according to match conditions. App Configuration centralizes feature settings; secrets should remain in Key Vault.
Failure handling isolates unhealthy dependencies and avoids request pileups. App Configuration centralizes feature settings; secrets should remain in Key Vault.
Before approving SQL database monitoring, the reviewer assesses this requirement: DBAs need CPU, DTU/vCore, wait and query performance evidence before changing the tier. Which of the reported outcomes is decisive?
Query and resource telemetry helps distinguish costly queries from insufficient database compute. Confirm using the measurable result: Top resource-consuming queries and resource-limit events are visible during peak load.
Dynamic data masking limits exposure in query results but is not a substitute for database access control. The offered observation would demonstrate SQL dynamic data masking: Support queries return masked values while appropriately authorized principals can access underlying values. The current validation is different: Top resource-consuming queries and resource-limit events are visible during peak load.
Ledger records cryptographically verifiable tamper-evidence for supported relational tables. Those observations validate SQL ledger immutability. They do not establish the required SQL database monitoring result: Top resource-consuming queries and resource-limit events are visible during peak load.
Hyperscale decouples storage scale from compute and supports large database sizes. The distinguishing check is: Top resource-consuming queries and resource-limit events are visible during peak load.
A high-volume database allows little cutover downtime and must synchronize changes before switch. Identify the most suitable implementation for an outcome where source and target reconcile and final cutover falls within the tolerated outage.
Online migration reduces cutover downtime by applying ongoing changes after the baseline copy. The selected architecture is use a supported online migration approach with initial load and continuous changes; confirm the result by checking that source and target reconcile and final cutover falls within the tolerated outage.
Hidden dependencies can break after migration even when VM replication succeeds. The current need is: A high-volume database allows little cutover downtime and must synchronize changes before switch.
Parallel operation compares business outputs before committing the cutover. It does not solve the specified SQL online migration condition.
AzCopy provides scripted high-throughput online transfers with resumability. The relevant requirement is: A high-volume database allows little cutover downtime and must synchronize changes before switch.
A solution must address both CDN static content and Azure Front Door caching. First requirement: Marketing assets should be delivered from regional edge nodes instead of a central origin. Second requirement: A global website serves the same static assets to users on several continents. Select TWO recommendations that meet these independent needs.
For the Azure Front Door caching half of this design, edge caching reduces origin load and latency for eligible cacheable content. Check: A repeat request from a distant location is served from the edge cache. The other half concerns CDN static content.
For the CDN static content half of this two-part design, edge content distribution can cache static resources near users. Verify: Measured image latency decreases after the edge cache warms. The other half concerns Azure Front Door caching.
APIM applies gateway policies authentication mediation throttling and API lifecycle controls. That plan is appropriate for API Management gateway. The two controls sought here are CDN static content and Azure Front Door caching.
Application Gateway provides application-aware path routing rather than basic L4 forwarding. Its own validation would be: Requests to each path arrive at the correct healthy backend pool. The current paired requirement is CDN static content and Azure Front Door caching.
Event Hubs provides a replayable ordered stream within partitions for large event volumes. The corresponding task is Event Hubs telemetry: Thousands of kiosks upload constant high-volume telemetry that several analytic consumers replay. It is not one of the two requested controls (CDN static content and Azure Front Door caching).
Architecture review: Resource group lifecycle and Role assignment scope. Requirement A: Short-lived environments must be removed together without deleting shared platform services. 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, resource groups provide a deployment and management boundary and facilitate cohesive cleanup. For requirement B, RBAC assignments inherit downward so narrower scope reduces unintended changes. Verify both independently: Deleting an approved test resource group removes only the intended environment resources; The engineer can change the assigned network group but not another group's resources.
RBAC assignments inherit downward so narrower scope reduces unintended changes. The other proposed action (adopt a standardized resource naming and tagging strategy in landing-zone governance) does not implement the first control. Resource groups provide a deployment and management boundary and facilitate cohesive cleanup.
This combines Resource naming governance and Cost export, which do not satisfy the distinct requirements for Resource group lifecycle and Role assignment scope.
The option covers one requirement but substitutes Cost export for Role assignment scope. The missing acceptance result is: The engineer can change the assigned network group but not another group's resources.
Please check your mailbox for a message from support@examlabs.com and follow the directions.