MindPyramid Limited is a multinational information technology and outsourcing company headquartered in Vizag, India and New Jersey, USA. Founded in 2003, the company employs approximately 2000 employees. The company offers consulting services in cloud computing, big data and analytics.
They offer services to major cloud providers including AWS. The team is working with one of the major clients having their infrastructure build on AWS. Currently the client is having lot of performance issues and wants to understand the design best practices from MindPyramid team.Please suggest the best practices in terms of loading data into tables. Select 4 options.

Answer options:

A.Use copy command here to load multiple files from Amazon S3, Amazon EMR, Amazon DynamoDB, or multiple data sources on remote hosts
B.for optimal parallelism, split your load data files so that the files are about equal size, between 1 MB and 1 GB after compression
C.The number of files should be a multiple of the (number of slices+ X) in your cluster. X indicates the number of leader nodes
D.Manage data consistency using a manifest file to load data and address eventual consistency issues
E.In order to reduce the need for VACCUM, load data in the sort key order of the table
F.Load the data in sequential blocks according to sort order to eliminate the need to vacuum.
G.Staging tables benefits inserts and updates but create performance issues when upserts are performed

Answer : A, D, E, F
Option A is correct - copy command to load multiple files is a best practice to load the data from S3, EMR and Others
https://docs.aws.amazon.com/redshift/latest/dg/c_best-practices-use-copy.html
Option B is incorrect -the optimal size of the files should be of equal size between 1 MB and 125 MB
https://docs.aws.amazon.com/redshift/latest/dg/c_best-practices-use-multiple-files.html
Option C is incorrect -the he number of files should be a multiple of the number of slices in your cluster
https://docs.aws.amazon.com/redshift/latest/dg/c_best-practices-use-multiple-files.html
Option D is correct - Manifest files address eventual consistency issues during loads
https://docs.aws.amazon.com/redshift/latest/dg/best-practices-preventing-load-data-errors.html
Option E is correct -Load your data in sort key order to avoid needing to vacuum.
https://docs.aws.amazon.com/redshift/latest/dg/c_best-practices-sort-key-order.html
Option F is correct -load the data in sequential blocks according to sort order to eliminate the need to vacuum.
https://docs.aws.amazon.com/redshift/latest/dg/c_best-practices-load-data-in-sequential-blocks.html
Option G is incorrect -the Use a staging table to perform a merge operations. load your data into a staging table and then join the staging table with your target table for an UPDATE statement and an INSERT statement.
https://docs.aws.amazon.com/redshift/latest/dg/c_best-practices-upsert.html