AWS Certified Data Analytics Specialty 2021 – Hands-On - Redshift Durability and Scaling

The video tutorial explains Amazon Redshift's data replication and backup processes, including storing data in multiple locations and performing periodic backups to S3. It covers how to restore clusters from backups, handle node failures, and manage availability zone outages. The tutorial also discusses scaling Redshift clusters both vertically and horizontally, ensuring data availability and performance during scaling operations.

How many copies of data does Redshift maintain, and where are they stored?

• Two copies: one in the cluster and one in S3

• Four copies: two in the cluster and two in S3

• One copy: only in the cluster

• Three copies: original, replica in the cluster, and S3 backup

What happens when a drive fails in a Redshift cluster?

• The cluster becomes completely unavailable

• The drive is rebuilt from a replica, with a slight performance decline

• The drive is ignored and not replaced

• The entire cluster is restored from S3

What is the recommended minimum number of nodes for a Redshift cluster in production?

• 4 nodes

• 3 nodes

• 2 nodes

• 1 node

How does Redshift handle scaling operations?

• The existing cluster is immediately replaced with a new one

• The existing cluster remains available for read operations while a new cluster is created

• The cluster is shut down during scaling

• Data is lost during the scaling process

What type of scaling does Redshift support?

• Neither vertical nor horizontal scaling

• Both vertical and horizontal scaling

• Only vertical scaling

• Only horizontal scaling