Practice Exams:

View All

Amazon AWS Solutions Architect Professional SAP-C02 Migration Data Transfer Application Movement Practice Test

Domain 4.2 • 24 original questions

This AWS SAP-C02 AWS Certified Solutions Architect – Professional practice test focuses on migration data transfer application movement network and dns through original architecture scenarios aligned to the current AWS Certification exam guide. Use the full ExamSnap SAP-C02 collection for practice across all four content domains. For broader exam preparation, review the Amazon AWS Certified Solutions Architect – Professional SAP-C02 Exam Dumps page.

Instructions: Select the best answer for each question. Review the explanation after answering; each distractor includes a reason it is not the best choice for that scenario.

Question 1

VanArsdel Energy has already validated the surrounding application components. The remaining architecture requirement for its customer-facing API is to choose between online DataSync and an offline Snow Family transfer based on bandwidth and deadline while fitting the change into a repeatable migration wave. Which option is best? The current estate includes 21 AWS accounts and active workloads in us-east-1 and us-west-2. The design must preserve security and auditability while meeting the stated objective.

Classify each workload using the 7Rs and document the business and technical rationale for the selected disposition
Choose DataSync, Transfer Family, S3 transfer features, or Snow Family according to source protocol, bandwidth, data volume, and migration window
Use AWS DMS for ongoing data replication and AWS SCT when heterogeneous schema conversion is required
Choose purpose-built storage and database services per component, using managed elasticity and caching where they fit the access pattern

Correct answer: B

Why: AWS provides online and offline data-transfer services; the correct choice depends on data size, network capacity, protocol, and acceptable transfer duration. This directly addresses the primary requirement and remains appropriate while fitting the change into a repeatable migration wave.

Option review:

A: The 7Rs provide a portfolio decision framework; the right choice depends on constraints, value, risk, and desired modernization depth. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose between online DataSync and an offline Snow Family transfer based on bandwidth and deadline under the additional constraint of while fitting the change into a repeatable migration wave.

B: AWS provides online and offline data-transfer services; the correct choice depends on data size, network capacity, protocol, and acceptable transfer duration. This directly addresses the primary requirement and remains appropriate while fitting the change into a repeatable migration wave.

C: DMS supports database data movement and change replication; SCT assists with schema and code conversion when source and target engines differ. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose between online DataSync and an offline Snow Family transfer based on bandwidth and deadline under the additional constraint of while fitting the change into a repeatable migration wave.

D: Modernization often improves scalability and operations by replacing one generalized data platform with services optimized for object, file, key-value, relational, or cache workloads. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose between online DataSync and an offline Snow Family transfer based on bandwidth and deadline under the additional constraint of while fitting the change into a repeatable migration wave.

Learning point: Choose DataSync, Transfer Family, S3 transfer features, or Snow Family according to source protocol, bandwidth, data volume, and migration window. AWS provides online and offline data-transfer services; the correct choice depends on data size, network capacity, protocol, and acceptable transfer duration. In this variant, the decision also has to work while fitting the change into a repeatable migration wave.

Question 2

While conducting a global expansion project, the cloud platform architect at Contoso Retail needs to replicate source servers continuously and cut over in planned waves while fitting the change into a repeatable migration wave. Which architecture decision best matches the stated constraints? The current estate includes 28 AWS accounts and active workloads in us-east-1 and eu-west-1. Select the option that satisfies the requirement with the fewest unnecessary moving parts.

Classify each workload using the 7Rs and document the business and technical rationale for the selected disposition
Choose DataSync, Transfer Family, S3 transfer features, or Snow Family according to source protocol, bandwidth, data volume, and migration window
Use migration discovery and assessment tooling such as Migration Hub and application inventory data to build a dependency-aware portfolio assessment
Use AWS Application Migration Service for supported rehost migrations and discovery tooling to understand server and dependency scope

Correct answer: D

Why: Application Migration Service is designed for lift-and-shift server migration with continuous replication and controlled cutover. This directly addresses the primary requirement and remains appropriate while fitting the change into a repeatable migration wave.

Option review:

A: The 7Rs provide a portfolio decision framework; the right choice depends on constraints, value, risk, and desired modernization depth. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to replicate source servers continuously and cut over in planned waves under the additional constraint of while fitting the change into a repeatable migration wave.

B: AWS provides online and offline data-transfer services; the correct choice depends on data size, network capacity, protocol, and acceptable transfer duration. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to replicate source servers continuously and cut over in planned waves under the additional constraint of while fitting the change into a repeatable migration wave.

C: Migration planning starts with reliable inventory, ownership, dependency, and utilization data so scope and sequencing reflect the real estate. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to replicate source servers continuously and cut over in planned waves under the additional constraint of while fitting the change into a repeatable migration wave.

D: Application Migration Service is designed for lift-and-shift server migration with continuous replication and controlled cutover. This directly addresses the primary requirement and remains appropriate while fitting the change into a repeatable migration wave.

Learning point: Use AWS Application Migration Service for supported rehost migrations and discovery tooling to understand server and dependency scope. Application Migration Service is designed for lift-and-shift server migration with continuous replication and controlled cutover. In this variant, the decision also has to work while fitting the change into a repeatable migration wave.

Question 3

During a multi-account governance review at Lucerne Publishing, the site reliability architect is designing a enterprise ERP system. The requirement is to provide predictable private connectivity for migration replication and keep transferred data protected in transit while fitting the change into a repeatable migration wave. Which architecture is the best fit? The current estate includes 35 AWS accounts and active workloads in ap-southeast-1 and ap-southeast-2. Choose the option that best meets the stated constraints without introducing an unrelated redesign.

Use appropriate Direct Connect or VPN connectivity, Route 53/DNS coexistence, encryption, and tightly scoped network/security controls for the migration path
Use TCO analysis plus dependency-aware wave planning to prioritize migrations and group workloads that should move together
Classify each workload using the 7Rs and document the business and technical rationale for the selected disposition
Use migration discovery and assessment tooling such as Migration Hub and application inventory data to build a dependency-aware portfolio assessment

