There is a Redshift table that is storing information for the employees. The Manager of the department needs to be able to see the information for the employees only in their respective department. How can you accomplish this in Redshift without the need for too much maintenance overheads?

Answer options:

A.Create a view in Redshift that can be used by the managers.
B.Create separate tables in Redshift based on the Managers ID.C.Create separate clusters in Redshift based on the Managers ID.D.Create a work management queue

Answer – A
Options B and C are incorrect since this would add more maintenance overhead to the solution
Option D is incorrect since this is used to define multiple query queues and to route queries to the appropriate queues at runtime
You can use views to hide and show only relevant information
The AWS Documentation mentions the following
To create a standard view, you need access to the underlying tables. To query a standard view, you need select privileges for the view itself, but you don`t need select privileges for the underlying tables. To query a late binding view, you need select privileges for the late binding view itself. You should also make sure the owner of the late binding view has select privileges to the referenced objects (tables, views, or user-defined functions).
Options B and C are incorrect since this would add more maintenance overhead to the solution
Option D is incorrect since this is used to define multiple query queues and to route queries to the appropriate queues at runtime
For more information on creating views, please refer to the below URL
https://docs.aws.amazon.com/redshift/latest/dg/r_CREATE_VIEW.html