Prepare and test your skills

Prepare and test your skills

Free sample question, answered and explained below. The Professional Data Engineer practice bank has 1,353 more like it. Try 10 free: instant score, no account.
An enterprise is implementing a federated data governance model on Google Cloud to support decentralized domain teams. A strategic business domain requires specialized data infrastructure components that are not currently available on the central self-service data platform's roadmap.
The domain team wants to build and operate its own custom platform components without delaying its data product deliverables, while the organization's governance board requires consistent security, metadata standards, and policy enforcement across all domains.
Which operating and accountability framework should the organization implement?
In a data mesh and federated governance architecture, the central self-service data platform team provides standardized infrastructure components, but domain teams retain the autonomy to build custom solutions when central offerings do not meet specialized domain requirements. Decentralized management is balanced by enterprise guardrails and collaborative engineering.
This approach strikes the proper balance between central standardization and domain autonomy. Rather than enforcing rigid centralization or allowing ungoverned fragmentation, it establishes a clear shared responsibility model that preserves organizational compliance while enabling rapid domain execution.
This model gives complete independence to the domain team, allowing it to bypass centralized architectural reviews, common metadata standards, and enterprise compliance frameworks.
The domain operated as a completely separate legal subsidiary with no shared data consumers, shared platforms, or common regulatory compliance obligations.
Promoting domain autonomy in a data mesh is not equivalent to creating an ungoverned technology landscape. Autonomy must always exist within bounded organizational guardrails.
This approach shifts the operational burden of domain data stewardship, metadata management, and pipeline maintenance entirely onto a central team of data governance engineers.
The organization had a non-federated, highly manual legacy data governance framework where a central team executed all compliance reviews manually.
Data governance engineers should focus on developing tools that auto-generate annotations and implement automated monitoring, leaving domain-specific stewardship to the domain teams.
This approach enforces strict, centralized control where all data infrastructure must be designed, provisioned, and managed exclusively by the central self-service data platform team before domain teams can proceed.
The organization were in the earliest nascent phase of a centralized data warehouse build where domain autonomy must be completely restricted to establish baseline platform capabilities.
While centralization simplifies initial policy enforcement, scaling a federated data architecture requires moving away from central gatekeeping toward self-service platform enablement and automated guardrails.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated