CRISC domain - 26% of the exam

Governance

Governance is 26% of the CRISC exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

75
Practice questions
10
Objectives
52
Medium
23
Hard

Where people go wrong

  • Confusing appetite, tolerance and capacity

    The wrong answers treat the three terms as interchangeable. One lifts a tolerance band up to the appetite, another approves a cloud service because it sits within appetite while it exceeds the tolerance for that objective, and another keeps appetite fixed after the capital buffer falls. Capacity is the most the organisation can absorb before its survival is threatened. Appetite must sit within capacity, and tolerance bounds a specific objective more tightly than appetite does.

    See it in a sample question
  • Judging correlated exposures one at a time

    The wrong answers keep ratings separate, average them, take the highest, or validate each acceptance alone. Three business units sharing one cloud provider, accepted data-loss exposures with the same root cause, and eleven systems behind one single sign-on service each look acceptable in isolation. Aggregation combines the related exposures into one position and reports it against enterprise appetite, which exposes the concentration that individual ratings and local tolerance bands hide.

    See it in a sample question
  • Blurring who operates a control and who assures it

    The wrong answers blur operating a control with assuring it. They have the risk function run a business control, run it jointly or hand it to internal audit, and they leave a team reviewing controls it configures while it tests more often or documents more. Where risk management merges with internal audit, or audit signs off control design, they blame the first or second line. The first line owns and operates controls, the second advises and monitors, and the third assures controls it neither designs nor operates.

    See it in a sample question
  • Mixing up policy, standard and guideline

    The wrong answers give a document the wrong force. Optional advice about screen locks where convenient is called a standard, and a procedure or guideline is offered where the missing piece is a mandatory, measurable requirement such as password length or a lockout threshold. A policy states leadership-approved intent, a standard turns that intent into mandatory measurable parameters, a guideline is advisory and left to discretion, and a procedure sets out sequenced steps.

    See it in a sample question
  • Treating a legal duty as negotiable

    The wrong answers let a contract clause, a cost argument, appetite or an internal exception override the law. A customer contract permitting broad data reuse and residual risk sitting within appetite are both offered as grounds to depart from a statute. Law sets a floor: a contract term that conflicts with mandatory law is generally unenforceable, and no internal risk acceptance or exception can waive a statutory control that carries no exception clause.

    See it in a sample question

Objectives in this domain

What to study

The official documents this domain's practice questions cite most.

Sample questions from this domain

Free sampleGovernancehard

A business unit proposes adopting a new cloud analytics service whose assessed residual data-confidentiality risk sits clearly within the enterprise risk appetite but slightly above the tolerance band set for that specific objective. How should the risk practitioner advise the decision be guided?

  • AApprove the service without change, because residual risk inside the enterprise appetite is automatically acceptable for any objective
  • BTreat the residual risk down to the objective tolerance band before approval, because tolerance constrains the specific decision even when appetite is met Correct
  • CReject the service outright, because any exposure above a tolerance band represents a breach of the enterprise risk capacity ceiling
  • DRaise the tolerance band for this objective to match appetite, because alignment between the two removes the conflict cleanly
Apply objective-level tolerance as the binding constraint on a decision even when enterprise appetite is satisfied. Appetite is an enterprise-wide willingness, while tolerance is the narrower acceptable variation around a specific objective; a decision must respect the tighter tolerance band, so exposure above it is treated before approval.

Why A is wrong: Sitting within appetite is tempting grounds for approval, but the tighter objective tolerance still governs this particular decision and is exceeded.

Why B is correct: Tolerance is the binding limit for that objective, so the exposure must be reduced into the band even though the broader appetite is satisfied.

Why C is wrong: Outright rejection conflates tolerance with capacity; exceeding a tolerance band is not the same as breaching the survival limit of the enterprise.

Why D is wrong: Lifting tolerance to appetite looks like tidy alignment, yet it discards the deliberate tighter limit set for this sensitive objective.

Free sampleGovernancehard

Over a quarter, several business units each accept a residual data-loss exposure that individually sits within tolerance, but the practitioner notices the accepted exposures share the same root cause and together approach the enterprise appetite limit for that category. What should the practitioner do?

  • AConfirm each acceptance independently, because every individual exposure remains within its own tolerance band and the unit owners have already authorised them
  • BAggregate the related accepted exposures and report the combined position against the enterprise appetite, escalating because the cumulative total approaches the appetite limit Correct
  • CRaise the tolerance bands for the affected units so the individual acceptances retain a clear margin and no further escalation becomes necessary this quarter
  • DDefer any action until one of the accepted exposures breaches its own tolerance band, since no single unit has yet crossed the limit set for its objective
Aggregate correlated risk acceptances and assess the combined exposure against enterprise risk appetite, not each decision alone. Tolerance bands govern individual objectives while appetite bounds the enterprise as a whole; exposures sharing a common cause are correlated, so they must be aggregated and measured against appetite, because the combined total can breach the enterprise limit even when every separate acceptance stays within tolerance.

Why A is wrong: Validating each decision in isolation feels procedurally correct, yet it ignores that correlated exposures combine into an enterprise position that can breach appetite while every part looks compliant.

