Transparency goals in distributed databases “Location transparency” in a distributed DBMS allows which stakeholders to behave as if all data were in one place?

Introduction / Context:
Distributed DBMSs strive for several transparencies: location, fragmentation, and replication. Location transparency means users and applications do not need to know the physical site of data. Instead, the system resolves where a fragment lives and routes operations automatically, improving usability and portability.

Given Data / Assumptions:

• The organization has data spread across multiple sites.
• Stakeholders include users, developers, and managers using tools and applications.
• The DBMS provides a single logical schema or global view.

Concept / Approach:

If location transparency holds, SQL queries, BI tools, and end-user applications operate against a unified catalog. The optimizer and data shipping layer select sites, plan sub-queries, and combine results without exposing site details to stakeholders. Thus, the property benefits all roles—not only DBAs—by hiding distribution complexity.

Step-by-Step Solution:

Verification / Alternative check:

Canonical definitions list location transparency as a core goal alongside replication and fragmentation transparency; examples include global schemas and location-independent naming.

Why Other Options Are Wrong:

• Restricting transparency to one role defeats the point of system-wide abstraction.

Common Pitfalls:

• Embedding site qualifiers in code, which erodes transparency and portability.

Final Answer:

All of the above.