Correct answer: A

Why: Migration networks often coexist with production; connectivity, DNS, encryption, and access controls must be designed for both the transition and final state. This directly addresses the primary requirement and remains appropriate while fitting the change into a repeatable migration wave.

Option review:

A: Migration networks often coexist with production; connectivity, DNS, encryption, and access controls must be designed for both the transition and final state. This directly addresses the primary requirement and remains appropriate while fitting the change into a repeatable migration wave.

B: Migration sequence and business case should account for dependencies, operational readiness, transition costs, and expected steady-state economics. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to provide predictable private connectivity for migration replication and keep transferred data protected in transit under the additional constraint of while fitting the change into a repeatable migration wave.

C: The 7Rs provide a portfolio decision framework; the right choice depends on constraints, value, risk, and desired modernization depth. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to provide predictable private connectivity for migration replication and keep transferred data protected in transit under the additional constraint of while fitting the change into a repeatable migration wave.

D: Migration planning starts with reliable inventory, ownership, dependency, and utilization data so scope and sequencing reflect the real estate. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to provide predictable private connectivity for migration replication and keep transferred data protected in transit under the additional constraint of while fitting the change into a repeatable migration wave.

Learning point: Use appropriate Direct Connect or VPN connectivity, Route 53/DNS coexistence, encryption, and tightly scoped network/security controls for the migration path. Migration networks often coexist with production; connectivity, DNS, encryption, and access controls must be designed for both the transition and final state. In this variant, the decision also has to work while fitting the change into a repeatable migration wave.

Question 4

Datum Analytics operates a data lake platform. In a migration wave planning session, the migration architect must choose between online DataSync and an offline Snow Family transfer based on bandwidth and deadline with a defined cutover and rollback checkpoint. Which option should be recommended? The current estate includes 42 AWS accounts and active workloads in eu-west-1 and eu-central-1. Assume all unspecified components already meet their requirements.
Choose DataSync, Transfer Family, S3 transfer features, or Snow Family according to source protocol, bandwidth, data volume, and migration window
Select the AWS storage service whose access protocol, durability, throughput, sharing model, and hybrid requirements match the application
Select ECS or EKS according to orchestration requirements and use Fargate when serverless container compute meets the workload needs
Integrate IAM Identity Center or Directory Service with the enterprise identity source and use temporary least-privilege roles during migration

Correct answer: A

Option review:

A: AWS provides online and offline data-transfer services; the correct choice depends on data size, network capacity, protocol, and acceptable transfer duration. This directly addresses the primary requirement and remains appropriate with a defined cutover and rollback checkpoint.

B: AWS storage services expose different block, file, object, and hybrid semantics; the correct target depends on how the application reads and writes data. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose between online DataSync and an offline Snow Family transfer based on bandwidth and deadline under the additional constraint of with a defined cutover and rollback checkpoint.

C: AWS container options provide different levels of Kubernetes compatibility, AWS-native orchestration, and infrastructure ownership. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose between online DataSync and an offline Snow Family transfer based on bandwidth and deadline under the additional constraint of with a defined cutover and rollback checkpoint.

D: Federated identity and role-based access preserve centralized governance and avoid proliferating long-lived local credentials during migration. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose between online DataSync and an offline Snow Family transfer based on bandwidth and deadline under the additional constraint of with a defined cutover and rollback checkpoint.

Question 5

A principal architect asks which AWS approach is intended to replicate source servers continuously and cut over in planned waves with a defined cutover and rollback checkpoint. What is the best answer? The current estate includes 49 AWS accounts and active workloads in us-east-1 and us-west-2. Prefer an AWS-managed capability when it meets the requirements with less operational overhead.

Use AWS Application Migration Service for supported rehost migrations and discovery tooling to understand server and dependency scope
Use Organizations and Control Tower with a defined account/OU model, guardrails, and delegated administration for the migration landing zone
Integrate IAM Identity Center or Directory Service with the enterprise identity source and use temporary least-privilege roles during migration
Select EC2, Elastic Beanstalk, ECS, EKS, or Fargate based on runtime constraints, orchestration requirements, portability, and desired operational ownership

Correct answer: A

Option review:

A: Application Migration Service is designed for lift-and-shift server migration with continuous replication and controlled cutover. This directly addresses the primary requirement and remains appropriate with a defined cutover and rollback checkpoint.

B: A governed landing zone gives migration teams repeatable account baselines and prevents each wave from inventing its own security and governance model. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to replicate source servers continuously and cut over in planned waves under the additional constraint of with a defined cutover and rollback checkpoint.

C: Federated identity and role-based access preserve centralized governance and avoid proliferating long-lived local credentials during migration. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to replicate source servers continuously and cut over in planned waves under the additional constraint of with a defined cutover and rollback checkpoint.

D: Compute and container choices should match application packaging and the amount of infrastructure and orchestration control the team actually needs. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to replicate source servers continuously and cut over in planned waves under the additional constraint of with a defined cutover and rollback checkpoint.

Question 6

Bellows University is changing its healthcare records application as part of a security design review. Which AWS approach best enables the team to provide predictable private connectivity for migration replication and keep transferred data protected in transit with a defined cutover and rollback checkpoint? The current estate includes 9 AWS accounts and active workloads in us-east-1 and eu-west-1. The team wants the most direct architecture decision for this requirement.

Use AWS DMS for ongoing data replication and AWS SCT when heterogeneous schema conversion is required
Select EC2, Elastic Beanstalk, ECS, EKS, or Fargate based on runtime constraints, orchestration requirements, portability, and desired operational ownership
Use appropriate Direct Connect or VPN connectivity, Route 53/DNS coexistence, encryption, and tightly scoped network/security controls for the migration path
Classify each workload using the 7Rs and document the business and technical rationale for the selected disposition

Correct answer: C

Option review:

