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
An API's Cosmos traffic varies tenfold through the day and manually fixed throughput is wasteful. A deployment must satisfy this operational criterion: Busy-hour requests meet RU demands and off-peak consumed RU declines. Which plan is appropriate?
Autoscale adjusts provisioned RU/s capacity according to measured load within a maximum. The selected architecture is use Cosmos DB autoscale throughput within tested RU limits; confirm the result by checking that busy-hour requests meet RU demands and off-peak consumed RU declines.
ADLS Gen2 adds directory semantics and access ACLs to blob-backed storage. The current need is: An API's Cosmos traffic varies tenfold through the day and manually fixed throughput is wasteful.
An in-memory cache reduces repeated origin queries when staleness and invalidation are controlled. It does not solve the specified Cosmos autoscale condition.
Immutable storage prevents overwrite and delete during the configured retention interval. The relevant requirement is: An API's Cosmos traffic varies tenfold through the day and manually fixed throughput is wasteful.
To validate the Blob vaulted backup deployment, reviewers revisit this operational need: Compliance requires offsite protected copies of blob data separate from only operational object versioning. What result confirms it was met?
Vaulted blob backup supplies protected backup storage with different capabilities than operational backups. Confirm using the measurable result: An eligible blob recovery point is restored using the protected vault workflow.
Backup private connectivity has service and workload prerequisites distinct from ordinary storage private endpoints. The distinguishing check is: An eligible blob recovery point is restored using the protected vault workflow.
Blob operational backup relies on point-in-time object protection features rather than VM-level backups. The Blob operational backup test checks a deleted supported blob is restored to the requested prior point in the configured interval; the relevant outcome is An eligible blob recovery point is restored using the protected vault workflow.
RTO is the maximum acceptable restoration duration, not the amount of lost data. The offered observation would demonstrate Recovery time objective: A regional failover test restores business service in less than the allowed interval. The current validation is different: An eligible blob recovery point is restored using the protected vault workflow.
A proposed solution for Application Gateway path routing is: Use Application Gateway URL-path-based routing with TLS and health probes. Select the strongest statement supporting the recommendation.
Application Gateway provides application-aware path routing rather than basic L4 forwarding. It is material here because one regional HTTPS endpoint needs /api requests routed to API pods and /shop to a web tier.
Queueing decouples front-end latency from downstream worker availability. That statement describes Queue asynchronous processing, while the question asks how Application Gateway path routing works: Application Gateway provides application-aware path routing rather than basic L4 forwarding.
Central secret retrieval separates sensitive credentials from source and build artifacts. Application Gateway provides application-aware path routing rather than basic L4 forwarding.
APIM can enforce per-client API consumption controls before requests reach backends. Application Gateway provides application-aware path routing rather than basic L4 forwarding.
Architecture review: Policy initiative and Management group hierarchy. Requirement A: Security standards require a reusable collection of tagging, encryption and diagnostics policies. Requirement B: A global enterprise requires central baseline policies applied to every subscription but autonomous project teams manage resources. Which complete two-part proposal satisfies both constraints?
For requirement A, initiatives bundle related policy rules and support shared compliance reporting. For requirement B, management groups supply governance scope above subscriptions without moving resources into a single subscription. Verify both independently: Compliance reporting shows the member controls under the assigned initiative; A new subscription inherits the applicable central compliance policy.
Initiatives bundle related policy rules and support shared compliance reporting. The other proposed action (use Azure Bicep modules and deployment pipelines with approval gates) addresses a different operation. Management groups supply governance scope above subscriptions without moving resources into a single subscription.
The option covers one requirement but substitutes Landing zones for Policy initiative. The missing acceptance result is: Compliance reporting shows the member controls under the assigned initiative.
Initiatives bundle related policy rules and support shared compliance reporting. Management groups supply governance scope above subscriptions without moving resources into a single subscription. The proposed steps (adopt an Azure landing-zone architecture following the Cloud Adoption Framework; use Azure Bicep modules and deployment pipelines with approval gates) address other capabilities instead of this required pair.
The target environment adopts this approach for DNS private zones: Link the appropriate Azure Private DNS zone and configure private endpoint DNS records. What property makes it suitable?
Private DNS zone links determine name resolution for VNets that consume private endpoints. It is material here because a service private endpoint resolves to a public address from a peered spoke VNet.
Application Gateway provides regional Layer 7 reverse proxy and routing for private backends. It belongs to Application Gateway internal. The stated architecture instead relies on: Private DNS zone links determine name resolution for VNets that consume private endpoints.
Edge WAF can inspect and filter HTTP requests before the proxy forwards them to origins. That statement describes Front Door WAF edge, while the question asks how DNS private zones works: Private DNS zone links determine name resolution for VNets that consume private endpoints.
Azure Firewall provides managed stateful filtering with network/application rule models. Private DNS zone links determine name resolution for VNets that consume private endpoints.
The design team completed work on Availability set. Its governing requirement was: A legacy VM workload runs in a region without required availability zones but needs protection from host maintenance faults. Identify the conclusive verification result.
Availability sets spread VM instances across host-related fault and update domains within a datacenter. Confirm using the measurable result: A planned host update does not make every VM unavailable at once.
Circuit breakers stop futile downstream calls temporarily and permit controlled re-entry. The distinguishing check is: A planned host update does not make every VM unavailable at once.
Cluster autoscaler adjusts nodes to schedule eligible pending pods. The AKS cluster autoscaler test checks pending pods move to new nodes before the measured capacity deadline; the relevant outcome is A planned host update does not make every VM unavailable at once.
Fault injection tests whether resilience patterns work under realistic failure conditions. The offered observation would demonstrate Chaos failure testing: The app maintains the defined availability objective during planned dependency failure. The current validation is different: A planned host update does not make every VM unavailable at once.
Architecture rationale review—Event Grid partner events: Evaluate Event Grid partner topics or a supported partner event source with subscriptions. Which explanation accurately distinguishes this capability?
Partner event integration routes supported third-party event types without custom polling. It is material here because an external SaaS integration publishes events that several Azure business systems must consume with filtered routing.
Service Bus is an enterprise message broker with delivery and dead-letter semantics. Partner event integration routes supported third-party event types without custom polling.
Dedicated pools supply reserved MPP compute suited for managed warehouse workloads. Partner event integration routes supported third-party event types without custom polling.
Stream Analytics supports SQL-like processing over streaming sources with time windows. It belongs to Stream Analytics window. The stated architecture instead relies on: Partner event integration routes supported third-party event types without custom polling.
Blob containers need protection against accidental deletion and malicious modification over a short operational window. A deployment must satisfy this operational criterion: A deleted supported blob is restored to the requested prior point in the configured interval. Which plan is appropriate?
Blob operational backup relies on point-in-time object protection features rather than VM-level backups. The selected architecture is use supported blob operational backup with versioning and change feed prerequisites; confirm the result by checking that a deleted supported blob is restored to the requested prior point in the configured interval.
Geo-restore is backup-based recovery with different RTO/RPO than active geo-replication. The relevant requirement is: Blob containers need protection against accidental deletion and malicious modification over a short operational window.
Backup private connectivity has service and workload prerequisites distinct from ordinary storage private endpoints. It does not solve the specified Blob operational backup condition.
Compute replication does not automatically guarantee complete application network reachability. That is useful for Azure-to-Azure ASR networking (Replicated VMs boot in the secondary region but application private DNS and subnets are unavailable). It does not meet the current Blob operational backup requirement: Blob containers need protection against accidental deletion and malicious modification over a short operational window.
One application needs a carefully controlled exception to a management group policy. Which Azure architecture would most directly achieve the required result: Only the approved application scope avoids the specified policy effect?
Policy scope and exclusions should be the smallest feasible exception rather than removing global guardrails. The selected architecture is use scoped policy exemptions or exclusion with documented rationale and review; confirm the result by checking that only the approved application scope avoids the specified policy effect.
Azure service quotas are often scoped by subscription and region and can constrain deployability. The current need is: One application needs a carefully controlled exception to a management group policy.
Budgets monitor and notify about spending and do not automatically stop resources. It does not solve the specified Policy exclusion scope condition.
Cost exports provide detailed recurring usage data for downstream allocation reporting. The relevant requirement is: One application needs a carefully controlled exception to a management group policy.
An architect must sign off on Conditional MFA. The business problem is: Administrators must use phishing-resistant authentication for high-privilege cloud portal actions. What observed test result provides valid evidence?
Authentication strengths let Conditional Access require supported strong methods based on conditions. Confirm using the measurable result: The admin can sign in with a compliant method and a weaker method is rejected.
PIM can time-bound eligible role activation with approvals MFA and justification. The distinguishing check is: The admin can sign in with a compliant method and a weaker method is rejected.
Delegated permissions represent what an application can do on behalf of an authenticated user. The App registration API scopes test checks the API token contains the required scope and access without that scope is rejected; the relevant outcome is The admin can sign in with a compliant method and a weaker method is rejected.
Managed identities provide Entra tokens to supported workloads while data-plane RBAC grants the actual blob permissions. The offered observation would demonstrate Managed identity for App Service: A token-based read works and the app has no stored storage-account key. The current validation is different: The admin can sign in with a compliant method and a weaker method is rejected.
A rollout addressing Service Bus ordering has reached acceptance testing. The original problem was: A billing workflow needs durable work messages with transactions, sessions and dead-letter handling. Which finding verifies its resolution?
Service Bus is an enterprise message broker with delivery and dead-letter semantics. Confirm using the measurable result: A poison message moves to the dead-letter queue while ordered session items retain their sequence.
Partner event integration routes supported third-party event types without custom polling. The Event Grid partner events test checks a partner-created event triggers only matching subscriptions across the consuming applications; the relevant outcome is A poison message moves to the dead-letter queue while ordered session items retain their sequence.
Pipeline control flow can orchestrate dependent stages instead of independent schedules. Those observations validate ADF pipeline dependency. They do not establish the required Service Bus ordering result: A poison message moves to the dead-letter queue while ordered session items retain their sequence.
Mapping data flows transform data on managed Spark compute from graphical mappings. The distinguishing check is: A poison message moves to the dead-letter queue while ordered session items retain their sequence.
Please check your mailbox for a message from support@examlabs.com and follow the directions.