A company has been using DynamoDB tables for 6 months and it contains millions of rows of data. They now need to port the data onto a Redshift table for conducting analysis on historical data. Which of the following needs to be kept in mind when porting data from DynamoDB to Redshift. Choose 2 answers from the options given below

Answer options:

A.Ensure to enable DynamoDB streams
B.Ensure that empty attribute values in DynamoDB are properly treated
C.Ensure the data type matches between engines
D.Ensure that global tables are enabled in DynamoDB

Answer – B and C
The AWS Documentation mentions the following
Before you can load data from a DynamoDB table, you must first create an Amazon Redshift table to serve as the destination for the data. Keep in mind that you are copying data from a NoSQL environment into a SQL environment, and that there are certain rules in one environment that do not apply in the other. Here are some of the differences to consider:
DynamoDB table names can contain up to 255 characters, including `.` (dot) and `-` (dash) characters, and are case-sensitive. Amazon Redshift table names are limited to 127 characters, cannot contain dots or dashes and are not case-sensitive. In addition, table names cannot conflict with any Amazon Redshift reserved words.
DynamoDB does not support the SQL concept of NULL. You need to specify how Amazon Redshift interprets empty or blank attribute values in DynamoDB, treating them either as NULLs or as empty fields.
DynamoDB data types do not correspond directly with those of Amazon Redshift. You need to ensure that each column in the Amazon Redshift table is of the correct data type and size to accommodate the data from DynamoDB.Since this is clearly mentioned in the AWS documentation , the other options are invalid
For more information on Redshift for DynamoDB, please refer to the below URL
https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/RedshiftforDynamoDB.html