A: DMS supports database data movement and change replication; SCT assists with schema and code conversion when source and target engines differ. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to provide predictable private connectivity for migration replication and keep transferred data protected in transit under the additional constraint of with a defined cutover and rollback checkpoint.

B: Compute and container choices should match application packaging and the amount of infrastructure and orchestration control the team actually needs. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to provide predictable private connectivity for migration replication and keep transferred data protected in transit under the additional constraint of with a defined cutover and rollback checkpoint.

C: Migration networks often coexist with production; connectivity, DNS, encryption, and access controls must be designed for both the transition and final state. This directly addresses the primary requirement and remains appropriate with a defined cutover and rollback checkpoint.

D: The 7Rs provide a portfolio decision framework; the right choice depends on constraints, value, risk, and desired modernization depth. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to provide predictable private connectivity for migration replication and keep transferred data protected in transit under the additional constraint of with a defined cutover and rollback checkpoint.

Question 7

An architecture board at Blue Yonder Airlines asks the enterprise architect to choose between online DataSync and an offline Snow Family transfer based on bandwidth and deadline without weakening the landing-zone security baseline for a enterprise ERP system. Which recommendation is most appropriate? The current estate includes 16 AWS accounts and active workloads in ap-southeast-1 and ap-southeast-2. The design must preserve security and auditability while meeting the stated objective.

Choose purpose-built storage and database services per component, using managed elasticity and caching where they fit the access pattern
Use AWS Application Migration Service for supported rehost migrations and discovery tooling to understand server and dependency scope
Choose DataSync, Transfer Family, S3 transfer features, or Snow Family according to source protocol, bandwidth, data volume, and migration window
Select the purpose-built managed database that matches relational, key-value, search, or other access patterns, retaining self-managed EC2 only when required controls justify it

Correct answer: C

Why: AWS provides online and offline data-transfer services; the correct choice depends on data size, network capacity, protocol, and acceptable transfer duration. This directly addresses the primary requirement and remains appropriate without weakening the landing-zone security baseline.

Option review:

A: Modernization often improves scalability and operations by replacing one generalized data platform with services optimized for object, file, key-value, relational, or cache workloads. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose between online DataSync and an offline Snow Family transfer based on bandwidth and deadline under the additional constraint of without weakening the landing-zone security baseline.

B: Application Migration Service is designed for lift-and-shift server migration with continuous replication and controlled cutover. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose between online DataSync and an offline Snow Family transfer based on bandwidth and deadline under the additional constraint of without weakening the landing-zone security baseline.

C: AWS provides online and offline data-transfer services; the correct choice depends on data size, network capacity, protocol, and acceptable transfer duration. This directly addresses the primary requirement and remains appropriate without weakening the landing-zone security baseline.

D: Database replatforming should balance access model, compatibility, scale, availability, and the operational burden the organization is willing to own. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose between online DataSync and an offline Snow Family transfer based on bandwidth and deadline under the additional constraint of without weakening the landing-zone security baseline.

Learning point: Choose DataSync, Transfer Family, S3 transfer features, or Snow Family according to source protocol, bandwidth, data volume, and migration window. AWS provides online and offline data-transfer services; the correct choice depends on data size, network capacity, protocol, and acceptable transfer duration. In this variant, the decision also has to work without weakening the landing-zone security baseline.

Question 8

For a data lake platform at City Power, a production readiness review identifies one priority: replicate source servers continuously and cut over in planned waves without weakening the landing-zone security baseline. Which AWS design should the team choose? The current estate includes 23 AWS accounts and active workloads in eu-west-1 and eu-central-1. Select the option that satisfies the requirement with the fewest unnecessary moving parts.

Use TCO analysis plus dependency-aware wave planning to prioritize migrations and group workloads that should move together
Use AWS Application Migration Service for supported rehost migrations and discovery tooling to understand server and dependency scope
Integrate IAM Identity Center or Directory Service with the enterprise identity source and use temporary least-privilege roles during migration
Select the AWS storage service whose access protocol, durability, throughput, sharing model, and hybrid requirements match the application

Correct answer: B

Why: Application Migration Service is designed for lift-and-shift server migration with continuous replication and controlled cutover. This directly addresses the primary requirement and remains appropriate without weakening the landing-zone security baseline.

Option review:

A: Migration sequence and business case should account for dependencies, operational readiness, transition costs, and expected steady-state economics. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to replicate source servers continuously and cut over in planned waves under the additional constraint of without weakening the landing-zone security baseline.

B: Application Migration Service is designed for lift-and-shift server migration with continuous replication and controlled cutover. This directly addresses the primary requirement and remains appropriate without weakening the landing-zone security baseline.

D: AWS storage services expose different block, file, object, and hybrid semantics; the correct target depends on how the application reads and writes data. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to replicate source servers continuously and cut over in planned waves under the additional constraint of without weakening the landing-zone security baseline.

Learning point: Use AWS Application Migration Service for supported rehost migrations and discovery tooling to understand server and dependency scope. Application Migration Service is designed for lift-and-shift server migration with continuous replication and controlled cutover. In this variant, the decision also has to work without weakening the landing-zone security baseline.

Question 9

Proseware Labs has already validated the surrounding application components. The remaining architecture requirement for its customer-facing API is to provide predictable private connectivity for migration replication and keep transferred data protected in transit without weakening the landing-zone security baseline. Which option is best? The current estate includes 30 AWS accounts and active workloads in us-east-1 and us-west-2. Choose the option that best meets the stated constraints without introducing an unrelated redesign.

Use TCO analysis plus dependency-aware wave planning to prioritize migrations and group workloads that should move together
Use event-driven integration with services such as SQS, SNS, EventBridge, Step Functions, and Lambda to decouple components and remove server management where appropriate
Use appropriate Direct Connect or VPN connectivity, Route 53/DNS coexistence, encryption, and tightly scoped network/security controls for the migration path
Classify each workload using the 7Rs and document the business and technical rationale for the selected disposition

Correct answer: C

