SOA-C02 · Question #726
A company stores customer data in an Amazon S3 bucket. Users from several AWS accounts need to access the data. The company owns some of the accounts. Partner companies own the other accounts that…
The correct answer is A. Create an AWS Lake Formation data lake. Add the S3 bucket as a data source. Use Lake. Lake Formation lets you register the S3 bucket once, define table/column permissions by role, and share those permissions across accounts via Lake Formation resource shares-so new users just assume the right role. Lake Formation audit logs show exactly which principals accessed…
Question
A company stores customer data in an Amazon S3 bucket. Users from several AWS accounts need to access the data. The company owns some of the accounts. Partner companies own the other accounts that need to access the data. A SysOps administrator needs to implement a solution to give users the ability to query the data. The solution must track which users access each object. Additionally, the solution must minimize ongoing administrative effort as new users are added in the future. Which solution will meet these requirements?
Options
- ACreate an AWS Lake Formation data lake. Add the S3 bucket as a data source. Use Lake
- BCreate an AWS Lake Formation data lake. Add the 3 bucket as a data source. Use Lake
- CEnable S3 bucket access logging. Modify the S3 bucket policy to allow access from Amazon
- DEnable S3 bucket access logging. Modify the S3 bucket policy to allow access from Amazon
How the community answered
(39 responses)- A72% (28)
- B18% (7)
- C8% (3)
- D3% (1)
Explanation
Lake Formation lets you register the S3 bucket once, define table/column permissions by role, and share those permissions across accounts via Lake Formation resource shares-so new users just assume the right role. Lake Formation audit logs show exactly which principals accessed which objects, satisfying the tracking requirement with minimal ongoing admin.
Topics
Community Discussion
No community discussion yet for this question.