DEA-C01 · Question #218
A company has as JSON file that contains personally identifiable information (PII) data and non- PII data. The company needs to make the data available for querying and analysis. The non-PII data…
The correct answer is C. Store the JSON file in an Amazon S3 bucket. Catalog the file schema in AWS Lake Formation. AWS Lake Formation lets you register your JSON file as a table in the data catalog and apply fine-grained permissions (down to columns or rows) without moving or transforming the underlying data. You can grant all employees access to the non-PII columns while restricting the…
Question
A company has as JSON file that contains personally identifiable information (PII) data and non- PII data. The company needs to make the data available for querying and analysis. The non-PII data must be available to everyone in the company. The PII data must be available only to a limited group of employees. Which solution will meet these requirements with the LEAST operational overhead?
Options
- AStore the JSON file in an Amazon S3 bucket. Configure AWS Glue to split the file into one file that
- BStore the JSON file in an Amazon S3 bucket. Use Amazon Macie to identify PII data and to grant
- CStore the JSON file in an Amazon S3 bucket. Catalog the file schema in AWS Lake Formation.
- DCreate two Amazon RDS PostgreSQL databases. Load the PII data and the non-PII data into the
How the community answered
(29 responses)- A14% (4)
- B7% (2)
- C76% (22)
- D3% (1)
Explanation
AWS Lake Formation lets you register your JSON file as a table in the data catalog and apply fine-grained permissions (down to columns or rows) without moving or transforming the underlying data. You can grant all employees access to the non-PII columns while restricting the PII columns to a small group, achieving your security requirements with minimal operational
Topics
Community Discussion
No community discussion yet for this question.