TOPIC
Data modeling
These are the same questions found in the library, grouped here by the capability each one mainly examines.
138 questions
Questions 1–50 of 138 on this page.
A · Professional problem solving and implementation8
- Enterprise knowledge documents may change, be withdrawn, or become restricted, yet users still receive answers citing old content. How would you propagate changes from source documents through chunks, indexes, caches, and existing citations, and prove that an update or deletion took effect?
- A RAG assistant cites an internal document, but its owner has updated the process and the new version is not indexed yet. How would you define freshness goals, propagation, and answer behavior during the gap?
- Two usernames that look identical are treated as different, or distinct spellings are treated as the same. How would you analyze Unicode normalization and identity comparison?
- In an admin console, inserts and deletes while paging by creation time cause duplicate or missing rows. How would you compare offset and cursor pagination and define the consistency expectation?
- Monthly aggregates initially match detail reports, but the gap grows over several weeks. How would you narrow the cause among definition changes, late data, duplicate processing, and historical backfills?
- A usage-based API product must combine request events from multiple regions into customer bills and allow later corrections. How would you design the usage-data processing flow?
- A team fine-tunes on user feedback, human labels, and synthetic samples, then receives a request to delete some source data. How would you trace impact and decide the scope of retraining?
- Users say answers sound plausible but omit a critical constraint present in the documents. How would you locate whether parsing, chunking, retrieval, ranking, or generation caused the failure?
No questions in this section match your target. ·
B · Business understanding and domain modeling41
- 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 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?
- 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?
- 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 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?
- 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?
- A model feature will be retired, but several online models and historical reports still depend on it. How would you plan retirement and replacement?
- 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?
- 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?
- 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 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?
- 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.
- 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?
- 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?
No questions in this section match your target. ·
C · Value judgment and direction setting1
No questions in this section match your target. ·