MSP Bank: Self-Data Discovery Platform on AWS with QuickSight

Deleting a Dataset and Its Impact on Analysis Generation

Question

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 segments internally and they are planning to launch a self-data discovery platform running out of AWS on QuickSight. Using QuickSight, multiple datasets are created and multiple analyses are generated respectively.

The Team identified a dataset that they want to delete, on which some analysis is already generated.

They submitted the deletion.

What happens next? Select 3 options.

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D. E.

Answer : A, D, E, F.

Option A is correct -Use a VPC endpoint to create a managed connection between your Amazon Redshift cluster in a VPC and Amazon Simple Storage Service (Amazon S3)

When you do, COPY and UNLOAD traffic between your cluster and your data on Amazon S3 stays in your Amazon VPC and both S3 and Redshift should be in the same region.

https://docs.aws.amazon.com/redshift/latest/mgmt/enhanced-vpc-working-with-endpoints.html

Option B is incorrect - Use a VPC endpoint to create a managed connection between your Amazon Redshift cluster in a VPC and Amazon Simple Storage Service (Amazon S3)

When you do, COPY and UNLOAD traffic between your cluster and your data on Amazon S3 stays in your Amazon VPC and both S3 and Redshift should be in the same region.

https://docs.aws.amazon.com/redshift/latest/mgmt/enhanced-vpc-working-with-endpoints.html

Option C is incorrect -Enable Enhanced VPC Routing when you create a cluster.

https://docs.aws.amazon.com/redshift/latest/mgmt/enhanced-vpc-working-with-endpoints.html

Option D is correct -Attach an endpoint policy to your endpoint to more closely manage access to your data.

https://docs.aws.amazon.com/redshift/latest/mgmt/enhanced-vpc-working-with-endpoints.html

Option E is correct -Enable Enhanced VPC Routing when you create a cluster.

https://docs.aws.amazon.com/redshift/latest/mgmt/enhanced-vpc-working-with-endpoints.html

Option F is correct -Enable Domain Name Service (DNS) resolution in your VPC.

https://docs.aws.amazon.com/redshift/latest/mgmt/enhanced-vpc-enabling-cluster.html

Option G is incorrect - Enable Domain Name Service (DNS) resolution in your VPC.

https://docs.aws.amazon.com/redshift/latest/mgmt/enhanced-vpc-enabling-cluster.html

When the team at MSP Bank deletes a dataset in QuickSight, the following three things can happen:

A. You receive a warning if you have any analyses that use the dataset you have chosen for deletion. Before the dataset is deleted, QuickSight checks to see if any analyses are dependent on the dataset. If so, it will display a warning message notifying the user that the dataset is being used in one or more analyses and should not be deleted without considering the impact on those analyses.

C. Dataset deletion does not delete the dependent analyses. Deleting a dataset in QuickSight does not delete the dependent analyses that were created using that dataset. The analyses will still be available and visible in the user's account. However, if the deleted dataset was used in any visuals, those visuals will not be available for further analysis or viewing, and any associated queries will fail.

D. Next time you open any of those analyses, you are prompted to select a new data set for any visuals that were based on the deleted data set. If an analysis depends on the deleted dataset, QuickSight will prompt the user to select a new dataset to replace the deleted one. The user can then choose a new dataset from the available data sources and re-run the analysis. The user can also choose to delete the dependent analysis if it is no longer needed.

Therefore, in summary, when a dataset is deleted in QuickSight, the dependent analyses are not deleted, but any visuals that were based on the deleted dataset will not be available, and the user will be prompted to select a new dataset to replace the deleted one if the analysis is dependent on the deleted dataset.