TOPIC
Risk management
These are the same questions found in the library, grouped here by the capability each one mainly examines.
163 questions
Questions 1–50 of 163 on this page.
A · Professional problem solving and implementation15
- A document assistant can submit most cases automatically, but mistakes have very different consequences. Human review has reduced errors, but the queue keeps growing. How would you decide which cases to automate or review, and keep the queue within the team’s capacity?
- A new model raises overall accuracy from 91% to 94%, but errors remain concentrated in cases that affect customer rights. The team wants to ship based on the aggregate score. How would you decide?
- An old system keeps accumulating new business and is becoming hard to maintain. How would you create an adapter boundary between old and new systems so legacy rules and data models do not spread into new code? Explain the migration steps and any compromises or risks you would accept.
- Tell me about an architecture upgrade. Why did it have to be upgraded rather than patched further, what challenges came up during migration, how did you keep the business running, and did the benefit materialize?
- Your solution depends on a lower-level service or library. If it changes substantially, how would you migrate, fall back to a version that preserves core features, or replace it?
- The root cause of an incident is still unknown, but business stakeholders ask when service will recover. How would you update them, communicate uncertainty, and avoid misleading commitments?
- A release must reach thousands of runtime nodes with varying versions and network conditions. How would you design rollout batches, health checks, and pause criteria?
- The application can be rolled back, but a database migration removed an old field and the previous version can no longer start. How would you redesign release order and rollback?
- A user requests deletion of personal data, but some records have reached backups, analytics warehouses, and downstream systems. How would you design a verifiable deletion process?
- Service failures have exceeded the target range, but the business has firm feature commitments. How would you adjust the release pace and investment in reliability?
- A new external service will access user data and trigger internal actions. How would you perform a lightweight but effective threat model?
- The system uses pre-signed URLs for private downloads, but links can be forwarded or retained for a long time. How would you design authorization and expiry boundaries?
- A third-party model provider changes its training, retention, or cross-border terms. When should calls pause or receive renewed approval?
- Average AI quality meets the target, but a few high-risk errors can cause harm. How would you set the release gate?
- When the model cannot establish an answer, should the product refuse, return a low-confidence result, or escalate to a person? What distinguishes the choices?
No questions in this section match your target. ·
B · Business understanding and domain modeling17
- 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 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?
- 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?
- 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?
- 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 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?
- 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 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?
- 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?
- 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?
- 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?
No questions in this section match your target. ·
C · Value judgment and direction setting4
- A checkout experiment improves payment completion, but complaints and refunds also increase. How would you judge whether the experiment succeeded, and how long would you wait before deciding?
- A new automated workflow doubles processing speed and reduces human review, but errors have a greater impact on a small group of high-value customers. How would you assess net value and decide whether to expand it?
- Interviews and support tickets repeatedly mention the same problem, but few users in a pilot are willing to change their current workflow. How would you determine whether the issue is how the need was expressed, switching cost, target-user selection, or problem priority?
- The annual conversion target depends on an untested channel assumption. How would you separate current commitments, assumptions to validate, and checkpoints for continuing, changing, or stopping?
No questions in this section match your target. ·
D · Delivery and ongoing operations10
- A data-write incident has stopped and service metrics look normal, but users still report missing records. How would you organize recovery validation and follow-up communication?
- For three consecutive quarters, several teams underestimated integration and acceptance time. How would you use forecasts and actuals to determine whether the error comes from estimation, scope change, or scheduling, and improve the next forecast?
- The organization requires every project to use the same weekly reports, reviews, and approval gates; a small exploratory effort now spends more time reporting than executing. How would you design tiered governance without missing high-risk work?
- A project depending on a platform interface is already integrating when the upstream team announces a semantic change this quarter and cannot support both formats indefinitely. How would you decide compatibility, migration order, and release boundaries across projects?
- Four months after delivery, the targeted cost reduction has not appeared in financial reports. The sponsor says the system is still in a learning period, while finance considers the project closed. How would you clarify benefit ownership and the validation window?
- A new service launches on schedule, but the project team is moving to other goals; on-call ownership, documentation, cost monitoring, and follow-up improvements have no clear owners. How would you determine whether the project is ready to hand off?
- A release project has capacity, vendor-delivery, and data-quality risks, each below its individual escalation threshold, but all may converge in the same week. How would you assess the combined risk and decide what action to take?
- During a major promotion, landing-page traffic meets expectations but add-to-cart and order rates are far below target. How would you quickly distinguish traffic quality, page information, pricing rules, inventory, and fulfillment issues?
- A limited-time promotion launches, but popular products run short. Some channels have already promised availability while others continue sending traffic. How would you adjust promotion, page promises, replenishment, and customer communication?
- To meet a quarterly goal, a partner asks to expand promotion delivery at short notice. An initial check suggests the new audience may exceed agreed authorization and brand boundaries. How would you move the decision forward within the deadline?
No questions in this section match your target. ·
F · People and organization building1
No questions in this section match your target. ·
H · Professional responsibility and work style3
- A business lead asks you to publish a financial-rule fix without the required second-person review to meet a promotion window. You do not yet have enough information to confirm rollback safety. How would you assess and respond?
- You discover that last week’s configuration change made part of a report inaccurate. Worried about appearing unreliable, you tried to correct it alone first; the impact is still unknown. What would you do now?
- Your quarterly outcome has not definitively failed, but new validation has sharply reduced the chance of meeting it on time. You worry early reporting will look like weak execution. How would you communicate and organize next steps?
No questions in this section match your target. ·