MSP Bank, Limited is a leading varied Japanese monetary institution that provides a full range of financial products and services to both institutional and individual customers.
It is headquartered in Tokyo.
MSP Bank is hosting their existing infrastructure on AWS.
MSP bank has many organizations internally and they are planning to launch a self-data discovery platform running out of AWS on QuickSight. A ‘transaction_details' dataset of 50 GB size has been created and will be used by different departments like Sales, Marketing, Business segments like Cards, Accounts, C Level, etc.
from the dataset, different organizations access different subsets of data which may or may overlay each other subsets.
The team needs a mechanism to enable row-level security, there restricting access to data elements in the dataset.
How can this be achieved?Select 4 options.
Click on the arrows to vote for the correct answer
A. B. C. D. E. F.Answer: A,B,C,F.
Restrict access to a data set by configuring row-level security on it and can be done before or after the dataset is shared.
Only the people you shared with can see any of the data.
By adding row-level security, you can further control their access.
https://docs.aws.amazon.com/quicksight/latest/user/restrict-access-to-a-data-set-using-row-level-security.html#create-row-level-securityTo enable row-level security and restrict access to data elements in the ‘transaction_details' dataset, MSP Bank can use the following options:
A. Creating Data Set Rules for Row-Level Security: This involves defining data set rules to control access to data at the row level. These rules are created using the QuickSight UI or by using the AWS Command Line Interface (CLI). Data set rules can be defined based on conditions such as user or group membership, geographic location, or any other attribute that can be used to identify users.
B. Apply row-level permissions by using a file or query that contains data set rules: This option involves creating a file or query that contains data set rules and then applying these rules to the data set. This can be done using the QuickSight UI or the AWS CLI.
C. Choose your permissions data set, and assign permission policies to users and groups: This involves selecting a permissions data set and assigning permission policies to users and groups. Permission policies are created based on the data set rules that have been defined.
D. You can assign row-level security only before sharing the transaction_details dataset: This option suggests that row-level security can only be assigned to the data set before it is shared with users or groups.
E. You can assign row-level security only after sharing the transaction_details dataset: This option suggests that row-level security can only be assigned to the data set after it has been shared with users or groups.
F. To apply the data set rules, you add the rules as a permissions data set to your data set: This option suggests that data set rules can be added as a permissions data set to the data set. This will enable the rules to be applied to the data set and will control access to the data at the row level.
To summarize, MSP Bank can enable row-level security and restrict access to data elements in the ‘transaction_details' dataset by defining data set rules, applying row-level permissions using a file or query, selecting a permissions data set, and assigning permission policies to users and groups. Row-level security can be assigned before or after sharing the data set. Data set rules can be added as a permissions data set to the data set to control access to data at the row level.