DAS-C01 · Question #128
An ecommerce company is migrating its business intelligence environment from on premises to the AWS Cloud. The company will use Amazon Redshift in a public subnet and Amazon QuickSight. The tables…
The correct answer is B. Add the QuickSight IP address range into the Amazon Redshift security group. A 'connection timed out' error during QuickSight data source validation indicates a network-level failure - the TCP connection to the Redshift cluster is not reaching the database. QuickSight connects from AWS-managed IP address ranges, and the Redshift security group must…
Question
An ecommerce company is migrating its business intelligence environment from on premises to the AWS Cloud. The company will use Amazon Redshift in a public subnet and Amazon QuickSight. The tables already are loaded into Amazon Redshift and can be accessed by a SQL tool. The company starts QuickSight for the first time. During the creation of the data source, a data analytics specialist enters all the information and tries to validate the connection. An error with the following message occurs: "Creating a connection to your data source timed out." How should the data analytics specialist resolve this error?
Options
- AGrant the SELECT permission on Amazon Redshift tables.
- BAdd the QuickSight IP address range into the Amazon Redshift security group.
- CCreate an IAM role for QuickSight to access Amazon Redshift.
- DUse a QuickSight admin user for creating the dataset.
How the community answered
(21 responses)- A10% (2)
- B86% (18)
- C5% (1)
Explanation
A 'connection timed out' error during QuickSight data source validation indicates a network-level failure - the TCP connection to the Redshift cluster is not reaching the database. QuickSight connects from AWS-managed IP address ranges, and the Redshift security group must include an inbound rule that allows traffic from those IP ranges on the Redshift port (5439 by default). Option A (SELECT permission) is a database-level authorization issue, not a connectivity issue. Option C (IAM role) addresses authorization between AWS services but does not resolve a network timeout - and Redshift in a public subnet with direct JDBC/ODBC connections uses database credentials, not IAM roles, by default. Option D (admin user) has no bearing on connection timeouts.
Topics
Community Discussion
No community discussion yet for this question.