Why: Migration networks often coexist with production; connectivity, DNS, encryption, and access controls must be designed for both the transition and final state. This directly addresses the primary requirement and remains appropriate without weakening the landing-zone security baseline.

Option review:

A: Migration sequence and business case should account for dependencies, operational readiness, transition costs, and expected steady-state economics. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to provide predictable private connectivity for migration replication and keep transferred data protected in transit under the additional constraint of without weakening the landing-zone security baseline.

B: Serverless and managed integration services can isolate failures, buffer bursts, and eliminate undifferentiated server operations for suitable workloads. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to provide predictable private connectivity for migration replication and keep transferred data protected in transit under the additional constraint of without weakening the landing-zone security baseline.

Learning point: Use appropriate Direct Connect or VPN connectivity, Route 53/DNS coexistence, encryption, and tightly scoped network/security controls for the migration path. Migration networks often coexist with production; connectivity, DNS, encryption, and access controls must be designed for both the transition and final state. In this variant, the decision also has to work without weakening the landing-zone security baseline.

Question 10

Which solution is the strongest match for the following professional-level architecture requirement: choose between online DataSync and an offline Snow Family transfer based on bandwidth and deadline while preserving data integrity through cutover? The current estate includes 37 AWS accounts and active workloads in us-east-1 and eu-west-1. Assume all unspecified components already meet their requirements.

Use event-driven integration with services such as SQS, SNS, EventBridge, Step Functions, and Lambda to decouple components and remove server management where appropriate
Choose DataSync, Transfer Family, S3 transfer features, or Snow Family according to source protocol, bandwidth, data volume, and migration window
Use AWS DMS for ongoing data replication and AWS SCT when heterogeneous schema conversion is required
Select ECS or EKS according to orchestration requirements and use Fargate when serverless container compute meets the workload needs

Correct answer: B

Option review:

A: Serverless and managed integration services can isolate failures, buffer bursts, and eliminate undifferentiated server operations for suitable workloads. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose between online DataSync and an offline Snow Family transfer based on bandwidth and deadline under the additional constraint of while preserving data integrity through cutover.

D: AWS container options provide different levels of Kubernetes compatibility, AWS-native orchestration, and infrastructure ownership. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose between online DataSync and an offline Snow Family transfer based on bandwidth and deadline under the additional constraint of while preserving data integrity through cutover.

Question 11

During a resilience assessment at Woodgrove Bank, the site reliability architect is designing a enterprise ERP system. The requirement is to replicate source servers continuously and cut over in planned waves while preserving data integrity through cutover. Which architecture is the best fit? The current estate includes 44 AWS accounts and active workloads in ap-southeast-1 and ap-southeast-2. Prefer an AWS-managed capability when it meets the requirements with less operational overhead.

Choose DataSync, Transfer Family, S3 transfer features, or Snow Family according to source protocol, bandwidth, data volume, and migration window
Use TCO analysis plus dependency-aware wave planning to prioritize migrations and group workloads that should move together
Use AWS Application Migration Service for supported rehost migrations and discovery tooling to understand server and dependency scope
Use appropriate Direct Connect or VPN connectivity, Route 53/DNS coexistence, encryption, and tightly scoped network/security controls for the migration path

Correct answer: C

Option review:

A: AWS provides online and offline data-transfer services; the correct choice depends on data size, network capacity, protocol, and acceptable transfer duration. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to replicate source servers continuously and cut over in planned waves under the additional constraint of while preserving data integrity through cutover.

B: Migration sequence and business case should account for dependencies, operational readiness, transition costs, and expected steady-state economics. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to replicate source servers continuously and cut over in planned waves under the additional constraint of while preserving data integrity through cutover.

C: Application Migration Service is designed for lift-and-shift server migration with continuous replication and controlled cutover. This directly addresses the primary requirement and remains appropriate while preserving data integrity through cutover.

D: Migration networks often coexist with production; connectivity, DNS, encryption, and access controls must be designed for both the transition and final state. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to replicate source servers continuously and cut over in planned waves under the additional constraint of while preserving data integrity through cutover.

Question 12

Relecloud Systems operates a data lake platform. In a new workload design, the migration architect must provide predictable private connectivity for migration replication and keep transferred data protected in transit while preserving data integrity through cutover. Which option should be recommended? The current estate includes 4 AWS accounts and active workloads in eu-west-1 and eu-central-1. The team wants the most direct architecture decision for this requirement.

Use Organizations and Control Tower with a defined account/OU model, guardrails, and delegated administration for the migration landing zone
Select the AWS storage service whose access protocol, durability, throughput, sharing model, and hybrid requirements match the application
Use appropriate Direct Connect or VPN connectivity, Route 53/DNS coexistence, encryption, and tightly scoped network/security controls for the migration path
Classify each workload using the 7Rs and document the business and technical rationale for the selected disposition

Correct answer: C

Option review:

A: A governed landing zone gives migration teams repeatable account baselines and prevents each wave from inventing its own security and governance model. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to provide predictable private connectivity for migration replication and keep transferred data protected in transit under the additional constraint of while preserving data integrity through cutover.

B: AWS storage services expose different block, file, object, and hybrid semantics; the correct target depends on how the application reads and writes data. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to provide predictable private connectivity for migration replication and keep transferred data protected in transit under the additional constraint of while preserving data integrity through cutover.

Question 13

A principal solutions architect at Fabrikam Health is reviewing a customer-facing API. The business requires the team to choose between online DataSync and an offline Snow Family transfer based on bandwidth and deadline while minimizing business interruption during migration. Which design most directly satisfies the requirement? The current estate includes 11 AWS accounts and active workloads in us-east-1 and us-west-2. The design must preserve security and auditability while meeting the stated objective.

