Exam AWS Certified Data Engineer - Associate DEA-C01 topic 1 question 228 discussion

Exam question from Amazon's AWS Certified Data Engineer - Associate DEA-C01

Question #: 228
Topic #: 1

[All AWS Certified Data Engineer - Associate DEA-C01 Questions]

A company uses an Amazon Redshift cluster as a data warehouse that is shared across two departments. To comply with a security policy, each department must have unique access permissions.

Department A must have access to tables and views for Department A. Department B must have access to tables and views for Department B.

The company often runs SQL queries that use objects from both departments in one query.

Which solution will meet these requirements with the LEAST operational overhead?

A. Group tables and views for each department into dedicated schemas. Manage permissions at the schema level.
B. Group tables and views for each department into dedicated databases. Manage permissions at the database level.
C. Update the names of the tables and views to follow a naming convention that contains the department names. Manage permissions based on the new naming convention.
D. Create an IAM user group for each department. Use identity-based IAM policies to grant table and view permissions based on the IAM user group.

Show Suggested Answer

Suggested Answer: A 🗳️

by rdiaz at July 4, 2025, 4:47 a.m.

Disclaimers:

- ExamTopics website is not related to, affiliated with, endorsed or authorized by Amazon.
- Trademarks, certification & product names are used for reference only and belong to Amazon.

Comments

Submit Cancel

rdiaz

1 month, 2 weeks ago

Selected Answer: A

Schemas in Amazon Redshift are logical groupings of database objects (tables, views, etc.) within the same database. • Using separate schemas for each department (e.g., schema_a, schema_b) allows granular access control via GRANT and REVOKE statements. • Cross-schema queries are supported in Redshift, so joining tables across departments is straightforward with fully qualified names (e.g., schema_a.table1 JOIN schema_b.table2). • This approach keeps everything within the same Redshift database, minimizing operational overhead and maximizing flexibility.

upvoted 1 times

...