10 free sample questions from a bank of 124, with the correct answers and explanations. No signup required — start practising right now.
C — The board. COBIT 2019 settles this in the Introduction and Methodology, so framework recall beats general intuition. Only C fits Who is responsible for the oversight of structures and mechanisms.
The board is correct because COBIT 2019 defines this behaviour and scope exactly that way in the framework text and figures. Applied to Who is responsible for the oversight of structures and mechanisms, governance versus management, the goals cascade and design-factor tailoring converge on C. The book definition alone selects C.
Remember C equals The board for this stem; drop options that narrow scope or swap governance with management.
B — a balance among benefits, risk and resources.. COBIT 2019 settles this in the Introduction and Methodology, so framework recall beats general intuition. Only B fits Within the principles for a governance system, the value generated.
a balance among benefits, risk and resources. is correct because COBIT 2019 defines this behaviour and scope exactly that way in the framework text and figures. Applied to Within the principles for a governance system, the value generated, governance versus management, the goals cascade and design-factor tailoring converge on B. The book definition alone selects B.
Remember B equals a balance among benefits, risk and resources. for this stem; drop options that narrow scope or swap governance with management.
Answer B is correct because COBIT 2019 defines levels 2 through 5 as all achieving the process purpose, with higher levels adding organization, measurement and optimization on top of that foundation.
This question tests COBIT performance management and the CMMI inspired capability scale from 0 to 5. Level 0 means incomplete, level 1 means initial and intuitive, level 2 means managed and performed, level 3 means defined and using organizational assets, level 4 means quantitatively measured, level 5 means optimizing. The stem asks for a common trait shared by all of levels 2 to 5.
B states that the process purpose is achieved. Every ISACA description of levels 2, 3, 4 and 5 begins with that same phrase, showing it is the shared baseline. Level 2 achieves purpose through a basic yet complete set of performed activities. Level 3 adds organization with assets and well defined practice. Level 4 adds quantitative measurement. Level 5 adds improvement driven by measurement. Purpose achievement is therefore the only option present at every level in the range.
A about performance being monitored describes mainly level 2 managed behavior and level 4 quantitative control, but monitoring alone is not the stated common denominator across 2 to 5 in the framework wording. C about description being well defined starts at level 3 established, so it excludes level 2 and cannot be common to the full 2 to 5 range. Only B covers the entire range without exception.
When you see capability level stems, recall the ladder phrases by heart. Level 1 more or less achieves purpose, level 2 achieves purpose, level 3 achieves purpose plus well defined, level 4 adds quantitatively measured, level 5 adds continuous improvement. If the stem says 2 to 5, look for achieves purpose. If it says 3 to 5, look for well defined.
A — Maturity level. COBIT 2019 settles this in the Introduction and Methodology, so framework recall beats general intuition. Only A fits Which of the following performance measures is used to assess a.
Maturity level is correct because COBIT 2019 defines this behaviour and scope exactly that way in the framework text and figures. Applied to Which of the following performance measures is used to assess a, governance versus management, the goals cascade and design-factor tailoring converge on A. The book definition alone selects A.
Remember A equals Maturity level for this stem; drop options that narrow scope or swap governance with management.
Answer A is correct because enterprise size most directly shapes the scope, complexity and resourcing of a new IT governance system during design, more than location spread or hosting model alone.
This question tests COBIT 2019 design factors and the Design Guide workflow for tailoring a governance system. The eleven factors include enterprise strategy, goals, risk profile, related issues, threat landscape, compliance, role of IT, sourcing model, implementation methods, technology adoption and enterprise size. Refining scope means deciding which objectives, practices and structures are relevant and at what capability.
A points to size of the enterprise. Size drives number of roles, layers, processes, assurance needs and documentation burden. A very small entity needs a light system, while a large complex entity needs broader coverage, segregation and formal oversight. ISACA treats size as a critical tailoring parameter that scales governance up or down. Location and cloud choices matter, but they refine within the size driven envelope rather than setting its overall magnitude.
B about national or international locations matters for compliance and geopolitical variation, yet a large single country firm can still need a bigger system than a tiny multinational. It is important but secondary to overall scale when refining scope. C about cloud versus on premises is a tactical sourcing choice that affects selected controls and service practices, not the overall governance scope. Size therefore outranks both for most significant driver.
For design factor scope questions, rank structural factors first. Size and strategy usually dominate scoping, compliance and threat shape priorities, sourcing and methods shape tactics. Do not pick a tactical hosting option when the stem asks for most significant scoping driver for a new system.
B — the enterprise's strategy.. COBIT 2019 settles this in the Introduction and Methodology, so framework recall beats general intuition. Only B fits Before designing an enterprise IT governance system, an organization.
the enterprise's strategy. is correct because COBIT 2019 defines this behaviour and scope exactly that way in the framework text and figures. Applied to Before designing an enterprise IT governance system, an organization, governance versus management, the goals cascade and design-factor tailoring converge on B. The book definition alone selects B.
Remember B equals the enterprise's strategy. for this stem; drop options that narrow scope or swap governance with management.
A — the enterprise's risk profile.. COBIT 2019 settles this in the Introduction and Methodology, so framework recall beats general intuition. Only A fits When designing an IT governance system, the NEXT step after.
the enterprise's risk profile. is correct because COBIT 2019 defines this behaviour and scope exactly that way in the framework text and figures. Applied to When designing an IT governance system, the NEXT step after, governance versus management, the goals cascade and design-factor tailoring converge on A. The book definition alone selects A.
Remember A equals the enterprise's risk profile. for this stem; drop options that narrow scope or swap governance with management.
C — IT governance is sponsored by executives.. COBIT 2019 settles this in the Introduction and Methodology, so framework recall beats general intuition. Only C fits Which of the following is IMPERATIVE to the successful implementation.
IT governance is sponsored by executives. is correct because COBIT 2019 defines this behaviour and scope exactly that way in the framework text and figures. Applied to Which of the following is IMPERATIVE to the successful implementation, governance versus management, the goals cascade and design-factor tailoring converge on C. The book definition alone selects C.
Remember C equals IT governance is sponsored by executives. for this stem; drop options that narrow scope or swap governance with management.
Answer A is correct because you must baseline current capability before you can set credible performance measures and targets for a process improvement initiative.
This question tests COBIT performance management and the implementation lifecycle. Improvement starts by knowing where you are, then defining where you want to be, then measuring progress. Capability assessment evaluates activities, artifacts and practices against levels 0 to 5. Performance measures need that baseline, otherwise targets are arbitrary and unrelated to process reality.
A requires conducting a capabilities assessment first. In COBIT, each governance and management objective has practices with expected capability levels. Assessing them reveals strengths, gaps and realistic improvement scope. Only after that can meaningful measures, indicators and target levels be defined and tracked. Risk assessment and ROI analysis use the baseline later to prioritize and justify, but they do not replace the baseline itself.
B about calculating return on investment is useful for business case justification, but ROI depends on knowing current performance and improvement cost, which you only know after assessment. Doing ROI first risks overstating benefits. C about process risk assessment identifies threats and control gaps, valuable for risk driven improvements, yet it does not establish the capability baseline needed to define measures for the whole initiative. Assessment must come first.
Watch for MUST be done before stems. COBIT loves assess current state before define measures, set targets or build roadmaps. If one option is assess capabilities or maturity and another is calculate ROI or define metrics, pick assessment first. Link this to APO02 assess current capabilities and MEA01 monitoring logic.
B — Customize COBIT guidance to meet specific enterprise needs.. COBIT 2019 settles this in the Introduction and Methodology, so framework recall beats general intuition. Only B fits Which of the following should a stakeholder do to optimize the use of.
Customize COBIT guidance to meet specific enterprise needs. is correct because COBIT 2019 defines this behaviour and scope exactly that way in the framework text and figures. Applied to Which of the following should a stakeholder do to optimize the use of, governance versus management, the goals cascade and design-factor tailoring converge on B. The book definition alone selects B.
Remember B equals Customize COBIT guidance to meet specific for this stem; drop options that narrow scope or swap governance with management.
Want the full bank of 124 questions for COBIT 2019 Foundation? See all practice exams.