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
The acceptance criterion for Policy exclusion scope comes from this issue: One application needs a carefully controlled exception to a management group policy. Which measured outcome is the strongest proof?
Policy scope and exclusions should be the smallest feasible exception rather than removing global guardrails. Confirm using the measurable result: Only the approved application scope avoids the specified policy effect.
Custom role actions can grant specific management operations without broad Contributor rights. The RBAC custom role test checks the operator restarts an approved service and cannot modify resource access assignments; the relevant outcome is Only the approved application scope avoids the specified policy effect.
Workbooks provide interactive analytical reports rather than the policy enforcement mechanism itself. The offered observation would demonstrate Managed governance dashboards: An auditor filters noncompliant resources by subscription and policy assignment. The current validation is different: Only the approved application scope avoids the specified policy effect.
Defender for Cloud aggregates recommendations and compliance state for supported frameworks. Those observations validate Defender compliance. They do not establish the required Policy exclusion scope result: Only the approved application scope avoids the specified policy effect.
A regional Azure platform incident affects databases but project teams have no subscription-specific warning. The acceptance test is: A platform health incident produces the configured subscription-scoped notification. Which design recommendation best satisfies both?
Service Health reports Azure platform incidents and planned maintenance relevant to a subscription. The selected architecture is create Service Health alerts scoped to affected subscriptions and services; confirm the result by checking that a platform health incident produces the configured subscription-scoped notification.
DCRs specify collected streams destinations and transformations for supported agent sources. The relevant requirement is: A regional Azure platform incident affects databases but project teams have no subscription-specific warning.
A log search alert can evaluate aggregated matching records instead of only raw metric time series. It does not solve the specified Azure service health condition.
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 regional Azure platform incident affects databases but project teams have no subscription-specific warning.
Architecture review: Logic Apps connector workflow and Durable Functions orchestration. Requirement A: A business process requires approvals plus connectors for Microsoft 365 and a SaaS ticketing system. Requirement B: A serverless order process needs retries and persisted orchestration across multiple long-running steps. Which complete two-part proposal satisfies both constraints?
For requirement A, logic Apps offers managed integration workflows and prebuilt service connectors. For requirement B, durable orchestrations checkpoint progress and coordinate stateful serverless workflows. Verify both independently: An approved request creates the expected ticket and notifies the right mailbox; Restarting a worker does not restart already completed business steps.
Both proposed halves address other use cases: API Management gateway and Event Hubs telemetry. The requested pair is Logic Apps connector workflow and Durable Functions orchestration.
The mismatched half is Event Hubs telemetry; Durable Functions orchestration instead needs: Choose Durable Functions with explicit orchestrator and activity functions.
The first step implements API Management gateway instead of Logic Apps connector workflow. The necessary change is to choose Logic Apps workflows with supported connector authentication.
A publicly reachable application needs additional DDoS mitigation beyond basic platform protections. The acceptance test is: Protection coverage reports the eligible public IP and test telemetry is available. Which design recommendation best satisfies both?
DDoS protection adds adaptive mitigation and telemetry for supported public resources. The selected architecture is evaluate Azure DDoS Network Protection for eligible public IPs and VNets; confirm the result by checking that protection coverage reports the eligible public IP and test telemetry is available.
Azure Load Balancer routes Layer 4 traffic inside a VNet without parsing HTTP URLs. It does not solve the specified DDoS protection condition.
A hub centralizes connectivity services while spoke VNets isolate applications. The relevant requirement is: A publicly reachable application needs additional DDoS mitigation beyond basic platform protections.
Route Server enables BGP exchange with NVAs without custom per-prefix UDR maintenance. The current need is: A publicly reachable application needs additional DDoS mitigation beyond basic platform protections.
A scaled-out web app stores user sessions on individual workers and loses sessions on failover. An architecture board will approve a solution only if this outcome is demonstrated: The user session persists after a web worker is intentionally removed. What should be selected?
Shared session state survives an individual stateless app worker replacement. The selected architecture is move session state to a shared Azure Redis-compatible cache or durable store; confirm the result by checking that the user session persists after a web worker is intentionally removed.
Failure handling isolates unhealthy dependencies and avoids request pileups. Its design target is Application resilience timeout. The stated requirement instead concerns: A scaled-out web app stores user sessions on individual workers and loses sessions on failover.
Application Gateway provides application-aware path routing rather than basic L4 forwarding. It does not solve the specified Azure Cache for Redis session condition.
Central secret retrieval separates sensitive credentials from source and build artifacts. The current need is: A scaled-out web app stores user sessions on individual workers and loses sessions on failover.
The design team completed work on Cosmos multi-write availability. Its governing requirement was: A global application must continue accepting writes from multiple regions when one region fails. Identify the conclusive verification result.
Multi-region writes allow eligible regions to accept writes but require handling conflicts. Confirm using the measurable result: After one region becomes unavailable another authorized region continues to accept writes.
Availability sets spread VM instances across host-related fault and update domains within a datacenter. Those observations validate Availability set. They do not establish the required Cosmos multi-write availability result: After one region becomes unavailable another authorized region continues to accept writes.
Availability zones isolate infrastructure failure domains within an enabled region. The distinguishing check is: After one region becomes unavailable another authorized region continues to accept writes.
Load Balancer routes TCP/UDP flows to healthy backends without terminating HTTP requests. The Zone-redundant load balancer test checks failed backend probes remove one instance and healthy zonal instances continue serving; the relevant outcome is After one region becomes unavailable another authorized region continues to accept writes.
Architecture review: Private observability and Agent collection rules. Requirement A: A regulated environment must ingest monitoring data from isolated private networks without exposing public workspace ingestion endpoints. Requirement B: Windows servers send performance counters that should differ by workload and environment. Which complete two-part proposal satisfies both constraints?
For requirement A, AMPLS provides private connectivity to supported Azure Monitor ingestion and query endpoints. For requirement B, dCRs specify collected streams destinations and transformations for supported agent sources. Verify both independently: Monitoring ingestion succeeds using private DNS resolution while public network access is restricted; Production servers send approved counters while test servers omit the excluded stream.
One action is correct. The other targets VM resource health, leaving Private observability unsolved. Its necessary action is: Use Azure Monitor Private Link Scope with supported private endpoints and DNS integration.
The mismatched half is Automated diagnostics policy; Agent collection rules instead needs: Use Azure Monitor Agent data collection rules targeted through data collection rule associations.
This combines VM resource health and Automated diagnostics policy, which do not satisfy the distinct requirements for Private observability and Agent collection rules.
Architecture review: Multifactor critical operations and Backup soft delete. Requirement A: Ransomware attackers should not disable backup protection with a single compromised admin account. Requirement B: An operator deletes a backup item by mistake and must recover its protected points before permanent purge. Which complete two-part proposal satisfies both constraints?
For requirement A, multi-user authorization separates approval boundaries for critical backup changes. For requirement B, soft delete retains recoverable protected backup data after deletion for a configured interval. Verify both independently: A destructive backup operation requires the independent authorized role; The deleted item is recoverable within the protected deletion window.
Soft delete retains recoverable protected backup data after deletion for a configured interval. The other proposed action (define re-protection, replication reversal, and tested failback procedures in the DR runbook) does not implement the first control. Multi-user authorization separates approval boundaries for critical backup changes.
Multi-user authorization separates approval boundaries for critical backup changes. The other proposed action (use application-consistent backup or coordinated snapshot mechanisms rather than uncoordinated disk copies) addresses a different operation. Soft delete retains recoverable protected backup data after deletion for a configured interval.
Both proposed halves address other use cases: Failback after recovery and Disk snapshot consistency. The requested pair is Multifactor critical operations and Backup soft delete.
A critical object store needs zone resilience in primary and a regional recovery copy. An engineer must deliver the following acceptance evidence: A regional recovery plan uses the secondary while zonal faults leave primary available. What design choice is defensible?
GZRS synchronously spreads primary copies across zones and asynchronously replicates to another region. The selected architecture is select GZRS or RA-GZRS based on read access needs and service support; confirm the result by checking that a regional recovery plan uses the secondary while zonal faults leave primary available.
Zone redundancy spreads eligible database availability replicas across zones. It does not solve the specified Blob GZRS durability condition.
Circuit breakers stop futile downstream calls temporarily and permit controlled re-entry. The relevant requirement is: A critical object store needs zone resilience in primary and a regional recovery copy.
Application Gateway offers L7 proxy capabilities with WAF unlike a basic L4 load balancer. That is useful for Application Gateway zone redundancy (A web workload requires HTTP routing and WAF across availability zones). It does not meet the current Blob GZRS durability requirement: A critical object store needs zone resilience in primary and a regional recovery copy.
A healthcare workload requires confidential computing protections during in-use processing. The acceptance test is: Guest attestation and encryption state meet the confidential VM policy. Which design recommendation best satisfies both?
Confidential VMs use hardware-backed protection for sensitive guest execution environments. The selected architecture is choose eligible Azure confidential VMs with supported confidential-computing features; confirm the result by checking that guest attestation and encryption state meet the confidential VM policy.
VMSS automates management and scaling of similar VMs in the same workload. It does not solve the specified Confidential VM condition.
Blue-green deployment preserves a prior known-good instance while testing a replacement. That is useful for App deployment blue-green (A mission-critical API needs a low-risk deployment with rapid rollback of application code). It does not meet the current Confidential VM requirement: A healthcare workload requires confidential computing protections during in-use processing.
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 healthcare workload requires confidential computing protections during in-use processing.
The design team completed work on Role assignment scope. Its governing requirement was: An engineer only operates one network resource group but has Contributor for the whole subscription. Identify the conclusive verification result.
RBAC assignments inherit downward so narrower scope reduces unintended changes. Confirm using the measurable result: The engineer can change the assigned network group but not another group's resources.
Subscriptions are billing and resource governance boundaries with independent quotas and RBAC assignment scopes. Those observations validate Subscription isolation. They do not establish the required Role assignment scope result: The engineer can change the assigned network group but not another group's resources.
Defender for Cloud aggregates recommendations and compliance state for supported frameworks. The Defender compliance test checks a noncompliant resource is reported under the relevant regulatory control; the relevant outcome is The engineer can change the assigned network group but not another group's resources.
DeployIfNotExists requires remediation for already deployed resources where appropriate. The offered observation would demonstrate Policy remediation: The noncompliant existing resources receive the required settings without manual per-resource editing. The current validation is different: 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.