DEA-C01 Data Store Management Practice Question
Exhibit
Refer to the exhibit.
```
[ec2-user@ip-10-0-0-1 ~]$ aws redshift describe-clusters --cluster-identifier mycluster
{
"Clusters": [
{
"ClusterIdentifier": "mycluster",
"NodeType": "dc2.large",
"NumberOfNodes": 2,
"ClusterStatus": "available",
"DBName": "dev",
"MasterUsername": "admin",
"AutomatedSnapshotRetentionPeriod": 7,
"ManualSnapshotRetentionPeriod": 30,
"ClusterVersion": "1.0"
}
]
}
```Refer to the exhibit. A data engineer notices that the Redshift cluster 'mycluster' does not have automated backups beyond 7 days. However, the compliance team requires a minimum of 35 days of backup retention. What should the engineer do?
⚠ Common exam trap
Watch out — candidates often confuse backup retention with node type capabilities or audit logging, assuming that hardware or logging features inherently extend backup duration, when in fact the retention period is a simple configuration parameter.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Modify the cluster's automated snapshot retention period to 35 days.
Amazon Redshift allows you to modify the automated snapshot retention period for a cluster up to 35 days. The engineer can use the AWS Management Console, CLI, or API to change the `automated_snapshot_retention_period` parameter from the current 7 days to 35 days, meeting the compliance requirement without additional manual intervention.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Change the node type to ra3.xlplus to enable automatic backups for 35 days.
Why it's wrong here
Node type governs compute and storage characteristics, not the automated snapshot retention period, which is a separate cluster setting. It is tempting because RA3 nodes decouple storage, but changing node type leaves the retention window at its current value.
- ✗
Enable audit logging to capture changes for recovery.
Why it's wrong here
Audit logging records connection and query activity for compliance auditing; it captures no data state and cannot restore a cluster. It is tempting because logging is often bundled with compliance controls, yet backup retention requires snapshot configuration, not log capture.
- ✗
Take manual snapshots every day and retain them for 35 days.
Why it's wrong here
Manual snapshots can reach 35 days but require custom scheduling and are not managed by Redshift's retention setting, so they do not satisfy the automated retention requirement cleanly. They are tempting because snapshots do provide backups, but the cluster's automated retention window is the parameter needing change.
- ✓
Modify the cluster's automated snapshot retention period to 35 days.
Why this is correct
Redshift's automated snapshot retention is a cluster-level setting adjustable from 1 to 35 days. Modifying it to 35 days satisfies the compliance requirement directly, without manual snapshots or a new cluster, since the current 7-day default falls short.
Go deeper
Related to this question
About these practice questions
This DEA-C01 question is part of Courseiva's 1,321-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This DEA-C01 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DEA-C01 exam.