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 target environment adopts this approach for VM maintenance handling: Distribute redundant VMs across appropriate zones or fault domains and use health-probed load balancing. What property makes it suitable?
Redundancy prevents a single host maintenance event from removing the only serving instance. It is material here because a VM-based API must survive scheduled host maintenance without customer-visible downtime.
VMSS automates management and scaling of similar VMs in the same workload. It belongs to VMSS dynamic scaling. The stated architecture instead relies on: Redundancy prevents a single host maintenance event from removing the only serving instance.
Queue-length scaling aligns worker count with pending work rather than idle CPU metrics. That statement describes Autoscaling based on queue, while the question asks how VM maintenance handling works: Redundancy prevents a single host maintenance event from removing the only serving instance.
Durable Functions manages stateful workflows over serverless function executions. Redundancy prevents a single host maintenance event from removing the only serving instance.
The design team completed work on Application Gateway path routing. Its governing requirement was: One regional HTTPS endpoint needs /api requests routed to API pods and /shop to a web tier. Identify the conclusive verification result.
Application Gateway provides application-aware path routing rather than basic L4 forwarding. Confirm using the measurable result: Requests to each path arrive at the correct healthy backend pool.
Queueing decouples front-end latency from downstream worker availability. The Queue asynchronous processing test checks checkout responds quickly and pending invoices process after the worker recovers; the relevant outcome is Requests to each path arrive at the correct healthy backend pool.
APIM can enforce per-client API consumption controls before requests reach backends. The offered observation would demonstrate APIM rate limiting: A burst beyond the quota is throttled while permitted traffic proceeds. The current validation is different: Requests to each path arrive at the correct healthy backend pool.
Central secret retrieval separates sensitive credentials from source and build artifacts. Those observations validate Key Vault app secrets. They do not establish the required Application Gateway path routing result: Requests to each path arrive at the correct healthy backend pool.
Architecture rationale review—Web PubSub real time: Use Azure Web PubSub with authenticated WebSocket clients and appropriate hub design. Which explanation accurately distinguishes this capability?
Web PubSub provides managed WebSocket connection fan-out so application servers need not hold all client sessions. It is material here because a collaboration app must send real-time server-to-client notifications to many concurrent browsers.
At-least-once message delivery requires application logic to deduplicate business side effects. That statement describes Reliable exactly-once effect, while the question asks how Web PubSub real time works: Web PubSub provides managed WebSocket connection fan-out so application servers need not hold all client sessions.
APIM applies gateway policies authentication mediation throttling and API lifecycle controls. Web PubSub provides managed WebSocket connection fan-out so application servers need not hold all client sessions.
Front Door rule sets change eligible request and response behavior at the edge according to match conditions. It belongs to Front Door rules engine. The stated architecture instead relies on: Web PubSub provides managed WebSocket connection fan-out so application servers need not hold all client sessions.
The team has justified its Web transaction traces design with: Instrument the app with Application Insights request and dependency telemetry. Which statement accurately describes why the approach works?
Application Insights correlates application requests exceptions and downstream dependencies rather than relying only on infrastructure CPU. It is material here because users report failed checkout requests across a multi-tier web app and only CPU graphs are available.
The Activity Log records Azure Resource Manager control-plane events independent of guest agents. Application Insights correlates application requests exceptions and downstream dependencies rather than relying only on infrastructure CPU.
A log search alert can evaluate aggregated matching records instead of only raw metric time series. It belongs to Log anomaly alert. The stated architecture instead relies on: Application Insights correlates application requests exceptions and downstream dependencies rather than relying only on infrastructure CPU.
Action groups define notifications and automated responses and can be reused by alert rules. That statement describes Notification routing, while the question asks how Web transaction traces works: Application Insights correlates application requests exceptions and downstream dependencies rather than relying only on infrastructure CPU.
A proposed solution for APIM rate limiting is: Configure API Management rate limiting or quota policies at the appropriate scope. Select the strongest statement supporting the recommendation.
APIM can enforce per-client API consumption controls before requests reach backends. It is material here because a popular API needs to reject excessive client requests without changing back-end services.
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.
Application Gateway provides application-aware path routing rather than basic L4 forwarding. That statement describes Application Gateway path routing, while the question asks how APIM rate limiting works: APIM can enforce per-client API consumption controls before requests reach backends.
App Configuration centralizes feature settings; secrets should remain in Key Vault. APIM can enforce per-client API consumption controls before requests reach backends.
Architecture review: Zone-redundant load balancer and App Service zone redundancy. Requirement A: A regional application needs one L4 frontend distributing traffic to healthy VMs across zones. Requirement B: A production App Service must resist a zone failure without managing VM instances. Which complete two-part proposal satisfies both constraints?
For requirement A, load Balancer routes TCP/UDP flows to healthy backends without terminating HTTP requests. For requirement B, eligible App Service plans distribute app workers across availability zones with sufficient capacity. Verify both independently: Failed backend probes remove one instance and healthy zonal instances continue serving; A zonal disruption leaves the application reachable via surviving workers.
One action is correct. The other targets Traffic Manager DNS routing, leaving App Service zone redundancy unsolved. Its necessary action is: Use a supported zone-redundant App Service plan with adequate instances.
Eligible App Service plans distribute app workers across availability zones with sufficient capacity. The other proposed action (enable AKS cluster autoscaler within approved node pool bounds) does not implement the first control. Load Balancer routes TCP/UDP flows to healthy backends without terminating HTTP requests.
Both proposed halves address other use cases: AKS cluster autoscaler and Traffic Manager DNS routing. The requested pair is Zone-redundant load balancer and App Service zone redundancy.
Architecture rationale review—Azure Front Door caching: Use Front Door edge caching with appropriate cache-control and purge policy. Which explanation accurately distinguishes this capability?
Edge caching reduces origin load and latency for eligible cacheable content. It is material here because a global website serves the same static assets to users on several continents.
Asynchronous projections can lag writes and need clear read-after-write expectations. That statement describes Eventual consistency UX, while the question asks how Azure Front Door caching works: Edge caching reduces origin load and latency for eligible cacheable content.
Durable orchestrations checkpoint progress and coordinate stateful serverless workflows. Edge caching reduces origin load and latency for eligible cacheable content.
App Configuration centralizes feature settings; secrets should remain in Key Vault. It belongs to App Configuration feature flags. The stated architecture instead relies on: Edge caching reduces origin load and latency for eligible cacheable content.
For Workload identity federation, operations are closing a change that addressed: A CI/CD job in GitHub Actions must deploy Azure resources without storing a long-lived service principal secret. Which post-change signal belongs in the acceptance record?
Federated credentials exchange trusted external OIDC assertions for Entra access tokens. Confirm using the measurable result: An approved pipeline deploys without a stored client secret and an untrusted subject is rejected.
Authentication strengths let Conditional Access require supported strong methods based on conditions. The offered observation would demonstrate Conditional MFA: The admin can sign in with a compliant method and a weaker method is rejected. The current validation is different: An approved pipeline deploys without a stored client secret and an untrusted subject is rejected.
App-only permissions grant service principal operations without a delegated signed-in user. Those observations validate Application permissions. They do not establish the required Workload identity federation result: An approved pipeline deploys without a stored client secret and an untrusted subject is rejected.
B2B collaboration supports guest principals and cross-organization access controls. The distinguishing check is: An approved pipeline deploys without a stored client secret and an untrusted subject is rejected.
Legal records must be WORM protected against modification for five years. Choose the architecture that can be validated by this result: An authorized user cannot modify a protected retained object before expiry.
Immutable storage prevents overwrite and delete during the configured retention interval. The selected architecture is configure compliant immutable blob retention policies at supported scope; confirm the result by checking that an authorized user cannot modify a protected retained object before expiry.
Tiering trades storage price against access and retrieval cost based on usage. The current need is: Legal records must be WORM protected against modification for five years.
An in-memory cache reduces repeated origin queries when staleness and invalidation are controlled. It does not solve the specified Blob immutability condition.
Blob Storage manages massively scalable object data rather than SMB-compatible shared volumes. Its design target is Blob object storage. The stated requirement instead concerns: Legal records must be WORM protected against modification for five years.
During technical sign-off for App registration API scopes, the architect selects: Define exposed API permissions in the app registration and require consent as appropriate. Which underlying behavior should be documented?
Delegated permissions represent what an application can do on behalf of an authenticated user. It is material here because a backend API should expose delegated scopes to a client on behalf of a signed-in user.
App-only permissions grant service principal operations without a delegated signed-in user. That statement describes Application permissions, while the question asks how App registration API scopes works: Delegated permissions represent what an application can do on behalf of an authenticated user.
Administrative units scope eligible directory management roles to selected objects, not data visibility. Delegated permissions represent what an application can do on behalf of an authenticated user.
Azure SQL supports Entra authentication and compatible managed identities can eliminate stored SQL secrets. Delegated permissions represent what an application can do on behalf of an authenticated user.
The team has justified its SQL long-term recovery design with: Configure Azure SQL long-term retention for the required backup schedule. Which statement accurately describes why the approach works?
LTR retains selected full backups over years rather than only the standard short PITR window. It is material here because a legal obligation requires recovery of relational records from a backup taken five years ago.
Geo-restore is backup-based recovery with different RTO/RPO than active geo-replication. LTR retains selected full backups over years rather than only the standard short PITR window.
Immutable backup settings can prevent specified destructive operations against protected backups. LTR retains selected full backups over years rather than only the standard short PITR window.
Geo-redundant vault storage can provide recovery copies in a paired region subject to feature settings. It belongs to Cross-region backup. The stated architecture instead relies on: LTR retains selected full backups over years rather than only the standard short PITR window.
Please check your mailbox for a message from support@examlabs.com and follow the directions.