ExamGecko
Question list
Search
Search

List of questions

Search

Related questions











Question 282 - DBS-C01 discussion

Report
Export

A company is using Amazon Redshift. A database specialist needs to allow an existing Redshift cluster to access data from other Redshift clusters. Amazon RDS for PostgreSQL databases, and AWS Glue Data Catalog tables.

Which combination of steps will meet these requirements with the MOST operational efficiency? (Choose three.)

A.
Take a snapshot of the required tables from the other Redshift clusters. Restore the snapshot into the existing Redshift cluster.
Answers
A.
Take a snapshot of the required tables from the other Redshift clusters. Restore the snapshot into the existing Redshift cluster.
B.
Create external tables in the existing Redshift database to connect to the AWS Glue Data Catalog tables.
Answers
B.
Create external tables in the existing Redshift database to connect to the AWS Glue Data Catalog tables.
C.
Unload the RDS tables and the tables from the other Redshift clusters into Amazon S3. Run COPY commands to load the tables into the existing Redshift cluster.
Answers
C.
Unload the RDS tables and the tables from the other Redshift clusters into Amazon S3. Run COPY commands to load the tables into the existing Redshift cluster.
D.
Use federated queries to access data in Amazon RDS.
Answers
D.
Use federated queries to access data in Amazon RDS.
E.
Use data sharing to access data from the other Redshift clusters.
Answers
E.
Use data sharing to access data from the other Redshift clusters.
F.
Use AWS Glue jobs to transfer the AWS Glue Data Catalog tables into Amazon S3. Create external tables in the existing Redshift database to access this data.
Answers
F.
Use AWS Glue jobs to transfer the AWS Glue Data Catalog tables into Amazon S3. Create external tables in the existing Redshift database to access this data.
Suggested answer: B, D, E

Explanation:

Explanation from Amazon documents:To allow an existing Redshift cluster to access data from other Redshift clusters, Amazon RDS for PostgreSQL databases, and AWS Glue Data Catalog tables, the database specialist should use the following features123:Create external tables in the existing Redshift database to connect to the AWS Glue Data Catalog tables. This feature allows you to query data stored in Amazon S3 using the AWS Glue Data Catalog as the metadata store. You can create external tables in your Redshift database that reference the data catalog tables and use SQL to query the data in S3. This feature is operationally efficient because it does not require moving or copying the data from S3 to Redshift1.Use federated queries to access data in Amazon RDS. This feature allows you to query and join data from one or more Amazon RDS for PostgreSQL and Amazon Aurora PostgreSQL databases with data already in your Amazon Redshift cluster. You can use SQL to query the RDS databases directly from your Redshift cluster without having to load or unload any data. This feature is operationally efficient because it reduces data movement and storage costs, and simplifies data access and analysis2.Use data sharing to access data from the other Redshift clusters. This feature allows you to securely share live data across different Redshift clusters without the complexity and delays associated with data copies and data movement. You can share data within or across AWS accounts using a consumer-producer model. The producer cluster grants privileges on one or more schemas, called datashares, to the consumer clusters. The consumer clusters can then query the shared data in the producer cluster as if it were local tables. This feature is operationally efficient because it enables real-time and transactionally consistent data access, and eliminates data duplication and stale data issues3.Therefore, option B, D, and E are the correct steps to meet the requirements with the most operational efficiency. Option A is not efficient because it involves taking and restoring snapshots, which can be time-consuming and costly. Option C is not efficient because it involves unloading and loading data between S3 and Redshift, which can also incur additional time and cost. Option F is not necessary because it involves transferring the AWS Glue Data Catalog tables into S3, which can be avoided by using external tables to connect to the data catalog tables directly.

asked 16/09/2024
David Murinda
42 questions
User
Your answer:
0 comments
Sorted by

Leave a comment first