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 proposed solution for SQL serverless idle cost is: Consider Azure SQL Database serverless compute with auto-pause eligibility checks. Select the strongest statement supporting the recommendation.
Serverless compute can scale usage and pause eligible databases to reduce idle cost. It is material here because a dev/test SQL database is idle for long periods but bursts during a short daily test window.
Ledger records cryptographically verifiable tamper-evidence for supported relational tables. Serverless compute can scale usage and pause eligible databases to reduce idle cost.
Always Encrypted supports encryption and decryption in capable clients to reduce exposure to the database engine. Serverless compute can scale usage and pause eligible databases to reduce idle cost.
Active geo-replication creates readable asynchronously updated secondary databases while primary remains writable. It belongs to SQL geo-replication reporting. The stated architecture instead relies on: Serverless compute can scale usage and pause eligible databases to reduce idle cost.
Administrators must use phishing-resistant authentication for high-privilege cloud portal actions. Identify the most suitable implementation for an outcome where the admin can sign in with a compliant method and a weaker method is rejected.
Authentication strengths let Conditional Access require supported strong methods based on conditions. The selected architecture is apply a Conditional Access policy with an appropriate authentication strength to privileged roles; confirm the result by checking that the admin can sign in with a compliant method and a weaker method is rejected.
Managed identities provide Entra tokens to supported workloads while data-plane RBAC grants the actual blob permissions. It does not solve the specified Conditional MFA condition.
PIM can time-bound eligible role activation with approvals MFA and justification. The current need is: Administrators must use phishing-resistant authentication for high-privilege cloud portal actions.
Delegated permissions represent what an application can do on behalf of an authenticated user. That is useful for App registration API scopes (A backend API should expose delegated scopes to a client on behalf of a signed-in user). It does not meet the current Conditional MFA requirement: Administrators must use phishing-resistant authentication for high-privilege cloud portal actions.
A migration project chooses premium PaaS services without considering steady-state usage and license rights. Which Azure architecture would most directly achieve the required result: The approved target design includes measured compute, storage, network and license costs?
Sizing, licensing and consumption assumptions materially affect target economics. The selected architecture is use Azure Migrate cost estimates and Well-Architected cost optimization assessment; confirm the result by checking that the approved target design includes measured compute, storage, network and license costs.
DNS cutover requires propagation and dependency planning independent of VM replication. The current need is: A migration project chooses premium PaaS services without considering steady-state usage and license rights.
File Sync preserves local namespace access while synchronizing with Azure file shares. That is useful for Azure File Sync (A branch file server should retain local caching while most data moves to Azure Files). It does not meet the current Modernization cost assessment requirement: A migration project chooses premium PaaS services without considering steady-state usage and license rights.
Target compatibility determines whether code changes or a different managed target are required. It does not solve the specified Modernization cost assessment condition.
The team has justified its Backup versus DR design with: Use replicated disaster recovery architecture and separately retain backups for point-in-time recovery. Which statement accurately describes why the approach works?
Nightly backups alone do not provide continuous workload replication or low recovery time. It is material here because executives expect a nightly VM backup to meet a five-minute regional recovery target.
Soft delete retains recoverable protected backup data after deletion for a configured interval. It belongs to Backup soft delete. The stated architecture instead relies on: Nightly backups alone do not provide continuous workload replication or low recovery time.
Azure Backup creates managed recovery points distinct from continuously replicating a running VM. That statement describes Azure VM backup policy, while the question asks how Backup versus DR works: Nightly backups alone do not provide continuous workload replication or low recovery time.
Periodic backups produce interval snapshots and are not the same as continuous point-in-time recovery. Nightly backups alone do not provide continuous workload replication or low recovery time.
A solution must address both Recovery time objective and Recovery point objective. First requirement: A payment system must resume in thirty minutes after a regional outage. Second requirement: A business may lose at most five minutes of writes during failover. Select TWO recommendations that meet these independent needs.
For the Recovery time objective half of this two-part design, RTO is the maximum acceptable restoration duration, not the amount of lost data. Verify: A regional failover test restores business service in less than the allowed interval. The other half concerns Recovery point objective.
For the Recovery point objective half of this design, RPO measures the maximum tolerated data loss period at a recovery point. Check: Failover comparison shows the latest committed recoverable write is within five minutes. The other half concerns Recovery time objective.
Soft delete retains recoverable protected backup data after deletion for a configured interval. The corresponding task is Backup soft delete: An operator deletes a backup item by mistake and must recover its protected points before permanent purge. It is not one of the two requested controls (Recovery time objective and Recovery point objective).
Continuous backup can support point-in-time restore for supported Cosmos API accounts. That plan is appropriate for Cosmos continuous backup. The two controls sought here are Recovery time objective and Recovery point objective.
Blob operational backup relies on point-in-time object protection features rather than VM-level backups. Its own validation would be: A deleted supported blob is restored to the requested prior point in the configured interval. The current paired requirement is Recovery time objective and Recovery point objective.
Research jobs run thousands of independent parameter simulations and require queued pool-based compute. Choose the architecture that can be validated by this result: The submitted job fans out tasks and combines outputs after all simulations complete.
Azure Batch schedules large-scale parallel workloads across managed compute pools. The selected architecture is use Azure Batch pools, tasks and job orchestration; confirm the result by checking that the submitted job fans out tasks and combines outputs after all simulations complete.
HPC workloads require specialized low-latency fabric support beyond commodity VMs. The current need is: Research jobs run thousands of independent parameter simulations and require queued pool-based compute.
App Service manages web hosting and supports deployment slots on eligible plans. It does not solve the specified Azure Batch scheduling condition.
Dedicated Host provides physical host isolation with separate placement and pricing controls. Its design target is Dedicated host. The stated requirement instead concerns: Research jobs run thousands of independent parameter simulations and require queued pool-based compute.
To validate the Physical server migration deployment, reviewers revisit this operational need: A legacy application runs on a physical Windows server and needs an IaaS move. What result confirms it was met?
Physical migration requires source capture and replication methods different from VMware agentless VM migration. Confirm using the measurable result: A cutover VM starts in Azure with its application settings preserved.
Rebuild replaces the application rather than merely moving its binaries. Those observations validate Rebuild cloud native. They do not establish the required Physical server migration result: A cutover VM starts in Azure with its application settings preserved.
Landing-zone foundations provide policy, connectivity and subscription placement for incoming workloads. The distinguishing check is: A cutover VM starts in Azure with its application settings preserved.
Retiring unused assets reduces migration risk and cloud cost rather than copying unnecessary VMs. The Retire unused services test checks decommissioned workloads create no application dependency failure; the relevant outcome is A cutover VM starts in Azure with its application settings preserved.
Cluster upgrades evict all replicas of an API despite multiple healthy nodes. Which Azure architecture would most directly achieve the required result: A planned node drain leaves the minimum healthy pod count running?
PDBs constrain voluntary disruptions but do not prevent all involuntary failures. The selected architecture is define PodDisruptionBudgets and rollout replica strategies for the service; confirm the result by checking that a planned node drain leaves the minimum healthy pod count running.
Zone-distributed nodes plus suitable Kubernetes scheduling reduce single-zone concentration. It does not solve the specified AKS pod disruption budget condition.
Front Door provides global application delivery and HTTP(S) origin failover at the edge. Its design target is Front Door global failover. The stated requirement instead concerns: Cluster upgrades evict all replicas of an API despite multiple healthy nodes.
A zone-separated standby supports automated failover where offered. The relevant requirement is: Cluster upgrades evict all replicas of an API despite multiple healthy nodes.
Marketing assets should be delivered from regional edge nodes instead of a central origin. A deployment must satisfy this operational criterion: Measured image latency decreases after the edge cache warms. Which plan is appropriate?
Edge content distribution can cache static resources near users. The selected architecture is use a supported Azure CDN or Front Door static asset distribution approach; confirm the result by checking that measured image latency decreases after the edge cache warms.
Edge caching reduces origin load and latency for eligible cacheable content. Its design target is Azure Front Door caching. The stated requirement instead concerns: Marketing assets should be delivered from regional edge nodes instead of a central origin.
Event Grid distributes discrete source events to configured subscribers. It does not solve the specified CDN static content condition.
Central secret retrieval separates sensitive credentials from source and build artifacts. The current need is: Marketing assets should be delivered from regional edge nodes instead of a central origin.
Architecture rationale review—Application dependency mapping: Build a dependency map and classify blockers before sequencing migration waves. Which explanation accurately distinguishes this capability?
Hidden dependencies can break after migration even when VM replication succeeds. It is material here because a business app appears self-contained but batch jobs communicate with undocumented on-prem systems.
Refactoring changes application structure and decouples independent workloads. Hidden dependencies can break after migration even when VM replication succeeds.
Server migration replication supports lift-and-shift of eligible VM workloads to Azure. It belongs to VM agentless migration. The stated architecture instead relies on: Hidden dependencies can break after migration even when VM replication succeeds.
Online migration reduces cutover downtime by applying ongoing changes after the baseline copy. That statement describes SQL online migration, while the question asks how Application dependency mapping works: Hidden dependencies can break after migration even when VM replication succeeds.
An architect must sign off on General purpose VM. The business problem is: A legacy Windows service requires full OS control and custom drivers but has moderate CPU and memory needs. What observed test result provides valid evidence?
General-purpose VMs balance CPU and memory while retaining OS-level control. Confirm using the measurable result: The workload runs its required driver within the provisioned compute budget.
AKS provides managed Kubernetes control-plane hosting with configurable worker clusters. The distinguishing check is: The workload runs its required driver within the provisioned compute budget.
Spot instances offer lower-priced spare capacity without guaranteed availability. The Spot VM suitability test checks an eviction event restarts work from its last saved checkpoint on available capacity; the relevant outcome is The workload runs its required driver within the provisioned compute budget.
ACR stores OCI images and supports Azure identity-based authorization to the registry. The offered observation would demonstrate Container Registry: A pipeline pushes a signed image and production pulls it without shared registry passwords. The current validation is different: The workload runs its required driver within the provisioned compute budget.
Please check your mailbox for a message from support@examlabs.com and follow the directions.