Multiple city departments share one Amazon S3 data lake, but police, parks, and finance each need different column- and table-level permissions for sensitive datasets. Which AWS capability is best suited to govern that fine-grained lake access?
Select an answer to reveal the explanation.
Short Explanation
A shared lake without a librarian turns into a free-for-all. Lake Formation is that librarian—central, fine-grained rules so police, parks, and finance each see what they’re allowed to see. Public ACLs, wide-open bucket policies, or Macie-only discovery don’t replace governed lake permissions.
Full Explanation
AWS Lake Formation helps govern data lakes with centralized, fine-grained access control over tables and columns for analytics consumers across accounts or departments. Public ACLs and overly permissive bucket policies undermine least privilege. Amazon Macie focuses on discovering and protecting sensitive data rather than serving as the primary fine-grained authorization layer for multi-engine lake access. Lake Formation is the service aligned with governed multi-department lake permissions.