Strangler Fig Pattern — Concept Check
Questions on Strangler Fig Pattern. Incrementally migrate a monolith by routing individual features to new microservices behind an API gateway until the monolith is completely replaced.
Questions in this quiz
8 questions on Strangler Fig Pattern — Concept Check. Work through them here, then start the quiz to answer them and see your score.
1.A company is migrating its monolith to microservices using the Strangler Fig pattern. They have added an API Gateway but notice no traffic is reaching the new microservices. What is likely the issue?
- AThe API Gateway is not compatible with microservices.
- BThe gateway routes are not configured to forward to microservices.
- CThe microservices are not running on separate servers.
- DThe monolith is still handling all traffic due to no feature extraction.
2.During a migration using the Strangler Fig pattern, a team extracts the order management feature into a microservice. What should they do next?
- ARemove the order management code from the monolith.
- BDecommission the monolith entirely.
- CUpdate the API Gateway to route order requests to the new service.
- DDeploy the new service without changing the gateway.
3.A team uses the Strangler Fig pattern but notices high latency when a new service is called. They suspect a distributed monolith. What might be causing this?
- AThe services are deployed independently.
- BThe services share a database schema.
- CThe monolith is still operational.
- DThe API Gateway is misconfigured.
4.Which approach helps synchronize data when a new microservice is extracted but still relies on the monolith's database?
- AManual data entry
- BShared DB (temporary)
- CData replication without CDC
- DDirect database access
5.While using the Strangler Fig pattern, a team decides to dual write during migration. What is a key step in this approach?
- AUse only the new service's database from the start.
- BSwitch reads to the new service's database after dual writing.
- CAvoid writing to both databases at any point.
- DStop writing to the monolith's database immediately.
6.A developer argues that the Strangler Fig pattern is risky because it involves a 'big bang' cutover. Why is this incorrect?
- AThe API Gateway handles all traffic, reducing risk.
- BThe pattern involves incremental feature extraction, not a 'big bang' cutover.
- CThe pattern requires complete monolith decommissioning first.
- DMicroservices are inherently risky, regardless of the pattern.
7.What is a warning sign that a team has created a distributed monolith during migration?
- AServices communicate asynchronously.
- BEach service has its own CI/CD pipeline.
- CServices must deploy in a specific order.
- DEach service owns its own data store.
8.A team using the Strangler Fig pattern is unsure how to handle data migration. Which method involves streaming changes from the monolith's database to the new service's database?
- AChange Data Capture (CDC)
- BDirect database access
- CShared DB (temporary)
- DManual data synchronization