Allianz Financial Services (AFS) is a banking group offering end-to-end banking and financial solutions in South East Asia through its consumer banking, business banking, Islamic banking, investment finance and stock broking businesses as well as unit trust and asset administration, having served the financial community over the past five decades.
AFS uses Redshift on AWS to fulfill the data warehousing needs and uses S3 as the staging area to host files. AFS uses other services like DynamoDB, Aurora, and Amazon RDS on remote hosts to fulfill other needs. The tem needs to design Time Series tables. Please advise the best practices to load the time series tables. select 3 options.

Answer options:

A.Organize data as a sequence of time-series tables for a fixed retention period and create a UNION ALL view to hide the fact that the data is stored in different tables
B.In the sequence, each table should be identical but contain data for different time ranges
C.In the sequence, each table should be identical but contain data for different specific column ranges, time based column is not required
D.One single table with extending time ranges
E.Use DROP TABLE instead of running a large-scale DELETE and a subsequent VACUUM process to reclaim space
F.Use DELETE and a subsequent VACUUM instead of running a DROP TABLE to reclaim space

Answer : A, B, E
Option A is correct - If your data has a fixed retention period, we strongly recommend that you organize your data as a sequence of time-series tables. In this sequence, each table should be identical but contain data for different time ranges. create a UNION ALL view to hide the fact that the data is stored in different tables 
https://docs.aws.amazon.com/redshift/latest/dg/c_best-practices-time-series-tables.html
Option B is correct - If your data has a fixed retention period, we strongly recommend that you organize your data as a sequence of time-series tables. In this sequence, each table should be identical but contain data for different time ranges. create a UNION ALL view to hide the fact that the data is stored in different tables 
https://docs.aws.amazon.com/redshift/latest/dg/c_best-practices-time-series-tables.html
Option C is incorrect -If your data has a fixed retention period, we strongly recommend that you organize your data as a sequence of time-series tables. In this sequence, each table should be identical but contain data for different time ranges. create a UNION ALL view to hide the fact that the data is stored in different tables 
https://docs.aws.amazon.com/redshift/latest/dg/c_best-practices-time-series-tables.html
Option D is incorrect - If your data has a fixed retention period, we strongly recommend that you organize your data as a sequence of time-series tables. In this sequence, each table should be identical but contain data for different time ranges. create a UNION ALL view to hide the fact that the data is stored in different tables 
https://docs.aws.amazon.com/redshift/latest/dg/c_best-practices-time-series-tables.html
Option E is correct -Create a UNION ALL view to hide the fact that the data is stored in different tables. When you delete old data, simply refine your UNION ALL view to remove the dropped tables. Similarly, as you load new time periods into new tables, add the new tables to the view. 
https://docs.aws.amazon.com/redshift/latest/dg/c_best-practices-time-series-tables.html
Option F is incorrect - Create a UNION ALL view to hide the fact that the data is stored in different tables. When you delete old data, simply refine your UNION ALL view to remove the dropped tables. Similarly, as you load new time periods into new tables, add the new tables to the view. 
https://docs.aws.amazon.com/redshift/latest/dg/c_best-practices-time-series-tables.html