TOPIC
Risk management
These are the same questions found in the library, grouped here by the capability each one mainly examines.
163 questions
Questions 101–150 of 163 on this page.
A · Professional problem solving and implementation5
- A core service remains within its monthly SLO, but its error budget is being consumed much faster and errors cluster around a recent feature release. How would you decide whether to pause rollout or roll back?
- A new model scores much better on an offline test set, but a small production rollout shows lower task completion for one user group and more complaints. How would you determine where the evaluation set, metrics, or release decision failed?
- A feature is fully launched, but switches created years ago still control several code paths; the team does not know which flags can be removed and relies on memory during rollback. How would you establish flag lifecycles and cleanup ownership?
- An AI assistant reads user-uploaded documents that may tell it to ignore existing rules and call external tools. How would you distinguish data from instructions, constrain tool permissions, and verify the safeguards?
- Users can upload archives for processing, and a past incident showed that malicious files could exhaust resources or access paths without authorization. How would you design isolation, extraction limits, content checks, and safe failure behavior?
No questions in this section match your target. ·
B · Business understanding and domain modeling4
- 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?
- 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?
- 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?
No questions in this section match your target. ·
C · Value judgment and direction setting5
- 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?
- 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?
- A low-traffic experiment shows a large conversion lift, but only dozens of users participated and a few large transactions account for most of the gain. How would you judge stability, risk, and whether to expand the sample?
- Security recommends stronger access auditing and anomaly detection, but no recent incident quantifies the benefit; Product wants customer-visible features first. How would you build risk scenarios, control evidence, and a reasonable investment level?
- One customer contributes nearly half of product revenue and asks for prioritized custom features; expanding similar accounts may grow faster but increase concentration and bargaining risk. How would you assess concentration, market opportunity, and product independence?
No questions in this section match your target. ·
D · Delivery and ongoing operations18
- An identity-field change affects clients, APIs, the warehouse, and external partners, but the initial plan lists only server development and a front-end update. How would you decompose the dependency graph and find missing migration, rollback, and acceptance work?
- The team plans to move order data to new storage, switching reads first and writes later; the plan includes development and launch but lacks data-difference checks and rollback criteria. How would you complete the migration breakdown?
- Every initiative in the quarterly portfolio is labeled top priority, but Product, Data, and Security lack capacity to support them all. How would you standardize priority definitions, expose dependencies, and make resource trade-offs?
- Five projects each look reasonable by their own value ranking, but they share three sequential dependency teams and cannot finish within the quarter. How would you identify portfolio bottlenecks, resequence work, and decide whether to split delivery?
- A major campaign overlaps with holidays, and support, review, and supply teams expect to run short on capacity; the campaign is already public. How would you plan staffing, control incoming demand, inform users, and escalate exceptions?
- A mobile release goes to 5% of users. The crash rate appears to double, but active devices are few and mostly one older model; a marketing campaign is near. How would you limit harm, gather evidence, and decide whether to continue, pause, or roll back?
- A new system depends on unverified third-party capabilities, so the full implementation cannot be estimated accurately; leadership still needs a credible time range. How would you sequence technical probes, risk validation, and delivery stages?
- Annual project funding is approved, but critical roles remain unfilled and outsourcing is limited by security requirements; another team has available people but needs role changes. How would you compare delay, scope reduction, internal transfer, and budget reallocation?
- Project plans list dependent teams but no delivery owners or confirmed dates; each project looks feasible alone, while the portfolio may compete for the same capacity. How would you build dependency commitments and a risk view?
- A project has requirements, design, testing, and launch reviews, but complete documents do not prove key assumptions; risks often surface only in the meeting. How would you make stage gates real decision checks?
- A vendor failure blocks a critical project. Business, Engineering, Legal, and Finance need information, but several status meetings delay action. What information would you send to whom, and in what order, to identify a decision owner and next steps quickly?
- An external provider's response time and first-contact resolution worsen for several weeks, but the contract specifies only a monthly average SLA; internal teams repeatedly compensate. How would you design segmented monitoring, reviews, remediation, and contract changes?
- A core service is partially unavailable and the cause is unknown; customers, executives, and partners request updates, while the team worries that early communication could mislead. How would you separate known facts, hypotheses, actions, and the next update time?
- The plan calls for a full launch by quarter end, but core data authorization and compliance review are unresolved. How would you set stage gates so preparation can continue without creating irreversible investment before key conditions are met?
- A project is nearly complete, but the business sponsor has left and the receiving team has no clear owner. How would you handle acceptance, handoff, and unresolved risk?
- An outage did not meet the threshold for a major customer incident, but affected a small group and exposed process gaps. How would you decide whether and how much to publish?
- The same remediation command has different effects in two regions, but the runbook describes only the default topology. Responders may use it in the wrong environment. How would you revise and prevent recurrence?
- Disaster-recovery drills notify every team a week in advance, and special scripts make the exercise succeed while real recovery still fails. How would you redesign the drill?
No questions in this section match your target. ·
E · Collaboration, communication, and influence10
- The business sponsor insists on the original release date, but a limited rollout shows refund rates and support tickets exceeding agreed bounds. Product thinks the sample is too small, while security wants to pause. How would you turn the dispute into a decision?
- A cross-functional review is shortened to ten minutes, and decision-makers only want to know whether launch can stay on schedule. Your evidence shows two risks with different impact scopes. How would you organize the information so they can make an informed choice quickly?
- When would you escalate a cross-team problem to a higher level, and how would you describe it?
- A cross-department meeting records a decision, but an affected team says it cannot deliver on time. How would you confirm who accepted the decision, which objections remain, and who owns the next step?
- The release owner decides to ship on schedule. The security team says residual risk exceeds its acceptance range, but leadership chooses to continue. How would you record dissent, responsibility, and review conditions and clarify executable scope and escalation boundaries?
- You are leaving a project with an unconfirmed risk that may affect launch. The successor has limited context. How would you hand it off?
- One person favors shipping on time and fixing later; another believes current defects harm customer trust. Each thinks the other is slowing the project. How would you handle it?
- You believe a project risk should be shared with a customer or executives, while your manager wants more evidence first. How would you handle it?
- Near launch, a security review finds design issues and the business says requirements arrived too late. How would you improve involvement in future projects?
- You find that an executive-backed plan may miss its goal and have no immediate alternative. You need to report the risk while keeping teams moving. How would you act?
No questions in this section match your target. ·
F · People and organization building2
- You are the final decision-maker on a cross-team choice. How do you let people in different positions raise new facts and request a review, and what signals would make you reopen it?
- Critical system knowledge sits with one senior engineer during a peak delivery period. How would you plan knowledge transfer, backup ownership, and short-term capacity?
No questions in this section match your target. ·
G · Learning, adaptation, and sustained growth2
- A high-pressure stretch has lasted several weeks. How do you judge whether to keep going or whether you are burning effort for nothing, and what do you adjust?
- Tell me about a project that did not succeed. Why did it fail, which causes were direct and which more fundamental, and how much of it related to your own judgment?
No questions in this section match your target. ·
H · Professional responsibility and work style4
- On call, you find a data-repair script that could quickly restore a report but might overwrite changes customers just submitted. The owner is unreachable and the business asks you to act immediately. How would you separate protective steps you can take, actions requiring authorization, and escalation?
- A customer is in a hurry and someone asks you to skip a rollback check before launch, where a failure could irreversibly damage user data. How do you judge whether this is a line that cannot be traded away, and how do you escalate it?
- You find a delay risk in a project you own, and your manager has been pleased with progress so far. When and how would you raise it?
- While reviewing a partner document, you find exposed customer credentials. This is outside your team’s remit, the owner is away, and the material may be public. How would you contain and hand off the risk?
No questions in this section match your target. ·