SOA-C03 · Question #110
A finance company stores confidential data in an Amazon S3 bucket. The company uses Amazon QuickSight to analyze the data and create dashboard reports. The company requires that all data access and…
The correct answer is A. Create an interface VPC endpoint for QuickSight. Configure the endpoint to connect to. To keep all QuickSight traffic and data access within the VPC boundary, you must use an interface VPC endpoint for QuickSight via AWS PrivateLink. This provides a private connection from your VPC to the QuickSight service without traversing the public internet. Then QuickSight…
Question
A finance company stores confidential data in an Amazon S3 bucket. The company uses Amazon QuickSight to analyze the data and create dashboard reports. The company requires that all data access and connections to QuickSight remain within the company's VPC network boundary. Which solution will meet these requirements?
Options
- ACreate an interface VPC endpoint for QuickSight. Configure the endpoint to connect to
- BSet up a VPC endpoint for QuickSight. Use an Amazon EC2 instance as a proxy to establish a
- CConfigure an Amazon S3 VPC gateway endpoint. Route all data from QuickSight through the
- DConfigure a NAT gateway in the company's VPC. Route all data from QuickSight through the
How the community answered
(52 responses)- A79% (41)
- B12% (6)
- C6% (3)
- D4% (2)
Explanation
To keep all QuickSight traffic and data access within the VPC boundary, you must use an interface VPC endpoint for QuickSight via AWS PrivateLink. This provides a private connection from your VPC to the QuickSight service without traversing the public internet. Then QuickSight can read data from S3 (referenced via a manifest file) while staying within the VPC path, as long as the proper S3 permissions are granted.
Topics
Community Discussion
No community discussion yet for this question.