DOMAIN B
Business understanding and domain modeling
Whether a person can state business objects, relations, rules, and data meaning precisely.
See this capability domain in stage expectations. Open the capability model
Choose a capability first. Each preview shows up to three questions; open it for focused batches.
170 questions · 6 capabilities
Business context28
How the business runs, who the users are, and where value comes from.
- Renewal fell by six percentage points this quarter, while the share of small customers among new accounts rose. How would you segment customers, usage periods, and service cost to determine whether product value fell or the customer mix changed?
- Besides your product, what else could users do to get the same job done? What does each alternative compete for, and when is it actually the better choice?
- Sales reports growth using signed contract value, but customers will not use the product for months. How would you distinguish contracting, fulfillment, revenue recognition, and customer value, and explain what the team should observe?
- A premium service tier earns more revenue but consumes more human support, and renewal has not improved. How would you determine whether it creates incremental value?
- A product is sold once but requires long-term support and upgrades. Revenue is growing while the service queue accumulates. How would you decide whether these sales still create value?
- Pick a module you own. Explain who it serves, what input it takes, what output it provides, and follow the user task through to the business result.
- When you explain a business, how do you first lay out the whole and then the position and value of the part you own within it? How does someone without a whole-picture view tell it, and what is the difference?
- The business says data must be real time, but no one can explain the cost of a fifteen-minute delay. How would you decide the architecture and freshness target?
- Map the value flow among users, suppliers, the platform, and payers in a two-sided marketplace you know. Explain how value and responsibility change when a service is not fulfilled.
- A new industry or regulatory requirement forces a product workflow change. How would you trace from the requirement to affected participants, value-chain steps, business commitments, and internal systems?
- The same person may encounter a product through ads, an agency, a partner, and a self-serve channel, and different parties may pay. How would you distinguish customer, buyer, user, and acquisition touchpoint in the business model?
- The team plans to enter an adjacent market where users, payers, and fulfillment parties differ. How would you map the value chain and determine whose problem the product should solve first?
- Marketplace transactions keep growing, but buyers wait longer, sellers cancel more often, and subsidy spending rises. How would you describe the exchange of value and constraints across participants, then decide whether growth reflects better matching or one-sided subsidy?
- Marketplace order value is rising, but merchants receive lower settlement amounts; the gap may involve discount sponsors, refunds, platform fees, and settlement timing. How would you explain participant value, money flows, and operating constraints along the transaction chain?
- Sales reports growth by signed contract value, Finance tracks recognized revenue, and Operations schedules work by fulfilled orders; all three call their number “business scale.” How would you map the process and definitions so teams can make one decision together?
- Enterprise customers expect a weekday response, while individual users expect self-service at any time; the team plans to standardize one support workflow. How would you analyze customer needs, issue urgency, service commitments, and delivery costs?
- A promotion increases subscriptions, but many subscribers renew at a lower price and full-price renewal has not yet reached its observation window. How would you decompose acquisition, renewal, discount, and churn to judge long-term value?
- A user reports that a service was not fulfilled as promised. Logs show the product flow triggered, the supplier did not confirm, and Operations says the contract is unclear. How would you map the service commitment, ownership boundaries, and remediation path?
- The company shifts from acquiring new customers to increasing value from existing customers, but sales incentives, product roadmaps, and service capacity still reflect acquisition goals. How would you map the value chain and incentives to find misalignment?
- Active users and revenue are growing, but human support hours, refunds, and infrastructure costs per user are rising faster. How would you use user segments, tasks, and service flows to assess the economic quality of growth?
- A service requires a user, platform, and partner to act in sequence. Each party measures its own SLA, yet users still wait repeatedly and resubmit information. How would you model the end-to-end journey, waiting ownership, and handoff costs?
- The same service faces different supply capacity, tax rules, and fulfillment times across regions, but the sales page uses one promise; some orders require manual rescheduling. How would you describe the relationship among regional constraints, service capability, and customer expectations?
- The company invested in a shared release platform, but most teams still use custom scripts. The platform team believes its features are sufficient, while product teams worry about migration risk and schedule conflicts. How would you analyze platform value, adoption cost, and incentives?
- High-revenue customers frequently request urgent support, consuming team capacity and delaying critical issues for others. How would you define service prioritization?
- A contract charges monthly, while the customer accepts work by project. Some months include preparation but no visible deliverable. How would you distinguish signing, performance, acceptance, and recognizable revenue?
- A channel brings many low-priced orders but requires extra manual checks and complex delivery. How would you assess whether revenue covers service cost, refunds, and supply risk?
- An account is active weekly and likely to renew, but many tasks rely on manual work by customer success. How would you distinguish product use, service assistance, and sustainable value?
- A partner charges per form submission, while sales counts only qualified opportunities. Is the dispute about definitions, data feedback, or audience quality? How would you reset the agreement?
No questions in this section match your target. ·
Product and project model28
Expressing a product or project as objects, boundaries, and states others can discuss.
- Map the area you have owned over time: what users are trying to do, where the main process obstacles are, what your module can influence, and what is outside its control.
- Write a one-page product overview for someone who just joined. How would you mark which statements are fact, which are inference, and which are simply unanswered questions?
- Where does your project sit in the wider business? Who gives it input, who uses its results, and who is affected if it is late or wrong?
- After a promotion ends, operations considers the campaign complete, product sees orders still being fulfilled, and finance says settlement is not yet possible. How would you define each party’s objects, states, and state transitions?
- Teams define “done,” “awaiting acceptance,” and “paused” differently, distorting roll-up data. How would you design a shared state model and transition rules?
- A user can belong to several organizations and hold different roles in each. How would you model identity, membership, and permissions without conflating accounts with business roles?
- An order moves through created, awaiting confirmation, processing, partially fulfilled, canceled, and refunded states; different pages and services interpret “complete” differently. How would you model state, events, and valid transitions so each client does not invent its own meaning?
- An enterprise customer uses one contract for several departments; employees may work across departments, and administrators may operate on behalf of multiple accounts. How would you distinguish organizations, contract accounts, individual identities, memberships, and authorization scope?
- A cross-team project launches on schedule, but user feedback, operating costs, and data corrections remain; the project team is about to disband. How would you model product, platform, operations, and project responsibilities after delivery?
- A product feature is configured by customer contract, adjusted by experiment group, and constrained by regional rules; analysts need to explain which combination shaped a user's experience. How would you model configuration sources, scope, effective time, and decision provenance?
- A plan includes entitlements, users can purchase add-on capacity or receive temporary campaign credits, and contract changes may require manual compensation. How would you distinguish entitlement definitions, granted balances, sources, expiry, and consumption records?
- A cross-team objective spans several projects, each with routine tasks, risks, and incidents; retrospectives struggle to trace which decisions and work drove an outcome. How would you model relationships among objectives, projects, work items, events, and evidence?
- Business users can edit rules ahead of time, schedule them after approval, and still have older versions referenced by some users and asynchronous jobs. How would you model draft, review, publication, effective time, and rollback?
- An accountant uses one identity to manage several legal entities, each with separate contracts, invoices, and approvers; some group reports allow cross-entity summaries. How would you model identity, membership, resource ownership, and cross-entity access?
- Several users file cases about one incident. Some can share a resolution, but each has different contract deadlines, communications, and compensation eligibility. How would you model the parent issue, linked cases, individual commitments, and closure criteria?
- Plans sold through different channels share a display name but have different features, quotas, and renewal terms; users may switch channels during an upgrade. How would you distinguish the catalog display, sellable offer, contract version, and effective entitlements?
- An employee creates a project space and later hands it to another owner; the department manager still approves its budget, while audit requires the original creator to remain visible. How would you separate resource ownership, operational responsibility, authorization, and historical attribution?
- An enterprise plan includes seats, feature modules, and regional restrictions. The customer adds and removes seats mid-term. How would you model the contract, entitlements, usage, and change history?
- A service depends on platform capabilities, partner fulfillment, and the customer’s own process. The owner wants to know where failures occur. How would you map the parties, commitments, handoffs, and outcomes?
- A user may try a service, subscribe, pause, and later return. Product, operations, and finance count different events. How would you define lifecycle stages and transition rules?
- A feature serves newcomers, administrators, and expert users, each with different obstacles. How would you separate shared needs from role-specific needs without forcing them into one solution?
- A customer-facing capability spans identity, billing, notifications, and data teams. Each team can explain its local behavior, but no one owns the end-to-end promise. How would you define interfaces, owners, and acceptance boundaries?
- Sales materials combine several features into one offer, while entitlements and service levels live in separate configurations. How would you map the customer promise to verifiable product capabilities?
- A partner replaces manual review with batch processing. Wait time drops, but exceptions appear later. How would you decide whether customer workflows, service promises, and internal operations should change together?
- Three business teams need similar approval capabilities. Some want a shared platform; others fear an abstraction layer will slow delivery. Which user tasks, change patterns, and governance costs would guide the boundary?
- Conversion rose after a product redesign, while the service team also changed its workflow. How would you model the shared outcome without attributing it only to the online funnel?
- A proposal repeatedly refers to “core users” without identification rules, observation windows, or exclusions. What would you clarify so the team can study the same population?
- Administrators want all data on the settings page, while members need only task information. How would you define a common information structure and role-specific presentation?
No questions in this section match your target. ·
Commercial rules28
Pricing, revenue share, settlement, and how such rules are expressed.
- A customer buys a bundle and then asks to refund one item. How should the original bundle discount be reallocated?
- A customer cancels before service begins, but the contract, product page, and support system describe the cancellation fee differently. How would you determine the refund and make future orders follow a consistent rule?
- A major customer has a special rate in its contract, but the exception may end at renewal. How would systems and operations avoid keeping the old exception indefinitely?
- A partner prepays credits that expire, and a customer uses or refunds them in several batches around the expiry date. How would you represent credits, consumption, expiry, and refunds in settlement?
- In a system that handles money, how should accounting and billing be designed so the numbers are clear and reconcile? How do you model accounts, entries, holds, settlement, and reconciliation, and how do you trace and correct an error?
- How should amounts, currencies, rounding, and time zones be expressed in a transaction and settlement model? Which practices look fine but break at reconciliation?
- An order may use a membership discount, channel offer, and coupon, with exceptions by product, contract, or region. How would you define eligibility and calculation order so customers see a consistent amount and finance can reconcile refunds?
- The revenue share between a platform and its creators changes in tiers with monthly volume. How would you express this settlement rule so product, engineering, and finance can each verify it independently?
- An enterprise product charges a monthly subscription, overage usage, and a minimum-spend true-up. How would you define billing periods, usage attribution, price effective time, and invoice explanations so a customer can reconcile the charges?
- A promotion increases sales volume, but new customers’ first orders remain unprofitable after discounts, channel fees, and fulfillment costs. How would you isolate the loss and decide whether to change the offer threshold, audience, channel, or stop the promotion?
- A user orders through a channel and later receives a refund, chargeback, or cancellation. How would you define order value, attribution window, and channel cost so marketing analysis and finance settlement can both explain the same outcome?
- A new plan makes more users willing to try the product, but some customers who would have bought a higher-priced plan switch to the cheaper option. What commercial model and observation window would you use to judge whether the plan portfolio creates incremental value?
- Customers upgrade, downgrade, or pause subscriptions mid-cycle, while sales and finance disagree on revenue recognition. How would you express the rules and handle historical invoices?
- A user upgrades mid-cycle and later requests a refund. The contract requires a calculation based on remaining service time, while promotional discounts and taxes also affect settlement. How would you decompose the rules and make the amount calculation traceable?
- A campaign allows each user to claim a discount once, but under high concurrency a user submits from multiple devices and receives several entitlements. How would you map the eligibility rule to atomic reservation, issuance records, and failure compensation?
- Customers pay by API usage, but usage events may be duplicated, arrive late, or be replayed at month-end; sent invoices can lead to disputes. How would you define billable units, deduplication keys, close windows, and corrections?
- Order revenue is shared by a platform, provider, and channel partner. Weeks later, part of the order is refunded; one party has already settled and lacks sufficient balance. How would you express allocation rules, refund responsibility, recovery, and reconciliation state?
- A product offers one free trial, but users may register with another email, share a device with family, or qualify through a partner channel. How would you define the eligible party, exception sources, abuse boundaries, and appeals?
- Customers can apply points to part of an amount and then use a cash coupon; points may be funded by the platform or a partner and some may need restoration after cancellation. How would you separate payment, discount, point liability, and refund rules?
- After a merchant updates a price, an item already in a cart may still show the old amount; a submitted but unpaid order may carry a different commitment. How would you define price locking, effective time, and user notice?
- An enterprise pays per active seat, but some employees share accounts across shifts while others have accounts they never use; the contract does not define “active.” How would you determine the billable entity, activity definition, and dispute evidence?
- An enterprise contract promises response and recovery times and grants service credits when breached; one incident affects several features and crosses a billing period. How would you define timing, impact scope, credit caps, and appeal evidence?
- An order is priced in one currency and paid in another; a refund occurs after the exchange rate changes, and line-item rounding leaves the total off by the smallest currency unit. How would you define rate timing, rounding order, and ownership of the difference?
- A promotion starts at local midnight, services run in UTC, and customers may move regions. How would you represent effective time and handle boundary invoices?
- Last month’s usage arrives this month. The contract bills monthly and paid invoices cannot be silently overwritten. How would you handle adjustments and notification?
- A plan has a free allowance, tiered unit prices, and a monthly cap. An upgrade changes the cap immediately, while the allowance resets monthly. How would you define calculation order and explain the invoice?
- A customer changes plans mid-year. The contract permits partial rollover but forbids stacking discounts. How would you define rollover, reversal, renewal, and invoice transition rules?
- Marketing proposes behavior-based discounts that may raise revenue, but customers can compare offers. How would you define pricing rules, disclosure, and risk monitoring?
No questions in this section match your target. ·
Data model37
Entities, relations, grain, and their mapping to storage.
- Product, finance, and growth teams each report “active users,” but the numbers differ. What would you ask before deciding whether to standardize the definition?
- Taking concepts such as orders, contracts, and settlements, how are they mapped into the data model? Which concepts were split into several entities, which were merged, and why?
- A user consented to product analytics, then withdrew consent. Derived metrics already reached reports, experiments, and model-training data. How would you model consent state, purpose scope, and propagation?
- A business object moves across teams as owners change. Audit must reconstruct the owner on a past date, while daily reporting needs current ownership. How would you model both queries?
- A user asks to have personal data deleted, while finance must retain transaction records for audit. How would you define the boundary among deletion, anonymization, and traceability?
- In a behavioral event table, what exactly does one row represent? Explain how you settle its grain, and which statistics go wrong when the grain is unclear.
- A monthly close report was sent to leadership. Days later, a late refund and price correction arrive. The business wants current figures updated, while finance must explain the prior report. How would you model this?
- How does your own business model interact with the industry's or a partner's common model? When fields, definitions, or concepts do not line up, how do you handle it?
- Mobile events may arrive days late, while reports must reflect event time. How would you model and process late, corrected, and duplicate events?
- Orders, payments, and refunds are often stored in one table. How would you distinguish their business identities, lifecycles, and cardinalities? Compare conditions, costs, and validation for separate models and combined storage.
- A critical dataset is reused by several products and reports, but no one can explain its sources, owners, or sensitive fields. How would you improve governance without blocking current use?
- An account moves from sales to customer success mid-month. Monthly metrics must show the outcome and who owned it at each point. How would you define ownership events and reporting rules?
- A fee rule changes today, but a disputed order was created under the old rule. How would you preserve rule versions and transaction facts so finance can reproduce the original calculation?
- A company buys 100 seats used across subsidiaries. Headquarters signs the contract, but some subsidiaries want separate invoices and permission administrators. How would you distinguish customer, contract, organization, account, member, and seat so access and billing stay consistent?
- Customer master data has separate identifiers and states in CRM, billing, and product systems, so downstream reports disagree. How would you establish explainable sources of truth?
- A quality check occasionally produces false alarms and blocks downstream jobs; removing it once let bad data reach settlement. How would you design tiered handling?
- An enterprise customer has multiple organizations, departments, and members, and a member may act for different organizations. When designing customer activity analysis, how would you define the grain and relationships among customer, account, organization, and user?
- Support agents merge duplicate tickets and sometimes split a complex issue into several cases. When modeling service-quality data, how would you define the issue, ticket, contact, and resolution?
- Partner settlement must connect external order IDs, internal orders, payments, and refunds, but systems use different keys and update times. How would you build the mappings and reconciliation process?
- Business units use an “active customer” metric, but some define it by payment, others by usage, and others by likelihood to renew. How would you decide which definitions should be standardized and which should remain distinct concepts?
- Business reports mix orders, order lines, and payment attempts, so metrics disagree across pages. How would you establish fact-table grain and validate aggregation semantics?
- The source database has deleted a customer, but a change data capture (CDC) pipeline and downstream summary views still show the old record. How would you trace the deletion event, update dependent views, and verify cleanup?
- A dashboard's total conversion rate cannot explain which customer segment or process step caused a change; teams want to drill down by channel, plan, and region, but dimensions have different grains. How would you define fact grain and valid aggregation rules?
- Business reporting needs the duration of every state transition, while an operations page needs only the object's current state; a wide table overwrote history during updates. How would you separate event facts, snapshots, and current-state models?
- CRM, billing, and product logs use customer IDs, contract IDs, and anonymous device identifiers; analysts need one customer's lifecycle. How would you model identity mappings, confidence, temporal validity, and correction?
- Several teams maintain customer profiles. When data is wrong, no one knows which system is authoritative, and systems also write values back to one another. How would you define field ownership, source of truth, synchronization direction, and dispute handling?
- Orders contain nested line items, shipping, and tax, while refunds may apply to only some items; joining order headers directly to lines doubles totals in existing reports. How would you model grain and aggregation semantics?
- Sales performance rolls up through a regional hierarchy. Midyear, a region is split; historical reports must remain unchanged, while future reports use the new hierarchy. How would you represent organization versions, effective time, and attribution?
- Some transaction details must be retained for years under policy, while product analytics wants to use them for user segmentation and experiments. How would you model purpose authorization, retention, and access views?
- A user requests personal-data deletion, but the system uses append-only events, search indexes, and offline analytics copies; some events must remain for business audit. How would you distinguish deletable fields, identity mappings, cryptographic erasure, and retention exceptions?
- Revenue was recognized for an order last month, and a partial refund occurs this month. Finance and growth disagree on order count, net revenue, and refund-month treatment. How would you establish consistent data semantics?
- A service rebuilds state from an event log, but the live snapshot differs and responders cannot tell which to repair. How would you define authority and the repair process?
- Payment is authorized but not captured, and goods are not fulfilled. The business report counts an order, while finance records no revenue yet. How would you design cross-domain metric semantics?
- A payment channel charges a fee on partial refunds, and the contract assigns it to the merchant, but reports combine refund amount and fee. How would you model this?
- A user belongs to several organizations. The browser retains prior-workspace cache, and old organization data briefly appears after switching. How would you design the boundary?
- Operations counts revenue when an order is placed, while finance recognizes it after fulfillment and refunds. A leader wants one number. How would you explain the two measurement methods and design shared measures for decisions?
- Several teams manually corrected an aggregate table, and later no one could explain why the number changed. How would you record sources, transformations, versions, owners, and recomputation evidence?
No questions in this section match your target. ·
Feature model25
Feature definitions, time semantics, and reproducible computation.
- An account may hold a base plan, temporary trial, campaign benefit, and support credit. Systems implement precedence differently, so access sometimes flips. How would you define eligibility and conflict rules?
- A model feature will be retired, but several online models and historical reports still depend on it. How would you plan retirement and replacement?
- An online feature must refresh every second, but it affects few requests and its maintenance cost keeps rising. How would you decide whether to keep it real time?
- A risk model uses later default as its training label, but many transactions have no final outcome before the observation window ends. How would you handle label maturity, sample inclusion, and retrospective evaluation?
- You are building a 'days active in the last 7 days' feature for a model that predicts next-day churn. How do you define its time semantics so training and online prediction mean the same thing?
- Enterprise contracts specify first response, service restoration, and final resolution times, each with different pause conditions. Support tracks one SLA timer, causing disputes. How would you model this?
- Recommendation and risk teams both need a “spend in the last 30 days” feature, but one uses calendar days and the other a rolling hour window, and refund handling differs. How would you decide whether the definition can be shared?
- A risk value is usually present in training data, but live serving often substitutes a default and model performance fluctuates. How would you find whether the cause is data collection, timing, missing-value handling, or implementation differences?
- Models, operational rules, and reports share a core feature, but the upstream business definition has changed and some consumers cannot migrate yet. How would you manage old and new definitions, ownership, and migration order?
- An upstream dependency change will increase refresh latency for a costly feature set from seconds to ten minutes. How would you determine which decisions are affected, which features must remain real time, and when a fallback value is acceptable?
- Two models call a feature with the same name but receive different values due to defaults and missing-data handling. How would you establish a contract and compatibility checks? Follow-up: If a critical feature refresh misses the real-time decision window, how would you choose among stale values, fallbacks, or refusing the decision?
- A user clicks a campaign link on Monday and purchases on Tuesday, but the purchase event uploads on Friday because the client was offline. How would you define event time, arrival time, attribution windows, and backfill rules so results remain explainable?
- A device reports a cumulative counter, but the counter resets after device replacement or data correction; the data platform may also backfill historical events. How would you define deltas, reset markers, negative differences, and recomputation boundaries?
- A numeric feature value of zero may mean the user had no activity, missing may mean the device did not report, and unknown may mean computation is unfinished; the pipeline currently fills all three with zero. How would you define the semantics and downstream handling?
- A global product counts daily activity by calendar day, but product analytics, the warehouse, and model serving use user time, UTC, and server time respectively; results often differ near month-end. How would you define boundaries and versioned semantics?
- A user's transaction enters a behavioral feature window, then is reversed days later due to refund or fraud review; downstream models and reports have already consumed the feature. How would you model reversal, window recomputation, and impact propagation?
- A team wants a ratio feature of completions divided by applications, but applications can be withdrawn, duplicated, or later invalidated beyond the observation window. How would you define numerator, denominator, maturity window, and recomputation semantics?
- New users have little behavioral history, and the feature pipeline fills missing values with a global average, making “not observed” indistinguishable from “average behavior.” How would you represent cold-start status and evidence boundaries?
- An online feature service can return its last computed value after a cache expires, but some predictions need the freshest feature while others tolerate brief staleness. How would you define freshness metadata, task constraints, and unavailable-value fallback?
- A click-through feature suggests low interest in an item, but it appeared briefly at the bottom of a page; the team still trains a recommender on clicks. How would you model exposure opportunity, position, visibility duration, and user action separately?
- A prediction formerly used individual history, but a product now recommends at the organization level; membership changes over time and a person may belong to several organizations. How would you define feature ownership, membership validity, and aggregation deduplication?
- After an upstream migration, a feature keeps falling even though business activity is stable; consumers did not know the source field had been deprecated. How would you define feature lineage, health state, and replacement-source cutover?
- After a feature definition is fixed, the modeling team wants a historical backfill. Training reproducibility requires the original version, while business reports want corrected values. How would you design both views?
- Risk teams need to reproduce decision inputs from three months ago, but the online feature store keeps only the latest state to save cost. How would you balance reproducibility and storage cost?
- A missing risk feature is automatically set to zero. Latency and error rates are stable, but denial rates changed significantly. How would you judge whether the default is safe?
No questions in this section match your target. ·
Model evolution24
Keeping history, migrating, and staying compatible when rules change.
- A producer plans to rename a field and change an enum’s meaning, while a dozen teams depend on the current schema. How would you manage the change?
- An order has a single status field that means both fulfillment progress and payment result, and several teams read it. How would you split it into two concepts and move old data and old consumers over smoothly?
- A service changes eligibility from “current account status” to “account status at application time plus a risk-review result.” Support needs to explain historical denials, and audit must reproduce the original decision. How would you evolve rules and data models without conflating old and new outcomes?
- Duplicate registration created two customer entities later confirmed to be the same company. Reports should unify them, while contracts, approvals, permissions, and personal actions must retain original responsibility. How would you model the merge?
- A support ticket can be reopened when a customer provides new evidence and may be split into follow-up work. How would you model states and events so closure, reopening, and splitting remain traceable?
- A business rule is corrected retroactively. Reports need corrected results, while decision-makers also need the results available at the time. How would you manage both historical views?
- A producer adds an order status, and an old consumer rejects the whole message because enum validation is strict. Teams disagree over who must update, and consumers have different owners. How would you design compatibility and rollout order?
- The commercial rule for a service changes from a free trial to a refund after conditions are met, while historical orders were signed under the old terms. How would you evolve the model and workflow so both old and new transactions remain explainable?
- A supplier API replaces one “delivered” status with “dispatched” and “received,” but historical data has no basis for distinguishing them. How would you update the domain model, external contract, and related reporting?
- A database field has been replaced, but reports, exports, and external integrations still read it; deleting it directly could cause silent errors. How would you plan compatibility migration, consumer confirmation, and final removal?
- Billing changes from calendar-month pricing to service-day pricing, with the new rule applying only to new contracts; old contracts cross the release date, and support still needs to explain past invoices. How would you version rules, contract applicability, and invoice snapshots?
- Business categories may be added, merged, or renamed. Reports must reproduce the definition used at the time and compare results under the current definition. How would you preserve source categories, mapping versions, and report definitions?
- An event producer wants to change a field from a string to a structured object, but some consumers deploy slowly and others drop unknown fields when writing records back. How would you stage dual writes, version negotiation, migration, and retirement of the old format?
- A customer-ownership field in historical events is wrong and must be corrected in bulk to recompute downstream metrics; the same events may also trigger notifications and partner callbacks. How would you separate data recomputation from side-effect replay?
- A new workflow requires every record to have an ownership field, but historical data lacks it and older clients still write records. How would you design backfill provenance, dual-read/write migration, validation gates, and retirement of old clients?
- The system changes its user key from email to an immutable ID, but mobile caches, partner callbacks, and historical exports still reference email. How would you design mappings, a dual-read period, privacy cleanup, and retirement of old references?
- The team wants to move eligibility checks from service code to a configurable rules engine so Operations can adjust them; many historical exceptions exist and execution order is implicit in code. How would you discover rules, verify semantic equivalence, and govern configuration access?
- An early consumer deduplicates only by order ID, but one order can have several legitimate changes; the key must include an event version and historical messages need replay. How would you migrate keys without losing or duplicating processing?
- A customer entity must be split into two real customers after an erroneous merge, while old orders, permissions, and metrics reference the original ID. How would you model the split, historical attribution, current-reference migration, and indeterminate records?
- Several teams define user-status events differently, and the platform plans to unify them; some consumers rely on special meanings in old fields and cannot migrate at once. How would you build compatibility adapters, parallel validation, and deprecation governance?
- A product changes permanently valid credits to monthly refreshes, but some older contracts promise permanent balances and users have accumulated unused credits. How would you version rules, balance lots, contract cutovers, and user explanations?
- A new model requires additional features and changes the meaning of existing ones, while online serving must still support rollback to the old model. How would you version feature contracts, deployment order, dual-read cost, and retirement criteria?
- Orders, inventory, and loyalty points are owned by separate services; messages may be duplicated, reordered, or delayed. How would you define event identity, idempotency boundaries, and compensation records?
- A product line splits into two business units. Old orders belong to the previous organization, while future orders use the new structure. How would you represent organization versions and historical views?
No questions in this section match your target. ·