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
Architecture review: CPU threshold alerts and Dynamic baseline alerts. Requirement A: A fleet needs immediate warning when sustained processor utilization exceeds its target without reading logs manually. Requirement B: A seasonal workload has normal daily peaks and a fixed metric threshold floods the alert queue. Which complete two-part proposal satisfies both constraints?
For requirement A, metrics are low-latency numeric series and alert evaluation can trigger actions independently of a log query. For requirement B, dynamic thresholds adapt alert boundaries to historical metric patterns after sufficient data exists. Verify both independently: A simulated sustained high-CPU period fires the metric alert and notifies the on-call team; The routine daily spike is tolerated while an atypical surge creates an actionable alert.
The option covers one requirement but substitutes Cross-tenant operations for Dynamic baseline alerts. The missing acceptance result is: The routine daily spike is tolerated while an atypical surge creates an actionable alert.
Dynamic thresholds adapt alert boundaries to historical metric patterns after sufficient data exists. The other proposed action (enable Azure Monitor managed service for Prometheus for supported Kubernetes clusters) does not implement the first control. Metrics are low-latency numeric series and alert evaluation can trigger actions independently of a log query.
This combines Managed Prometheus and Cross-tenant operations, which do not satisfy the distinct requirements for CPU threshold alerts and Dynamic baseline alerts.
A latency-sensitive enterprise app needs high-throughput shared NFS volumes with managed storage. Choose the architecture that can be validated by this result: An authorized NFS client mounts the volume with required throughput.
NetApp Files offers enterprise file protocols and performance controls for supported workloads. The selected architecture is evaluate Azure NetApp Files capacity pools and volume service levels; confirm the result by checking that an authorized NFS client mounts the volume with required throughput.
Concurrent writes require a conflict resolution policy to prevent unintended last-writer outcomes. That is useful for Cosmos conflict handling (A multi-write-region Cosmos account can update the same logical item concurrently). It does not meet the current Azure NetApp Files requirement: A latency-sensitive enterprise app needs high-throughput shared NFS volumes with managed storage.
Soft delete retains recoverable deleted objects or containers during the configured period. Its design target is Blob soft delete. The stated requirement instead concerns: A latency-sensitive enterprise app needs high-throughput shared NFS volumes with managed storage.
Bounded staleness constrains replication read lag according to allowed versions/time. It does not solve the specified Azure NetApp Files condition.
An internet-facing API gateway must call a private service not directly exposed to the internet. Which Azure architecture would most directly achieve the required result: External callers only reach the backend through the controlled APIM endpoint?
An API gateway can broker external requests to private backends without direct public backend access. The selected architecture is use an APIM networking tier/mode and private backend connectivity supported by the chosen plan; confirm the result by checking that external callers only reach the backend through the controlled APIM endpoint.
Shared session state survives an individual stateless app worker replacement. Its design target is Azure Cache for Redis session. The stated requirement instead concerns: An internet-facing API gateway must call a private service not directly exposed to the internet.
Failure handling isolates unhealthy dependencies and avoids request pileups. It does not solve the specified API private backends condition.
Event Hubs provides a replayable ordered stream within partitions for large event volumes. That is useful for Event Hubs telemetry (Thousands of kiosks upload constant high-volume telemetry that several analytic consumers replay). It does not meet the current API private backends requirement: An internet-facing API gateway must call a private service not directly exposed to the internet.
A mission-critical API needs a low-risk deployment with rapid rollback of application code. A deployment must satisfy this operational criterion: A failed health check returns traffic to the prior application version. Which plan is appropriate?
Blue-green deployment preserves a prior known-good instance while testing a replacement. The selected architecture is use App Service deployment slots or equivalent supported blue-green routing; confirm the result by checking that a failed health check returns traffic to the prior application version.
App Service manages web hosting and supports deployment slots on eligible plans. The relevant requirement is: A mission-critical API needs a low-risk deployment with rapid rollback of application code.
Azure Batch schedules large-scale parallel workloads across managed compute pools. It does not solve the specified App deployment blue-green condition.
Durable Functions manages stateful workflows over serverless function executions. That is useful for Azure Functions durable workflow (A workflow waits hours between steps while retaining orchestration state through restarts). It does not meet the current App deployment blue-green requirement: A mission-critical API needs a low-risk deployment with rapid rollback of application code.
A solution must address both VM scale set autoscaling and Graceful scale-in. First requirement: Demand for a stateless API swings by 10x and manual provisioning causes downtime. Second requirement: A stateless API behind a load balancer loses in-flight requests when autoscale removes instances mid-response. Select TWO recommendations that meet these independent needs.
For the Graceful scale-in half of this design, graceful scale-in lets existing requests finish while the removed instance stops taking new traffic. Check: The scale-in test completes active requests while newly arriving calls use surviving workers. The other half concerns VM scale set autoscaling.
For the VM scale set autoscaling half of this two-part design, VMSS can add or remove similarly configured VM instances based on supported signals. Verify: Traffic spikes scale instances out and scale-in does not lose persistent session state. The other half concerns Graceful scale-in.
A zone-separated standby supports automated failover where offered. The corresponding task is PostgreSQL zone redundant HA: A mission-critical PostgreSQL workload requires HA across zones within a region. It is not one of the two requested controls (VM scale set autoscaling and Graceful scale-in).
ZRS synchronously replicates data across primary-region zones. Its own validation would be: Reading and writing a test blob continues while one zone is unavailable. The current paired requirement is VM scale set autoscaling and Graceful scale-in.
Traffic Manager is DNS-based and clients connect directly to the returned service endpoint. The corresponding task is Traffic Manager DNS routing: A TCP application requires global endpoint selection using DNS without a global L7 reverse proxy. It is not one of the two requested controls (VM scale set autoscaling and Graceful scale-in).
The target environment adopts this approach for Reliable exactly-once effect: Design an idempotent handler using a durable business operation key. What property makes it suitable?
At-least-once message delivery requires application logic to deduplicate business side effects. It is material here because a retrying order processor may receive the same message multiple times and must avoid duplicate billing.
Failure handling isolates unhealthy dependencies and avoids request pileups. It belongs to Application resilience timeout. The stated architecture instead relies on: At-least-once message delivery requires application logic to deduplicate business side effects.
Edge content distribution can cache static resources near users. That statement describes CDN static content, while the question asks how Reliable exactly-once effect works: At-least-once message delivery requires application logic to deduplicate business side effects.
APIM can enforce per-client API consumption controls before requests reach backends. At-least-once message delivery requires application logic to deduplicate business side effects.
A single VM becomes unavailable but the Azure region itself is healthy. Identify the most suitable implementation for an outcome where the specific VM shows an unavailable health state while the regional Service Health feed remains normal.
Resource Health reports the platform-side availability history of individual Azure resources. The selected architecture is use Azure Resource Health and resource health alerts for the VM; confirm the result by checking that the specific VM shows an unavailable health state while the regional Service Health feed remains normal.
Dynamic thresholds adapt alert boundaries to historical metric patterns after sufficient data exists. Its design target is Dynamic baseline alerts. The stated requirement instead concerns: A single VM becomes unavailable but the Azure region itself is healthy.
Resource diagnostic settings forward selected resource logs whereas subscription Activity Log tracks management operations. It does not solve the specified VM resource health condition.
Metrics are low-latency numeric series and alert evaluation can trigger actions independently of a log query. That is useful for CPU threshold alerts (A fleet needs immediate warning when sustained processor utilization exceeds its target without reading logs manually). It does not meet the current VM resource health requirement: A single VM becomes unavailable but the Azure region itself is healthy.
A business-critical vault should not be deleted during routine administration by contributors. Choose the architecture that can be validated by this result: A test deletion is denied while approved read and update actions remain available.
Locks prevent specified management operations even for users with broad Azure RBAC roles. The selected architecture is apply a CanNotDelete resource lock where operational impacts are understood; confirm the result by checking that a test deletion is denied while approved read and update actions remain available.
Policy exemptions record approved exceptions while the policy remains assigned. The relevant requirement is: A business-critical vault should not be deleted during routine administration by contributors.
Azure deployment what-if previews resource changes before applying a template. It does not solve the specified Resource locks condition.
Management groups supply governance scope above subscriptions without moving resources into a single subscription. Its design target is Management group hierarchy. The stated requirement instead concerns: A business-critical vault should not be deleted during routine administration by contributors.
The acceptance criterion for Resource RBAC versus data access comes from this issue: A user can view a storage account resource but cannot download its blobs. Which measured outcome is the strongest proof?
Management-plane Azure RBAC Reader does not automatically authorize blob data-plane reads. Confirm using the measurable result: The user downloads an approved blob without gaining storage management privileges.
Azure SQL supports Entra authentication and compatible managed identities can eliminate stored SQL secrets. Those observations validate Passwordless app connection. They do not establish the required Resource RBAC versus data access result: The user downloads an approved blob without gaining storage management privileges.
Key Vault secrets support controlled retrieval and rotation separate from packaged application code. The distinguishing check is: The user downloads an approved blob without gaining storage management privileges.
Key Vault RBAC data permissions differ from vault resource-management permissions. The offered observation would demonstrate Vault RBAC least privilege: The user retrieves authorized secret values but cannot alter vault access configuration. The current validation is different: The user downloads an approved blob without gaining storage management privileges.
Architecture review: Automated diagnostics policy and Control-plane audit. Requirement A: New storage accounts across many subscriptions often appear with no diagnostic configuration. Requirement B: A tenant auditor needs subscription-level records for resource create and delete operations, not VM guest logs. Which complete two-part proposal satisfies both constraints?
For requirement A, deployIfNotExists can evaluate related configurations and deploy missing compliant resources with appropriate permissions. For requirement B, the Activity Log records Azure Resource Manager control-plane events independent of guest agents. Verify both independently: A newly provisioned supported storage account gets the intended diagnostics after policy remediation; A denied deployment and a successful resource deletion appear with caller and operation name.
One action is correct. The other targets Private observability, leaving Automated diagnostics policy unsolved. Its necessary action is: Use Azure Policy deployIfNotExists with remediation identity for supported diagnostic settings.
DeployIfNotExists can evaluate related configurations and deploy missing compliant resources with appropriate permissions. The Activity Log records Azure Resource Manager control-plane events independent of guest agents. The proposed steps (use Azure Monitor Private Link Scope with supported private endpoints and DNS integration; route supported platform diagnostic events to an Event Hubs namespace) address other capabilities instead of this required pair.
The option covers one requirement but substitutes Security-event streaming for Control-plane audit. The missing acceptance result is: A denied deployment and a successful resource deletion appear with caller and operation name.
A proposed solution for SQL serverless idle cost is: Consider Azure SQL Database serverless compute with auto-pause eligibility checks. Select the strongest statement supporting the recommendation.
Serverless compute can scale usage and pause eligible databases to reduce idle cost. It is material here because a dev/test SQL database is idle for long periods but bursts during a short daily test window.
Ledger records cryptographically verifiable tamper-evidence for supported relational tables. Serverless compute can scale usage and pause eligible databases to reduce idle cost.
Always Encrypted supports encryption and decryption in capable clients to reduce exposure to the database engine. Serverless compute can scale usage and pause eligible databases to reduce idle cost.
Active geo-replication creates readable asynchronously updated secondary databases while primary remains writable. It belongs to SQL geo-replication reporting. The stated architecture instead relies on: Serverless compute can scale usage and pause eligible databases to reduce idle cost.
Please check your mailbox for a message from support@examlabs.com and follow the directions.