Bounded Contexts — Concept Check
Questions on Bounded Contexts. A bounded context defines the boundary within which a particular domain model is valid and consistent; each microservice ideally maps to one bounded context.
Questions in this quiz
8 questions on Bounded Contexts — Concept Check. Work through them here, then start the quiz to answer them and see your score.
1.A team is designing a microservice architecture. They notice that their 'Order' entity is overloaded with fields for both shipping and billing. What should they do?
- ACreate a shared kernel for 'Order' across all services
- BUse a nanoservice for each field in 'Order'
- CKeep 'Order' as is to maintain a single source of truth
- DSplit 'Order' into separate models for shipping and billing contexts
2.In a microservices architecture, a service is experiencing high latency due to frequent synchronous calls to another service. What is a likely cause?
- AThe services are well-bounded and independent
- BThe services are using a published language for communication
- CThe services are too tightly coupled, resembling a distributed monolith
- DThe services are using an anti-corruption layer
3.A team uses the term 'Customer' in both their CRM and Order contexts. What is a potential issue?
- A'Customer' must be identical across all contexts
- B'Customer' should be a shared kernel between contexts
- C'Customer' may have different meanings in each context
- D'Customer' should only exist in one context
4.What is the primary role of an Anti-Corruption Layer in a microservices architecture?
- ATo share databases between services
- BTo merge different bounded contexts
- CTo translate external models to local models
- DTo enforce synchronous communication
5.A service is independently deployable and owns its database. What does this indicate?
- AThe service uses a shared kernel
- BThe service is a nanoservice
- CThe service is part of a distributed monolith
- DThe service is well-bounded
6.In a context map, what does the Customer/Supplier relationship imply?
- AThe upstream and downstream are tightly coupled
- BThe downstream controls the upstream's model
- CBoth contexts share the same database
- DThe upstream must not break the downstream
7.A team is struggling with microservices complexity due to incorrect boundaries. What is a common mistake they might have made?
- ADefining clear, independent bounded contexts
- BCreating nanoservices with too fine-grained boundaries
- CUsing an anti-corruption layer for every service
- DImplementing a published language for communication
8.What is a key sign of a poorly-bounded service in a microservices architecture?
- ASharing a database schema with another service
- BHaving a small, stable API surface
- CBeing independently deployable
- DOwning its own database