Choose DataSync, Transfer Family, S3 transfer features, or Snow Family according to source protocol, bandwidth, data volume, and migration window
Select EC2, Elastic Beanstalk, ECS, EKS, or Fargate based on runtime constraints, orchestration requirements, portability, and desired operational ownership
Use TCO analysis plus dependency-aware wave planning to prioritize migrations and group workloads that should move together
Select the AWS storage service whose access protocol, durability, throughput, sharing model, and hybrid requirements match the application

Correct answer: A

Option review:

B: Compute and container choices should match application packaging and the amount of infrastructure and orchestration control the team actually needs. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose between online DataSync and an offline Snow Family transfer based on bandwidth and deadline under the additional constraint of while minimizing business interruption during migration.

C: Migration sequence and business case should account for dependencies, operational readiness, transition costs, and expected steady-state economics. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose between online DataSync and an offline Snow Family transfer based on bandwidth and deadline under the additional constraint of while minimizing business interruption during migration.

D: AWS storage services expose different block, file, object, and hybrid semantics; the correct target depends on how the application reads and writes data. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose between online DataSync and an offline Snow Family transfer based on bandwidth and deadline under the additional constraint of while minimizing business interruption during migration.

Question 14

Trey Research is changing its healthcare records application as part of a global expansion project. Which AWS approach best enables the team to replicate source servers continuously and cut over in planned waves while minimizing business interruption during migration? The current estate includes 18 AWS accounts and active workloads in us-east-1 and eu-west-1. Select the option that satisfies the requirement with the fewest unnecessary moving parts.

Select EC2, Elastic Beanstalk, ECS, EKS, or Fargate based on runtime constraints, orchestration requirements, portability, and desired operational ownership
Use migration discovery and assessment tooling such as Migration Hub and application inventory data to build a dependency-aware portfolio assessment
Classify each workload using the 7Rs and document the business and technical rationale for the selected disposition
Use AWS Application Migration Service for supported rehost migrations and discovery tooling to understand server and dependency scope

Correct answer: D

Option review:

A: Compute and container choices should match application packaging and the amount of infrastructure and orchestration control the team actually needs. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to replicate source servers continuously and cut over in planned waves under the additional constraint of while minimizing business interruption during migration.

B: Migration planning starts with reliable inventory, ownership, dependency, and utilization data so scope and sequencing reflect the real estate. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to replicate source servers continuously and cut over in planned waves under the additional constraint of while minimizing business interruption during migration.

C: The 7Rs provide a portfolio decision framework; the right choice depends on constraints, value, risk, and desired modernization depth. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to replicate source servers continuously and cut over in planned waves under the additional constraint of while minimizing business interruption during migration.

Question 15

Which AWS architecture principle or service combination best addresses this requirement for Northwind Media: provide predictable private connectivity for migration replication and keep transferred data protected in transit while minimizing business interruption during migration? The current estate includes 25 AWS accounts and active workloads in ap-southeast-1 and ap-southeast-2. Choose the option that best meets the stated constraints without introducing an unrelated redesign.

Select the purpose-built managed database that matches relational, key-value, search, or other access patterns, retaining self-managed EC2 only when required controls justify it
Choose DataSync, Transfer Family, S3 transfer features, or Snow Family according to source protocol, bandwidth, data volume, and migration window
Use appropriate Direct Connect or VPN connectivity, Route 53/DNS coexistence, encryption, and tightly scoped network/security controls for the migration path
Integrate IAM Identity Center or Directory Service with the enterprise identity source and use temporary least-privilege roles during migration

Correct answer: C

Option review:

A: Database replatforming should balance access model, compatibility, scale, availability, and the operational burden the organization is willing to own. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to provide predictable private connectivity for migration replication and keep transferred data protected in transit under the additional constraint of while minimizing business interruption during migration.

B: AWS provides online and offline data-transfer services; the correct choice depends on data size, network capacity, protocol, and acceptable transfer duration. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to provide predictable private connectivity for migration replication and keep transferred data protected in transit under the additional constraint of while minimizing business interruption during migration.

D: Federated identity and role-based access preserve centralized governance and avoid proliferating long-lived local credentials during migration. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to provide predictable private connectivity for migration replication and keep transferred data protected in transit under the additional constraint of while minimizing business interruption during migration.

Question 16

For a data lake platform at Coho Financial, a migration wave planning session identifies one priority: choose between online DataSync and an offline Snow Family transfer based on bandwidth and deadline while accounting for workload dependencies before sequencing the move. Which AWS design should the team choose? The current estate includes 32 AWS accounts and active workloads in eu-west-1 and eu-central-1. Assume all unspecified components already meet their requirements.

Use migration discovery and assessment tooling such as Migration Hub and application inventory data to build a dependency-aware portfolio assessment
Integrate IAM Identity Center or Directory Service with the enterprise identity source and use temporary least-privilege roles during migration
Choose DataSync, Transfer Family, S3 transfer features, or Snow Family according to source protocol, bandwidth, data volume, and migration window
Choose purpose-built storage and database services per component, using managed elasticity and caching where they fit the access pattern

Correct answer: C

Why: AWS provides online and offline data-transfer services; the correct choice depends on data size, network capacity, protocol, and acceptable transfer duration. This directly addresses the primary requirement and remains appropriate while accounting for workload dependencies before sequencing the move.

Option review:

A: Migration planning starts with reliable inventory, ownership, dependency, and utilization data so scope and sequencing reflect the real estate. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose between online DataSync and an offline Snow Family transfer based on bandwidth and deadline under the additional constraint of while accounting for workload dependencies before sequencing the move.

B: Federated identity and role-based access preserve centralized governance and avoid proliferating long-lived local credentials during migration. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose between online DataSync and an offline Snow Family transfer based on bandwidth and deadline under the additional constraint of while accounting for workload dependencies before sequencing the move.

C: AWS provides online and offline data-transfer services; the correct choice depends on data size, network capacity, protocol, and acceptable transfer duration. This directly addresses the primary requirement and remains appropriate while accounting for workload dependencies before sequencing the move.

