Zealynx AcademyZealynx Academy
Course checkpoint

Audit Scope, Evidence and Retesting

Question 1 of 5Score 0/5

What makes a proposed code-review scope reproducible?

Review and apply

Worked answers

Try the quiz above first, then open an answer to compare your reasoning. These notes are also available to read without completing an attempt.

  1. 1. What makes a proposed code-review scope reproducible?

    • A.Repository, fixed commit, included components and explicit assumptions or exclusions.
    • B.Only a project name and a launch month.
    • C.Only a promise that the latest branch is stable.
    • D.Only the desired marketing badge.
    Answer and explanation

    A. Repository, fixed commit, included components and explicit assumptions or exclusions.

    A fixed revision and scope identify what was reviewed. Dependencies, configuration and exclusions need explicit treatment; the latest branch can change during an engagement.

  2. 2. A team fixes a reported issue. What should retesting establish?

    • A.Every future version is now safe.
    • B.The fix addresses the original failure on an identified revision, with relevant regression evidence.
    • C.The entire product has no unknown vulnerabilities.
    • D.The original report should be deleted.
    Answer and explanation

    B. The fix addresses the original failure on an identified revision, with relevant regression evidence.

    Retesting is scoped evidence about a fix. Record the revised commit and checks, including nearby behavior; it is not a guarantee covering arbitrary future changes.

  3. 3. Two proposals quote different prices. What should you normalize before comparing?

    • A.Only the number of logo badges.
    • B.Only the proposal’s page count.
    • C.Scope, reviewer effort, assumptions, deliverables and included retesting.
    • D.Only the cheapest headline number.
    Answer and explanation

    C. Scope, reviewer effort, assumptions, deliverables and included retesting.

    Prices are meaningful only alongside the work included. A smaller scope or omitted retest may explain a lower figure; neither price alone nor report length proves review quality.

  4. 4. A critical dependency is explicitly out of scope. How should the launch decision treat it?

    • A.Assume it was implicitly reviewed anyway.
    • B.Remove it from the architecture diagram.
    • C.Call the whole system fully audited.
    • D.Record the remaining dependency risk and assign an owner for additional evidence or mitigation.
    Answer and explanation

    D. Record the remaining dependency risk and assign an owner for additional evidence or mitigation.

    An exclusion does not remove the dependency’s risk. Make the assumption visible and obtain the missing evidence or choose a documented mitigation.

  5. 5. The code changes after the final report. Which statement is accurate?

    • A.The report describes the reviewed revision; changes need risk assessment and possibly more review.
    • B.The report automatically covers the new revision.
    • C.All future changes require no tests.
    • D.The previous report becomes evidence that every change is safe.
    Answer and explanation

    A. The report describes the reviewed revision; changes need risk assessment and possibly more review.

    Assurance is tied to a scope and point in time. The effect of each change determines the extra work needed; do not imply a blanket guarantee.

Read alongside: Zealynx: audit methodology