▸case-12 Specify the context mapping between Order Management (upstream) and Warehouse Fulfillment (downstream), where Order Management emits OrderPlaced events, but Warehouse Fulfillment requires a PickListCreated command payload. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-08 Our Logistics system relies on Salesforce CRM for account metadata. Salesforce exposes a standard REST API that we must adapt to, but our internal model for accounts is identical to Salesforce's schema and we accept their model directly. What relationship pattern should be documented? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-11 The Reservation Context and Inventory Context must evolve their APIs synchronously because a booking requires simultaneous hold-and-deduct operations. Neither team can release features without the other releasing at the same time. How should this relationship and ownership be modeled? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-04 Inside our Accounting bounded context, we need to model Money and Currency. How should we implement these as immutable value objects in Java code with internal validation rules? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-13 We are integrating an Accounts context with a Notification context. When the Accounts context releases API v2, existing v1 calls must not break immediately, and if Notification is down, account updates must succeed. What operational policies need to be defined? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-01 Our team is designing interactions across three domain contexts: User Management, Billing, and Messaging. Can you create a comprehensive context integration document that includes a mapping of pairwise dependencies, an ownership matrix for API contracts, explicit translation decisions for boundary protection, and a risk assessment covering coupling vulnerabilities? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-22 Create a contract ownership matrix for a Checkout context integrating with Fraud, Inventory, and Shipping contexts, where Fraud requires a synchronous API, Inventory uses event streaming, and Shipping uses webhooks. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-16 In a B2B Portal context integrating with Vendor Inventory (external) and Internal Purchasing (internal), who owns the schema definitions for vendor intake files versus internal purchase orders? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-20 Global Identity context (US-East) syncs user authorization scopes to Regional Fulfillment context (EU-West). Cross-Atlantic network partitions occur twice a month. What translation and fallback rules are required? | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-03 We need to pick cloud infrastructure tooling for hosting our microservices on AWS. Should we use Managed Kafka (MSK), SQS/SNS, or Amazon EventBridge for async event transport? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-10 The Marketing Analytics context wants recommendation engine predictions from the AI Core context, but integrating across the network adds 400ms latency and complex integration overhead. The analytics team only needs basic rule-based calculations. What relationship pattern resolves this without network coupling? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-05 Our modern E-Commerce context must consume customer profile updates from a 20-year-old COBOL mainframe system whose data model uses cryptic 8-character field codes. The mainframe team refuses to change their schema. How should we structure the integration boundary to prevent legacy data model leakage? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-21 An IoT Telemetry context emits raw sensor readings with vendor-specific hardware fields into an Analytics context. Analytics developers are using raw hardware field names inside their SQL queries. What mapping pattern fixes this coupling risk? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-14 In a downstream Reporting context relying on upstream Claims Processing context APIs, upstream developers frequently deploy breaking changes without notice. What context mapping choices and risk mitigations protect Reporting? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-09 The Order Fulfiller team and Shipping Manager team are closely allied and share a core domain library containing Address and PackageWeight. Modifications to this library require mutual consent from both team leads. Define the relationship and governance rules. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-07 The Product Catalog context provides read-only item data to 15 different internal and external consumer applications. The catalog team cannot negotiate custom interfaces for each consumer. How should the catalog expose its boundary and schema? | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-19 We are extracting a Billing context out of a monolithic ERP system. Modern services must communicate with extracted Billing without being contaminated by the legacy ERP database schema. Detail the context boundary protection strategy. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-18 The Checkout context depends on Fraud Service, Inventory Service, and Tax Calculation Service. If Tax Calculation Service times out, Checkout currently crashes. Provide a context mapping plan that addresses this dependency vulnerability. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-15 Map the dependencies and relationships across four contexts: Core Ledger, Fraud Detection, User Profile, and Audit Logging. Core Ledger calls Fraud Detection synchronously and logs events to Audit Logging asynchronously. User Profile supplies customer attributes to Fraud Detection. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-06 The Payment Processing team provides payment tokenization to the Checkout team. Checkout frequently needs schema additions, and both teams have agreed to coordinate planning cycles where Payment Processing prioritizes Checkout's interface requests. What relationship pattern and contract ownership model applies here? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-02 We are building an Order entity inside a single monolithic e-commerce repository with no external system integrations. How should we structure the internal class design, methods, and encapsulation for the Order aggregate? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-17 A hospital's Electronic Health Record (EHR) context uses HL7 v2 messaging. A modern Patient Mobile App context uses REST/JSON with FHIR formats. How should translation between these two contexts be structured? | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |