DAS-C01 · Question #69
A company stores its sales and marketing data that includes personally identifiable information (PII) in Amazon S3. The company allows its analysts to launch their own Amazon EMR cluster and run…
The correct answer is C. Enable the block public access setting for Amazon EMR at the account level before any EMR. Amazon EMR Block Public Access is an account-level setting that automatically blocks any EMR cluster from being created with security group rules that allow inbound traffic from the public internet (0.0.0.0/0 or ::/0). Enabling it once protects all current and future clusters…
Question
A company stores its sales and marketing data that includes personally identifiable information (PII) in Amazon S3. The company allows its analysts to launch their own Amazon EMR cluster and run analytics reports with the data. To meet compliance requirements, the company must ensure the data is not publicly accessible throughout this process. A data engineer has secured Amazon S3 but must ensure the individual EMR clusters created by the analysts are not exposed to the public internet. Which solution should the data engineer to meet this compliance requirement with LEAST amount of effort?
Options
- ACreate an EMR security configuration and ensure the security configuration is associated with the
- BCheck the security group of the EMR clusters regularly to ensure it does not allow inbound traffic
- CEnable the block public access setting for Amazon EMR at the account level before any EMR
- DUse AWS WAF to block public internet access to the EMR clusters across the board.
How the community answered
(18 responses)- A11% (2)
- B6% (1)
- C78% (14)
- D6% (1)
Explanation
Amazon EMR Block Public Access is an account-level setting that automatically blocks any EMR cluster from being created with security group rules that allow inbound traffic from the public internet (0.0.0.0/0 or ::/0). Enabling it once protects all current and future clusters across the account with no per-cluster configuration needed. Option A (EMR security configuration) must be explicitly attached to each cluster, relying on analysts to use it. Option B (regularly checking security groups) is a detective control, not a preventive one. Option D (AWS WAF) protects web applications, not EMR cluster networking.
Topics
Community Discussion
No community discussion yet for this question.