D: Modernization often improves scalability and operations by replacing one generalized data platform with services optimized for object, file, key-value, relational, or cache workloads. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose between online DataSync and an offline Snow Family transfer based on bandwidth and deadline under the additional constraint of while accounting for workload dependencies before sequencing the move.

Learning point: Choose DataSync, Transfer Family, S3 transfer features, or Snow Family according to source protocol, bandwidth, data volume, and migration window. AWS provides online and offline data-transfer services; the correct choice depends on data size, network capacity, protocol, and acceptable transfer duration. In this variant, the decision also has to work while accounting for workload dependencies before sequencing the move.

Question 17

Lamna Healthcare has already validated the surrounding application components. The remaining architecture requirement for its customer-facing API is to replicate source servers continuously and cut over in planned waves while accounting for workload dependencies before sequencing the move. Which option is best? The current estate includes 39 AWS accounts and active workloads in us-east-1 and us-west-2. Prefer an AWS-managed capability when it meets the requirements with less operational overhead.

Select ECS or EKS according to orchestration requirements and use Fargate when serverless container compute meets the workload needs
Use AWS Application Migration Service for supported rehost migrations and discovery tooling to understand server and dependency scope
Use TCO analysis plus dependency-aware wave planning to prioritize migrations and group workloads that should move together
Select the AWS storage service whose access protocol, durability, throughput, sharing model, and hybrid requirements match the application

Correct answer: B

Why: Application Migration Service is designed for lift-and-shift server migration with continuous replication and controlled cutover. This directly addresses the primary requirement and remains appropriate while accounting for workload dependencies before sequencing the move.

Option review:

A: AWS container options provide different levels of Kubernetes compatibility, AWS-native orchestration, and infrastructure ownership. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to replicate source servers continuously and cut over in planned waves under the additional constraint of while accounting for workload dependencies before sequencing the move.

B: Application Migration Service is designed for lift-and-shift server migration with continuous replication and controlled cutover. This directly addresses the primary requirement and remains appropriate while accounting for workload dependencies before sequencing the move.

C: Migration sequence and business case should account for dependencies, operational readiness, transition costs, and expected steady-state economics. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to replicate source servers continuously and cut over in planned waves under the additional constraint of while accounting for workload dependencies before sequencing the move.

D: AWS storage services expose different block, file, object, and hybrid semantics; the correct target depends on how the application reads and writes data. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to replicate source servers continuously and cut over in planned waves under the additional constraint of while accounting for workload dependencies before sequencing the move.

Learning point: Use AWS Application Migration Service for supported rehost migrations and discovery tooling to understand server and dependency scope. Application Migration Service is designed for lift-and-shift server migration with continuous replication and controlled cutover. In this variant, the decision also has to work while accounting for workload dependencies before sequencing the move.

Question 18

While conducting a security design review, the cloud platform architect at Fourth Coffee needs to provide predictable private connectivity for migration replication and keep transferred data protected in transit while accounting for workload dependencies before sequencing the move. Which architecture decision best matches the stated constraints? The current estate includes 46 AWS accounts and active workloads in us-east-1 and eu-west-1. The team wants the most direct architecture decision for this requirement.

Select ECS or EKS according to orchestration requirements and use Fargate when serverless container compute meets the workload needs
Use Organizations and Control Tower with a defined account/OU model, guardrails, and delegated administration for the migration landing zone
Use appropriate Direct Connect or VPN connectivity, Route 53/DNS coexistence, encryption, and tightly scoped network/security controls for the migration path
Use AWS DMS for ongoing data replication and AWS SCT when heterogeneous schema conversion is required

Correct answer: C

Why: Migration networks often coexist with production; connectivity, DNS, encryption, and access controls must be designed for both the transition and final state. This directly addresses the primary requirement and remains appropriate while accounting for workload dependencies before sequencing the move.

Option review:

A: AWS container options provide different levels of Kubernetes compatibility, AWS-native orchestration, and infrastructure ownership. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to provide predictable private connectivity for migration replication and keep transferred data protected in transit under the additional constraint of while accounting for workload dependencies before sequencing the move.

B: A governed landing zone gives migration teams repeatable account baselines and prevents each wave from inventing its own security and governance model. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to provide predictable private connectivity for migration replication and keep transferred data protected in transit under the additional constraint of while accounting for workload dependencies before sequencing the move.

D: DMS supports database data movement and change replication; SCT assists with schema and code conversion when source and target engines differ. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to provide predictable private connectivity for migration replication and keep transferred data protected in transit under the additional constraint of while accounting for workload dependencies before sequencing the move.

Learning point: Use appropriate Direct Connect or VPN connectivity, Route 53/DNS coexistence, encryption, and tightly scoped network/security controls for the migration path. Migration networks often coexist with production; connectivity, DNS, encryption, and access controls must be designed for both the transition and final state. In this variant, the decision also has to work while accounting for workload dependencies before sequencing the move.

Question 19

During a modernization initiative at Consolidated Messenger, the site reliability architect is designing a enterprise ERP system. The requirement is to choose between online DataSync and an offline Snow Family transfer based on bandwidth and deadline while keeping governance consistent across destination accounts. Which architecture is the best fit? The current estate includes 6 AWS accounts and active workloads in ap-southeast-1 and ap-southeast-2. The design must preserve security and auditability while meeting the stated objective.

Choose DataSync, Transfer Family, S3 transfer features, or Snow Family according to source protocol, bandwidth, data volume, and migration window
Use TCO analysis plus dependency-aware wave planning to prioritize migrations and group workloads that should move together
Use AWS Application Migration Service for supported rehost migrations and discovery tooling to understand server and dependency scope
Integrate IAM Identity Center or Directory Service with the enterprise identity source and use temporary least-privilege roles during migration

Correct answer: A

Why: AWS provides online and offline data-transfer services; the correct choice depends on data size, network capacity, protocol, and acceptable transfer duration. This directly addresses the primary requirement and remains appropriate while keeping governance consistent across destination accounts.

Option review:

