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
Compliance requires offsite protected copies of blob data separate from only operational object versioning. The acceptance test is: An eligible blob recovery point is restored using the protected vault workflow. Which design recommendation best satisfies both?
Vaulted blob backup supplies protected backup storage with different capabilities than operational backups. The selected architecture is evaluate supported vaulted backup for blobs with documented feature and region limits; confirm the result by checking that an eligible blob recovery point is restored using the protected vault workflow.
A non-disruptive DR test validates recovery sequences and dependencies before a real disaster. The relevant requirement is: Compliance requires offsite protected copies of blob data separate from only operational object versioning.
Failback is a separate operational sequence after workloads run in the recovery site. It does not solve the specified Blob vaulted backup condition.
Share snapshots preserve file-share point-in-time state for supported restoration. That is useful for Azure Files snapshots (An Azure Files SMB share needs hourly recovery of files accidentally overwritten by users). It does not meet the current Blob vaulted backup requirement: Compliance requires offsite protected copies of blob data separate from only operational object versioning.
Architecture rationale review—SQL geo-replication reporting: Configure supported Azure SQL active geo-replication and route stale-tolerant reads to the replica. Which explanation accurately distinguishes this capability?
Active geo-replication creates readable asynchronously updated secondary databases while primary remains writable. It is material here because a geographically distributed app needs a readable secondary SQL database to offload reports without moving the primary write location.
Elastic pools share resources across independent databases with non-synchronized demand. Active geo-replication creates readable asynchronously updated secondary databases while primary remains writable.
IaaS retains operating-system and SQL instance control that PaaS databases do not provide. Active geo-replication creates readable asynchronously updated secondary databases while primary remains writable.
SQL auditing captures database events as configured separately from application request telemetry. That statement describes SQL auditing, while the question asks how SQL geo-replication reporting works: Active geo-replication creates readable asynchronously updated secondary databases while primary remains writable.
A proposed solution for Memory optimized VM is: Select a memory-optimized Azure VM family after measuring peak resident memory. Select the strongest statement supporting the recommendation.
Memory-optimized sizes offer higher RAM-to-vCPU ratio for large in-memory working sets. It is material here because an in-memory analytics engine repeatedly pages memory on a standard VM size.
Queue-length scaling aligns worker count with pending work rather than idle CPU metrics. It belongs to Autoscaling based on queue. The stated architecture instead relies on: Memory-optimized sizes offer higher RAM-to-vCPU ratio for large in-memory working sets.
ASE provides dedicated App Service hosting in a customer virtual-network environment. That statement describes App Service isolation, while the question asks how Memory optimized VM works: Memory-optimized sizes offer higher RAM-to-vCPU ratio for large in-memory working sets.
Compute Gallery distributes managed image versions for repeatable VM deployments. Memory-optimized sizes offer higher RAM-to-vCPU ratio for large in-memory working sets.
A multinational firm needs centrally managed branch and VNet transit across many regions. Which Azure architecture would most directly achieve the required result: A branch reaches authorized remote VNets through the intended virtual hub routes?
Virtual WAN provides managed global transit architecture with integrated branch connectivity. The selected architecture is evaluate Azure Virtual WAN secured virtual hubs and routing intent; confirm the result by checking that a branch reaches authorized remote VNets through the intended virtual hub routes.
DDoS protection adds adaptive mitigation and telemetry for supported public resources. That is useful for DDoS protection (A publicly reachable application needs additional DDoS mitigation beyond basic platform protections). It does not meet the current Virtual WAN global hubs requirement: A multinational firm needs centrally managed branch and VNet transit across many regions.
VPN Gateway can establish encrypted IPsec tunnels over public networks. Its design target is Site-to-site VPN. The stated requirement instead concerns: A multinational firm needs centrally managed branch and VNet transit across many regions.
Service endpoints keep the platform public endpoint while allowing VNet-based service firewall authorization. It does not solve the specified Virtual WAN global hubs condition.
A TCP application requires global endpoint selection using DNS without a global L7 reverse proxy. The acceptance test is: DNS responses prefer the healthy endpoint as monitoring marks another unavailable. Which design recommendation best satisfies both?
Traffic Manager is DNS-based and clients connect directly to the returned service endpoint. The selected architecture is consider Azure Traffic Manager with priority/performance routing and endpoint monitoring; confirm the result by checking that DNS responses prefer the healthy endpoint as monitoring marks another unavailable.
PDBs constrain voluntary disruptions but do not prevent all involuntary failures. Its design target is AKS pod disruption budget. The stated requirement instead concerns: A TCP application requires global endpoint selection using DNS without a global L7 reverse proxy.
GZRS synchronously spreads primary copies across zones and asynchronously replicates to another region. It does not solve the specified Traffic Manager DNS routing condition.
Multi-region writes allow eligible regions to accept writes but require handling conflicts. That is useful for Cosmos multi-write availability (A global application must continue accepting writes from multiple regions when one region fails). It does not meet the current Traffic Manager DNS routing requirement: A TCP application requires global endpoint selection using DNS without a global L7 reverse proxy.
The acceptance criterion for Azure managed disks comes from this issue: An Azure VM runs a database requiring block device storage attached as a virtual disk. Which measured outcome is the strongest proof?
Managed disks provide block storage to Azure VMs rather than object or SMB interfaces. Confirm using the measurable result: The disk attaches to the VM and meets measured random IO latency.
Tiering trades storage price against access and retrieval cost based on usage. The offered observation would demonstrate Blob hot/cool/cold: Old eligible blobs transition to the intended tier and remain retrievable. The current validation is different: The disk attaches to the VM and meets measured random IO latency.
NetApp Files offers enterprise file protocols and performance controls for supported workloads. The distinguishing check is: The disk attaches to the VM and meets measured random IO latency.
Partition key distribution governs data/throughput placement and query efficiency. The Cosmos partition key test checks rU consumption distributes across partitions and the query includes its expected partition key; the relevant outcome is The disk attaches to the VM and meets measured random IO latency.
The application firewall blocks legitimate requests but developers cannot see the matching rule. The acceptance test is: A blocked test request identifies its matching WAF rule and client context in the destination logs. Which design recommendation best satisfies both?
WAF rule and access diagnostics identify rule IDs and request outcomes that aggregate health metrics miss. The selected architecture is enable Application Gateway WAF diagnostics and send them to Log Analytics; confirm the result by checking that a blocked test request identifies its matching WAF rule and client context in the destination logs.
Container insights exposes Kubernetes workload health and container logs beyond generic virtual-machine statistics. It does not solve the specified WAF decision logs condition.
Lighthouse enables delegated management across tenants without relocating customer-owned resources. Its design target is Cross-tenant operations. The stated requirement instead concerns: The application firewall blocks legitimate requests but developers cannot see the matching rule.
Action groups define notifications and automated responses and can be reused by alert rules. The relevant requirement is: The application firewall blocks legitimate requests but developers cannot see the matching rule.
For the Cosmos autoscale requirement, the proposed architecture uses: Use Cosmos DB autoscale throughput within tested RU limits. Why does that design fit?
Autoscale adjusts provisioned RU/s capacity according to measured load within a maximum. It is material here because an API's Cosmos traffic varies tenfold through the day and manually fixed throughput is wasteful.
Immutable storage prevents overwrite and delete during the configured retention interval. It belongs to Blob immutability. The stated architecture instead relies on: Autoscale adjusts provisioned RU/s capacity according to measured load within a maximum.
An in-memory cache reduces repeated origin queries when staleness and invalidation are controlled. Autoscale adjusts provisioned RU/s capacity according to measured load within a maximum.
ADLS Gen2 adds directory semantics and access ACLs to blob-backed storage. Autoscale adjusts provisioned RU/s capacity according to measured load within a maximum.
To validate the Azure service health deployment, reviewers revisit this operational need: A regional Azure platform incident affects databases but project teams have no subscription-specific warning. What result confirms it was met?
Service Health reports Azure platform incidents and planned maintenance relevant to a subscription. Confirm using the measurable result: A platform health incident produces the configured subscription-scoped notification.
Dynamic thresholds adapt alert boundaries to historical metric patterns after sufficient data exists. The Dynamic baseline alerts test checks the routine daily spike is tolerated while an atypical surge creates an actionable alert; the relevant outcome is A platform health incident produces the configured subscription-scoped notification.
DCRs specify collected streams destinations and transformations for supported agent sources. Those observations validate Agent collection rules. They do not establish the required Azure service health result: A platform health incident produces the configured subscription-scoped notification.
A log search alert can evaluate aggregated matching records instead of only raw metric time series. The distinguishing check is: A platform health incident produces the configured subscription-scoped notification.
Architecture review: Key Vault app secrets and Reliable exactly-once effect. Requirement A: A deployed API must rotate an external vendor credential without checking a new secret into Git. Requirement B: A retrying order processor may receive the same message multiple times and must avoid duplicate billing. Which complete two-part proposal satisfies both constraints?
For requirement A, central secret retrieval separates sensitive credentials from source and build artifacts. For requirement B, at-least-once message delivery requires application logic to deduplicate business side effects. Verify both independently: Credential rotation works without modifying committed application configuration; Two deliveries of the same order ID create only one invoice.
This combines Publish subscribe topics and API Management gateway, which do not satisfy the distinct requirements for Key Vault app secrets and Reliable exactly-once effect.
One action is correct. The other targets API Management gateway, leaving Reliable exactly-once effect unsolved. Its necessary action is: Design an idempotent handler using a durable business operation key.
At-least-once message delivery requires application logic to deduplicate business side effects. The other proposed action (use Service Bus topics with subscriptions when reliable broker delivery is needed) does not implement the first control. Central secret retrieval separates sensitive credentials from source and build artifacts.
For the SQL dynamic data masking requirement, the proposed architecture uses: Configure SQL dynamic data masking for selected columns and test permission bypass behavior. Why does that design fit?
Dynamic data masking limits exposure in query results but is not a substitute for database access control. It is material here because customer support may query a user table but should not see complete personal identifiers in routine result sets.
Pooling reuses connections and reduces setup overhead relative to per-request creation. Dynamic data masking limits exposure in query results but is not a substitute for database access control.
Migration assessment identifies blockers and target-fit issues before a cutover. That statement describes SQL migration assessment, while the question asks how SQL dynamic data masking works: Dynamic data masking limits exposure in query results but is not a substitute for database access control.
Flexible Server offers managed open-source PostgreSQL with supported extensions and deployment options. Dynamic data masking limits exposure in query results but is not a substitute for database access control.
Please check your mailbox for a message from support@examlabs.com and follow the directions.