A business intelligence developer is trying to make use of Amazon Quicksight to create different types of visualizations. One of the data sets consists of a date column which is not being recognized in QuickSight. Which of the following can be done to ensure the data comes up properly in Quicksight with the least amount of effort?

Answer options:

A.Change the date values in the data set to reflect the supported data types in Quicksight
B.Change the format of the date column in the data set
C.Create a new data set with the formatted date data type
D.Use a Calculated field for the date column

Answer – B
All of the other options are invalid because they would all require additional effort
The AWS Documentation mentions the following
Amazon QuickSight natively supports a limited number of date formats. However, you can’t always control the format of the data provided to you. When your data contains a date in an unsupported format, you can tell Amazon QuickSight how to interpret it.
You can do this by editing the data set, and changing the format of the column from text or numeric to date. A screen appears after you make this change, so you can enter the format. For example, if you are using a relational data source, you can specify MM-dd-yyyy for a text field containing `09-19-2017`, so it is interpreted as 2017-09-19T00:00:00.000Z. If you are using a nonrelational data source, you can do the same thing starting with a numeric field or a text field.
All of the other options are invalid because they would all require additional effort
For more information on using unsupported dates, please visit the url
https://docs.aws.amazon.com/quicksight/latest/user/using-unsupported-dates.html