The Open Group TOGAF Enterprise Architecture Part 2 - OGEA-102 Exam Practice Test

A. You commence an iteration of ADM Phase A, identifying the stakeholders and revising the Architecture Vision. You perform a Stakeholder Analysis and update the Stakeholder Map. You conduct workshops and interviews to reflect the stakeholders who are now the key drivers for the digital products and services. You coordinate with the CIO to ensure alignment with the overall roadmap and update the Implementation and Migration Plan accordingly.

B. You research leading data companies, using your findings to help in developing high-level Target Data, Application, and Technology Architectures. You review the Architecture Vision to determine the level of detail, time, and scope of the ADM cycle phases required for each project. You identify and estimate the cost of the main resources. You then prepare an Architecture Roadmap and request the Architecture Board to review the roadmap. You then start the project.

C. You look outside the company to study how other companies organize their data models and application portfolios. You create just enough architecture description for the Application, Data, and Technology Architectures to identify the different options. For each project, this includes identification of candidate architecture and solution building blocks. You then identify solution providers, perform a readiness assessment, and assess the viability and fitness of the solution options. You then write the draft Implementation and Migration plan.

D. You refer to the superior architecture for guidance. You review the projects identified, their dependencies, and synergies, then decide the sequence for starting the projects. You develop high-level architecture descriptions. For each project, you determine how much work is needed, identify reference architectures, and candidate building blocks. You identify the resource needs taking into account cost and value. You document the different options, risks, and ways to control them to enable feasibility analysis and trade-off with the stakeholders.

A. Common Use Applications promotes standardization across divisions for the solutions, aligning with the company's existing practice of standardized medical coding. Information Management is Everybody ' s Business is relevant because clinical staff, administrative personnel, and IT teams all need to collaborate on information management decisions. Data is Accessible is highly relevant to the healthcare industry. This is needed for users to perform their functions and leads to efficiency and effectiveness.

B. Responsive Change Management emphasizes implementing changes in a timely manner to meet user needs and limiting downtime during change. Primacy of Principles makes it clear that the set of principles applies equally to all divisions and clinical departments. This will ensure that the regulatory requirements across the company are met. Maximize Benefit to the Enterprise will ensure that decisions are made to provide maximum benefit to the company.

C. Compliance with the Law is critical for a company operating in one of the most heavily regulated industries. This principle provides the foundation for ensuring the initiative meets all legal requirements for patient data handling. Interoperability ensuring systems can exchange and use information is important for cross-provider data sharing. Control Technical Diversity will be vital for standardizing the Al implementations across multiple divisions that share electronic health records with standardized medical coding.

D. Common Vocabulary and Data Definitions is essential for standardized medical coding and cross- provider data sharing. This ensures the solutions will properly interpret clinical data consistently across divisions. Data Security is critical to protect patient information aligned with the regulations. It ensures data integrity and system availability for critical care. Requirements-Based Change ensures changes respond to business and clinical needs, supporting changes being driven by clinical requirements.

A. You recommend conducting an analysis that separates the different types of stakeholders into groups.
They can be put into categories including corporate functions, end-user organization, project organization, systems, and external. Models should be developed for each stakeholder category to ensure that that all the necessary information and details are considered. A meeting should be held with the stakeholders to verify that their concerns have been addressed. Risk management will be considered during the Implementation Governance phase.

B. You recommend that the key stakeholders be formally identified. This should include those who will be most helpful for the change to be successful. A Communication Plan should be made to address their needs. This plan should include a report that summarizes the key features of the architecture based on stakeholder requirements and addressing concerns. You meet with each key stakeholder to make sure their concerns are being addressed. You make sure that the architecture being developed clearly addresses risk management.

C. You recommend an assessment of the power, influence, and interest of key individuals affected by the project. This includes documenting the positions, concerns, issues, and cultural factors of each interest group. This information will shape how the architecture is presented and explained. The concerns and relevant views can be defined for each group and recorded in the Architecture Vision document. The requirements for addressing risk should be recorded in the Architecture Requirements Specification and checked through regular assessments and feedback.

D. You recommend creating an Organization Map to display the links between different parts of the agency. This will help the EA team to find and involve all areas of the agency impacted by this strategic change. Multiple business models should then be created that can be applied to Al related projects. A meeting will be held with the stakeholders to teach them how to interpret the models and see how their concerns are being addressed. Risk will be managed as part of the Security Architecture development.

A. You will perform a qualitative risk assessment for the data assets exchanged with partners. This will deliver a set of priorities, high to medium to low, based on identified threats, the likelihood of occurrence, and the impact if it did occur. Using the priorities, you would then develop a Business Risk Model which will detail the risk strategy including classifications to determine what mitigation is enough.

B. You will focus on data quality as it is a key factor in risk management. You will identify the datasets that need to be safeguarded. For each dataset, you will assign ownership and responsibility for the quality of data needs. A security classification will be defined and applied to each dataset. The dataset owner will then be able to authorize processes that are trusted for a certain activity on the dataset under certain circumstances.

C. You will create a security domain model so that assets with the same level can be managed under one security policy. Since data is being shared across partners, you will establish a security federation to include them. This would include contractual arrangements, and a definition of the responsibility areas for the data exchanged, as well as security implications. You would undertake a risk assessment determining risks relevant to specific data assets.

D. You will focus on the relationship with the third parties required for the travel assistance systems and define a trust framework. This will describe the relationship with each party. Digital certificates are a key part of the framework and will be used to create trust between parties. You will monitor legal and regulatory changes across all the countries to keep the trust framework in compliance.

A. Control Technical Diversity, Interoperability, Data is an Asset, Data is Shared, Business Continuity

B. Common Vocabulary and Data Definitions, Compliance with the Law, Requirements Based Change, Responsive Change Management, Data Security

C. Maximize Benefit to the Enterprise, Common Use Applications, Data is an Asset, Responsive Change Management, Technology Independence

D. Common Use Applications, Data is an Asset, Data is Accessible, Ease of Use, Business Continuity