Sharing Redshift Data Products with Lake Formation

DEA-C01 By islever Editorial Last updated

Automate data processing by using AWS services. Apply authorization mechanisms.

Short answer

BD Create a Redshift data share and register it in the Lake Formation catalog to enable centralized governance and access.

Question

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.)
  1. Create views of the tables that need to be shared. Include only the required columns.
  2. Create an Amazon Redshift data share that includes the tables that need to be shared. Correct Answer
  3. Create an Amazon Redshift managed VPC endpoint in the marketing team’s account. Grant the marketing team access to the views.
  4. Share the Amazon Redshift data share to the Lake Formation catalog in the governance account. Correct Answer
  5. Share the Amazon Redshift data share to the Amazon Redshift Serverless workgroup in the marketing team's account.

Key Takeaways

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.

Common mistake: Many learners select A because they focus on column subsetting, missing the requirement for central governance via Lake Formation which necessitates Data Shares.

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

https://docs.aws.amazon.com/lake-formation/latest/dg/data-sharing.html

This link opens the official vendor documentation in a new tab.

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.

More DEA-C01 FAQ →

Community Votes

BD
57%
D
43%

57% of anonymous learners picked answer BD. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 4 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 4

  1. ae35a02 👍 4
    workgroups don't manage permission to tables and views, they manage resource allocation for queries execution.
  2. Eleftheriia 👍 3 Answered D
    I think that D is one of the correct answers as described https://aws.amazon.com/blogs/big-data/centrally-manage-access-and-permissions-for-amazon-redshift-data-sharing-with-aws-lake-formation/
  3. ae35a02 👍 2
    i think not A because they say access and permissions are centrally managed in Lake Formation ... therefore : BD
  4. Parandhaman_Margan 👍 2
    Answer:AD

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Amazon Redshift Compound Sort Key Query Optimization

S-grade

Secure Redshift Spectrum Access with VPC Endpoints

S-grade

Athena Federated Query for Multi-Source Iceberg Pipelines

S-grade

Reclaiming Storage in Amazon Redshift Materialized Views

S-grade

Practice All DEA-C01 Questions

Access 100 questions with complete answers and detailed explanations.

View Full DEA-C01 Practice Test →

← Back to DEA-C01 Study Guide