nerdexam
Microsoft

PL-600 · Question #210

You are documenting a company's current enterprise architecture. You need to evaluate the architecture of the data to identify its influences. Which three data influences should you ask the company…

The correct answer is B. quality D. location E. history. When evaluating a company's data architecture, quality (B), location (D), and history (E) are recognized data-specific influences that directly shape how data is governed, stored, and managed across the enterprise. Quality reveals data accuracy, consistency, and…

Submitted by salim_om· Apr 18, 2026Architect a solution

Question

You are documenting a company's current enterprise architecture. You need to evaluate the architecture of the data to identify its influences. Which three data influences should you ask the company about? Each correct answer presents a complete solution. (Choose three.) NOTE: Each correct selection is worth one point.

Options

  • Auser access
  • Bquality
  • Cpain points
  • Dlocation
  • Ehistory

How the community answered

(28 responses)
  • A
    7% (2)
  • B
    79% (22)
  • C
    14% (4)

Explanation

When evaluating a company's data architecture, quality (B), location (D), and history (E) are recognized data-specific influences that directly shape how data is governed, stored, and managed across the enterprise.

  • Quality reveals data accuracy, consistency, and fitness-for-purpose issues that drive architectural decisions around cleansing, validation, and master data management.
  • Location captures where data physically resides (on-premises, cloud, regional data centers), which influences latency, sovereignty/compliance requirements, and replication strategies.
  • History exposes how data has evolved over time - including legacy migrations, system changes, and data lineage - which constrains or informs what future architecture is feasible.

Why the distractors are wrong: User access (A) is an application-layer or security concern (identity and access management), not a data influence itself. Pain points (C) are a business stakeholder elicitation technique - they describe problems with the current state, not an architectural data characteristic.

Memory tip: Think of data as a living artifact - it has a past (history), a present condition (quality), and a place (location). Those three dimensions = the three data influences. Access and pain points belong to the people and process layer, not the data layer itself.

Topics

#Enterprise Architecture#Data Architecture#Data Influences#Architecture Evaluation

Community Discussion

No community discussion yet for this question.

Full PL-600 Practice