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 design team completed work on Blob immutability. Its governing requirement was: Legal records must be WORM protected against modification for five years. Identify the conclusive verification result.
Immutable storage prevents overwrite and delete during the configured retention interval. Confirm using the measurable result: An authorized user cannot modify a protected retained object before expiry.
Blob Inventory produces scheduled object inventories without crawling each object individually. Those observations validate Blob inventory. They do not establish the required Blob immutability result: An authorized user cannot modify a protected retained object before expiry.
Cosmos DB provides a distributed document database with configurable consistency and throughput. The Cosmos DB NoSQL test checks the app reads JSON documents across the planned partitions with predictable latency; the relevant outcome is An authorized user cannot modify a protected retained object before expiry.
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 authorized user cannot modify a protected retained object before expiry.
A vault must be reachable only from approved private Azure networks and not from arbitrary internet clients. An engineer must deliver the following acceptance evidence: A workload resolves the private vault endpoint and a public-network test cannot use the forbidden path. What design choice is defensible?
Private Link gives a private address path to supported vault endpoints when DNS resolves accordingly. The selected architecture is use a Key Vault private endpoint and correctly configured private DNS and firewall policy; confirm the result by checking that a workload resolves the private vault endpoint and a public-network test cannot use the forbidden path.
Authentication strengths let Conditional Access require supported strong methods based on conditions. It does not solve the specified Vault network boundary condition.
App-only permissions grant service principal operations without a delegated signed-in user. Its design target is Application permissions. The stated requirement instead concerns: A vault must be reachable only from approved private Azure networks and not from arbitrary internet clients.
Key Vault secrets support controlled retrieval and rotation separate from packaged application code. The current need is: A vault must be reachable only from approved private Azure networks and not from arbitrary internet clients.
Architecture review: App Service web and AKS full Kubernetes. Requirement A: An HTTP API needs custom deployment slots and managed PaaS hosting without a Kubernetes operations team. Requirement B: A platform team needs custom Kubernetes network policies controllers and cluster API access. Which complete two-part proposal satisfies both constraints?
For requirement A, App Service manages web hosting and supports deployment slots on eligible plans. For requirement B, AKS provides managed Kubernetes control-plane hosting with configurable worker clusters. Verify both independently: Traffic swaps to a warmed-up deployment slot without SSH management of app hosts; Custom controllers and policy resources function under the supported cluster configuration.
AKS provides managed Kubernetes control-plane hosting with configurable worker clusters. The other proposed action (select a memory-optimized Azure VM family after measuring peak resident memory) does not implement the first control. App Service manages web hosting and supports deployment slots on eligible plans.
The option covers one requirement but substitutes Container Registry for AKS full Kubernetes. The missing acceptance result is: Custom controllers and policy resources function under the supported cluster configuration.
App Service manages web hosting and supports deployment slots on eligible plans. AKS provides managed Kubernetes control-plane hosting with configurable worker clusters. The proposed steps (select a memory-optimized Azure VM family after measuring peak resident memory; use Azure Container Registry with controlled image push and pull access) address other capabilities instead of this required pair.
Architecture review: Premium SSD v2 and Azure NetApp Files. Requirement A: A VM workload needs independently adjustable provisioned IOPS and throughput with SSD latency. Requirement B: A latency-sensitive enterprise app needs high-throughput shared NFS volumes with managed storage. Which complete two-part proposal satisfies both constraints?
For requirement A, premium SSD v2 decouples some provisioned performance settings from disk capacity. For requirement B, netApp Files offers enterprise file protocols and performance controls for supported workloads. Verify both independently: The disk achieves its provisioned IOPS and throughput under a supported VM configuration; An authorized NFS client mounts the volume with required throughput.
This combines Blob soft delete and Blob hot/cool/cold, which do not satisfy the distinct requirements for Premium SSD v2 and Azure NetApp Files.
The option covers one requirement but substitutes Blob soft delete for Premium SSD v2. The missing acceptance result is: The disk achieves its provisioned IOPS and throughput under a supported VM configuration.
The mismatched half is Blob hot/cool/cold; Azure NetApp Files instead needs: Evaluate Azure NetApp Files capacity pools and volume service levels.
For Cosmos periodic backup, operations are closing a change that addressed: A Cosmos DB workload uses periodic backups and the team expects minute-level arbitrary restores. Which post-change signal belongs in the acceptance record?
Periodic backups produce interval snapshots and are not the same as continuous point-in-time recovery. Confirm using the measurable result: The new design demonstrates recovery granularity consistent with the RPO.
Failback is a separate operational sequence after workloads run in the recovery site. Those observations validate Failback after recovery. They do not establish the required Cosmos periodic backup result: The new design demonstrates recovery granularity consistent with the RPO.
Multi-user authorization separates approval boundaries for critical backup changes. The distinguishing check is: The new design demonstrates recovery granularity consistent with the RPO.
RPO measures the maximum tolerated data loss period at a recovery point. The offered observation would demonstrate Recovery point objective: Failover comparison shows the latest committed recoverable write is within five minutes. The current validation is different: The new design demonstrates recovery granularity consistent with the RPO.
Architecture review: VMSS dynamic scaling and App deployment blue-green. Requirement A: An autoscaling API needs several identical VMs during peak hours and only a few at night. Requirement B: A mission-critical API needs a low-risk deployment with rapid rollback of application code. Which complete two-part proposal satisfies both constraints?
For requirement A, VMSS automates management and scaling of similar VMs in the same workload. For requirement B, blue-green deployment preserves a prior known-good instance while testing a replacement. Verify both independently: The scale set adds instances at load and returns to baseline under low demand; A failed health check returns traffic to the prior application version.
One action is correct. The other targets GPU VM, leaving App deployment blue-green unsolved. Its necessary action is: Use App Service deployment slots or equivalent supported blue-green routing.
This combines VM maintenance handling and GPU VM, which do not satisfy the distinct requirements for VMSS dynamic scaling and App deployment blue-green.
The option covers one requirement but substitutes VM maintenance handling for VMSS dynamic scaling. The missing acceptance result is: The scale set adds instances at load and returns to baseline under low demand.
An architect must sign off on API Management gateway. The business problem is: Partners need one secured API entry point with subscription policies quotas and versioned back ends. What observed test result provides valid evidence?
APIM applies gateway policies authentication mediation throttling and API lifecycle controls. Confirm using the measurable result: An expired subscription key fails while an authorized request routes to the correct version.
Edge caching reduces origin load and latency for eligible cacheable content. The Azure Front Door caching test checks a repeat request from a distant location is served from the edge cache; the relevant outcome is An expired subscription key fails while an authorized request routes to the correct version.
APIM can enforce per-client API consumption controls before requests reach backends. Those observations validate APIM rate limiting. They do not establish the required API Management gateway result: An expired subscription key fails while an authorized request routes to the correct version.
Topics fan out a message to independently managed subscriptions with durable handling. The distinguishing check is: An expired subscription key fails while an authorized request routes to the correct version.
To validate the SQL connection pooling deployment, reviewers revisit this operational need: A serverless API makes many short SQL connections and exhausts available database sessions. What result confirms it was met?
Pooling reuses connections and reduces setup overhead relative to per-request creation. Confirm using the measurable result: Connection counts stabilize while expected API throughput is maintained.
Read replicas offload eligible read-only queries but are asynchronously updated from the writer. The offered observation would demonstrate PostgreSQL read replica: The reports run on a replica while primary transaction performance improves. The current validation is different: Connection counts stabilize while expected API throughput is maintained.
IaaS retains operating-system and SQL instance control that PaaS databases do not provide. Those observations validate SQL Server on Azure VM. They do not establish the required SQL connection pooling result: Connection counts stabilize while expected API throughput is maintained.
Dynamic data masking limits exposure in query results but is not a substitute for database access control. The SQL dynamic data masking test checks support queries return masked values while appropriately authorized principals can access underlying values; the relevant outcome is Connection counts stabilize while expected API throughput is maintained.
A rollout addressing Error trend queries has reached acceptance testing. The original problem was: Operations must aggregate intermittent HTTP 500s by service and hour from application traces. Which finding verifies its resolution?
KQL summarizes timestamped structured log data across dimensions such as operation and cloud role. Confirm using the measurable result: An hourly chart returns grouped failure counts and identifies the affected service.
AMPLS provides private connectivity to supported Azure Monitor ingestion and query endpoints. The distinguishing check is: An hourly chart returns grouped failure counts and identifies the affected service.
Managed Prometheus collects Prometheus-format metrics separately from traditional container log collection. The Managed Prometheus test checks a PromQL dashboard graphs the selected container metric with the expected Kubernetes labels; the relevant outcome is An hourly chart returns grouped failure counts and identifies the affected service.
Resource Health reports the platform-side availability history of individual Azure resources. The offered observation would demonstrate VM resource health: The specific VM shows an unavailable health state while the regional Service Health feed remains normal. The current validation is different: An hourly chart returns grouped failure counts and identifies the affected service.
The Autoscaling based on queue review proposes: Use an event-driven worker scaling mechanism such as Container Apps KEDA trigger. Which Azure behavior is the technical justification for this decision?
Queue-length scaling aligns worker count with pending work rather than idle CPU metrics. It is material here because 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. That statement describes Azure HPC design, while the question asks how Autoscaling based on queue works: Queue-length scaling aligns worker count with pending work rather than idle CPU metrics.
Compute-optimized instances prioritize vCPU capacity over excess memory. Queue-length scaling aligns worker count with pending work rather than idle CPU metrics.
Encryption sets connect managed disk encryption to customer-owned keys. Queue-length scaling aligns worker count with pending work rather than idle CPU metrics.
A small branch needs encrypted connectivity to a VNet over its existing internet link. Identify the most suitable implementation for an outcome where encrypted traffic reaches the approved private Azure subnet from the branch.
VPN Gateway can establish encrypted IPsec tunnels over public networks. The selected architecture is deploy Azure VPN Gateway site-to-site tunnels with matching local/remote IPsec settings; confirm the result by checking that encrypted traffic reaches the approved private Azure subnet from the branch.
ExpressRoute links customer WAN to Azure backbone privately through provider connectivity. It does not solve the specified Site-to-site VPN condition.
NSGs provide stateful Layer 3/4 access rules rather than application-layer inspection. The current need is: A small branch needs encrypted connectivity to a VNet over its existing internet link.
Peering connects VNet address spaces through the Microsoft backbone without creating transitive routing by default. That is useful for VNet peering (Two Azure VNets in nearby regions need low-latency private connectivity without VPN gateways). It does not meet the current Site-to-site VPN requirement: A small branch needs encrypted connectivity to a VNet over its existing internet link.
Please check your mailbox for a message from support@examlabs.com and follow the directions.