Question 900
Workload context: A retailer has dozens of coupled applications and needs migration waves ordered by shared database, network and identity dependencies. The implemented remedy is: Use discovered application dependency maps to group cutover waves with tested inter-service connectivity and rollback. Which ongoing practice most specifically prevents recurrence of this failure: The first migrated app is unusable because its required database remains unreachable on-premises.?
- Track unsupported framework dependencies and adapt them before production cutover.
- Validate landing-zone readiness gates for each new subscription.
- Maintain wave sequencing and connectivity tests as dependencies are uncovered.
- Rehearse dual-write avoidance, validation and DNS reversal before live migrations.
Explanation
Correct Answer
C:This is an ongoing protection specific to the fault: Maintain wave sequencing and connectivity tests as dependencies are uncovered. The recurrence risk is: Migration order ignored dependency connectivity and shared service placement. It should be checked using: Cut over a low-risk cohort and verify dependent login, database and message flows before the next wave.
Incorrect Answers
A:Tracking unsupported framework dependencies and adapt them would not maintain wave sequencing and connectivity tests as dependencies are uncovered.
B:Validating landing-zone readiness gates for each new subscription would not maintain wave sequencing and connectivity tests as dependencies are uncovered.
D:DNS configuration would not maintain wave sequencing and connectivity tests as dependencies are uncovered. Migration order ignored dependency connectivity and shared service placement.
Question 901
A solution architect is reviewing a workload: A regulated database migration requires a documented rollback if post-cutover consistency validation fails within the change window. The observed incident is: Both old and new databases accept conflicting updates after a failed migration cutover. Which architecture choice most directly removes the identified weakness?
- Establish pre-cutover synchronization, validation checkpoints, source write-freeze/rollback plan and recovery roles.
- Use the supported Azure Migrate server-migration workflow with replication, test migration and final cutover.
- Use discovered application dependency maps to group cutover waves with tested inter-service connectivity and rollback.
- Choose supported Azure Database Migration Service or equivalent approved migration workflow matching offline/online capability.
Explanation
Correct Answer
A:This option addresses the actual design defect: Rollback ownership and write-direction controls were not defined. The correction is: Establish pre-cutover synchronization, validation checkpoints, source write-freeze/rollback plan and recovery roles. Confirm the outcome with: Simulate a failed integrity check and execute the rollback steps without split-brain writes.
Incorrect Answers
B:Using the supported Azure Migrate server-migration workflow with replication, test migration and final cutover would not establish pre-cutover synchronization, validation checkpoints, source write-freeze/rollback plan and recovery roles.
C:Using discovered application dependency maps to group cutover waves with tested inter-service connectivity and rollback would not establish pre-cutover synchronization, validation checkpoints, source write-freeze/rollback plan and recovery roles.
D:Choosing supported Azure Database Migration Service or equivalent approved migration workflow matching offline/online capability would not establish pre-cutover synchronization, validation checkpoints, source write-freeze/rollback plan and recovery roles.
Question 902
An architect proposes this change: Establish pre-cutover synchronization, validation checkpoints, source write-freeze/rollback plan and recovery roles. The workload context is: A regulated database migration requires a documented rollback if post-cutover consistency validation fails within the change window. Which evidence would most directly validate the change?
- Cut over a low-risk cohort and verify dependent login, database and message flows before the next wave.
- Run a nonproduction test migration and validate application services before committing final cutover.
- Rehearse replication/cutover, validate row counts and measure actual outage duration.
- Simulate a failed integrity check and execute the rollback steps without split-brain writes.
Explanation
Correct Answer
D:This observation directly verifies the intended design: Simulate a failed integrity check and execute the rollback steps without split-brain writes. The architecture being tested is: Establish pre-cutover synchronization, validation checkpoints, source write-freeze/rollback plan and recovery roles. The original symptom was: Both old and new databases accept conflicting updates after a failed migration cutover.
Incorrect Answers
A:The architecture being tested is: Establish pre-cutover synchronization, validation checkpoints, source write-freeze/rollback plan and recovery roles.
B:That observation pertains to a separate failure: A one-time disk copy causes extended outage and incomplete changes after initial transfer. Its cause is: A continuous migration replication and controlled cutover process was not planned. It does not confirm the result of this design. The direct proof would be: Simulate a failed integrity check and execute the rollback steps without split-brain writes.
C:The alternative test targets: Choose supported Azure Database Migration Service or equivalent approved migration workflow matching offline/online capability. The scenario's actual proposed remedy is: Establish pre-cutover synchronization, validation checkpoints, source write-freeze/rollback plan and recovery roles. Verify that one by: Simulate a failed integrity check and execute the rollback steps without split-brain writes.
Question 903
During architecture troubleshooting, a team reports: Both old and new databases accept conflicting updates after a failed migration cutover. Context: A regulated database migration requires a documented rollback if post-cutover consistency validation fails within the change window. Which underlying design mistake explains the observed behavior most precisely?
- Migration order ignored dependency connectivity and shared service placement.
- Migration mode and cutover sequencing do not meet the allowed service interruption.
- A continuous migration replication and controlled cutover process was not planned.
- Rollback ownership and write-direction controls were not defined.
Explanation
Correct Answer
D:The incident is explained by: Rollback ownership and write-direction controls were not defined. The reported symptom is: Both old and new databases accept conflicting updates after a failed migration cutover. The corresponding design fix is: Establish pre-cutover synchronization, validation checkpoints, source write-freeze/rollback plan and recovery roles.
Incorrect Answers
A:The alternative diagnosis “Migration order ignored dependency connectivity and shared service placement” does not match the observed symptom: Both old and new databases accept conflicting updates after a failed migration cutover. Context: A regulated database migration requires a documented rollback if post-cutover consistency validation fails within the change window. The incident is explained by: Rollback ownership and write-direction controls were not defined. The reported symptom is: Both old and new databases accept conflicting updates after a failed migration cutover. The evidence instead supports “Rollback ownership and write-direction controls were not defined”.
B:The alternative diagnosis “Migration mode and cutover sequencing do not meet the allowed service interruption” does not match the observed symptom: Both old and new databases accept conflicting updates after a failed migration cutover. Context: A regulated database migration requires a documented rollback if post-cutover consistency validation fails within the change window. The incident is explained by: Rollback ownership and write-direction controls were not defined. The reported symptom is: Both old and new databases accept conflicting updates after a failed migration cutover. The evidence instead supports “Rollback ownership and write-direction controls were not defined”.
C:The alternative diagnosis “A continuous migration replication and controlled cutover process was not planned” does not match the observed symptom: Both old and new databases accept conflicting updates after a failed migration cutover. Context: A regulated database migration requires a documented rollback if post-cutover consistency validation fails within the change window. The incident is explained by: Rollback ownership and write-direction controls were not defined. The reported symptom is: Both old and new databases accept conflicting updates after a failed migration cutover. The evidence instead supports “Rollback ownership and write-direction controls were not defined”.
Question 904
The design change is: Establish pre-cutover synchronization, validation checkpoints, source write-freeze/rollback plan and recovery roles. The original failure was: Both old and new databases accept conflicting updates after a failed migration cutover. Which ongoing control best prevents recurrence of the same root cause?
- Document rollback point and source write-freeze rules during migration.
- Rehearse dual-write avoidance, validation and DNS reversal before live migrations.
- Rehearse test migration, cleanup and rollback after source VM changes.
- Maintain wave sequencing and connectivity tests as dependencies are uncovered.
Explanation
Correct Answer
B:This is an ongoing protection specific to the fault: Rehearse dual-write avoidance, validation and DNS reversal before live migrations. The recurrence risk is: Rollback ownership and write-direction controls were not defined. It should be checked using: Simulate a failed integrity check and execute the rollback steps without split-brain writes.
Incorrect Answers
A:The alternative diagnosis “Document rollback point and source write-freeze rules during migration” does not match the observed symptom: The design change is: Establish pre-cutover synchronization, validation checkpoints, source write-freeze/rollback plan and recovery roles. The original failure was: Both old and new databases accept conflicting updates after a failed migration cutover. Which ongoing control best prevents recurrence of the same root cause?. This is an ongoing protection specific to the fault: Rehearse dual-write avoidance, validation and DNS reversal before live migrations. The recurrence risk is: Rollback ownership and write-direction controls were not defined. The evidence instead supports “Rehearse dual-write avoidance, validation and DNS reversal before live migrations”.
C:The alternative diagnosis “Rehearse test migration, cleanup and rollback after source VM changes” does not match the observed symptom: The design change is: Establish pre-cutover synchronization, validation checkpoints, source write-freeze/rollback plan and recovery roles. The original failure was: Both old and new databases accept conflicting updates after a failed migration cutover. Which ongoing control best prevents recurrence of the same root cause?. This is an ongoing protection specific to the fault: Rehearse dual-write avoidance, validation and DNS reversal before live migrations. The recurrence risk is: Rollback ownership and write-direction controls were not defined. The evidence instead supports “Rehearse dual-write avoidance, validation and DNS reversal before live migrations”.
D:The alternative diagnosis “Maintain wave sequencing and connectivity tests as dependencies are uncovered” does not match the observed symptom: The design change is: Establish pre-cutover synchronization, validation checkpoints, source write-freeze/rollback plan and recovery roles. The original failure was: Both old and new databases accept conflicting updates after a failed migration cutover. Which ongoing control best prevents recurrence of the same root cause?. This is an ongoing protection specific to the fault: Rehearse dual-write avoidance, validation and DNS reversal before live migrations. The recurrence risk is: Rollback ownership and write-direction controls were not defined. The evidence instead supports “Rehearse dual-write avoidance, validation and DNS reversal before live migrations”.
Question 905
A design workshop has this requirement: A company operates twenty Azure spoke VNets with shared outbound firewalling and identity services and wants centrally governed connectivity. Operators currently observe: Every spoke deploys its own unmanaged internet egress and inconsistent security policies. Select the ONE design remedy that best addresses the root cause.
- Deploy Azure Firewall with suitable Firewall Policy and route spokes through the firewall where supported.
- Use a hub-and-spoke topology with appropriate VNet peering and centralized firewall/routing controls.
- Add supported transit design with explicit routing and peering gateway forwarding as required; VNet peering is not automatically transitive.
- Use Azure Virtual WAN hubs and supported site connectivity/policies instead of managing many separate custom transit meshes.
Explanation
Correct Answer
B:The targeted implementation is: Use a hub-and-spoke topology with appropriate VNet peering and centralized firewall/routing controls. The problem is not generic resource availability: No central hub networking and route control is designed. Verify the result by: Connect a test spoke and verify its approved traffic traverses shared hub security services.
Incorrect Answers
A:The alternative diagnosis “Deploy Azure Firewall with suitable Firewall Policy and route spokes through the firewall where supported” does not match the observed symptom: Every spoke deploys its own unmanaged internet egress and inconsistent security policies. The targeted implementation is: Use a hub-and-spoke topology with appropriate VNet peering and centralized firewall/routing controls. The problem is not generic resource availability: No central hub networking and route control is designed. The evidence instead supports “Use a hub-and-spoke topology with appropriate VNet peering and centralized firewall/routing controls”.
C:The alternative diagnosis “Add supported transit design with explicit routing and peering gateway forwarding as required; VNet peering is not automatically transitive” does not match the observed symptom: Every spoke deploys its own unmanaged internet egress and inconsistent security policies. The targeted implementation is: Use a hub-and-spoke topology with appropriate VNet peering and centralized firewall/routing controls. The problem is not generic resource availability: No central hub networking and route control is designed. The evidence instead supports “Use a hub-and-spoke topology with appropriate VNet peering and centralized firewall/routing controls”.
D:The alternative diagnosis “Use Azure Virtual WAN hubs and supported site connectivity/policies instead of managing many separate custom transit meshes” does not match the observed symptom: Every spoke deploys its own unmanaged internet egress and inconsistent security policies. The targeted implementation is: Use a hub-and-spoke topology with appropriate VNet peering and centralized firewall/routing controls. The problem is not generic resource availability: No central hub networking and route control is designed. The evidence instead supports “Use a hub-and-spoke topology with appropriate VNet peering and centralized firewall/routing controls”.
Question 906
The planned architecture is: Use a hub-and-spoke topology with appropriate VNet peering and centralized firewall/routing controls. Workload context: A company operates twenty Azure spoke VNets with shared outbound firewalling and identity services and wants centrally governed connectivity. Which acceptance test demonstrates that the required behavior works?
- Connect a test spoke and verify its approved traffic traverses shared hub security services.
- Test effective routes and traffic between A and B through the intended hub routing device.
- Test allowed and denied flows and verify matching firewall diagnostic logs.
- Onboard a test branch and verify it reaches permitted VNets through the intended virtual hub.
Explanation
Correct Answer
A:The acceptance test is specific: Connect a test spoke and verify its approved traffic traverses shared hub security services. Its purpose is to establish that the proposed architecture works: Use a hub-and-spoke topology with appropriate VNet peering and centralized firewall/routing controls.
Incorrect Answers
B:The alternative test targets: Add supported transit design with explicit routing and peering gateway forwarding as required; VNet peering is not automatically transitive. The scenario's actual proposed remedy is: Use a hub-and-spoke topology with appropriate VNet peering and centralized firewall/routing controls. Verify that one by: Connect a test spoke and verify its approved traffic traverses shared hub security services.
C:Its purpose is to establish that the proposed architecture works: Use a hub-and-spoke topology with appropriate VNet peering and centralized firewall/routing controls.
D:That observation pertains to a separate failure: Hundreds of ad hoc peering and branch tunnels are unmanageable and route propagation becomes inconsistent. Its cause is: Global branch transit lacks an appropriate managed hub/routing architecture. It does not confirm the result of this design. The direct proof would be: Connect a test spoke and verify its approved traffic traverses shared hub security services.
Question 907
The customer states: A company operates twenty Azure spoke VNets with shared outbound firewalling and identity services and wants centrally governed connectivity. An incident reveals: Every spoke deploys its own unmanaged internet egress and inconsistent security policies. What cause best accounts for this evidence?
- Routes bypass the centralized Azure Firewall or its policy lacks the required rule.
- VNet peering does not create arbitrary transitive route propagation by itself.
- Global branch transit lacks an appropriate managed hub/routing architecture.
- No central hub networking and route control is designed.
Explanation
Correct Answer
D:This is the failure mechanism rather than an incidental symptom: No central hub networking and route control is designed. It accounts for: Every spoke deploys its own unmanaged internet egress and inconsistent security policies. The architectural repair is: Use a hub-and-spoke topology with appropriate VNet peering and centralized firewall/routing controls.
Incorrect Answers
A:Routes bypass the centralized Azure Firewall or its policy lacks the required rule. No central hub networking and route control is designed.
B:VNet peering does not create arbitrary transitive route propagation by itself. No central hub networking and route control is designed.
C:Global branch transit lacks an appropriate managed hub/routing architecture. No central hub networking and route control is designed.
Question 908
Workload context: A company operates twenty Azure spoke VNets with shared outbound firewalling and identity services and wants centrally governed connectivity. The implemented remedy is: Use a hub-and-spoke topology with appropriate VNet peering and centralized firewall/routing controls. Which ongoing practice most specifically prevents recurrence of this failure: Every spoke deploys its own unmanaged internet egress and inconsistent security policies.?
- Validate new spoke effective routes and hub NVA forwarding after each peering update.
- Inspect effective routes and rule collections after network expansions.
- Audit spoke route tables, peer flags and common firewall policies during onboarding.
- Review virtual hub route tables and secured hub policies after new regions are added.
Explanation
Correct Answer
C:The preventive control is: Audit spoke route tables, peer flags and common firewall policies during onboarding. It targets the earlier cause: No central hub networking and route control is designed. Confirm ongoing effectiveness by: Connect a test spoke and verify its approved traffic traverses shared hub security services.
Incorrect Answers
A:Validating new spoke effective routes and hub NVA forwarding after each peering update would not audit spoke route tables, peer flags and common firewall policies during onboarding.
B:Inspecting effective routes and rule collections after network expansions would not audit spoke route tables, peer flags and common firewall policies during onboarding.
D:Reviewing virtual hub route tables and secured hub policies after new regions are added would not audit spoke route tables, peer flags and common firewall policies during onboarding.
Question 909
A solution architect is reviewing a workload: Spoke A is peered to Hub and Hub is peered to Spoke B; engineers incorrectly assume that A and B automatically communicate. The observed incident is: Spoke A cannot reach Spoke B despite both VNets having healthy peering to Hub. Which architecture choice most directly removes the identified weakness?
- Add supported transit design with explicit routing and peering gateway forwarding as required; VNet peering is not automatically transitive.
- Use Azure Private DNS zones with proper VNet links and Azure DNS Private Resolver or supported forwarders.
- Use a hub-and-spoke topology with appropriate VNet peering and centralized firewall/routing controls.
- Use Azure Virtual WAN hubs and supported site connectivity/policies instead of managing many separate custom transit meshes.
Explanation
Correct Answer
A:The targeted implementation is: Add supported transit design with explicit routing and peering gateway forwarding as required; VNet peering is not automatically transitive. The problem is not generic resource availability: VNet peering does not create arbitrary transitive route propagation by itself. Verify the result by: Test effective routes and traffic between A and B through the intended hub routing device.
Incorrect Answers
B:Using Azure Private DNS zones with proper VNet links and Azure DNS Private Resolver or supported forwarders would not add supported transit design with explicit routing and peering gateway forwarding as required.
C:Using a hub-and-spoke topology with appropriate VNet peering and centralized firewall/routing controls would not add supported transit design with explicit routing and peering gateway forwarding as required.
D:Using Azure Virtual WAN hubs and supported site connectivity/policies would not add supported transit design with explicit routing and peering gateway forwarding as required.
Question 910
An architect proposes this change: Add supported transit design with explicit routing and peering gateway forwarding as required; VNet peering is not automatically transitive. The workload context is: Spoke A is peered to Hub and Hub is peered to Spoke B; engineers incorrectly assume that A and B automatically communicate. Which evidence would most directly validate the change?
- Resolve a private endpoint FQDN from a spoke and an on-prem client and verify the intended private address.
- Test effective routes and traffic between A and B through the intended hub routing device.
- Connect a test spoke and verify its approved traffic traverses shared hub security services.
- Onboard a test branch and verify it reaches permitted VNets through the intended virtual hub.
Explanation
Correct Answer
B:This observation directly verifies the intended design: Test effective routes and traffic between A and B through the intended hub routing device. The architecture being tested is: Add supported transit design with explicit routing and peering gateway forwarding as required; VNet peering is not automatically transitive. The original symptom was: Spoke A cannot reach Spoke B despite both VNets having healthy peering to Hub.
Incorrect Answers
A:The alternative test targets: Use Azure Private DNS zones with proper VNet links and Azure DNS Private Resolver or supported forwarders. The scenario's actual proposed remedy is: Add supported transit design with explicit routing and peering gateway forwarding as required; VNet peering is not automatically transitive. Verify that one by: Test effective routes and traffic between A and B through the intended hub routing device.
C:That observation pertains to a separate failure: Every spoke deploys its own unmanaged internet egress and inconsistent security policies. Its cause is: No central hub networking and route control is designed. It does not confirm the result of this design. The direct proof would be: Test effective routes and traffic between A and B through the intended hub routing device.
D:The alternative test targets: Use Azure Virtual WAN hubs and supported site connectivity/policies instead of managing many separate custom transit meshes. The scenario's actual proposed remedy is: Add supported transit design with explicit routing and peering gateway forwarding as required; VNet peering is not automatically transitive. Verify that one by: Test effective routes and traffic between A and B through the intended hub routing device.
Designing Microsoft Azure Infrastructure Solutions (AZ-305) Practice Tests