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 production app's manually changed resource settings diverge from the approved IaC template. An architecture board will approve a solution only if this outcome is demonstrated: The change report identifies manual drift and approved deployment restores the intended state. What should be selected?
Azure deployment what-if previews resource changes before applying a template. The selected architecture is use a what-if deployment comparison and controlled remediation for the declared configuration; confirm the result by checking that the change report identifies manual drift and approved deployment restores the intended state.
Workbooks provide interactive analytical reports rather than the policy enforcement mechanism itself. The current need is: A production app's manually changed resource settings diverge from the approved IaC template.
Subscriptions are billing and resource governance boundaries with independent quotas and RBAC assignment scopes. That is useful for Subscription isolation (A regulated subsidiary needs separate billing and policy boundaries from the parent business unit). It does not meet the current Deployment drift requirement: A production app's manually changed resource settings diverge from the approved IaC template.
Defender for Cloud aggregates recommendations and compliance state for supported frameworks. It does not solve the specified Deployment drift condition.
Architecture review: Synapse serverless SQL and Data Factory hybrid copy. Requirement A: Data analysts must run ad hoc SQL queries over Parquet files in a data lake without provisioning a cluster. Requirement B: A nightly pipeline must copy on-premises SQL data to Azure Data Lake without opening an inbound corporate firewall port. Which complete two-part proposal satisfies both constraints?
For requirement A, serverless SQL queries external lake files with consumption-based query compute. For requirement B, self-hosted integration runtime initiates supported outbound communications to access private sources. Verify both independently: A SELECT reads the Parquet dataset with no dedicated SQL pool running; The scheduled copy reads on-premises data and lands it in the lake without inbound firewall exceptions.
One action is correct. The other targets Event Grid partner events, leaving Data Factory hybrid copy unsolved. Its necessary action is: Use Azure Data Factory with a self-hosted integration runtime and Copy activity.
This combines ADF tumbling window and Event Grid partner events, which do not satisfy the distinct requirements for Synapse serverless SQL and Data Factory hybrid copy.
The option covers one requirement but substitutes ADF tumbling window for Synapse serverless SQL. The missing acceptance result is: A SELECT reads the Parquet dataset with no dedicated SQL pool running.
A solution must address both PostgreSQL read replica and PostgreSQL flexible server. First requirement: An application uses PostgreSQL for writes but analysts overload the writer with complex read-only reports. Second requirement: An application depends on PostgreSQL extensions and wants managed PostgreSQL without a VM. Select TWO recommendations that meet these independent needs.
For the PostgreSQL flexible server half of this design, flexible Server offers managed open-source PostgreSQL with supported extensions and deployment options. Check: The required extension is available and the app connects without an OS-managed database host. The other half concerns PostgreSQL read replica.
For the PostgreSQL read replica half of this two-part design, read replicas offload eligible read-only queries but are asynchronously updated from the writer. Verify: The reports run on a replica while primary transaction performance improves. The other half concerns PostgreSQL flexible server.
Database-per-tenant provides a distinct security and backup boundary versus one shared schema. This alternative solves SQL schema isolation, while the question separately requires PostgreSQL read replica and PostgreSQL flexible server.
Business Critical uses a local SSD-oriented architecture with high availability replicas. The corresponding task is Business Critical SQL latency: A transaction-heavy database requires low latency local SSD and multiple synchronous replicas within the region. It is not one of the two requested controls (PostgreSQL read replica and PostgreSQL flexible server).
IaaS retains operating-system and SQL instance control that PaaS databases do not provide. That plan is appropriate for SQL Server on Azure VM. The two controls sought here are PostgreSQL read replica and PostgreSQL flexible server.
The acceptance criterion for Azure HPC design comes from this issue: A parallel scientific workload depends on low-latency internode communication and high-performance storage. Which measured outcome is the strongest proof?
HPC workloads require specialized low-latency fabric support beyond commodity VMs. Confirm using the measurable result: MPI benchmark meets its target communication latency across allocated nodes.
VMSS automates management and scaling of similar VMs in the same workload. The offered observation would demonstrate VMSS dynamic scaling: The scale set adds instances at load and returns to baseline under low demand. The current validation is different: MPI benchmark meets its target communication latency across allocated nodes.
ASE provides dedicated App Service hosting in a customer virtual-network environment. Those observations validate App Service isolation. They do not establish the required Azure HPC design result: MPI benchmark meets its target communication latency across allocated nodes.
App Service manages web hosting and supports deployment slots on eligible plans. The distinguishing check is: MPI benchmark meets its target communication latency across allocated nodes.
The target environment adopts this approach for Cost budgets: Configure Cost Management budgets and alert thresholds. What property makes it suitable?
Budgets monitor and notify about spending and do not automatically stop resources. It is material here because a department must be notified when cloud spend nears its monthly budget without terminating workloads.
Landing zones combine platform foundations with repeatable application subscription governance. Budgets monitor and notify about spending and do not automatically stop resources.
Management groups supply governance scope above subscriptions without moving resources into a single subscription. That statement describes Management group hierarchy, while the question asks how Cost budgets works: Budgets monitor and notify about spending and do not automatically stop resources.
Azure Policy can deny targeted resource types without revoking all contributor operations. Budgets monitor and notify about spending and do not automatically stop resources.
A proposed solution for VM guest performance is: Enable VM insights with the Azure Monitor Agent and appropriate data collection rule. Select the strongest statement supporting the recommendation.
VM insights and the agent collect supported guest operating-system counters and process data. It is material here because server owners need guest memory and disk performance for VMs rather than only host-level platform metrics.
Application Insights correlates application requests exceptions and downstream dependencies rather than relying only on infrastructure CPU. It belongs to Web transaction traces. The stated architecture instead relies on: VM insights and the agent collect supported guest operating-system counters and process data.
Container insights exposes Kubernetes workload health and container logs beyond generic virtual-machine statistics. That statement describes AKS container diagnosis, while the question asks how VM guest performance works: VM insights and the agent collect supported guest operating-system counters and process data.
Event Hubs provides durable high-throughput event ingestion for downstream stream consumers. VM insights and the agent collect supported guest operating-system counters and process data.
To validate the VNet peering deployment, reviewers revisit this operational need: Two Azure VNets in nearby regions need low-latency private connectivity without VPN gateways. What result confirms it was met?
Peering connects VNet address spaces through the Microsoft backbone without creating transitive routing by default. Confirm using the measurable result: Private IP traffic flows between the peered VNets with appropriate NSG permissions.
NAT Gateway provides outbound SNAT for supported subnet internet traffic. The NAT Gateway outbound test checks external partners observe only the approved outbound IP during simultaneous worker sessions; the relevant outcome is Private IP traffic flows between the peered VNets with appropriate NSG permissions.
Application Gateway provides regional Layer 7 reverse proxy and routing for private backends. The offered observation would demonstrate Application Gateway internal: Internal clients reach /api and /web paths through the private gateway and external clients cannot. The current validation is different: Private IP traffic flows between the peered VNets with appropriate NSG permissions.
Azure Load Balancer routes Layer 4 traffic inside a VNet without parsing HTTP URLs. The distinguishing check is: Private IP traffic flows between the peered VNets with appropriate NSG permissions.
An architect must sign off on Cost export. The business problem is: Finance must regularly ingest actual cloud cost details into a data warehouse for chargeback. What observed test result provides valid evidence?
Cost exports provide detailed recurring usage data for downstream allocation reporting. Confirm using the measurable result: A monthly export lands in the correct storage path with resource and cost fields.
Landing zones combine platform foundations with repeatable application subscription governance. The offered observation would demonstrate Landing zones: New app subscriptions start with baseline policies, connectivity and logging. The current validation is different: A monthly export lands in the correct storage path with resource and cost fields.
Azure Policy can deny targeted resource types without revoking all contributor operations. Those observations validate Resource type restriction. They do not establish the required Cost export result: A monthly export lands in the correct storage path with resource and cost fields.
Subscriptions are billing and resource governance boundaries with independent quotas and RBAC assignment scopes. The distinguishing check is: A monthly export lands in the correct storage path with resource and cost fields.
A solution must address both Rehost versus refactor and Physical server migration. First requirement: A legacy monolith must migrate within weeks with few code changes and no supported PaaS target. Second requirement: A legacy application runs on a physical Windows server and needs an IaaS move. Select TWO recommendations that meet these independent needs.
For the Rehost versus refactor half of this two-part design, rehosting prioritizes speed and minimal code changes over immediate PaaS modernization. Verify: The app runs on Azure VMs with unchanged interfaces before later refactoring. The other half concerns Physical server migration.
For the Physical server migration half of this design, physical migration requires source capture and replication methods different from VMware agentless VM migration. Check: A cutover VM starts in Azure with its application settings preserved. The other half concerns Rehost versus refactor.
Offline migration can simplify cutover when application downtime is acceptable. That plan is appropriate for SQL offline migration. The two controls sought here are Rehost versus refactor and Physical server migration.
Landing-zone foundations provide policy, connectivity and subscription placement for incoming workloads. Its own validation would be: The first migrated app uses approved network, DNS and access standards. The current paired requirement is Rehost versus refactor and Physical server migration.
Parallel operation compares business outputs before committing the cutover. This alternative solves Parallel-run cutover, while the question separately requires Rehost versus refactor and Physical server migration.
A department must be notified when cloud spend nears its monthly budget without terminating workloads. The acceptance test is: A threshold crossing issues notifications while the app remains running. Which design recommendation best satisfies both?
Budgets monitor and notify about spending and do not automatically stop resources. The selected architecture is configure Cost Management budgets and alert thresholds; confirm the result by checking that a threshold crossing issues notifications while the app remains running.
Azure Policy can deny targeted resource types without revoking all contributor operations. That is useful for Resource type restriction (A business unit must prevent unapproved public IP resources but permit private network components). It does not meet the current Cost budgets requirement: A department must be notified when cloud spend nears its monthly budget without terminating workloads.
Management groups supply governance scope above subscriptions without moving resources into a single subscription. Its design target is Management group hierarchy. The stated requirement instead concerns: A department must be notified when cloud spend nears its monthly budget without terminating workloads.
Landing zones combine platform foundations with repeatable application subscription governance. It does not solve the specified Cost budgets condition.
A solution must address both App Configuration feature flags and Web PubSub real time. First requirement: Operators must turn a feature on for a pilot group without rebuilding application binaries. Second requirement: A collaboration app must send real-time server-to-client notifications to many concurrent browsers. Select TWO recommendations that meet these independent needs.
For the Web PubSub real time half of this design, web PubSub provides managed WebSocket connection fan-out so application servers need not hold all client sessions. Check: Two connected clients immediately receive the authorized published event. The other half concerns App Configuration feature flags.
For the App Configuration feature flags half of this two-part design, app Configuration centralizes feature settings; secrets should remain in Key Vault. Verify: Pilot users see the feature after refresh and others retain the previous behavior. The other half concerns Web PubSub real time.
Queueing decouples front-end latency from downstream worker availability. This alternative solves Queue asynchronous processing, while the question separately requires App Configuration feature flags and Web PubSub real time.
Event Hubs provides a replayable ordered stream within partitions for large event volumes. The corresponding task is Event Hubs telemetry: Thousands of kiosks upload constant high-volume telemetry that several analytic consumers replay. It is not one of the two requested controls (App Configuration feature flags and Web PubSub real time).
Topics fan out a message to independently managed subscriptions with durable handling. That plan is appropriate for Publish subscribe topics. The two controls sought here are App Configuration feature flags and Web PubSub real time.
Please check your mailbox for a message from support@examlabs.com and follow the directions.