DBS-C01 Monitoring and Troubleshooting Practice Question
Which TWO actions should be taken to troubleshoot high memory usage on an Amazon ElastiCache for Redis node? (Choose two.)
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
✓
Monitor the Evictions CloudWatch metric.
Monitoring the Evictions CloudWatch metric is the only valid action among the options for troubleshooting high memory usage on an Amazon ElastiCache for Redis node. Option B is incorrect because the maxmemory parameter is determined by the node type and cannot be increased; it is fixed. Options C, D, and E are not direct troubleshooting steps for memory pressure. Option C monitors CPU, not memory. Option D (enabling cluster mode) is a scaling action, not a troubleshooting step for an existing node. Option E (Reserved Memory) is a preventive setting but not a primary troubleshooting action.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Monitor the Evictions CloudWatch metric.
Why this is correct
Correct. Monitoring the Evictions metric directly indicates memory pressure because Redis evicts keys when it reaches the maxmemory limit. A high eviction count signals high memory usage.
- ✗
Increase the maxmemory parameter to allow more memory usage.
Why it's wrong here
Incorrect. In Amazon ElastiCache for Redis, the maxmemory parameter is fixed based on the node type and cannot be increased via a parameter change. This action is not feasible.
- ✗
Monitor CPUUtilization CloudWatch metric.
Why it's wrong here
Incorrect. CPUUtilization measures CPU usage, not memory usage. While high memory usage can sometimes impact CPU, it is not a direct indicator of memory pressure.
- ✗
Enable cluster mode to distribute memory across shards.
Why it's wrong here
Incorrect. Enabling cluster mode distributes data across shards, which is a long-term scaling solution, not a troubleshooting step for an existing node's memory usage.
- ✗
Enable Reserved Memory parameter group setting.
Why it's wrong here
Incorrect. Reserved Memory sets aside a portion of memory for Redis overhead, but it does not help troubleshoot existing high memory usage; it is a preventive configuration.
Go deeper
Related to this question
About these practice questions
This DBS-C01 question is part of Courseiva's 1,663-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 DBS-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 DBS-C01 exam.