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: Azure Cache for Redis session and App Configuration feature flags. Requirement A: A scaled-out web app stores user sessions on individual workers and loses sessions on failover. Requirement B: Operators must turn a feature on for a pilot group without rebuilding application binaries. Which complete two-part proposal satisfies both constraints?
For requirement A, shared session state survives an individual stateless app worker replacement. For requirement B, app Configuration centralizes feature settings; secrets should remain in Key Vault. Verify both independently: The user session persists after a web worker is intentionally removed; Pilot users see the feature after refresh and others retain the previous behavior.
The mismatched half is Event Hubs telemetry; App Configuration feature flags instead needs: Store nonsecret feature flags in Azure App Configuration with app-side refresh.
The option covers one requirement but substitutes Event Grid notification for Azure Cache for Redis session. The missing acceptance result is: The user session persists after a web worker is intentionally removed.
Shared session state survives an individual stateless app worker replacement. App Configuration centralizes feature settings; secrets should remain in Key Vault. The proposed steps (use Event Grid as an event routing and notification mechanism; use Event Hubs partitions and consumer groups for streaming ingestion) address other capabilities instead of this required pair.
A solution must address both Parallel-run cutover and VM agentless migration. First requirement: A financial application requires consistent outputs during migration before stopping the old deployment. Second requirement: VMware VMs need replicated migration to Azure with a controlled cutover and minimal app redesign. Select TWO recommendations that meet these independent needs.
For the VM agentless migration half of this design, server migration replication supports lift-and-shift of eligible VM workloads to Azure. Check: A test migration boots the replicated VM and validates application dependencies. The other half concerns Parallel-run cutover.
For the Parallel-run cutover half of this two-part design, parallel operation compares business outputs before committing the cutover. Verify: The reconciled reports match while controlled rollback remains available. The other half concerns VM agentless migration.
Online migration reduces cutover downtime by applying ongoing changes after the baseline copy. The corresponding task is SQL online migration: A high-volume database allows little cutover downtime and must synchronize changes before switch. It is not one of the two requested controls (Parallel-run cutover and VM agentless 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 Parallel-run cutover and VM agentless migration.
Replatforming changes hosting characteristics while preserving most app behavior. This alternative solves Replatform database, while the question separately requires Parallel-run cutover and VM agentless migration.
The team has justified its Modernization cost assessment design with: Use Azure Migrate cost estimates and Well-Architected cost optimization assessment. Which statement accurately describes why the approach works?
Sizing, licensing and consumption assumptions materially affect target economics. It is material here because a migration project chooses premium PaaS services without considering steady-state usage and license rights.
DNS cutover requires propagation and dependency planning independent of VM replication. Sizing, licensing and consumption assumptions materially affect target economics.
Target compatibility determines whether code changes or a different managed target are required. It belongs to Database schema assessment. The stated architecture instead relies on: Sizing, licensing and consumption assumptions materially affect target economics.
File Sync preserves local namespace access while synchronizing with Azure file shares. Sizing, licensing and consumption assumptions materially affect target economics.
A rollout addressing SQL Server on Azure VM has reached acceptance testing. The original problem was: A database application depends on a third-party kernel-level driver installed alongside SQL Server. Which finding verifies its resolution?
IaaS retains operating-system and SQL instance control that PaaS databases do not provide. Confirm using the measurable result: The vendor driver runs on the VM while maintenance responsibilities are explicitly assigned.
Serverless compute can scale usage and pause eligible databases to reduce idle cost. The SQL serverless idle cost test checks compute charges drop during idle periods and the test workload resumes within tolerated delay; the relevant outcome is The vendor driver runs on the VM while maintenance responsibilities are explicitly assigned.
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: The vendor driver runs on the VM while maintenance responsibilities are explicitly assigned.
Flexible Server provides managed MySQL compute storage and backups. Those observations validate MySQL managed service. They do not establish the required SQL Server on Azure VM result: The vendor driver runs on the VM while maintenance responsibilities are explicitly assigned.
Executives expect a nightly VM backup to meet a five-minute regional recovery target. Which Azure architecture would most directly achieve the required result: The DR drill meets recovery objectives while backup restore still supports historical rollback?
Nightly backups alone do not provide continuous workload replication or low recovery time. The selected architecture is use replicated disaster recovery architecture and separately retain backups for point-in-time recovery; confirm the result by checking that the DR drill meets recovery objectives while backup restore still supports historical rollback.
LTR retains selected full backups over years rather than only the standard short PITR window. Its design target is SQL long-term recovery. The stated requirement instead concerns: Executives expect a nightly VM backup to meet a five-minute regional recovery target.
Independent crash-consistent snapshots may not preserve database write ordering across disks. It does not solve the specified Backup versus DR condition.
RTO is the maximum acceptable restoration duration, not the amount of lost data. That is useful for Recovery time objective (A payment system must resume in thirty minutes after a regional outage). It does not meet the current Backup versus DR requirement: Executives expect a nightly VM backup to meet a five-minute regional recovery target.
The acceptance criterion for VM scale set autoscaling comes from this issue: Demand for a stateless API swings by 10x and manual provisioning causes downtime. Which measured outcome is the strongest proof?
VMSS can add or remove similarly configured VM instances based on supported signals. Confirm using the measurable result: Traffic spikes scale instances out and scale-in does not lose persistent session state.
ZRS synchronously replicates data across primary-region zones. The offered observation would demonstrate Blob ZRS availability: Reading and writing a test blob continues while one zone is unavailable. The current validation is different: Traffic spikes scale instances out and scale-in does not lose persistent session state.
Traffic Manager is DNS-based and clients connect directly to the returned service endpoint. Those observations validate Traffic Manager DNS routing. They do not establish the required VM scale set autoscaling result: Traffic spikes scale instances out and scale-in does not lose persistent session state.
Eligible App Service plans distribute app workers across availability zones with sufficient capacity. The distinguishing check is: Traffic spikes scale instances out and scale-in does not lose persistent session state.
A dev/test SQL database is idle for long periods but bursts during a short daily test window. Choose the architecture that can be validated by this result: Compute charges drop during idle periods and the test workload resumes within tolerated delay.
Serverless compute can scale usage and pause eligible databases to reduce idle cost. The selected architecture is consider Azure SQL Database serverless compute with auto-pause eligibility checks; confirm the result by checking that compute charges drop during idle periods and the test workload resumes within tolerated delay.
Query and resource telemetry helps distinguish costly queries from insufficient database compute. It does not solve the specified SQL serverless idle cost condition.
CMK encryption protects database data at rest while keys are managed under customer control. Its design target is SQL customer-managed keys. The stated requirement instead concerns: A dev/test SQL database is idle for long periods but bursts during a short daily test window.
Elastic pools share resources across independent databases with non-synchronized demand. The relevant requirement is: A dev/test SQL database is idle for long periods but bursts during a short daily test window.
For External B2B partner, operations are closing a change that addressed: A supplier must access a specific application without becoming an employee in the home tenant. Which post-change signal belongs in the acceptance record?
B2B collaboration supports guest principals and cross-organization access controls. Confirm using the measurable result: The supplier opens the assigned application but cannot access unrelated tenant resources.
Managed identities provide Entra tokens to supported workloads while data-plane RBAC grants the actual blob permissions. The Managed identity for App Service test checks a token-based read works and the app has no stored storage-account key; the relevant outcome is The supplier opens the assigned application but cannot access unrelated tenant resources.
Key Vault certificates support managed lifecycle and distribution to compatible Azure integrations. The offered observation would demonstrate Key Vault certificate lifecycle: The renewed certificate is used by the endpoint before the old certificate expires. The current validation is different: The supplier opens the assigned application but cannot access unrelated tenant resources.
Secure secret handling removes reusable credentials from source while preserving automation. Those observations validate Secrets in deployment pipeline. They do not establish the required External B2B partner result: The supplier opens the assigned application but cannot access unrelated tenant resources.
To validate the Managed Prometheus deployment, reviewers revisit this operational need: A Kubernetes platform emits Prometheus metrics and needs Azure-native managed scraping and Grafana dashboards. What result confirms it was met?
Managed Prometheus collects Prometheus-format metrics separately from traditional container log collection. Confirm using the measurable result: A PromQL dashboard graphs the selected container metric with the expected Kubernetes labels.
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 PromQL dashboard graphs the selected container metric with the expected Kubernetes labels.
Storage-based diagnostic archives and immutability serve compliance preservation rather than interactive KQL search. The offered observation would demonstrate Immutable evidence archive: A retained log blob rejects unauthorized deletion during its compliance retention window. The current validation is different: A PromQL dashboard graphs the selected container metric with the expected Kubernetes labels.
Service Health reports Azure platform incidents and planned maintenance relevant to a subscription. Those observations validate Azure service health. They do not establish the required Managed Prometheus result: A PromQL dashboard graphs the selected container metric with the expected Kubernetes labels.
A rollout addressing Immutable evidence archive has reached acceptance testing. The original problem was: Auditors require tamper-resistant retention of exported logs that are rarely queried. Which finding verifies its resolution?
Storage-based diagnostic archives and immutability serve compliance preservation rather than interactive KQL search. Confirm using the measurable result: A retained log blob rejects unauthorized deletion during its compliance retention window.
A log search alert can evaluate aggregated matching records instead of only raw metric time series. The offered observation would demonstrate Log anomaly alert: A controlled failed-login burst creates the specified log-query alert with source IP context. The current validation is different: A retained log blob rejects unauthorized deletion during its compliance retention window.
Managed Prometheus collects Prometheus-format metrics separately from traditional container log collection. The distinguishing check is: A retained log blob rejects unauthorized deletion during its compliance retention window.
Entra diagnostic export makes identity sign-in events available for central retention and KQL correlation. The Identity-signin monitoring test checks risky sign-ins can be queried with resource access events over the chosen time window; the relevant outcome is A retained log blob rejects unauthorized deletion during its compliance retention window.
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.
Please check your mailbox for a message from support@examlabs.com and follow the directions.