nerdexam
Amazon

SAA-C03 · Question #179

A company uses Amazon S3 to store customer data that contains personally identifiable information (PII) attributes. The company needs to make the customer information available to company resources th

The correct answer is C. Use AWS Lake Formation to provide the specified IAM roles access to the PII data.. AWS Lake Formationis designed for managing fine-grained access control to data in an efficient Granular Permissions: Lake Formation allows column-level, row-level, and table-level access controls, which can precisely define access to PII data. Integration with AWS Glue Catalog: L

Submitted by daniela_cl· Mar 4, 2026Design Secure Architectures

Question

A company uses Amazon S3 to store customer data that contains personally identifiable information (PII) attributes. The company needs to make the customer information available to company resources through an AWS Glue Catalog. The company needs to have fine-grained access control for the data so that only specific IAM roles can access the PII data. Which solution will meet this requirement?

Options

  • ACreate one IAM policy that grants access to PII. Create a second IAM policy that grants access to
  • BCreate one IAM role that grants access to PII. Create a second IAM role that grants access to
  • CUse AWS Lake Formation to provide the specified IAM roles access to the PII data.
  • DUse AWS Glue to create one view for PII data. Create a second view for non-PII data. Provide the

How the community answered

(24 responses)
  • A
    4% (1)
  • B
    13% (3)
  • C
    79% (19)
  • D
    4% (1)

Explanation

AWS Lake Formationis designed for managing fine-grained access control to data in an efficient Granular Permissions: Lake Formation allows column-level, row-level, and table-level access controls, which can precisely define access to PII data. Integration with AWS Glue Catalog: Lake Formation natively integrates with AWS Glue for seamless data cataloging and access control. Operational Efficiency: Centralized access control policies minimize the need for separate IAM roles or policies. Why Other Options Are Not Ideal: Creating multiple IAM policies introduces complexity and lacks column-level access control.Not Managing multiple IAM roles for granular access is operationally complex.Not efficient. Creating views in Glue adds unnecessary complexity and may not provide the level of granularity that Lake Formation offers.Not the best choice.

Community Discussion

No community discussion yet for this question.

Full SAA-C03 Practice