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
A processing worker should scale according to Service Bus backlog, not HTTP request count. Identify the most suitable implementation for an outcome where the number of workers grows with queue backlog and contracts after processing.
Queue-length scaling aligns worker count with pending work rather than idle CPU metrics. The selected architecture is use an event-driven worker scaling mechanism such as Container Apps KEDA trigger; confirm the result by checking that the number of workers grows with queue backlog and contracts after processing.
Compute-optimized instances prioritize vCPU capacity over excess memory. The relevant requirement is: A processing worker should scale according to Service Bus backlog, not HTTP request count.
HPC workloads require specialized low-latency fabric support beyond commodity VMs. It does not solve the specified Autoscaling based on queue condition.
Encryption sets connect managed disk encryption to customer-owned keys. That is useful for VM disk encryption (A finance VM needs customer-managed encryption keys for managed disks). It does not meet the current Autoscaling based on queue requirement: A processing worker should scale according to Service Bus backlog, not HTTP request count.
Architecture review: Virtual WAN global hubs and UDR firewall inspection. Requirement A: A multinational firm needs centrally managed branch and VNet transit across many regions. Requirement B: A subnet must send internet-bound flows through a centrally managed inspection firewall. Which complete two-part proposal satisfies both constraints?
For requirement A, virtual WAN provides managed global transit architecture with integrated branch connectivity. For requirement B, user-defined routes can override platform routing to steer approved subnets through an NVA/firewall. Verify both independently: A branch reaches authorized remote VNets through the intended virtual hub routes; Traceroute and firewall logs show the intended inspected egress path.
The option covers one requirement but substitutes Network Watcher diagnosis for Virtual WAN global hubs. The missing acceptance result is: A branch reaches authorized remote VNets through the intended virtual hub routes.
Virtual WAN provides managed global transit architecture with integrated branch connectivity. User-defined routes can override platform routing to steer approved subnets through an NVA/firewall. The proposed steps (use Network Watcher connection troubleshoot and IP flow verify where supported; use Azure VPN Gateway point-to-site with an appropriate identity provider) address other capabilities instead of this required pair.
The mismatched half is Point-to-site VPN; UDR firewall inspection instead needs: Configure a route table with default route next hop to the firewall and enable required forwarding.
An architect must sign off on Automated diagnostics policy. The business problem is: New storage accounts across many subscriptions often appear with no diagnostic configuration. What observed test result provides valid evidence?
DeployIfNotExists can evaluate related configurations and deploy missing compliant resources with appropriate permissions. Confirm using the measurable result: A newly provisioned supported storage account gets the intended diagnostics after policy remediation.
Action groups define notifications and automated responses and can be reused by alert rules. Those observations validate Notification routing. They do not establish the required Automated diagnostics policy result: A newly provisioned supported storage account gets the intended diagnostics after policy remediation.
A log search alert can evaluate aggregated matching records instead of only raw metric time series. The distinguishing check is: A newly provisioned supported storage account gets the intended diagnostics after policy remediation.
Dynamic thresholds adapt alert boundaries to historical metric patterns after sufficient data exists. The offered observation would demonstrate Dynamic baseline alerts: The routine daily spike is tolerated while an atypical surge creates an actionable alert. The current validation is different: A newly provisioned supported storage account gets the intended diagnostics after policy remediation.
To validate the Blob soft delete deployment, reviewers revisit this operational need: A developer accidentally deletes a container and the organization wants short-term recovery. What result confirms it was met?
Soft delete retains recoverable deleted objects or containers during the configured period. Confirm using the measurable result: An accidentally deleted test object is recovered before retention expires.
Concurrent writes require a conflict resolution policy to prevent unintended last-writer outcomes. The distinguishing check is: An accidentally deleted test object is recovered before retention expires.
Directory ACLs provide path-level data authorization when hierarchical namespace is enabled. The offered observation would demonstrate ADLS ACLs: A test identity reads its assigned folder but is denied a sibling folder. The current validation is different: An accidentally deleted test object is recovered before retention expires.
Blob change feed records changes to blob objects for downstream processing. Those observations validate Blob change feed. They do not establish the required Blob soft delete result: An accidentally deleted test object is recovered before retention expires.
An order service writes asynchronously into a read model and users momentarily see old data. The acceptance test is: The UI shows pending status until the read model catches up without duplicate updates. Which design recommendation best satisfies both?
Asynchronous projections can lag writes and need clear read-after-write expectations. The selected architecture is design an eventual-consistency contract with status tracking and idempotent updates; confirm the result by checking that the UI shows pending status until the read model catches up without duplicate updates.
An API gateway can broker external requests to private backends without direct public backend access. Its design target is API private backends. The stated requirement instead concerns: An order service writes asynchronously into a read model and users momentarily see old data.
Web PubSub provides managed WebSocket connection fan-out so application servers need not hold all client sessions. The relevant requirement is: An order service writes asynchronously into a read model and users momentarily see old data.
APIM can enforce per-client API consumption controls before requests reach backends. It does not solve the specified Eventual consistency UX condition.
Data analysts must run ad hoc SQL queries over Parquet files in a data lake without provisioning a cluster. The acceptance test is: A SELECT reads the Parquet dataset with no dedicated SQL pool running. Which design recommendation best satisfies both?
Serverless SQL queries external lake files with consumption-based query compute. The selected architecture is use supported serverless SQL capabilities over files in Azure Synapse Analytics; confirm the result by checking that a SELECT reads the Parquet dataset with no dedicated SQL pool running.
Mapping data flows transform data on managed Spark compute from graphical mappings. The relevant requirement is: Data analysts must run ad hoc SQL queries over Parquet files in a data lake without provisioning a cluster.
Stream Analytics supports SQL-like processing over streaming sources with time windows. The current need is: Data analysts must run ad hoc SQL queries over Parquet files in a data lake without provisioning a cluster.
Hybrid/private integration requires a reachable private network path rather than open public DB exposure. It does not solve the specified Synapse serverless SQL condition.
Cloud pipelines must access a private database over private routing without publishing its port. An engineer must deliver the following acceptance evidence: The pipeline reads the database through the authorized private path while public access fails. What design choice is defensible?
Hybrid/private integration requires a reachable private network path rather than open public DB exposure. The selected architecture is use approved private integration runtime and networking features for the chosen data service; confirm the result by checking that the pipeline reads the database through the authorized private path while public access fails.
Tumbling-window triggers model contiguous time slices with support for backfill. The current need is: Cloud pipelines must access a private database over private routing without publishing its port.
Partner event integration routes supported third-party event types without custom polling. It does not solve the specified Private integration access condition.
Stream Analytics supports SQL-like processing over streaming sources with time windows. The relevant requirement is: Cloud pipelines must access a private database over private routing without publishing its port.
For Front Door global failover, operations are closing a change that addressed: Two regional web endpoints need internet-edge routing and automatic failover to a healthy region. Which post-change signal belongs in the acceptance record?
Front Door provides global application delivery and HTTP(S) origin failover at the edge. Confirm using the measurable result: Requests shift to healthy origin after simulated regional endpoint failure.
Load Balancer routes TCP/UDP flows to healthy backends without terminating HTTP requests. The distinguishing check is: Requests shift to healthy origin after simulated regional endpoint failure.
Circuit breakers stop futile downstream calls temporarily and permit controlled re-entry. The Circuit breaker behavior test checks unhealthy requests fail quickly and the service resumes calls after recovery; the relevant outcome is Requests shift to healthy origin after simulated regional endpoint failure.
Cluster autoscaler adjusts nodes to schedule eligible pending pods. The offered observation would demonstrate AKS cluster autoscaler: Pending pods move to new nodes before the measured capacity deadline. The current validation is different: Requests shift to healthy origin after simulated regional endpoint failure.
Architecture review: Resource type restriction and Subscription isolation. Requirement A: A business unit must prevent unapproved public IP resources but permit private network components. Requirement B: A regulated subsidiary needs separate billing and policy boundaries from the parent business unit. Which complete two-part proposal satisfies both constraints?
For requirement A, Azure Policy can deny targeted resource types without revoking all contributor operations. For requirement B, subscriptions are billing and resource governance boundaries with independent quotas and RBAC assignment scopes. Verify both independently: A public IP create is denied while a private subnet deployment proceeds; The subsidiary's budget and policy reports stay distinct from the parent.
The mismatched half is Landing zones; Subscription isolation instead needs: Place regulated workloads in designated subscriptions under suitable management groups.
Both proposed halves address other use cases: Standardized IaC and Landing zones. The requested pair is Resource type restriction and Subscription isolation.
One action is correct. The other targets Standardized IaC, leaving Resource type restriction unsolved. Its necessary action is: Assign a policy that disallows specified resource types or properties at the unit scope.
During technical sign-off for Azure Firewall rules, the architect selects: Use Azure Firewall with correct rule collections and hub routing. Which underlying behavior should be documented?
Azure Firewall provides managed stateful filtering with network/application rule models. It is material here because a central security team needs network and application filtering across multiple spokes.
Virtual WAN provides managed global transit architecture with integrated branch connectivity. Azure Firewall provides managed stateful filtering with network/application rule models.
Edge WAF can inspect and filter HTTP requests before the proxy forwards them to origins. Azure Firewall provides managed stateful filtering with network/application rule models.
Service endpoints keep the platform public endpoint while allowing VNet-based service firewall authorization. It belongs to Service endpoint. The stated architecture instead relies on: Azure Firewall provides managed stateful filtering with network/application rule models.
An external-facing consumer application requires local and social identity sign-in separate from workforce identities. The acceptance test is: The consumer completes the intended registration journey without receiving workforce resource roles. Which design recommendation best satisfies both?
External ID consumer capabilities support customer journeys distinct from employee workforce governance. The selected architecture is use an appropriate Microsoft Entra External ID customer identity design; confirm the result by checking that the consumer completes the intended registration journey without receiving workforce resource roles.
Key Vault RBAC data permissions differ from vault resource-management permissions. The current need is: An external-facing consumer application requires local and social identity sign-in separate from workforce identities.
Administrative units scope eligible directory management roles to selected objects, not data visibility. It does not solve the specified Consumer sign-in condition.
Management locks guard against accidental resource deletes and operate separately from authorization roles. The relevant requirement is: An external-facing consumer application requires local and social identity sign-in separate from workforce identities.
Please check your mailbox for a message from support@examlabs.com and follow the directions.