B: Migration sequence and business case should account for dependencies, operational readiness, transition costs, and expected steady-state economics. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose between online DataSync and an offline Snow Family transfer based on bandwidth and deadline under the additional constraint of while keeping governance consistent across destination accounts.

C: Application Migration Service is designed for lift-and-shift server migration with continuous replication and controlled cutover. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose between online DataSync and an offline Snow Family transfer based on bandwidth and deadline under the additional constraint of while keeping governance consistent across destination accounts.

Learning point: Choose DataSync, Transfer Family, S3 transfer features, or Snow Family according to source protocol, bandwidth, data volume, and migration window. AWS provides online and offline data-transfer services; the correct choice depends on data size, network capacity, protocol, and acceptable transfer duration. In this variant, the decision also has to work while keeping governance consistent across destination accounts.

Question 20

Litware Manufacturing is documenting its target-state architecture. Which choice most accurately addresses the need to replicate source servers continuously and cut over in planned waves while keeping governance consistent across destination accounts? The current estate includes 13 AWS accounts and active workloads in eu-west-1 and eu-central-1. Select the option that satisfies the requirement with the fewest unnecessary moving parts.

Use event-driven integration with services such as SQS, SNS, EventBridge, Step Functions, and Lambda to decouple components and remove server management where appropriate
Use AWS Application Migration Service for supported rehost migrations and discovery tooling to understand server and dependency scope
Choose purpose-built storage and database services per component, using managed elasticity and caching where they fit the access pattern
Classify each workload using the 7Rs and document the business and technical rationale for the selected disposition

Correct answer: B

Why: Application Migration Service is designed for lift-and-shift server migration with continuous replication and controlled cutover. This directly addresses the primary requirement and remains appropriate while keeping governance consistent across destination accounts.

Option review:

A: Serverless and managed integration services can isolate failures, buffer bursts, and eliminate undifferentiated server operations for suitable workloads. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to replicate source servers continuously and cut over in planned waves under the additional constraint of while keeping governance consistent across destination accounts.

B: Application Migration Service is designed for lift-and-shift server migration with continuous replication and controlled cutover. This directly addresses the primary requirement and remains appropriate while keeping governance consistent across destination accounts.

C: Modernization often improves scalability and operations by replacing one generalized data platform with services optimized for object, file, key-value, relational, or cache workloads. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to replicate source servers continuously and cut over in planned waves under the additional constraint of while keeping governance consistent across destination accounts.

D: The 7Rs provide a portfolio decision framework; the right choice depends on constraints, value, risk, and desired modernization depth. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to replicate source servers continuously and cut over in planned waves under the additional constraint of while keeping governance consistent across destination accounts.

Learning point: Use AWS Application Migration Service for supported rehost migrations and discovery tooling to understand server and dependency scope. Application Migration Service is designed for lift-and-shift server migration with continuous replication and controlled cutover. In this variant, the decision also has to work while keeping governance consistent across destination accounts.

Question 21

A principal solutions architect at Humongous Insurance is reviewing a customer-facing API. The business requires the team to provide predictable private connectivity for migration replication and keep transferred data protected in transit while keeping governance consistent across destination accounts. Which design most directly satisfies the requirement? The current estate includes 20 AWS accounts and active workloads in us-east-1 and us-west-2. Choose the option that best meets the stated constraints without introducing an unrelated redesign.

Select ECS or EKS according to orchestration requirements and use Fargate when serverless container compute meets the workload needs
Use appropriate Direct Connect or VPN connectivity, Route 53/DNS coexistence, encryption, and tightly scoped network/security controls for the migration path
Use migration discovery and assessment tooling such as Migration Hub and application inventory data to build a dependency-aware portfolio assessment
Select the purpose-built managed database that matches relational, key-value, search, or other access patterns, retaining self-managed EC2 only when required controls justify it

Correct answer: B

Why: Migration networks often coexist with production; connectivity, DNS, encryption, and access controls must be designed for both the transition and final state. This directly addresses the primary requirement and remains appropriate while keeping governance consistent across destination accounts.

Option review:

A: AWS container options provide different levels of Kubernetes compatibility, AWS-native orchestration, and infrastructure ownership. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to provide predictable private connectivity for migration replication and keep transferred data protected in transit under the additional constraint of while keeping governance consistent across destination accounts.

B: Migration networks often coexist with production; connectivity, DNS, encryption, and access controls must be designed for both the transition and final state. This directly addresses the primary requirement and remains appropriate while keeping governance consistent across destination accounts.

C: Migration planning starts with reliable inventory, ownership, dependency, and utilization data so scope and sequencing reflect the real estate. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to provide predictable private connectivity for migration replication and keep transferred data protected in transit under the additional constraint of while keeping governance consistent across destination accounts.

D: Database replatforming should balance access model, compatibility, scale, availability, and the operational burden the organization is willing to own. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to provide predictable private connectivity for migration replication and keep transferred data protected in transit under the additional constraint of while keeping governance consistent across destination accounts.

Learning point: Use appropriate Direct Connect or VPN connectivity, Route 53/DNS coexistence, encryption, and tightly scoped network/security controls for the migration path. Migration networks often coexist with production; connectivity, DNS, encryption, and access controls must be designed for both the transition and final state. In this variant, the decision also has to work while keeping governance consistent across destination accounts.

Question 22

Tailspin Logistics is changing its healthcare records application as part of a hybrid connectivity redesign. Which AWS approach best enables the team to choose between online DataSync and an offline Snow Family transfer based on bandwidth and deadline without forcing an unrelated refactor before the migration can proceed? The current estate includes 27 AWS accounts and active workloads in us-east-1 and eu-west-1. Assume all unspecified components already meet their requirements.

Integrate IAM Identity Center or Directory Service with the enterprise identity source and use temporary least-privilege roles during migration
Choose purpose-built storage and database services per component, using managed elasticity and caching where they fit the access pattern
Choose DataSync, Transfer Family, S3 transfer features, or Snow Family according to source protocol, bandwidth, data volume, and migration window
Select the AWS storage service whose access protocol, durability, throughput, sharing model, and hybrid requirements match the application

