What Is the Correct Dataplex Lake and Zone Design for Data Mesh?
Your company operates in three domains: airlines, hotels, and ride-hailing services. Each domain has two teams: analytics and data science, which create data assets in BigQuery with the help of a central data platform team. However, as each domain is evolving rapidly, the central data platform team is becoming a bottleneck. This is causing delays in deriving insights from data, and resulting in stale data when pipelines are not kept up to date. You need to design a data mesh architecture by using Dataplex to eliminate the bottleneck. What should you do?
Community Votes
100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The exam tests data mesh domain ownership: each business domain gets its own Dataplex lake, and each team inside the domain gets a zone; the trap is confusing teams with domains.
Need a data mesh architecture in Dataplex? Create one lake per domain and one zone per team; community consensus votes for Option C.
Most common wrong answer is choosing one lake per team (A/B). This mistake treats a team as the data mesh domain boundary, but data mesh principles require the business domain to own the lake, with teams sharing that domain-level lake.
Community Discussion (6 comments)
- each domain should manage their own lake’s data assets
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Option C correctly aligns with data mesh principles: lakes are created for each business domain (airlines, hotels, ride-hailing), and zones are created for each team (analytics, data science). This gives domain teams autonomy to manage their own data assets while the central data platform team only provides shared governance. The community comments overwhelmingly support C, emphasizing that each domain should manage its own lake’s data assets and attach BigQuery datasets to the corresponding zone.Why the Other Options Are Wrong
Options A and B (one lake per team) are incorrect because a team is not the data mesh domain boundary; analytics and data science teams belong to the same domain and should share a domain-level lake. Creating a separate lake for each team would fragment data ownership, increase overhead, and recreate the central bottleneck at a lower level. The identical-looking C and D options show that in the actual exam only the full text of C includes the required steps for attaching datasets and assigning domain ownership.Community Comment Notes
Comment [1] and [4] strongly support C, noting that each domain manages its own lake’s data assets. Comment [2] agrees that Option C creates a lake per domain with team-level zones. Comment [3] votes B, but this is a minority and misses the data mesh principle that business domains, not teams, are the primary ownership unit. Overall, the consensus points to C as the correct answer.Official Reference
Exam Strategy
In data mesh exam scenarios, identify the core business domain first and make it the lake owner; then allocate zones to teams like analytics and data science. Remember that Dataplex zones organize assets within a domain lake, and each domain should govern its own data assets.