Sharing Redshift Data Products with Lake Formation
A company implements a data mesh that has a central governance account. The company needs to catalog all data in the governance account. The governance account uses AWS Lake Formation to centrally share data and grant access permissions. The company has created a new data product that includes a group of Amazon Redshift Serverless tables. A data engineer needs to share the data product with a marketing team. The marketing team must have access to only a subset of columns. The data engineer needs to share the same data product with a compliance team. The compliance team must have access to a different subset of columns than the marketing team needs access to. Which combination of steps should the data engineer take to meet these requirements? (Choose two.)
Community Votes
57% of anonymous learners picked answer BD. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests the integration of Redshift Data Shares with Lake Formation; the trap is confusing resource allocation (workgroups) or local views with centralized cataloging and permission management.
This page explains how to share Amazon Redshift data products across accounts using AWS Lake Formation for centralized governance and column-level security.
Many learners select A because they focus on column subsetting, missing the requirement for central governance via Lake Formation which necessitates Data Shares.
Community Discussion (4 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
To meet the requirements of centralized governance and sharing a data product, the engineer must use Amazon Redshift Data Shares. Option B is correct because creating a data share allows the inclusion of tables (or views) to be shared. Option D is correct because registering this data share in the Lake Formation catalog enables centralized access control and permission granting, which satisfies the governance account's role.Why the Other Options Are Wrong
Option A creates local views but does not inherently solve the cross-account sharing or central governance aspect without further configuration not implied as the primary step. Option C involves a VPC endpoint, which handles network connectivity, not data permissions or sharing logic. Option E attempts to share directly to a workgroup, but workgroups manage compute resources, not data access policies or catalog entries.Community Comment Notes
Community consensus strongly supports BD. One user noted that 'workgroups don't manage permission to tables and views', clarifying why E is incorrect. Another user referenced an AWS blog post confirming that Lake Formation centrally manages access for Redshift Data Sharing, validating D.Official Reference
Exam Strategy
When 'central governance' and 'Lake Formation' are mentioned together with Redshift, always look for 'Data Share' registered in the catalog. Avoid options focusing on local views or VPC endpoints unless network isolation is the explicit barrier.
Frequently Asked Questions
Why can't I just create views in each account?
Views don't automatically handle cross-account sharing or central governance via Lake Formation without additional steps like Data Shares.
What is the role of the Redshift workgroup here?
Workgroups manage query execution resources, not data access permissions or catalog registration.
Related Analysis
Practice All DEA-C01 Questions
Access 100 questions with complete answers and detailed explanations.
View Full DEA-C01 Practice Test →