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
Architecture review: Physical server migration and Azure File Sync. Requirement A: A legacy application runs on a physical Windows server and needs an IaaS move. Requirement B: A branch file server should retain local caching while most data moves to Azure Files. Which complete two-part proposal satisfies both constraints?
For requirement A, physical migration requires source capture and replication methods different from VMware agentless VM migration. For requirement B, file Sync preserves local namespace access while synchronizing with Azure file shares. Verify both independently: A cutover VM starts in Azure with its application settings preserved; Frequently used files remain locally available and cold files tier to cloud.
File Sync preserves local namespace access while synchronizing with Azure file shares. The other proposed action (evaluate replatforming to Azure SQL Managed Instance or Database after compatibility tests) does not implement the first control. Physical migration requires source capture and replication methods different from VMware agentless VM migration.
Physical migration requires source capture and replication methods different from VMware agentless VM migration. The other proposed action (perform schema and compatibility assessment before choosing Azure SQL Database or Managed Instance) addresses a different operation. File Sync preserves local namespace access while synchronizing with Azure file shares.
Both proposed halves address other use cases: Replatform database and Database schema assessment. The requested pair is Physical server migration and Azure File Sync.
Checkout requests should return promptly while invoices are generated asynchronously with retry support. Which Azure architecture would most directly achieve the required result: Checkout responds quickly and pending invoices process after the worker recovers?
Queueing decouples front-end latency from downstream worker availability. The selected architecture is use durable Service Bus queue messages between the checkout and invoice services; confirm the result by checking that checkout responds quickly and pending invoices process after the worker recovers.
At-least-once message delivery requires application logic to deduplicate business side effects. The relevant requirement is: Checkout requests should return promptly while invoices are generated asynchronously with retry support.
Edge caching reduces origin load and latency for eligible cacheable content. The current need is: Checkout requests should return promptly while invoices are generated asynchronously with retry support.
Web PubSub provides managed WebSocket connection fan-out so application servers need not hold all client sessions. It does not solve the specified Queue asynchronous processing condition.
To validate the WAF decision logs deployment, reviewers revisit this operational need: The application firewall blocks legitimate requests but developers cannot see the matching rule. What result confirms it was met?
WAF rule and access diagnostics identify rule IDs and request outcomes that aggregate health metrics miss. Confirm using the measurable result: 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. Those observations validate AKS container diagnosis. They do not establish the required WAF decision logs result: A blocked test request identifies its matching WAF rule and client context in the destination logs.
Action groups define notifications and automated responses and can be reused by alert rules. The Notification routing test checks a simulated critical alert pages the incident team while a capacity warning sends email only; the relevant outcome is A blocked test request identifies its matching WAF rule and client context in the destination logs.
Lighthouse enables delegated management across tenants without relocating customer-owned resources. The offered observation would demonstrate Cross-tenant operations: Authorized MSP operators view the delegated customer's resource health from their managing tenant. The current validation is different: A blocked test request identifies its matching WAF rule and client context in the destination logs.
Architecture review: Peering nontransitivity and Hub-spoke topology. Requirement A: Spoke A peers with the hub and spoke B peers with the same hub but cannot communicate directly. Requirement B: Many app VNets need shared DNS firewall and on-prem connectivity without each owning a gateway. Which complete two-part proposal satisfies both constraints?
For requirement A, vNet peering alone is not transitive and forwarding needs explicit architecture. For requirement B, a hub centralizes connectivity services while spoke VNets isolate applications. Verify both independently: Permitted spoke-to-spoke traffic follows inspected hub path and denied traffic fails; A spoke accesses approved hub services and another spoke only through authorized routing.
VNet peering alone is not transitive and forwarding needs explicit architecture. A hub centralizes connectivity services while spoke VNets isolate applications. The proposed steps (deploy Azure VPN Gateway site-to-site tunnels with matching local/remote IPsec settings; evaluate Azure Virtual WAN secured virtual hubs and routing intent) address other capabilities instead of this required pair.
A hub centralizes connectivity services while spoke VNets isolate applications. The other proposed action (deploy Azure VPN Gateway site-to-site tunnels with matching local/remote IPsec settings) does not implement the first control. VNet peering alone is not transitive and forwarding needs explicit architecture.
VNet peering alone is not transitive and forwarding needs explicit architecture. The other proposed action (evaluate Azure Virtual WAN secured virtual hubs and routing intent) addresses a different operation. A hub centralizes connectivity services while spoke VNets isolate applications.
The target environment adopts this approach for Azure service health: Create Service Health alerts scoped to affected subscriptions and services. What property makes it suitable?
Service Health reports Azure platform incidents and planned maintenance relevant to a subscription. It is material here because a regional Azure platform incident affects databases but project teams have no subscription-specific warning.
A log search alert can evaluate aggregated matching records instead of only raw metric time series. Service Health reports Azure platform incidents and planned maintenance relevant to a subscription.
DCRs specify collected streams destinations and transformations for supported agent sources. Service Health reports Azure platform incidents and planned maintenance relevant to a subscription.
Dynamic thresholds adapt alert boundaries to historical metric patterns after sufficient data exists. It belongs to Dynamic baseline alerts. The stated architecture instead relies on: Service Health reports Azure platform incidents and planned maintenance relevant to a subscription.
The target environment adopts this approach for Traffic Manager DNS routing: Consider Azure Traffic Manager with priority/performance routing and endpoint monitoring. What property makes it suitable?
Traffic Manager is DNS-based and clients connect directly to the returned service endpoint. It is material here because a TCP application requires global endpoint selection using DNS without a global L7 reverse proxy.
PDBs constrain voluntary disruptions but do not prevent all involuntary failures. Traffic Manager is DNS-based and clients connect directly to the returned service endpoint.
Multi-region writes allow eligible regions to accept writes but require handling conflicts. Traffic Manager is DNS-based and clients connect directly to the returned service endpoint.
GZRS synchronously spreads primary copies across zones and asynchronously replicates to another region. That statement describes Blob GZRS durability, while the question asks how Traffic Manager DNS routing works: Traffic Manager is DNS-based and clients connect directly to the returned service endpoint.
DBAs need CPU, DTU/vCore, wait and query performance evidence before changing the tier. An engineer must deliver the following acceptance evidence: Top resource-consuming queries and resource-limit events are visible during peak load. What design choice is defensible?
Query and resource telemetry helps distinguish costly queries from insufficient database compute. The selected architecture is use Azure SQL query performance insight and Azure Monitor metrics/diagnostics; confirm the result by checking that top resource-consuming queries and resource-limit events are visible during peak load.
Migration assessment identifies blockers and target-fit issues before a cutover. The current need is: DBAs need CPU, DTU/vCore, wait and query performance evidence before changing the tier.
Pooling reuses connections and reduces setup overhead relative to per-request creation. It does not solve the specified SQL database monitoring condition.
Read replicas offload eligible read-only queries but are asynchronously updated from the writer. The relevant requirement is: DBAs need CPU, DTU/vCore, wait and query performance evidence before changing the tier.
To validate the Control-plane audit deployment, reviewers revisit this operational need: A tenant auditor needs subscription-level records for resource create and delete operations, not VM guest logs. What result confirms it was met?
The Activity Log records Azure Resource Manager control-plane events independent of guest agents. Confirm using the measurable result: A denied deployment and a successful resource deletion appear with caller and operation name.
Event Hubs provides durable high-throughput event ingestion for downstream stream consumers. The distinguishing check is: A denied deployment and a successful resource deletion appear with caller and operation name.
A workspace can aggregate resource telemetry across subscription boundaries when access and diagnostic routing are configured. The Cross-subscription workspace test checks the same query returns events labeled with all four source subscription IDs; the relevant outcome is A denied deployment and a successful resource deletion appear with caller and operation name.
DeployIfNotExists can evaluate related configurations and deploy missing compliant resources with appropriate permissions. The offered observation would demonstrate Automated diagnostics policy: A newly provisioned supported storage account gets the intended diagnostics after policy remediation. The current validation is different: A denied deployment and a successful resource deletion appear with caller and operation name.
Architecture rationale review—Blob inventory: Configure Azure Storage Blob Inventory reports. Which explanation accurately distinguishes this capability?
Blob Inventory produces scheduled object inventories without crawling each object individually. It is material here because operations needs a weekly manifest of millions of blobs with properties and access tiers.
A user-delegation SAS is authorized through Entra credentials and avoids distributing account keys. Blob Inventory produces scheduled object inventories without crawling each object individually.
Blob Storage manages massively scalable object data rather than SMB-compatible shared volumes. Blob Inventory produces scheduled object inventories without crawling each object individually.
Blob change feed records changes to blob objects for downstream processing. It belongs to Blob change feed. The stated architecture instead relies on: Blob Inventory produces scheduled object inventories without crawling each object individually.
The target environment adopts this approach for Disk snapshot consistency: Use application-consistent backup or coordinated snapshot mechanisms rather than uncoordinated disk copies. What property makes it suitable?
Independent crash-consistent snapshots may not preserve database write ordering across disks. It is material here because a multi-disk database VM needs a rollback that does not corrupt an in-flight transaction.
Compute replication does not automatically guarantee complete application network reachability. Independent crash-consistent snapshots may not preserve database write ordering across disks.
Managed PostgreSQL backups support rebuilding a server at a selected valid recovery time. Independent crash-consistent snapshots may not preserve database write ordering across disks.
Geo-restore is backup-based recovery with different RTO/RPO than active geo-replication. It belongs to SQL geo-restore. The stated architecture instead relies on: Independent crash-consistent snapshots may not preserve database write ordering across disks.
A user can view a storage account resource but cannot download its blobs. Which Azure architecture would most directly achieve the required result: The user downloads an approved blob without gaining storage management privileges?
Management-plane Azure RBAC Reader does not automatically authorize blob data-plane reads. The selected architecture is assign an appropriate Blob Data Reader role rather than only management-plane Reader; confirm the result by checking that the user downloads an approved blob without gaining storage management privileges.
Key Vault RBAC data permissions differ from vault resource-management permissions. The current need is: A user can view a storage account resource but cannot download its blobs.
Key Vault secrets support controlled retrieval and rotation separate from packaged application code. Its design target is Key Vault secrets. The stated requirement instead concerns: A user can view a storage account resource but cannot download its blobs.
Azure SQL supports Entra authentication and compatible managed identities can eliminate stored SQL secrets. It does not solve the specified Resource RBAC versus data access condition.
Please check your mailbox for a message from support@examlabs.com and follow the directions.