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 Recovery drill governance comes from this issue: Auditors require evidence that a disaster recovery plan works without disrupting production traffic. Which measured outcome is the strongest proof?
A non-disruptive DR test validates recovery sequences and dependencies before a real disaster. Confirm using the measurable result: The test network runs recovered workloads and production endpoints remain unaffected.
Multi-user authorization separates approval boundaries for critical backup changes. Those observations validate Multifactor critical operations. They do not establish the required Recovery drill governance result: The test network runs recovered workloads and production endpoints remain unaffected.
RPO measures the maximum tolerated data loss period at a recovery point. The distinguishing check is: The test network runs recovered workloads and production endpoints remain unaffected.
Immutable backup settings can prevent specified destructive operations against protected backups. The Vault immutability test checks a forbidden backup deletion or retention reduction is rejected during the configured protection period; the relevant outcome is The test network runs recovered workloads and production endpoints remain unaffected.
Architecture review: SQL read scaling and PostgreSQL read replica. Requirement A: An online retailer has heavy read-only reporting queries that interfere with its primary transactional database. Requirement B: An application uses PostgreSQL for writes but analysts overload the writer with complex read-only reports. Which complete two-part proposal satisfies both constraints?
For requirement A, read-only replicas can offload reporting from the primary where the tier provides the capability. For requirement B, read replicas offload eligible read-only queries but are asynchronously updated from the writer. Verify both independently: Reporting connections route to a readable replica while transactions remain on primary; The reports run on a replica while primary transaction performance improves.
One action is correct. The other targets SQL managed instance compatibility, leaving PostgreSQL read replica unsolved. Its necessary action is: Add supported PostgreSQL Flexible Server read replicas with suitable replication-lag expectations.
The first step implements SQL geo-replication reporting instead of SQL read scaling. The necessary change is to use supported SQL read scale-out replicas or a compatible reporting architecture.
Both proposed halves address other use cases: SQL geo-replication reporting and SQL managed instance compatibility. The requested pair is SQL read scaling and PostgreSQL read replica.
Users report failed checkout requests across a multi-tier web app and only CPU graphs are available. Which Azure architecture would most directly achieve the required result: A failed transaction trace identifies its failing dependency and correlated exception?
Application Insights correlates application requests exceptions and downstream dependencies rather than relying only on infrastructure CPU. The selected architecture is instrument the app with Application Insights request and dependency telemetry; confirm the result by checking that a failed transaction trace identifies its failing dependency and correlated exception.
The Activity Log records Azure Resource Manager control-plane events independent of guest agents. It does not solve the specified Web transaction traces condition.
A log search alert can evaluate aggregated matching records instead of only raw metric time series. The current need is: Users report failed checkout requests across a multi-tier web app and only CPU graphs are available.
Action groups define notifications and automated responses and can be reused by alert rules. That is useful for Notification routing (Critical infrastructure alerts need pager escalation while routine capacity warnings go only to email). It does not meet the current Web transaction traces requirement: Users report failed checkout requests across a multi-tier web app and only CPU graphs are available.
A customer portal must read its own updates while accepting that other users may briefly see stale writes. An engineer must deliver the following acceptance evidence: The writing session immediately reads its own update while other sessions may lag. What design choice is defensible?
Session consistency offers read-your-writes within a session without strong global consistency. The selected architecture is use Cosmos DB session consistency with proper session token handling; confirm the result by checking that the writing session immediately reads its own update while other sessions may lag.
Soft delete retains recoverable deleted objects or containers during the configured period. The relevant requirement is: A customer portal must read its own updates while accepting that other users may briefly see stale writes.
Azure Files provides managed SMB file shares whereas Blob Storage is object-oriented. It does not solve the specified Cosmos session consistency condition.
Service endpoints secure selected Azure service traffic from VNets but do not create a private IP for the PaaS service. Its design target is Storage service endpoints. The stated requirement instead concerns: A customer portal must read its own updates while accepting that other users may briefly see stale writes.
A solution must address both SQL failover groups HA and Azure SQL zone redundancy. First requirement: The database service must recover a read/write endpoint when the primary Azure region fails. Second requirement: A transactional SQL database must withstand a full zone failure with minimal manual intervention. Select TWO recommendations that meet these independent needs.
For the SQL failover groups HA half of this two-part design, failover-group listeners abstract the primary location during regional failover. Verify: The app reconnects after an orchestrated failover without endpoint edits. The other half concerns Azure SQL zone redundancy.
For the Azure SQL zone redundancy half of this design, zone redundancy spreads eligible database availability replicas across zones. Check: A zone failure does not permanently interrupt application database access. The other half concerns SQL failover groups HA.
Transient-failure handling reduces unnecessary outages while preventing retry storms. Its own validation would be: A simulated 503 triggers spaced retries and a successful response without duplicate writes. The current paired requirement is SQL failover groups HA and Azure SQL zone redundancy.
Traffic Manager is DNS-based and clients connect directly to the returned service endpoint. This alternative solves Traffic Manager DNS routing, while the question separately requires SQL failover groups HA and Azure SQL zone redundancy.
PDBs constrain voluntary disruptions but do not prevent all involuntary failures. The corresponding task is AKS pod disruption budget: Cluster upgrades evict all replicas of an API despite multiple healthy nodes. It is not one of the two requested controls (SQL failover groups HA and Azure SQL zone redundancy).
A globally distributed document API needs local low-latency reads near users in multiple regions. Identify the most suitable implementation for an outcome where read latency declines for remote users while sessions observe selected consistency.
Read regions bring replicas closer to users without inherently adding multi-write semantics. The selected architecture is add appropriate Cosmos DB read regions and choose the fitting consistency level; confirm the result by checking that read latency declines for remote users while sessions observe selected consistency.
VMSS can add or remove similarly configured VM instances based on supported signals. Its design target is VM scale set autoscaling. The stated requirement instead concerns: A globally distributed document API needs local low-latency reads near users in multiple regions.
Fault injection tests whether resilience patterns work under realistic failure conditions. It does not solve the specified Cosmos multi-region reads condition.
PDBs constrain voluntary disruptions but do not prevent all involuntary failures. The current need is: A globally distributed document API needs local low-latency reads near users in multiple regions.
A regional help desk should manage only user accounts in its country without becoming tenant-wide admin. An architecture board will approve a solution only if this outcome is demonstrated: The regional admin can reset an assigned user's password but cannot administer an out-of-scope user. What should be selected?
Administrative units scope eligible directory management roles to selected objects, not data visibility. The selected architecture is create appropriately scoped administrative units and assign suitable delegated Entra administrative roles; confirm the result by checking that the regional admin can reset an assigned user's password but cannot administer an out-of-scope user.
Key Vault secrets support controlled retrieval and rotation separate from packaged application code. The relevant requirement is: A regional help desk should manage only user accounts in its country without becoming tenant-wide admin.
Azure SQL supports Entra authentication and compatible managed identities can eliminate stored SQL secrets. It does not solve the specified Delegation with admin units condition.
Data-plane roles control access to blob content and least-scope assignment reduces unnecessary privileges. That is useful for Managed-identity scope (A workload requires write access to one blob container but must not inherit owner rights over the subscription). It does not meet the current Delegation with admin units requirement: A regional help desk should manage only user accounts in its country without becoming tenant-wide admin.
The acceptance criterion for API private backends comes from this issue: An internet-facing API gateway must call a private service not directly exposed to the internet. Which measured outcome is the strongest proof?
An API gateway can broker external requests to private backends without direct public backend access. Confirm using the measurable result: External callers only reach the backend through the controlled APIM endpoint.
APIM applies gateway policies authentication mediation throttling and API lifecycle controls. The offered observation would demonstrate API Management gateway: An expired subscription key fails while an authorized request routes to the correct version. The current validation is different: External callers only reach the backend through the controlled APIM endpoint.
App Configuration centralizes feature settings; secrets should remain in Key Vault. The distinguishing check is: External callers only reach the backend through the controlled APIM endpoint.
Web PubSub provides managed WebSocket connection fan-out so application servers need not hold all client sessions. The Web PubSub real time test checks two connected clients immediately receive the authorized published event; the relevant outcome is External callers only reach the backend through the controlled APIM endpoint.
For the External B2B partner requirement, the proposed architecture uses: Use Microsoft Entra B2B collaboration with scoped application access and appropriate external identities policy. Why does that design fit?
B2B collaboration supports guest principals and cross-organization access controls. It is material here because a supplier must access a specific application without becoming an employee in the home tenant.
Key Vault certificates support managed lifecycle and distribution to compatible Azure integrations. B2B collaboration supports guest principals and cross-organization access controls.
Managed identities provide Entra tokens to supported workloads while data-plane RBAC grants the actual blob permissions. It belongs to Managed identity for App Service. The stated architecture instead relies on: B2B collaboration supports guest principals and cross-organization access controls.
Secure secret handling removes reusable credentials from source while preserving automation. That statement describes Secrets in deployment pipeline, while the question asks how External B2B partner works: B2B collaboration supports guest principals and cross-organization access controls.
Architecture rationale review—Backup private endpoints: Use approved private endpoint configuration for the supported backup scenario. Which explanation accurately distinguishes this capability?
Backup private connectivity has service and workload prerequisites distinct from ordinary storage private endpoints. It is material here because backup workloads in restricted networks must avoid general public service access where supported.
RTO is the maximum acceptable restoration duration, not the amount of lost data. It belongs to Recovery time objective. The stated architecture instead relies on: Backup private connectivity has service and workload prerequisites distinct from ordinary storage private endpoints.
Blob operational backup relies on point-in-time object protection features rather than VM-level backups. Backup private connectivity has service and workload prerequisites distinct from ordinary storage private endpoints.
Periodic backups produce interval snapshots and are not the same as continuous point-in-time recovery. Backup private connectivity has service and workload prerequisites distinct from ordinary storage private endpoints.
The Policy audit versus deny review proposes: Roll out an Azure Policy rule initially with audit then switch to deny after remediation. Which Azure behavior is the technical justification for this decision?
Audit effects collect compliance findings without blocking resource creation. It is material here because the platform team needs to measure the impact of a new restriction before blocking deployments.
Management groups supply governance scope above subscriptions without moving resources into a single subscription. That statement describes Management group hierarchy, while the question asks how Policy audit versus deny works: Audit effects collect compliance findings without blocking resource creation.
Modify effects can update eligible metadata and require the required remediation permissions. Audit effects collect compliance findings without blocking resource creation.
Defender for Cloud aggregates recommendations and compliance state for supported frameworks. It belongs to Defender compliance. The stated architecture instead relies on: Audit effects collect compliance findings without blocking resource creation.
Please check your mailbox for a message from support@examlabs.com and follow the directions.