Why B is correct: Appetite is an enterprise-level boundary, so correlated acceptances must be summed and assessed together; the combined figure, not each isolated decision, is what governs against appetite.

Why C is wrong: Widening the unit limits removes the appearance of pressure, but it loosens controls precisely where shared exposure is building and conceals the growing enterprise total.

Why D is wrong: Waiting for a single-unit breach is tempting restraint, but cumulative exposure can exceed enterprise appetite long before any one unit crosses its local band.

Free sampleGovernancemedium

Concerned that a business unit operates its key reconciliation control poorly, the enterprise risk function proposes to take over running that control itself so the outcome improves. A risk practitioner is asked whether this is sound under the lines of defence model. What should the practitioner advise?

  • AThe risk function should run the control, since improving the outcome matters more than which line performs the day-to-day task
  • BThe risk function should advise on redesigning the control and monitor it, while the business unit continues to own and operate it Correct
  • CThe risk function should run the control jointly with the business unit so accountability for the result is shared between them
  • DInternal audit should take over the control because it is the most independent function and can be trusted to run it well
The second line advises on and monitors controls but must not operate first-line controls, or it loses the independence needed to challenge them. The model works because each line does a different job: the first line owns and runs controls, the second line sets standards and challenges, and the third line gives independent assurance. If the second line starts operating a control, it ends up overseeing its own work, so there is no objective challenge left and the business unit quietly sheds the ownership it must retain. Advising and monitoring keeps the boundary intact while still improving the control.

Why A is wrong: Better outcomes are tempting, but having the second line operate a first-line control destroys its ability to challenge that control objectively and leaves no independent oversight of it.

Why B is correct: Keeping operation with the first line and limiting the second line to advice and monitoring preserves the separation between owning a control and overseeing it, which is the core discipline of the model.

Why C is wrong: Shared operation sounds collaborative but blurs ownership; when both lines run the control, neither can independently oversee it and accountability becomes impossible to pin down.

Why D is wrong: This misreads the third line; audit provides independent assurance and cannot operate a control it must later evaluate without forfeiting that independence entirely.

Free sampleGovernancemedium

A risk practitioner is explaining to a project team why an enterprise data-retention policy alone is not enough and why supporting standards must also be issued. The policy states only that personal data must not be kept longer than necessary. What is the primary reason standards are needed alongside such a policy?

  • AStandards translate the policy intent into specific, measurable requirements so that controls can be implemented and tested consistently across systems. Correct
  • BStandards replace the policy over time so that the organisation can retire the higher-level statement once the detail is documented.
  • CStandards record the senior management intent that the data-retention policy is unable to express on its own to the wider organisation.
  • DStandards give business units the discretion to decide locally how long each type of personal data should be retained for their own needs.
Understand that standards operationalise policy intent into specific, testable requirements for consistent control implementation. A policy sets high-level intent that is too broad to act on directly, so standards are needed to translate that intent into specific, measurable and mandatory requirements, which is what lets controls be built and tested consistently across the estate.

Why A is correct: Standards convert broad policy intent into specific testable requirements, giving teams a concrete baseline to build and assess controls against consistently.

Why B is wrong: It is tempting to think detail supersedes intent, but standards support and derive from the policy rather than replacing it within the hierarchy.

Why C is wrong: This reverses the hierarchy, because expressing management intent is the role of the policy, not of the supporting standards beneath it.

Why D is wrong: Local discretion sounds flexible, but standards exist to set a consistent mandatory baseline, and discretionary advice is the role of guidelines instead.

Free sampleGovernancemedium

A new data protection law imposes obligations that conflict with an existing customer contract clause permitting broad data reuse. What should the risk practitioner advise the organisation to treat as the governing requirement when setting controls?

  • AThe statutory data protection obligation, because applicable law overrides conflicting contract terms and non-compliance carries enforcement and penalty exposure. Correct
  • BThe customer contract clause, because the signed agreement reflects a negotiated commitment that the organisation is legally bound to honour before any later law.
  • CWhichever requirement the business owner judges to be lower cost to implement, documenting the rationale for the decision in the risk register for later review.
  • DBoth requirements equally, applying whichever control is stricter on a clause-by-clause basis and escalating only the residual differences to senior management.
When a contract clause conflicts with applicable law, the statutory obligation governs and controls must satisfy the law first. Mandatory legal requirements sit above private contractual terms in the obligation hierarchy, so a contract clause that conflicts with the law is unenforceable and controls must be designed to meet the statute, with the clause renegotiated.

Why A is correct: Statutory obligations take precedence over private contract terms, so controls must satisfy the law first and the conflicting clause should be renegotiated or treated as unenforceable.

Why B is wrong: A contract is binding between parties, but a clause that conflicts with mandatory law is generally unenforceable, so prioritising it would create legal exposure.

Why C is wrong: Cost is a valid input to control design but cannot override a mandatory legal obligation, so a cost-driven choice here would accept unlawful processing.

Why D is wrong: Applying the stricter control sounds prudent, but treating an unenforceable clause as equal to law misstates the hierarchy and can still breach the statute.

Other domains in this exam

See also the CRISC cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by ISACA. Original, blueprint-aligned practice material only.