First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.
Continue in the practice tool above to load more questions, 50 at a time.
Question 1EA Concepts and Framework Basics
Which statement best describes the purpose of an enterprise architecture framework?
- It defines the accounting standards an organization must follow for financial reporting.
- It specifies the programming languages that must be used to build enterprise software.
- It lists the hardware vendors approved for procurement in a data center.
- It provides a structured set of concepts, models, and methods for describing and planning an organization's architecture. Correct answer.
Explanation
An EA framework supplies a common vocabulary, viewpoints, and method for describing current and target states and the roadmap between them. It is a management and modeling discipline, not a technology mandate or procurement list.
Question 2EA Concepts and Framework Basics
In enterprise architecture, what does the term 'baseline architecture' refer to?
- The long-term target state the organization intends to reach.
- The set of architecture principles approved by the board.
- The documented description of the architecture as it currently exists. Correct answer.
- The budget allocated to architecture governance for the year.
Explanation
The baseline (as-is) architecture describes what exists today, while the target (to-be) architecture describes the desired future state. Comparing the two produces the gap analysis that drives the roadmap.
Question 3EA Concepts and Framework Basics
An architect groups related business processes, applications, and data into a coherent functional area to reduce coupling. Which core EA concept does this grouping illustrate?
- Depreciation
- Segmentation Correct answer.
- Encryption
- Procurement
Explanation
Segmentation divides the enterprise into manageable, loosely coupled domains or blocks so each can be architected and governed coherently. It is a foundational structuring technique in EA.
Question 4EA Concepts and Framework Basics
What is the primary role of architecture principles within an EA practice?
- To replace the need for any architecture governance process.
- To document the individual performance reviews of architects.
- To record the detailed technical configuration of each server.
- To serve as enduring statements that guide architecture decisions and constrain designs. Correct answer.
Explanation
Architecture principles are durable, agreed statements of intent that steer design choices and provide a basis for evaluating compliance. They guide decisions rather than replace governance or record technical detail.
Question 5EA Concepts and Framework Basics
Which of the following is a stakeholder of an enterprise architecture?
- Any individual or group with an interest in or affected by the architecture. Correct answer.
- Only the software developers who implement systems.
- Only external regulators.
- Only the chief architect who authors the architecture.
Explanation
A stakeholder is any person or group with an interest in the architecture, including business owners, IT staff, auditors, customers, and regulators. Architecture must address the concerns of many such parties.
Question 6EA Concepts and Framework Basics
In EA terminology, what is an architecture 'viewpoint'?
- A single diagram drawn by an architect.
- A physical location where architecture reviews take place.
- A list of approved software licenses.
- A specification of the perspective and conventions used to construct a view for a stakeholder. Correct answer.
Explanation
A viewpoint defines the perspective, concerns, and modeling conventions from which a view is built; the view is the resulting representation. This distinction lets different stakeholders see the architecture through relevant lenses.
Question 7EA Concepts and Framework Basics
Which activity most directly distinguishes architecture governance from architecture modeling?
- Establishing decision rights, compliance checks, and escalation paths for architecture choices. Correct answer.
- Drawing diagrams of the target state.
- Interviewing business users about their requirements.
- Cataloging the inventory of application servers.
Explanation
Governance is about decision rights, accountability, compliance, and escalation, ensuring architecture decisions are made and honored. Modeling and requirements gathering produce architecture content but do not by themselves govern decisions.
Question 8EA Concepts and Framework Basics
A team defines a target architecture with a roadmap of transition states. What is the main purpose of modeling transition architectures?
- To show how the enterprise will move incrementally from baseline to target. Correct answer.
- To freeze all change until the roadmap is complete.
- To replace the need for a baseline architecture.
- To avoid ever having to define a final target state.
Explanation
Transition architectures describe intermediate states that deliver value incrementally while managing risk and dependencies on the path to the target. They complement, rather than replace, the target and baseline.
Question 9EA Concepts and Framework Basics
Which pairing correctly matches an architecture domain with the type of concern it primarily addresses?
- Technology architecture - organizational reporting lines.
- Business architecture - server patch schedules.
- Data architecture - meaning, structure, and lifecycle of enterprise data assets. Correct answer.
- Application architecture - employee compensation bands.
Explanation
Data architecture concerns the definition, structure, quality, and lifecycle of data assets. Each architecture domain addresses a distinct layer of concern within the overall enterprise architecture.
Question 10EA Concepts and Framework Basics
An organization wants to assess how well its current systems support a business capability. Which EA concept most directly supports this analysis?
- Capability mapping with associated application and data dependencies. Correct answer.
- A vendor discount schedule.
- A staff holiday calendar.
- A network cable inventory.
Explanation
Capability maps link business capabilities to supporting applications, data, and processes, enabling gap and impact analysis. This linkage is a core use of business and application architecture together.
Question 11EA Concepts and Framework Basics
What distinguishes an architecture 'pattern' from an architecture 'reference model'?
- A pattern is a reusable solution to a recurring problem, while a reference model is a standardized, reusable structure or taxonomy for a domain. Correct answer.
- A pattern is always vendor-specific, while a reference model is always proprietary.
- A pattern applies only to data, while a reference model applies only to networks.
- A pattern is a legal contract, while a reference model is a financial statement.
Explanation
Patterns capture proven solutions to recurring design problems, whereas reference models provide standardized structures and taxonomies that can be reused and tailored. Both are reusable assets but serve different purposes.
Question 12EA Concepts and Framework Basics
Which of the following best describes the relationship between enterprise architecture and solution architecture?
- Solution architecture is only concerned with business processes and never with technology.
- Enterprise architecture provides the strategic context and standards within which solution architectures are designed. Correct answer.
- Solution architecture sets enterprise-wide strategy, while enterprise architecture implements individual projects.
- They are identical concepts with different names.
Explanation
Enterprise architecture defines the target state, principles, and standards, and solution architecture applies them to a specific initiative. The relationship is one of strategic context guiding project-level design.
Question 13EA Concepts and Framework Basics
What is the main benefit of maintaining an architecture repository?
- It replaces the need for stakeholder communication.
- It automatically generates project budgets.
- It guarantees that no architecture change will ever fail.
- It provides a governed, reusable store of architecture models, standards, and decisions. Correct answer.
Explanation
A repository centralizes architecture artifacts and decisions so they can be reused, governed, and referenced consistently. It supports, but does not replace, communication and decision-making.
Question 14EA Concepts and Framework Basics
An architect documents the current application portfolio, identifies redundant systems, and proposes consolidation. Which EA discipline does this primarily represent?
- Human resource succession planning.
- Application portfolio management within application architecture. Correct answer.
- Facilities space planning.
- Network cable management.
Explanation
Application portfolio management assesses the application estate for redundancy, cost, and fit, and drives rationalization decisions. It is a core application architecture activity.
Question 15EA Concepts and Framework Basics
Which statement correctly describes the concept of 'architecture maturity'?
- It counts the number of diagrams produced in a year.
- It records the number of architects employed.
- It assesses how systematically and effectively an organization performs architecture practices over time. Correct answer.
- It measures the physical age of servers in the data center.
Explanation
Architecture maturity models assess the capability and consistency of architecture practices, not raw output counts or asset age. Higher maturity reflects more systematic, embedded, and effective practice.
Question 16EA Concepts and Framework Basics
Which of the following is the best example of an architecture 'concern'?
- The number of chairs in a meeting room.
- A stakeholder's interest in system availability and disaster recovery. Correct answer.
- The name of the architecture team lead.
- The color scheme used in presentation slides.
Explanation
A concern is an interest of a stakeholder in the architecture, such as availability, security, or cost. Viewpoints are chosen to address such concerns.
Question 17EA Concepts and Framework Basics
In an EA framework, what is the role of a 'metamodel'?
- It is a financial model for calculating ROI.
- It is a physical model of the data center building.
- It defines the types of entities and the relationships permitted in architecture models. Correct answer.
- It is the final implementation of the production system.
Explanation
A metamodel specifies the entity types and relationship rules that architecture models must follow, providing consistency across the repository. It governs how models are constructed rather than being a system or financial artifact.
Question 18EA Concepts and Framework Basics
An organization decides to adopt an EA framework. Which outcome indicates the framework is being applied effectively?
- Every team creates its own unique notation and vocabulary.
- Architecture documents are produced once and never revisited.
- Architecture decisions are made consistently using shared models and agreed principles. Correct answer.
- Governance reviews are skipped to save time.
Explanation
Effective framework application yields consistency, shared vocabulary, and principle-based decision-making across teams. Fragmented notation, stale documents, and bypassed governance indicate weak application.
Question 19EA Concepts and Framework Basics
Which statement best captures the difference between 'as-is' and 'to-be' analysis in EA?
- As-is analysis describes the future state; to-be analysis describes the current state.
- Both describe only the desired future state.
- As-is analysis describes current state; to-be analysis describes the desired future state. Correct answer.
- Both describe only the current state.
Explanation
As-is (baseline) analysis documents what currently exists, and to-be (target) analysis defines the intended future state. The gap between them informs the transformation roadmap.
Question 20EA Concepts and Framework Basics
Why do EA frameworks emphasize multiple, consistent viewpoints rather than a single all-purpose diagram?
- Because a single diagram is technically impossible to draw.
- Because regulators forbid unified diagrams.
- Because different stakeholders have different concerns that require tailored representations. Correct answer.
- Because architects prefer drawing many pictures.
Explanation
Stakeholders such as executives, developers, and auditors have distinct concerns, so architecture is presented through multiple coherent viewpoints. This improves communication and decision relevance without sacrificing consistency.
Question 21EA Concepts and Framework Basics
Which of the following best describes 'architecture debt' or 'technical debt' at the enterprise level?
- The accumulated cost and risk of short-term design compromises that will require later remediation. Correct answer.
- The number of architects required to staff a project.
- The interest rate on a corporate loan.
- The money owed to hardware leasing companies.
Explanation
Architecture or technical debt captures the future cost and risk created by expedient design choices that defer proper solutions. It is a management concept for prioritizing remediation, not a financial liability to a lender.
Question 22EA Concepts and Framework Basics
What is the primary purpose of a gap analysis in enterprise architecture?
- To list employees who are absent from work.
- To compare vendor price lists.
- To calculate the tax gap owed by the organization.
- To identify the differences between the baseline and target architectures that must be addressed. Correct answer.
Explanation
Gap analysis compares baseline and target states to reveal missing capabilities, systems, or data that the roadmap must deliver. It directly informs transition planning.
Question 23EA Concepts and Framework Basics
Which of the following is a characteristic of a well-formed architecture principle?
- It is stated vaguely so it can mean anything to anyone.
- It is specific, justifiable, and measurable so compliance can be assessed. Correct answer.
- It is kept secret from stakeholders.
- It changes every week based on team preference.
Explanation
Good principles are specific, rational, and testable, enabling consistent decisions and compliance evaluation. Vague, volatile, or hidden statements cannot guide or be governed effectively.
Question 24EA Concepts and Framework Basics
Which concept describes the alignment of IT investments and systems with business strategy and goals?
- Network segmentation
- Data replication
- Software licensing
- Business-IT alignment Correct answer.
Explanation
Business-IT alignment is the degree to which technology strategy, investments, and systems support business objectives. It is a central outcome that enterprise architecture aims to achieve.
Question 25EA Concepts and Framework Basics
An architecture review board evaluates a proposed project against architecture standards before approval. Which governance mechanism does this represent?
- Financial auditing of the project budget.
- Compliance assessment within architecture governance. Correct answer.
- Recruitment of new architects.
- Marketing campaign planning.
Explanation
Compliance assessment checks proposed work against agreed standards and principles as part of architecture governance. It ensures decisions align with the target architecture and approved standards.
Question 26EA Concepts and Framework Basics
Which statement best defines enterprise architecture?
- A discipline that aligns business strategy with the processes, information, applications, and technology needed to execute it Correct answer.
- A method for writing and enforcing coding standards across development teams
- A project scheduling technique used to sequence software releases
- A procurement process for selecting hardware vendors
Explanation
Enterprise architecture is a holistic discipline that connects business strategy to the operating model, information, applications, and infrastructure. It provides a structured description of the enterprise to guide change. Coding standards, procurement, and scheduling are narrower operational activities.
Question 27EA Concepts and Framework Basics
In EA terminology, what does an architecture 'artifact' refer to?
- A temporary funding mechanism for architecture projects
- A contractual obligation between the enterprise and a supplier
- A concrete work product, such as a diagram, catalog, or document, that describes the architecture Correct answer.
- A role responsible for approving architecture changes
Explanation
An artifact is a tangible work product produced during architecture work, such as a model, diagram, matrix, or catalog entry. Artifacts are the visible outputs of the architecture description. Funding mechanisms, roles, and contracts are organizational concepts, not artifacts.
Question 28EA Concepts and Framework Basics
Which of the following is the primary purpose of an architecture framework?
- To guarantee regulatory compliance for every IT system
- To replace project management with architecture documentation
- To provide a structured set of concepts, methods, and vocabulary for describing and developing architectures Correct answer.
- To prescribe a single mandatory technology stack for the enterprise
Explanation
A framework supplies a common structure, vocabulary, and method so that architectures are described consistently and comparably. It is guidance, not a technology mandate. It complements rather than replaces project management or compliance programs.
Question 29EA Concepts and Framework Basics
Which statement best distinguishes an architecture 'stakeholder' from an architecture 'concern'?
- A stakeholder is a technical system component, while a concern is a business process
- A stakeholder is a document describing the architecture, while a concern is a diagram within it
- A stakeholder is a governance board, while a concern is a funding decision
- A stakeholder is a person or group with an interest in the architecture, while a concern is an interest or issue that matters to that stakeholder Correct answer.
Explanation
Stakeholders are the parties affected by or interested in the architecture, and concerns are the specific interests, needs, or issues they hold. Viewpoints are then chosen to address those concerns. Documents, components, and funding are different categories entirely.
Question 30EA Concepts and Framework Basics
Which of the following best describes an architecture 'building block'?
- A reusable component of the architecture that can be assembled with others to deliver capability Correct answer.
- A budget line item for architecture tooling
- A physical data center facility
- A person who approves architecture exceptions
Explanation
Building blocks are reusable, composable elements of the architecture, defined at various levels of abstraction. They are the modular units from which architecture descriptions and solutions are assembled. Facilities, roles, and budgets are not building blocks.
Question 31EA Concepts and Framework Basics
Which statement best describes the role of an architecture 'view'?
- It presents a representation of the architecture from the perspective of a chosen set of concerns Correct answer.
- It records the approval status of architecture change requests
- It specifies the vendor contract terms for cloud services
- It defines the enterprise's hiring plan for architects
Explanation
A view is a representation of the whole architecture that addresses a specific set of concerns, typically selected via a viewpoint. Views make the architecture understandable to particular stakeholders. Approval records, staffing, and contracts are not views.
Question 32EA Concepts and Framework Basics
Which of the following best characterizes the 'architecture description'?
- A budget forecast for architecture initiatives
- A list of unresolved defects in production systems
- A contract defining service levels with a vendor
- A set of work products that document an architecture for its stakeholders Correct answer.
Explanation
The architecture description is the collection of artifacts that express an architecture so stakeholders can understand and use it. It is the documented output, not a financial or operational record. Defect lists and service contracts are separate management artifacts.
Question 33EA Concepts and Framework Basics
An architect is selecting a viewpoint to communicate with executives who care about cost, risk, and business outcomes. Which criterion should drive the choice?
- Whether the viewpoint addresses the concerns of that stakeholder group Correct answer.
- Whether the viewpoint was created by the most senior architect
- Whether the viewpoint uses the newest diagramming notation
- Whether the viewpoint contains the largest number of elements
Explanation
Viewpoints are selected to frame the concerns of the intended stakeholders. For executives, the relevant concerns are cost, risk, and outcomes, so the viewpoint must address those. Notation novelty, authorship, and diagram size are not selection criteria.
Question 34EA Concepts and Framework Basics
A large retailer wants one consistent way to describe business processes, data, applications, and technology across all divisions. Which EA concept most directly provides that consistency?
- A vendor discount agreement
- A service desk ticketing workflow
- A common metamodel defining the entity types and relationships used in architecture descriptions Correct answer.
- A single project charter for the largest IT program
Explanation
A metamodel defines the entity types, attributes, and relationships used consistently across architecture descriptions. It is what makes descriptions from different divisions comparable and integrable. Charters, ticketing, and vendor agreements do not standardize architecture content.
Question 35EA Concepts and Framework Basics
An architecture team must show how a proposed change moves the enterprise from its current state to a future state through intermediate states. Which EA concept organizes this?
- A list of architecture principles
- A single point-in-time application inventory
- A stakeholder communication plan
- A roadmap of transition architectures Correct answer.
Explanation
Transition architectures describe intermediate states, and a roadmap sequences them from the baseline to the target. Together they express how change is staged over time. Inventories, principles, and communication plans do not sequence states.
Question 36EA Concepts and Framework Basics
A program proposes a design that conflicts with an approved architecture principle. What is the most appropriate EA response?
- Reject the design without discussion because principles are absolute
- Evaluate the conflict and, if justified, route a documented exception through architecture governance Correct answer.
- Delete the principle so the conflict disappears
- Silently approve the design to avoid delaying the program
Explanation
Principles guide decisions but governance provides a mechanism for justified exceptions. The proper path is to assess the conflict and escalate a documented exception for a decision. Silent approval, blanket rejection, and removing the principle all undermine governance.
Question 37EA Concepts and Framework Basics
An architect must decide whether a capability gap is best closed by a new system, a process change, or a partnership. Which EA analysis most directly supports that decision?
- A network latency benchmark
- A gap analysis comparing baseline and target states with options for closing each gap Correct answer.
- A staff training attendance log
- A code coverage report
Explanation
Gap analysis identifies the differences between baseline and target and frames options for closing them, including non-technology alternatives. That directly informs the choice among system, process, or partnership. Latency benchmarks, code coverage, and attendance logs are narrow operational measures.
Question 38EA Concepts and Framework Basics
A company wants architecture descriptions from different teams to be comparable and reusable in a shared repository. Which practice most directly supports this?
- Allowing each team to invent its own notation and entity names
- Adopting a common metamodel and content framework for architecture descriptions Correct answer.
- Standardizing the color scheme of all presentations
- Requiring every team to use the same project management tool
Explanation
Shared metamodels and content frameworks define common entity types, relationships, and structure so descriptions are comparable and reusable. Free-form notation defeats comparability. Project tooling and presentation colors do not affect architecture content structure.
Question 39EA Concepts and Framework Basics
Which scenario best illustrates the application of an architecture principle rather than a mere preference?
- A decision to buy rather than build is justified by a documented principle favoring reuse of commercial capabilities Correct answer.
- A manager selects a vendor because of a personal relationship
- A team chooses a database because a developer prefers its syntax
- A project adopts a tool because a competitor uses it
Explanation
A principle is an enduring, agreed guide that is cited to justify a decision consistently across the enterprise. Invoking a documented reuse principle to justify buy-versus-build is a principle-driven decision. Personal preference, relationships, and imitation are not principle-based.
Question 40EA Concepts and Framework Basics
An architect maps which business services depend on which applications, and which applications depend on which infrastructure. Which EA concept is being used?
- A cost allocation model for chargeback
- A service-level agreement catalog
- A relationship model linking architecture entities across domains Correct answer.
- A risk register for project delivery
Explanation
Modeling dependencies between business services, applications, and infrastructure uses relationships defined in the metamodel to link entities across domains. This supports impact analysis and traceability. Chargeback, risk registers, and SLAs are management artifacts, not dependency models.
Question 41EA Concepts and Framework Basics
Which statement best explains why architecture descriptions are organized into domains such as business, data, application, and technology?
- Each domain is independent and never needs to reference the others
- Domains are chosen randomly and have no analytical purpose
- Each domain groups related concerns so that specialists can address them while the whole remains integrated Correct answer.
- Domains exist only to assign blame when projects fail
Explanation
Domain partitioning groups related concerns for focused analysis while the metamodel keeps the parts integrated. This division of labor improves clarity without losing coherence. Domains are neither isolated nor arbitrary, and they are not accountability devices.
Question 42EA Concepts and Framework Basics
A review finds that several projects each built a similar capability independently, raising long-term maintenance cost. Which EA concept best frames this finding?
- A complete architecture description
- Duplication and technical debt at the enterprise level Correct answer.
- A validated transition architecture
- A well-formed architecture principle
Explanation
Independently built, redundant capabilities create duplication and enterprise-level technical debt that raises maintenance cost. The finding is a portfolio-level architectural issue. Principles, transition architectures, and descriptions are tools, not the problem being described.
Question 43EA Concepts and Framework Basics
Why does an EA practice separate the 'architecture' from its 'architecture description'?
- They are identical, and the terms are interchangeable
- The architecture is a document, while the description is a physical system
- The architecture is the underlying structure of the enterprise, while the description is the documented representation of it Correct answer.
- The architecture applies only to software, while the description applies only to hardware
Explanation
The architecture is the fundamental organization of a system or enterprise, and the architecture description is the set of artifacts that represent it. Separating them clarifies that documentation is a representation, not the reality. They are not interchangeable, nor split by document versus system or software versus hardware.
Question 44EA Concepts and Framework Basics
Two stakeholders disagree about an architecture because each is using a different model of the same system. Which EA practice most directly resolves the disagreement?
- Establishing consistent viewpoints and a shared metamodel so both parties reason from compatible representations Correct answer.
- Removing the architecture description to avoid conflict
- Increasing the number of diagrams until one satisfies everyone
- Escalating to procurement to select a new tool
Explanation
Disagreement often stems from incompatible representations. Consistent viewpoints tied to a shared metamodel let stakeholders compare and reconcile their models. Adding diagrams, deleting documentation, or buying tools does not resolve semantic mismatch.
Question 45EA Concepts and Framework Basics
An enterprise has a detailed target architecture but no defined way to decide which initiatives advance it. Which EA element is most clearly missing?
- A more detailed application inventory
- A larger set of architecture principles
- Architecture governance that ties initiative decisions to the target architecture Correct answer.
- A new diagramming notation
Explanation
A target architecture only guides change when governance processes connect initiative approval and funding decisions to it. Without that linkage the target remains aspirational. More principles, inventory detail, or notation do not establish decision rights.
Question 46EA Concepts and Framework Basics
An architect argues that a framework should be tailored rather than adopted wholesale. Which reasoning best supports this?
- Wholesale adoption always produces lower cost than tailoring
- Frameworks are generic guidance, and tailoring aligns them with the enterprise's context, scope, and maturity Correct answer.
- Frameworks are legally binding and must always be applied in full
- Tailoring guarantees that no architecture risk will remain
Explanation
Frameworks provide generic structures that must be adapted to an organization's context, scope, and maturity to be useful. Tailoring is expected practice, not a deviation. Frameworks are not legally binding, do not eliminate risk, and are not always cheaper when adopted wholesale.
Question 47EA Concepts and Framework Basics
A capability is currently supported by a legacy system and an informal manual workaround. Which EA analysis best exposes the risk that the workaround masks?
- Recording the workaround owner's job title
- Modeling the baseline state to show how the capability is actually delivered, including informal elements Correct answer.
- Listing the legacy system's license costs
- Documenting only the target state and omitting the baseline
Explanation
A baseline model captures how capabilities are actually delivered, including informal workarounds, making hidden dependencies and risks visible. Omitting the baseline hides the problem. License costs and job titles do not expose the operational risk.
Question 48EA Concepts and Framework Basics
Which statement best captures the relationship between a framework, a method, and a technique in EA?
- A framework is a tool, a method is a diagram, and a technique is a budget
- A framework organizes concepts, a method structures the work, and a technique is a specific way of performing a step Correct answer.
- They are synonyms and can be used interchangeably
- A technique organizes concepts, a method is a tool, and a framework is a step
Explanation
Frameworks provide conceptual structure, methods organize the sequence of work, and techniques are the specific procedures used within steps. Each plays a distinct role in the discipline. The other options confuse or conflate these roles.
Question 49EA Concepts and Framework Basics
An organization wants to measure whether its EA practice is improving over time. Which approach best reflects the concept of architecture maturity?
- Assessing the practice against defined capability levels and tracking progress across them Correct answer.
- Counting the total number of diagrams produced each quarter
- Measuring the number of architects employed
- Comparing the size of the architecture repository to competitors
Explanation
Architecture maturity is assessed against defined capability levels that describe increasing sophistication of practice, and progress is tracked across them. Volume metrics such as diagram counts, headcount, or repository size do not indicate maturity.
Question 50EA Concepts and Framework Basics
A new regulation requires the enterprise to prove that personal data flows only to approved locations. Which EA artifact most directly supports this proof?
- A marketing campaign calendar
- A list of employee performance ratings
- A project Gantt chart
- A data-flow model linked to application and infrastructure entities in the architecture repository Correct answer.
Explanation
A data-flow model tied to applications and infrastructure shows where data originates, moves, and resides, enabling evidence of approved locations. Gantt charts, campaign calendars, and performance ratings contain no data-location information.