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 program plans 100 app moves but lacks identity, DNS, governance and network foundations. Identify the most suitable implementation for an outcome where the first migrated app uses approved network, DNS and access standards.
Landing-zone foundations provide policy, connectivity and subscription placement for incoming workloads. The selected architecture is create an Azure landing zone before migration waves using CAF guidance; confirm the result by checking that the first migrated app uses approved network, DNS and access standards.
Physical migration requires source capture and replication methods different from VMware agentless VM migration. That is useful for Physical server migration (A legacy application runs on a physical Windows server and needs an IaaS move). It does not meet the current Migration landing zone requirement: A program plans 100 app moves but lacks identity, DNS, governance and network foundations.
Object count alone cannot establish content integrity or ACL preservation. Its design target is Storage migration validation. The stated requirement instead concerns: A program plans 100 app moves but lacks identity, DNS, governance and network foundations.
PostgreSQL migration requires extension, version and connectivity compatibility checks. It does not solve the specified Migration landing zone condition.
For the App deployment blue-green requirement, the proposed architecture uses: Use App Service deployment slots or equivalent supported blue-green routing. Why does that design fit?
Blue-green deployment preserves a prior known-good instance while testing a replacement. It is material here because a mission-critical API needs a low-risk deployment with rapid rollback of application code.
Durable Functions manages stateful workflows over serverless function executions. That statement describes Azure Functions durable workflow, while the question asks how App deployment blue-green works: Blue-green deployment preserves a prior known-good instance while testing a replacement.
App Service manages web hosting and supports deployment slots on eligible plans. Blue-green deployment preserves a prior known-good instance while testing a replacement.
Azure Batch schedules large-scale parallel workloads across managed compute pools. Blue-green deployment preserves a prior known-good instance while testing a replacement.
Before approving Storage bulk offline transfer, the reviewer assesses this requirement: A remote facility must move 500 TB to Azure but WAN bandwidth is too slow for the deadline. Which of the reported outcomes is decisive?
Physical data transfer can shorten initial bulk migration when network transfer is impractical. Confirm using the measurable result: The imported objects reconcile against checksums and manifests.
PostgreSQL migration requires extension, version and connectivity compatibility checks. The PostgreSQL migration test checks the database app passes read/write tests against the target flexible server; the relevant outcome is The imported objects reconcile against checksums and manifests.
Offline migration can simplify cutover when application downtime is acceptable. The offered observation would demonstrate SQL offline migration: The migrated database passes consistency checks before reopening writes. The current validation is different: The imported objects reconcile against checksums and manifests.
Hidden dependencies can break after migration even when VM replication succeeds. Those observations validate Application dependency mapping. They do not establish the required Storage bulk offline transfer result: The imported objects reconcile against checksums and manifests.
An on-prem estate has hundreds of VMs and architects need dependency-aware discovery before sizing Azure. An architecture board will approve a solution only if this outcome is demonstrated: Assessment lists discovered servers, interdependencies and estimated Azure sizing. What should be selected?
Azure Migrate inventories servers and supports readiness and sizing assessments. The selected architecture is run Azure Migrate discovery and assessment with dependency analysis where supported; confirm the result by checking that assessment lists discovered servers, interdependencies and estimated Azure sizing.
Offline migration can simplify cutover when application downtime is acceptable. The relevant requirement is: An on-prem estate has hundreds of VMs and architects need dependency-aware discovery before sizing Azure.
Physical data transfer can shorten initial bulk migration when network transfer is impractical. The current need is: An on-prem estate has hundreds of VMs and architects need dependency-aware discovery before sizing Azure.
PostgreSQL migration requires extension, version and connectivity compatibility checks. It does not solve the specified Azure Migrate inventory condition.
Architecture review: SQL geo-restore and Cross-region backup. Requirement A: A SQL database without an active geo-secondary needs disaster recovery from geo-redundant backups. Requirement B: An organization requires VM backup copies surviving the loss of an entire Azure region. Which complete two-part proposal satisfies both constraints?
For requirement A, geo-restore is backup-based recovery with different RTO/RPO than active geo-replication. For requirement B, geo-redundant vault storage can provide recovery copies in a paired region subject to feature settings. Verify both independently: A region-loss exercise recovers a database from the latest supported geo backup; A supported secondary-region restore yields the expected recovery point.
The option covers one requirement but substitutes Disk snapshot consistency for SQL geo-restore. The missing acceptance result is: A region-loss exercise recovers a database from the latest supported geo backup.
Geo-restore is backup-based recovery with different RTO/RPO than active geo-replication. Geo-redundant vault storage can provide recovery copies in a paired region subject to feature settings. The proposed steps (use application-consistent backup or coordinated snapshot mechanisms rather than uncoordinated disk copies; use Azure Backup soft delete with suitable retention and security settings) address other capabilities instead of this required pair.
The mismatched half is Backup soft delete; Cross-region backup instead needs: Select an appropriate geo-redundant backup vault and validate cross-region restore eligibility.
A multi-write-region Cosmos account can update the same logical item concurrently. The acceptance test is: A controlled simultaneous update resolves according to the documented business rule. Which design recommendation best satisfies both?
Concurrent writes require a conflict resolution policy to prevent unintended last-writer outcomes. The selected architecture is define supported multi-region conflict resolution strategy and concurrency controls; confirm the result by checking that a controlled simultaneous update resolves according to the documented business rule.
Managed disks provide block storage to Azure VMs rather than object or SMB interfaces. Its design target is Azure managed disks. The stated requirement instead concerns: A multi-write-region Cosmos account can update the same logical item concurrently.
Partition key distribution governs data/throughput placement and query efficiency. It does not solve the specified Cosmos conflict handling condition.
Service endpoints secure selected Azure service traffic from VNets but do not create a private IP for the PaaS service. The current need is: A multi-write-region Cosmos account can update the same logical item concurrently.
Architecture rationale review—NAT Gateway outbound: Attach a NAT Gateway to the worker subnet with the approved public IP resources. Which explanation accurately distinguishes this capability?
NAT Gateway provides outbound SNAT for supported subnet internet traffic. It is material here because a subnet-based worker fleet needs stable outbound public IPs without per-VM public IP addresses.
Network Watcher diagnostic tools identify effective network behavior and filtering decisions. That statement describes Network Watcher diagnosis, while the question asks how NAT Gateway outbound works: NAT Gateway provides outbound SNAT for supported subnet internet traffic.
A hub centralizes connectivity services while spoke VNets isolate applications. NAT Gateway provides outbound SNAT for supported subnet internet traffic.
Peering connects VNet address spaces through the Microsoft backbone without creating transitive routing by default. It belongs to VNet peering. The stated architecture instead relies on: NAT Gateway provides outbound SNAT for supported subnet internet traffic.
A rollout addressing Blob hot/cool/cold has reached acceptance testing. The original problem was: A log archive sees frequent access for a month and rare access afterward. Which finding verifies its resolution?
Tiering trades storage price against access and retrieval cost based on usage. Confirm using the measurable result: Old eligible blobs transition to the intended tier and remain retrievable.
Session consistency offers read-your-writes within a session without strong global consistency. The offered observation would demonstrate Cosmos session consistency: The writing session immediately reads its own update while other sessions may lag. The current validation is different: Old eligible blobs transition to the intended tier and remain retrievable.
Archive tier minimizes long-term storage cost but archived objects must be rehydrated before reading. The distinguishing check is: Old eligible blobs transition to the intended tier and remain retrievable.
An in-memory cache reduces repeated origin queries when staleness and invalidation are controlled. The Azure Cache for Redis test checks cache hits reduce SQL query volume and expired entries refresh correctly; the relevant outcome is Old eligible blobs transition to the intended tier and remain retrievable.
An architect must sign off on Azure Files identity access. The business problem is: Windows clients must access Azure Files using on-premises AD identities and SMB permissions. What observed test result provides valid evidence?
Azure Files can integrate with supported directory-based SMB authentication while share and NTFS ACLs govern access. Confirm using the measurable result: Approved domain users mount the share and unauthorized users fail the access test.
External ID consumer capabilities support customer journeys distinct from employee workforce governance. Those observations validate Consumer sign-in. They do not establish the required Azure Files identity access result: Approved domain users mount the share and unauthorized users fail the access test.
Access reviews periodically recertify assigned access and can remove access for denied reviews. The distinguishing check is: Approved domain users mount the share and unauthorized users fail the access test.
App-only permissions grant service principal operations without a delegated signed-in user. The Application permissions test checks the service obtains an app-only token and performs only the approved Graph actions; the relevant outcome is Approved domain users mount the share and unauthorized users fail the access test.
A rollout addressing Azure SQL zone redundancy has reached acceptance testing. The original problem was: A transactional SQL database must withstand a full zone failure with minimal manual intervention. Which finding verifies its resolution?
Zone redundancy spreads eligible database availability replicas across zones. Confirm using the measurable result: A zone failure does not permanently interrupt application database access.
Fault injection tests whether resilience patterns work under realistic failure conditions. The distinguishing check is: A zone failure does not permanently interrupt application database access.
Application Gateway offers L7 proxy capabilities with WAF unlike a basic L4 load balancer. The Application Gateway zone redundancy test checks the gateway keeps HTTP traffic flowing when a backend zone is unavailable; the relevant outcome is A zone failure does not permanently interrupt application database access.
Availability zones isolate infrastructure failure domains within an enabled region. Those observations validate Availability zones for VM tier. They do not establish the required Azure SQL zone redundancy result: A zone failure does not permanently interrupt application database access.
Before approving Subscription isolation, the reviewer assesses this requirement: A regulated subsidiary needs separate billing and policy boundaries from the parent business unit. Which of the reported outcomes is decisive?
Subscriptions are billing and resource governance boundaries with independent quotas and RBAC assignment scopes. Confirm using the measurable result: The subsidiary's budget and policy reports stay distinct from the parent.
Azure deployment what-if previews resource changes before applying a template. The Deployment drift test checks the change report identifies manual drift and approved deployment restores the intended state; the relevant outcome is The subsidiary's budget and policy reports stay distinct from the parent.
RBAC assignments inherit downward so narrower scope reduces unintended changes. The offered observation would demonstrate Role assignment scope: The engineer can change the assigned network group but not another group's resources. The current validation is different: The subsidiary's budget and policy reports stay distinct from the parent.
Budgets monitor and notify about spending and do not automatically stop resources. Those observations validate Cost budgets. They do not establish the required Subscription isolation result: The subsidiary's budget and policy reports stay distinct from the parent.
Please check your mailbox for a message from support@examlabs.com and follow the directions.