Isaca Updated COBIT-2019 Exam Questions and Answers by zunaira

The strategy archetype is a design factor that describes how an enterprise uses information and technology to achieve its goals and objectives. There are six strategy archetypes defined in COBIT 2019: customer intimacy, product leadership, operational excellence, compliance-driven, data-driven, and innovation-driven. Each archetype has different implications for the governance and management of information and technology in terms of focus areas, processes, practices, roles, structures, and metrics. The best approach when determining which strategy archetype most closely aligns with an enterprise’s own strategy is to select the one that reflects the enterprise’s information and technology risk profile, which is another design factor that describes how an enterprise identifies, assesses, responds to, monitors, and reports on information and technology risks. The risk profile helps to determine the level of risk appetite and tolerance that an enterprise has for its information and technology activities, as well as the level of control and assurance that is required for its governance framework. By selecting the strategy archetype that matches the risk profile, an enterprise can ensure that its governance framework is appropriate for its context and objectives5 References: 5: COBIT 2019 Design Guide, page 35-39 : COBIT 2019 Design Guide, page 41-43

The function of a mapping table when determining the initial scope of a new governance system is to indicate the relevance of a governance or management objective with a particular design factor. A mapping table is a tool that helps to identify and prioritize the governance and management objectives that are most applicable and important for the enterprise, based on its specific characteristics and context. A design factor is one of the characteristics of the enterprise that influence the design and operation of a governance system, such as size, industry, culture, strategy, etc. A mapping table shows the degree of relevance of each governance and management objective with each design factor, using a scale from 0 (not relevant) to 5 (very relevant). The function is based on the COBIT 2019 Design Guide, page 23. References: : COBIT 2019 Design Guide | Digital | English

The level achieved when all processes of a focus area achieve a particular capability level is referred to as the maturity level. A focus area is a topic or issue that can be addressed by governance objectives, such as digital transformation, cybersecurity, privacy, etc. A focus area consists of a set of processes that are relevant and applicable for the topic or issue. A capability level is a measure of how well a process or activity is performed in terms of effectiveness, efficiency, completeness, reliability, etc. A capability level can range from 0 (incomplete) to 5 (optimizing). A maturity level is the level achieved when all processes of a focus area achieve a particular capability level. A maturity level can range from 0 (non-existent) to 5 (optimized).12 References: COBIT 2019 Framework: Introduction and Methodology, COBIT 2019 Framework: Governance System

The governance system design workflow is a workflow that describes how an enterprise can design and implement a governance system using COBIT 2019. The governance system design workflow consists of six steps: determine initial scope; identify relevant design factors; prioritize governance and management objectives; define target capability levels; identify gaps; finalize scope. The governance system design workflow allows for consideration of all design factors in order to develop a customized governance system. The design factors are the characteristics or conditions that influence how an enterprise designs and implements its governance system using COBIT 2019. The design factors include aspects such as enterprise strategy archetype; enterprise goals; IT-related goals; risk profile; IT deployment; threat landscape; compliance requirement; operating environment; size of enterprise; culture; stakeholders; etc. By considering all design factors in the governance system design workflow, an enterprise can ensure that its governance system is appropriate for its context and needs, that it delivers value and benefits to the enterprise and its stakeholders, that it aligns with the relevant standards, guidelines, regulations, best practices, etc., that it meets stakeholder requirements and expectations, etc.References: : COBIT 2019 Design Guide: page 33-48