Continuity Scope and Service Priorities

Review questions

Integrated summary: Continuity Scope and Service Priorities

Continuity design starts with a service that produces a valid outcome for a beneficiary, not an inventory of systems or departments. The learner bounds booking, dispatch and settlement while separating supplier ownership from the organization’s responsibility to understand a dependency. They build impact across meaningful time points, distinguish request intake from valid confirmation, and calculate backlog and net clearance with explicit denominators. A dependency graph then tests whether apparent fallback routes share one failure point or one authorized employee. Finally, the learner reconciles an owner’s claim, register data and supplier promises by separating observation from assumption. The module yields a service charter, impact table, dependency graph and conflict ledger, each tied to a conditional priority and evidence that could change it.

Review questions

Test your understanding with these questions. Marking and saved results are available with a free account.

Question 1Which action preserves service scope and decision rights? Treat phone as wholly independent Name the confirmation decision owner and register escalation before promising appointments Give the supplier ownership of the service decision in the charter Declare phone fallback successful when calls ring
Question 2Which priority comparison is supported? A always, because it accumulates faster B always, because its clearance capacity is smaller Calculate each backlog-clearance time against its own impact limit Treat them as equal because outage duration is equal
Question 3What is whole-route capacity before another intervention? Forty-eight; authorization remains the constraint Fifty-four because vehicles are below triage Seventy because the alternate site adds triage capacity Sixty because that is required demand
Question 4What evidence is needed before assigning cause? Accept the supplier account because it has timestamps Attribute the entire two and a half hours to detection Delete approval time from the record Separate detection, decision and execution intervals with each stage's logs
Question 5What is the recovery-point judgment? Pass because the service returned quickly Permanent failure of every entry without review The potential gap is twenty-five minutes; verify entries before settlement confirmation Reset the objective to twenty-five minutes after the event
Question 6How should comparison begin? Give cost more weight so the cheaper route wins Check data-use eligibility before scoring benefits Choose the faster one and seek an exception later Treat the prohibition as a risk that a low weight can offset
Question 7What team-confirmation ceiling is demonstrated now? Ten hourly before queue and handoff checks Fifteen because the third name is on the plan Twenty because the supplier accepts that many Five because one absence cancels everyone's authority
Question 8What should govern the next release of funds? Pay because the pilot cost is sunk Double twenty-five on paper and call it fifty Skip verification because funding is available Pause release until sixty valid cases are proved at representative load
Question 9Which record prevents an unauthorized handoff? Switch first and find delegation later Count 09:30 approval as the first valid output Publish a return promise before route verification Record event, detection and approval times, then verify execution authority and first valid output
Question 10What is the safe-return step? Reconfirm every request immediately Reconcile A1 and A2 and resolve A3 before issuing any new confirmation Choose the visually newest row and delete the rest Count three completed cases because three identifiers exist
Question 11What correction is appropriate? Correct the claim, report seventy proved and fifty limited, and arrange contact for ten Leave the notice because most cases are fine Blame the supplier for fifty without logs Declare all 120 failed because some cases are unknown
Question 12Which estimate is sound before making that promise? One and a half hours because capacity is sixty Two hours because new requests can be ignored Net clearance is twenty hourly; 150 cannot clear in two hours Three hours by rounding 150 divided by sixty
Question 13Which exercise objective is falsifiable? Measure satisfaction with the briefing Ask whether the team feels ready Run an isolated route for two hours and count valid orders against thirty Declare readiness when all named staff attend
Question 14How should the card be repaired? Keep it to save time Give the disruption and observed data without naming the route or outcome Tell the participant the right choice before measuring it Hide the supplier entirely although it is a known dependency
Question 15What is the judgment against thirty correct delivered orders? PASS because thirty were unique PASS because twenty-five delivered is close Always UNVERIFIED because the observer is not a developer FAIL by seven; use logs to locate delivery and validity loss
Question 16How should the debrief separate the two judgments? Decision FAIL by three minutes; capacity UNVERIFIED with the stop reason Both PASS because a decision was made Capacity FAIL and decision UNVERIFIED because the trial stopped Hide the stop so the report looks stronger
Question 17How should the finding be written before testing causes? The supplier certainly caused forty minutes Technical return preceded valid output by forty minutes; cause remains unresolved The 09:40 application return proves service recovery Delete the interval because stage logs are missing
Question 18Which weekly schedule is defensible? Do all seven person-days of work within six Prioritize presentation training because its date is near Choose only the report because management sees it Contain confirmation, complete and test identifier repair, then allocate remaining time by report risk
Question 19What is the defect-closure judgment? Keep open until reconciliation proves twenty-five valid unique records Close because count and time met criteria Close if a developer saw no error message Fail timing because reconciliation took five minutes
Question 20What decision card fits before testing the new interface? Ready without limit because an old trial succeeded Every service is unready even if it does not use this supplier New scenario unverified; restrict operation to manual capacity with an owner and dated test Treat postponement as proof of technical failure