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 architect must sign off on Networking cutover DNS. The business problem is: A migrated app uses a new Azure IP but clients have a hardcoded old DNS endpoint. What observed test result provides valid evidence?
DNS cutover requires propagation and dependency planning independent of VM replication. Confirm using the measurable result: Clients resolve the new endpoint and the rollback procedure returns traffic if needed.
Target compatibility determines whether code changes or a different managed target are required. The Database schema assessment test checks the assessment reports blocking SQL features and chosen remediation before migration; the relevant outcome is Clients resolve the new endpoint and the rollback procedure returns traffic if needed.
Refactoring changes application structure and decouples independent workloads. The offered observation would demonstrate Refactor monolith: One service can scale independently and failures are isolated through messaging. The current validation is different: Clients resolve the new endpoint and the rollback procedure returns traffic if needed.
Server migration replication supports lift-and-shift of eligible VM workloads to Azure. Those observations validate VM agentless migration. They do not establish the required Networking cutover DNS result: Clients resolve the new endpoint and the rollback procedure returns traffic if needed.
Windows servers send performance counters that should differ by workload and environment. An engineer must deliver the following acceptance evidence: Production servers send approved counters while test servers omit the excluded stream. What design choice is defensible?
DCRs specify collected streams destinations and transformations for supported agent sources. The selected architecture is use Azure Monitor Agent data collection rules targeted through data collection rule associations; confirm the result by checking that production servers send approved counters while test servers omit the excluded stream.
Analytics and longer-term retention options have different query and storage cost characteristics. The relevant requirement is: Windows servers send performance counters that should differ by workload and environment.
Service Health reports Azure platform incidents and planned maintenance relevant to a subscription. It does not solve the specified Agent collection rules condition.
Storage-based diagnostic archives and immutability serve compliance preservation rather than interactive KQL search. That is useful for Immutable evidence archive (Auditors require tamper-resistant retention of exported logs that are rarely queried). It does not meet the current Agent collection rules requirement: Windows servers send performance counters that should differ by workload and environment.
Hundreds of tenant databases have peaks at different times and waste money with dedicated compute. A deployment must satisfy this operational criterion: Aggregated tenant peaks stay within pool limits at lower cost than individually overprovisioned databases. Which plan is appropriate?
Elastic pools share resources across independent databases with non-synchronized demand. The selected architecture is place eligible Azure SQL databases in an elastic pool with shared compute; confirm the result by checking that aggregated tenant peaks stay within pool limits at lower cost than individually overprovisioned databases.
Migration assessment identifies blockers and target-fit issues before a cutover. The current need is: Hundreds of tenant databases have peaks at different times and waste money with dedicated compute.
SQL auditing captures database events as configured separately from application request telemetry. It does not solve the specified SQL elastic pool condition.
Managed Instance supports many instance-scoped SQL Server capabilities with a managed service. The relevant requirement is: Hundreds of tenant databases have peaks at different times and waste money with dedicated compute.
A proposed solution for Key Vault cryptographic signing is: Use Azure Key Vault key operations with a suitable key type and access permissions. Select the strongest statement supporting the recommendation.
Key Vault keys can perform cryptographic operations while restricting private key exposure. It is material here because an application must sign payloads with a centrally controlled key without exporting its private material.
B2B collaboration supports guest principals and cross-organization access controls. That statement describes External B2B partner, while the question asks how Key Vault cryptographic signing works: Key Vault keys can perform cryptographic operations while restricting private key exposure.
Key Vault RBAC data permissions differ from vault resource-management permissions. Key Vault keys can perform cryptographic operations while restricting private key exposure.
Management locks guard against accidental resource deletes and operate separately from authorization roles. Key Vault keys can perform cryptographic operations while restricting private key exposure.
During technical sign-off for Azure Functions durable workflow, the architect selects: Use Durable Functions orchestration with proper idempotent activity design. Which underlying behavior should be documented?
Durable Functions manages stateful workflows over serverless function executions. It is material here because a workflow waits hours between steps while retaining orchestration state through restarts.
GPU instances provide accelerators not present on standard CPU-only VMs. That statement describes GPU VM, while the question asks how Azure Functions durable workflow works: Durable Functions manages stateful workflows over serverless function executions.
Confidential VMs use hardware-backed protection for sensitive guest execution environments. Durable Functions manages stateful workflows over serverless function executions.
General-purpose VMs balance CPU and memory while retaining OS-level control. It belongs to General purpose VM. The stated architecture instead relies on: Durable Functions manages stateful workflows over serverless function executions.
A rollout addressing MySQL managed service has reached acceptance testing. The original problem was: An existing MySQL application needs automated patching and backups with minimal database changes. Which finding verifies its resolution?
Flexible Server provides managed MySQL compute storage and backups. Confirm using the measurable result: The application retains its MySQL driver and PITR test succeeds.
Managed SQL compute tiers can scale resources but scaling may have operational consequences. Those observations validate SQL compute scaling. They do not establish the required MySQL managed service result: The application retains its MySQL driver and PITR test succeeds.
Read replicas offload eligible read-only queries but are asynchronously updated from the writer. The distinguishing check is: The application retains its MySQL driver and PITR test succeeds.
Elastic pools share resources across independent databases with non-synchronized demand. The SQL elastic pool test checks aggregated tenant peaks stay within pool limits at lower cost than individually overprovisioned databases; the relevant outcome is The application retains its MySQL driver and PITR test succeeds.
The ADLS ACLs review proposes: Configure suitable POSIX-style data lake ACLs and scope broader RBAC intentionally. Which Azure behavior is the technical justification for this decision?
Directory ACLs provide path-level data authorization when hierarchical namespace is enabled. It is material here because a Spark job has storage RBAC access at container level but must isolate sensitive folders.
NetApp Files offers enterprise file protocols and performance controls for supported workloads. Directory ACLs provide path-level data authorization when hierarchical namespace is enabled.
Cosmos DB provides a distributed document database with configurable consistency and throughput. It belongs to Cosmos DB NoSQL. The stated architecture instead relies on: Directory ACLs provide path-level data authorization when hierarchical namespace is enabled.
A user-delegation SAS is authorized through Entra credentials and avoids distributing account keys. Directory ACLs provide path-level data authorization when hierarchical namespace is enabled.
During technical sign-off for Cosmos bounded staleness, the architect selects: Evaluate Cosmos DB bounded staleness with configured K/T limits. Which underlying behavior should be documented?
Bounded staleness constrains replication read lag according to allowed versions/time. It is material here because a globally replicated document store accepts a known upper bound on read lag but not unbounded eventual lag.
Managed disks provide block storage to Azure VMs rather than object or SMB interfaces. It belongs to Azure managed disks. The stated architecture instead relies on: Bounded staleness constrains replication read lag according to allowed versions/time.
Partition key distribution governs data/throughput placement and query efficiency. Bounded staleness constrains replication read lag according to allowed versions/time.
Immutable storage prevents overwrite and delete during the configured retention interval. Bounded staleness constrains replication read lag according to allowed versions/time.
A proposed solution for Peering nontransitivity is: Design a routing/transit solution with a supported NVA or Azure Firewall where required. Select the strongest statement supporting the recommendation.
VNet peering alone is not transitive and forwarding needs explicit architecture. It is material here because spoke A peers with the hub and spoke B peers with the same hub but cannot communicate directly.
VPN Gateway can establish encrypted IPsec tunnels over public networks. VNet peering alone is not transitive and forwarding needs explicit architecture.
Private endpoints attach supported PaaS access to a private IP and require DNS resolution. VNet peering alone is not transitive and forwarding needs explicit architecture.
Route Server enables BGP exchange with NVAs without custom per-prefix UDR maintenance. It belongs to Route Server dynamic routing. The stated architecture instead relies on: VNet peering alone is not transitive and forwarding needs explicit architecture.
An architect must sign off on SQL online migration. The business problem is: A high-volume database allows little cutover downtime and must synchronize changes before switch. What observed test result provides valid evidence?
Online migration reduces cutover downtime by applying ongoing changes after the baseline copy. Confirm using the measurable result: Source and target reconcile and final cutover falls within the tolerated outage.
Hidden dependencies can break after migration even when VM replication succeeds. The offered observation would demonstrate Application dependency mapping: A test workload executes its dependent calls from the planned Azure subnet. The current validation is different: Source and target reconcile and final cutover falls within the tolerated outage.
Parallel operation compares business outputs before committing the cutover. Those observations validate Parallel-run cutover. They do not establish the required SQL online migration result: Source and target reconcile and final cutover falls within the tolerated outage.
AzCopy provides scripted high-throughput online transfers with resumability. The AzCopy online migration test checks the destination blob set and hashes match the source manifest; the relevant outcome is Source and target reconcile and final cutover falls within the tolerated outage.
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.
Please check your mailbox for a message from support@examlabs.com and follow the directions.