DAS-C01 · Question #64
A retail company's data analytics team recently created multiple product sales analysis dashboards for the average selling price per product using Amazon QuickSight. The dashboards were created from…
The correct answer is D. Create dataset rules with row-level security. Amazon QuickSight's Row-Level Security (RLS) feature lets you create dataset rules that filter rows based on the viewer's identity. You define a permission dataset mapping QuickSight usernames or groups to specific field values (e.g., product IDs), and QuickSight automatically…
Question
A retail company's data analytics team recently created multiple product sales analysis dashboards for the average selling price per product using Amazon QuickSight. The dashboards were created from .csv files uploaded to Amazon S3. The team is now planning to share the dashboards with the respective external product owners by creating individual users in Amazon QuickSight. For compliance and governance reasons, restricting access is a key requirement. The product owners should view only their respective product analysis in the dashboard reports. Which approach should the data analytics team take to allow product owners to view only their products in the dashboard?
Options
- ASeparate the data by product and use S3 bucket policies for authorization.
- BSeparate the data by product and use IAM policies for authorization.
- CCreate a manifest file with row-level security.
- DCreate dataset rules with row-level security.
How the community answered
(41 responses)- A10% (4)
- B5% (2)
- C2% (1)
- D83% (34)
Explanation
Amazon QuickSight's Row-Level Security (RLS) feature lets you create dataset rules that filter rows based on the viewer's identity. You define a permission dataset mapping QuickSight usernames or groups to specific field values (e.g., product IDs), and QuickSight automatically filters query results at the row level for each user. Option C is incorrect because manifest files are an S3 concept for specifying data sources, not a QuickSight security mechanism. Options A and B (S3/IAM policies) control access to the underlying files, not individual rows within a shared dataset already loaded into QuickSight.
Topics
Community Discussion
No community discussion yet for this question.