Documenting Current Enterprise Architecture Components
A company plans to adopt Microsoft Power Platform. You need to document the current enterprise architecture of the company. Which two components should you incorporate? Each correct answer presents a complete solution. (Choose two.) NOTE: Each correct selection is worth one point.
Community Votes
100% of anonymous learners picked answer AE. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
This question tests the distinction between current technical assets and future solution needs, with the common trap being selecting functional requirements instead of existing infrastructure.
When adopting Microsoft Power Platform, architects must map the existing IT landscape to ensure seamless integration. This page establishes that documenting data locations and applications used are the critical components for capturing the current enterprise architecture.
Learners often incorrectly select 'functional requirements' (D) or 'process diagrams' (C), failing to recognize that these describe the desired solution or business logic rather than the existing technical environment.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Option A (data locations) and Option E (applications used) represent the foundational layers of the current Application and Data architectures. To successfully adopt Power Platform, an architect must identify where data resides to address compliance, latency, and integration needs, and catalog existing applications to determine replacement strategies or integration points.Why the Other Options Are Wrong
Option D (functional requirements) describes the goals of the future solution, not the current state of the enterprise. Option C (process diagrams) details business workflows which, while useful for design, are distinct from the technical architecture. Option B (organizational structure) is relevant for security but is secondary to the physical and logical mapping of systems and data.Community Comment Notes
Learners emphasize that process diagrams are often too detailed for a high-level architecture overview. As Tootru2bReal noted, the focus should remain on the 'architectural diagram' elements like data locations and applications, rather than low-level process details.Official Reference
Exam Strategy
Distinguish between the 'As-Is' (current state) and 'To-Be' (future state). When asked to document the current architecture, always prioritize options describing existing tangible assets like apps and data over requirements or new processes.