Hard1 markMultiple Choice
Domain 4.3: Migration StrategyModernizationStrangler PatternMicroservices

AWS SAP-C02 · Question 73 · Domain 4.3: Migration Strategy

A company is migrating a complex, multi-tier application to AWS. They want to use a 'Strangler Fig' pattern to gradually modernize the application from a monolith to microservices without downtime. Which FOUR architectural patterns or services support this strategy? (Select FOUR)

Answer options:

A.

Deploy an API Gateway or Application Load Balancer to act as a routing facade.

B.

Perform a one-time cutover of the database using AWS Snowball.

C.

Gradually route specific API paths (e.g., /users) to new AWS Lambda functions or ECS containers.

D.

Use AWS Application Migration Service to lift-and-shift the entire application at once.

E.

Keep the legacy monolith running on-premises or on EC2 to handle un-migrated routes.

F.

Use AWS Database Migration Service (DMS) to keep the legacy and modern databases in sync during the transition.

G.

Use AWS CloudFormation to deploy the monolith.

H.

Use Amazon CloudFront to cache the monolith.

How to approach this question

Identify the components of the Strangler Fig pattern.

Full Answer

A, C, E, F
The Strangler Fig pattern involves placing a routing facade (like API Gateway or ALB) in front of the legacy monolith. You gradually build new microservices (Lambda/ECS) and route specific paths to them, while the monolith handles the rest. DMS keeps the databases in sync during this transition.

Common mistakes

Confusing Strangler pattern with a lift-and-shift migration.

Practice the full AWS Solutions Architect Professional SAP-C02 Practice Exam 6

75 questions · hints · full answers · grading

More questions from this exam