Review the assurance handover

Objectives

The migration lead wants six statements accepted into the assurance pack. She argues that public means exposed and managed means no customer evidence. Judge each statement on the stated facts, not her shorthand.

Accept technically sound statements. Reject each incorrect statement using the single applicable reason code: characteristic-confusion, deployment-confusion, ownership-error, or evidence-gap.

Verdicts are accept or reject. Every rejection needs one reason code from: characteristic-confusion | deployment-confusion | ownership-error | evidence-gap.

CC-1 Metered storage consumption demonstrates measured service, not by itself rapid elasticity.
CC-2 A public cloud deployment means every customer record must be publicly readable.
CC-3 In IaaS the provider patches the customer's guest OS merely because it owns the physical host.
CC-4 For SaaS tenant offboarding operated solely by the customer, a facilities-only provider report is sufficient evidence of removal.
CC-5 A PaaS customer still maintains vulnerable dependencies bundled in its own deployed application under the stated contract.
CC-6 A private cloud may be operated off premises by a third party for one organisation's exclusive use.

Step-by-step hints

The guided walkthrough, in full. It is free: no XP cost, and it does not touch the paid hint ladder or the reveal gate.

1. Step 1

   Read the request before the artefact

   Read each claim as a testable assertion. Distinguish resource behaviour, permitted consumer population, maintenance duties and evidential scope.

2. Step 2

   Judge every line, including the boring ones

   Account for every fixture row exactly once, including correct statements that need no repair.

   Every line in the fixture carries a verdict

3. Step 3

   Separate what is wrong from what is merely ugly

   Compare each assertion against the service boundary or deployment definition. Correct statements can acknowledge retained customer work without denying provider obligations.

   Accept and reject land on the right lines

4. Step 4

   Say why, in the vocabulary the programme uses

   Match the failed assertion to the supplied code definitions: resource behaviour, consumer population, control performer, or proof of operation. Choose the category of the actual error rather than a nearby topic.

   Each rejection cites a valid reason code

Rules summary

• XP on pass

  40 bonus XP the first time every check goes green.

• Paid hints

  2 available. Each costs 25% of the lab XP (about 10 XP).

• Reveal solution

  Scores 0 XP and unlocks only after 3 check runs.

• Attempt cap

  60 check runs per learner. The runner warns you in the last 10.

• Drafts

  Your editor content is saved in this browser, so a reload will not lose work.

• Walkthrough

  Always free and never penalised: use it before spending a hint.