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
For Dedicated host, operations are closing a change that addressed: A regulated app requires a physically dedicated server host for VM placement and host-level isolation. Which post-change signal belongs in the acceptance record?
Dedicated Host provides physical host isolation with separate placement and pricing controls. Confirm using the measurable result: The deployed VMs are listed on the reserved dedicated host.
Confidential VMs use hardware-backed protection for sensitive guest execution environments. Those observations validate Confidential VM. They do not establish the required Dedicated host result: The deployed VMs are listed on the reserved dedicated host.
ASE provides dedicated App Service hosting in a customer virtual-network environment. The distinguishing check is: The deployed VMs are listed on the reserved dedicated host.
General-purpose VMs balance CPU and memory while retaining OS-level control. The General purpose VM test checks the workload runs its required driver within the provisioned compute budget; the relevant outcome is The deployed VMs are listed on the reserved dedicated host.
A solution must address both Rebuild cloud native and Physical server migration. First requirement: An obsolete application codebase has no maintainable runtime and must use current cloud services. 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 Rebuild cloud native half of this two-part design, rebuild replaces the application rather than merely moving its binaries. Verify: The new app meets functional acceptance while retiring the unsupported runtime. 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 Rebuild cloud native.
Replatforming changes hosting characteristics while preserving most app behavior. That plan is appropriate for Replatform database. The two controls sought here are Rebuild cloud native and Physical server migration.
Retiring unused assets reduces migration risk and cloud cost rather than copying unnecessary VMs. The corresponding task is Retire unused services: An application inventory shows unused servers with no business owner or dependent traffic. It is not one of the two requested controls (Rebuild cloud native and Physical server migration).
Hidden dependencies can break after migration even when VM replication succeeds. That plan is appropriate for Application dependency mapping. The two controls sought here are Rebuild cloud native and Physical server migration.
A solution must address both AKS availability zones and Application Gateway zone redundancy. First requirement: A production AKS cluster requires pods and nodes across three availability zones. Second requirement: A web workload requires HTTP routing and WAF across availability zones. Select TWO recommendations that meet these independent needs.
For the Application Gateway zone redundancy half of this design, application Gateway offers L7 proxy capabilities with WAF unlike a basic L4 load balancer. Check: The gateway keeps HTTP traffic flowing when a backend zone is unavailable. The other half concerns AKS availability zones.
For the AKS availability zones half of this two-part design, zone-distributed nodes plus suitable Kubernetes scheduling reduce single-zone concentration. Verify: After a simulated zone failure, surviving pods maintain API availability and replacement replicas become Ready within the tested recovery window on healthy-zone nodes. The other half concerns Application Gateway zone redundancy.
Load Balancer routes TCP/UDP flows to healthy backends without terminating HTTP requests. Its own validation would be: Failed backend probes remove one instance and healthy zonal instances continue serving. The current paired requirement is AKS availability zones and Application Gateway zone redundancy.
PDBs constrain voluntary disruptions but do not prevent all involuntary failures. This alternative solves AKS pod disruption budget, while the question separately requires AKS availability zones and Application Gateway zone redundancy.
Failover-group listeners abstract the primary location during regional failover. That plan is appropriate for SQL failover groups HA. The two controls sought here are AKS availability zones and Application Gateway zone redundancy.
A solution must address both Blob change feed and Blob object storage. First requirement: An integration service needs an ordered log of changes to objects without scanning containers every minute. Second requirement: A media service stores millions of image and video objects accessed through REST without a shared file system. Select TWO recommendations that meet these independent needs.
For the Blob change feed half of this two-part design, blob change feed records changes to blob objects for downstream processing. Verify: The consumer reads expected object creation and deletion change records. The other half concerns Blob object storage.
For the Blob object storage half of this design, Blob Storage manages massively scalable object data rather than SMB-compatible shared volumes. Check: A client uploads and downloads an object using its scoped authorization. The other half concerns Blob change feed.
Session consistency offers read-your-writes within a session without strong global consistency. This alternative solves Cosmos session consistency, while the question separately requires Blob change feed and Blob object storage.
Tiering trades storage price against access and retrieval cost based on usage. The corresponding task is Blob hot/cool/cold: A log archive sees frequent access for a month and rare access afterward. It is not one of the two requested controls (Blob change feed and Blob object storage).
Bounded staleness constrains replication read lag according to allowed versions/time. This alternative solves Cosmos bounded staleness, while the question separately requires Blob change feed and Blob object storage.
A rollout addressing App registration API scopes has reached acceptance testing. The original problem was: A backend API should expose delegated scopes to a client on behalf of a signed-in user. Which finding verifies its resolution?
Delegated permissions represent what an application can do on behalf of an authenticated user. Confirm using the measurable result: The API token contains the required scope and access without that scope is rejected.
Administrative units scope eligible directory management roles to selected objects, not data visibility. Those observations validate Delegation with admin units. They do not establish the required App registration API scopes result: The API token contains the required scope and access without that scope is rejected.
Azure SQL supports Entra authentication and compatible managed identities can eliminate stored SQL secrets. The Passwordless app connection test checks the workload queries its database with an Entra token and rotation of the former password has no effect; the relevant outcome is The API token contains the required scope and access without that scope is rejected.
App-only permissions grant service principal operations without a delegated signed-in user. The offered observation would demonstrate Application permissions: The service obtains an app-only token and performs only the approved Graph actions. The current validation is different: The API token contains the required scope and access without that scope is rejected.
A financial application requires consistent outputs during migration before stopping the old deployment. An architecture board will approve a solution only if this outcome is demonstrated: The reconciled reports match while controlled rollback remains available. What should be selected?
Parallel operation compares business outputs before committing the cutover. The selected architecture is run old and new environments in a controlled parallel validation phase with consistency checks; confirm the result by checking that the reconciled reports match while controlled rollback remains available.
Replatforming changes hosting characteristics while preserving most app behavior. That is useful for Replatform database (A SQL application can move to managed SQL with a few configuration changes but needs no redesign). It does not meet the current Parallel-run cutover requirement: A financial application requires consistent outputs during migration before stopping the old deployment.
Sizing, licensing and consumption assumptions materially affect target economics. The relevant requirement is: A financial application requires consistent outputs during migration before stopping the old deployment.
Online migration reduces cutover downtime by applying ongoing changes after the baseline copy. It does not solve the specified Parallel-run cutover condition.
After copying storage objects the team assumes file count equality proves complete accuracy. The acceptance test is: Checksums, timestamps and access checks reconcile source and destination. Which design recommendation best satisfies both?
Object count alone cannot establish content integrity or ACL preservation. The selected architecture is validate file hashes, metadata and permissions against a migration manifest; confirm the result by checking that checksums, timestamps and access checks reconcile source and destination.
Rehosting prioritizes speed and minimal code changes over immediate PaaS modernization. It does not solve the specified Storage migration validation condition.
Retiring unused assets reduces migration risk and cloud cost rather than copying unnecessary VMs. The current need is: After copying storage objects the team assumes file count equality proves complete accuracy.
Hidden dependencies can break after migration even when VM replication succeeds. That is useful for Application dependency mapping (A business app appears self-contained but batch jobs communicate with undocumented on-prem systems). It does not meet the current Storage migration validation requirement: After copying storage objects the team assumes file count equality proves complete accuracy.
Architecture review: Blob operational backup and Blob vaulted backup. Requirement A: Blob containers need protection against accidental deletion and malicious modification over a short operational window. Requirement B: Compliance requires offsite protected copies of blob data separate from only operational object versioning. Which complete two-part proposal satisfies both constraints?
For requirement A, blob operational backup relies on point-in-time object protection features rather than VM-level backups. For requirement B, vaulted blob backup supplies protected backup storage with different capabilities than operational backups. Verify both independently: A deleted supported blob is restored to the requested prior point in the configured interval; An eligible blob recovery point is restored using the protected vault workflow.
The option covers one requirement but substitutes Azure VM backup policy for Blob vaulted backup. The missing acceptance result is: An eligible blob recovery point is restored using the protected vault workflow.
Blob operational backup relies on point-in-time object protection features rather than VM-level backups. Vaulted blob backup supplies protected backup storage with different capabilities than operational backups. The proposed steps (use Cosmos DB continuous backup mode with appropriate restore capabilities; protect the VM with Azure Backup using a supported vault and retention policy) address other capabilities instead of this required pair.
Vaulted blob backup supplies protected backup storage with different capabilities than operational backups. The other proposed action (use Cosmos DB continuous backup mode with appropriate restore capabilities) does not implement the first control. Blob operational backup relies on point-in-time object protection features rather than VM-level backups.
A proposed solution for Identity-signin monitoring is: Export supported Microsoft Entra sign-in logs using diagnostic settings to the approved workspace. Select the strongest statement supporting the recommendation.
Entra diagnostic export makes identity sign-in events available for central retention and KQL correlation. It is material here because security analysts require long-term sign-in analysis alongside cloud resource diagnostics.
The Activity Log records Azure Resource Manager control-plane events independent of guest agents. Entra diagnostic export makes identity sign-in events available for central retention and KQL correlation.
VM insights and the agent collect supported guest operating-system counters and process data. It belongs to VM guest performance. The stated architecture instead relies on: Entra diagnostic export makes identity sign-in events available for central retention and KQL correlation.
Application Insights correlates application requests exceptions and downstream dependencies rather than relying only on infrastructure CPU. Entra diagnostic export makes identity sign-in events available for central retention and KQL correlation.
The team has justified its PostgreSQL flexible server design with: Select Azure Database for PostgreSQL Flexible Server and verify extension availability. Which statement accurately describes why the approach works?
Flexible Server offers managed open-source PostgreSQL with supported extensions and deployment options. It is material here because an application depends on PostgreSQL extensions and wants managed PostgreSQL without a VM.
Partition elimination and aligned indexes can reduce scans when predicates match partition keys. That statement describes SQL database partitioning, while the question asks how PostgreSQL flexible server works: Flexible Server offers managed open-source PostgreSQL with supported extensions and deployment options.
Active geo-replication creates readable asynchronously updated secondary databases while primary remains writable. Flexible Server offers managed open-source PostgreSQL with supported extensions and deployment options.
Managed SQL compute tiers can scale resources but scaling may have operational consequences. Flexible Server offers managed open-source PostgreSQL with supported extensions and deployment options.
Managers need quarterly evidence that external guest access to privileged applications is still justified. An engineer must deliver the following acceptance evidence: A rejected guest review removes the corresponding app assignment after the review closes. What design choice is defensible?
Access reviews periodically recertify assigned access and can remove access for denied reviews. The selected architecture is run Microsoft Entra access reviews with suitable reviewers and removal actions; confirm the result by checking that a rejected guest review removes the corresponding app assignment after the review closes.
Delegated permissions represent what an application can do on behalf of an authenticated user. Its design target is App registration API scopes. The stated requirement instead concerns: Managers need quarterly evidence that external guest access to privileged applications is still justified.
PIM can time-bound eligible role activation with approvals MFA and justification. The relevant requirement is: Managers need quarterly evidence that external guest access to privileged applications is still justified.
Management locks guard against accidental resource deletes and operate separately from authorization roles. It does not solve the specified Identity lifecycle audits condition.
Please check your mailbox for a message from support@examlabs.com and follow the directions.