USE CASE
Promotion preparation
Start with reviewed core questions. The extended library remains available below for broader exploration.
1060 questions
Extended library · not reviewed question by question
These questions remain useful for discovery, but have not received the same question-specific review as the core set.
Extended questions 401–450 of 996 on this page.
B · Business understanding and domain modeling32
- 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?
- 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?
- 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?
- 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'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 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 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?
- 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 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 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?
- 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?
- 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?
No questions in this section match your target. ·
C · Value judgment and direction setting18
- A mobile onboarding redesign helps more users complete setup on day one, but active retention drops two weeks later; the flow also requests more permissions. How would you judge whether short-term conversion masks lower long-term value or loss of trust?
- An AI assistant increases apparent task-completion rates, but users recheck every result and some errors cause downstream rework. How would you judge whether automation actually lowers total task cost?
- A new checkout flow omits a fee explanation and increases payment conversion, but refund questions and cancellations also rise. How would you decide whether short-term conversion is worth it and identify evidence that the design created an expectation gap?
- Analytics show target users skipping the product's main flow and using exports, spreadsheets, or manual coordination instead; the team believes this is a user-habit problem. How would you decide whether the product conflicts with real work practices?
- A new operations dashboard is visited often, but interviews show most people only take screenshots before reviews and do not adjust resources or actions. How would you decide whether it creates decision value or only serves a display need?
- A keyboard-navigation defect affects few users but prevents them from completing a critical task; a feature expected to add revenue is also waiting. How would you compare user harm, obligations, opportunity cost, and repair scope?
- A premium feature available only on mobile has few users, but they renew and show strong willingness to pay; continued support increases cross-platform differences and testing cost. How would you decide whether to expand, retain it as a premium capability, or stop investing?
- Two projects are both committed for this quarter and depend on the only expert familiar with a legacy system; splitting that person's time would slow both. How would you compare delay cost, alternatives, and investment in shared capability?
- The team can launch a limited but imperfect experiment this week, or wait three months for broader research before a large commitment; the latter may miss a key market window. How would you compare learning value, delay cost, and decision risk?
- A failure affects few requests but can cause unrecoverable data loss; a new feature is expected to add revenue but would delay reliability work. How would you compare probability, severity, detectability, and opportunity cost?
- Growth, Support, and Product each want a new home-page entry; each change helps one group but could make the core task harder for first-time users to find. How would you choose the entry priority and experiment sequence?
- A new market opportunity emerges mid-quarter and leadership wants an immediate pivot; customer promises, team goals, and partner schedules have already been published. How would you compare the opportunity window with the cost of breaking commitments and decide what to keep, reduce, or renegotiate?
- Several teams spend hours each month resolving deployment configuration problems; a platform change could remove repeated work but adds no immediate revenue, while product features have explicit revenue targets. How would you estimate attributable platform value and investment limits?
- A redesign improves average conversion but increases task failure for a constrained user group; expanding the sample requires more research time. How would you prioritize the risk and decide whether to pause rollout?
- Policy and procurement cycles in a new market are unclear, yet the company must set annual goals and budgets. How would you translate long-term direction into quarterly hypotheses, validation milestones, and triggers for adjusting the plan?
- The team plans to pilot a service in three cities, but supply quality, repeat use, and unit economics are unproven; sales materials already show a firm expansion timeline. How would you rewrite stage goals and external commitments?
- The same product has different technical debt, release cadence, and user behavior on iOS, Android, and web; the roadmap still schedules uniform feature milestones, leaving one platform early and another far behind. How would you plan across platforms and define consistency boundaries?
- The company sets an annual revenue target, while teams control only parts of product features, channels, or service capacity; quarter-end reviews often dispute attribution. How would you build a goal tree, dependencies, and team-controllable outcome measures?
No questions in this section match your target. ·