Correct answer: C

Why: AWS provides online and offline data-transfer services; the correct choice depends on data size, network capacity, protocol, and acceptable transfer duration. This directly addresses the primary requirement and remains appropriate without forcing an unrelated refactor before the migration can proceed.

Option review:

A: Federated identity and role-based access preserve centralized governance and avoid proliferating long-lived local credentials during migration. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose between online DataSync and an offline Snow Family transfer based on bandwidth and deadline under the additional constraint of without forcing an unrelated refactor before the migration can proceed.

B: Modernization often improves scalability and operations by replacing one generalized data platform with services optimized for object, file, key-value, relational, or cache workloads. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose between online DataSync and an offline Snow Family transfer based on bandwidth and deadline under the additional constraint of without forcing an unrelated refactor before the migration can proceed.

D: AWS storage services expose different block, file, object, and hybrid semantics; the correct target depends on how the application reads and writes data. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose between online DataSync and an offline Snow Family transfer based on bandwidth and deadline under the additional constraint of without forcing an unrelated refactor before the migration can proceed.

Learning point: Choose DataSync, Transfer Family, S3 transfer features, or Snow Family according to source protocol, bandwidth, data volume, and migration window. AWS provides online and offline data-transfer services; the correct choice depends on data size, network capacity, protocol, and acceptable transfer duration. In this variant, the decision also has to work without forcing an unrelated refactor before the migration can proceed.

Question 23

An architecture board at Alpine Sports asks the enterprise architect to replicate source servers continuously and cut over in planned waves without forcing an unrelated refactor before the migration can proceed for a enterprise ERP system. Which recommendation is most appropriate? The current estate includes 34 AWS accounts and active workloads in ap-southeast-1 and ap-southeast-2. Prefer an AWS-managed capability when it meets the requirements with less operational overhead.

Classify each workload using the 7Rs and document the business and technical rationale for the selected disposition
Use Organizations and Control Tower with a defined account/OU model, guardrails, and delegated administration for the migration landing zone
Use AWS Application Migration Service for supported rehost migrations and discovery tooling to understand server and dependency scope
Use AWS DMS for ongoing data replication and AWS SCT when heterogeneous schema conversion is required

Correct answer: C

Why: Application Migration Service is designed for lift-and-shift server migration with continuous replication and controlled cutover. This directly addresses the primary requirement and remains appropriate without forcing an unrelated refactor before the migration can proceed.

Option review:

A: The 7Rs provide a portfolio decision framework; the right choice depends on constraints, value, risk, and desired modernization depth. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to replicate source servers continuously and cut over in planned waves under the additional constraint of without forcing an unrelated refactor before the migration can proceed.

D: DMS supports database data movement and change replication; SCT assists with schema and code conversion when source and target engines differ. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to replicate source servers continuously and cut over in planned waves under the additional constraint of without forcing an unrelated refactor before the migration can proceed.

Learning point: Use AWS Application Migration Service for supported rehost migrations and discovery tooling to understand server and dependency scope. Application Migration Service is designed for lift-and-shift server migration with continuous replication and controlled cutover. In this variant, the decision also has to work without forcing an unrelated refactor before the migration can proceed.

Question 24

For a data lake platform at Adventure Works, a new workload design identifies one priority: provide predictable private connectivity for migration replication and keep transferred data protected in transit without forcing an unrelated refactor before the migration can proceed. Which AWS design should the team choose? The current estate includes 41 AWS accounts and active workloads in eu-west-1 and eu-central-1. The team wants the most direct architecture decision for this requirement.

Integrate IAM Identity Center or Directory Service with the enterprise identity source and use temporary least-privilege roles during migration
Use appropriate Direct Connect or VPN connectivity, Route 53/DNS coexistence, encryption, and tightly scoped network/security controls for the migration path
Select the AWS storage service whose access protocol, durability, throughput, sharing model, and hybrid requirements match the application
Use AWS DMS for ongoing data replication and AWS SCT when heterogeneous schema conversion is required

Correct answer: B

Why: Migration networks often coexist with production; connectivity, DNS, encryption, and access controls must be designed for both the transition and final state. This directly addresses the primary requirement and remains appropriate without forcing an unrelated refactor before the migration can proceed.

Option review:

A: Federated identity and role-based access preserve centralized governance and avoid proliferating long-lived local credentials during migration. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to provide predictable private connectivity for migration replication and keep transferred data protected in transit under the additional constraint of without forcing an unrelated refactor before the migration can proceed.

B: Migration networks often coexist with production; connectivity, DNS, encryption, and access controls must be designed for both the transition and final state. This directly addresses the primary requirement and remains appropriate without forcing an unrelated refactor before the migration can proceed.

C: AWS storage services expose different block, file, object, and hybrid semantics; the correct target depends on how the application reads and writes data. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to provide predictable private connectivity for migration replication and keep transferred data protected in transit under the additional constraint of without forcing an unrelated refactor before the migration can proceed.

D: DMS supports database data movement and change replication; SCT assists with schema and code conversion when source and target engines differ. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to provide predictable private connectivity for migration replication and keep transferred data protected in transit under the additional constraint of without forcing an unrelated refactor before the migration can proceed.

Learning point: Use appropriate Direct Connect or VPN connectivity, Route 53/DNS coexistence, encryption, and tightly scoped network/security controls for the migration path. Migration networks often coexist with production; connectivity, DNS, encryption, and access controls must be designed for both the transition and final state. In this variant, the decision also has to work without forcing an unrelated refactor before the migration can proceed.

Question 1

Question 2

Question 3

Question 4

Question 5

Question 6

Question 7

Question 8

Question 9

Question 10

Question 11

Question 12

Question 13

Question 14

Question 15

Question 16

Question 17

Question 18

Question 19

Question 20

Question 21

Question 22

Question 23

Question 24

Related posts: