Question 937 of 1,730
Monitoring and TroubleshootingmediumMultiple SelectObjective-mapped

DBS-C01 Monitoring and Troubleshooting Practice Question

This DBS-C01 practice question tests your understanding of monitoring and troubleshooting. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

A database engineer is troubleshooting high CPU usage on an Amazon RDS for PostgreSQL instance. Amazon CloudWatch shows CPU Utilization consistently above 90% during business hours. Which combination of actions should the engineer take to identify the root cause? (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

Review the slow query log to identify long-running queries.

Option B is correct because reviewing the slow query log directly identifies long-running queries that can cause sustained high CPU usage on RDS for PostgreSQL. Option D is correct because Performance Insights provides a visual dashboard of database load and top SQL queries, making it easy to pinpoint which queries are consuming the most CPU resources.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Enable Enhanced Monitoring and review OS process list.

    Why it's wrong here

    Enhanced Monitoring shows OS-level metrics like memory and disk I/O, but not query-level CPU usage.

  • Review the slow query log to identify long-running queries.

    Why this is correct

    Slow query logs can reveal queries that consume significant CPU resources.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Scale up the DB instance to a larger instance class.

    Why it's wrong here

    Scaling up addresses symptoms but does not identify the root cause; it may also increase costs unnecessarily.

  • Enable Performance Insights and review the top SQL queries.

    Why this is correct

    Performance Insights provides query-level performance data to pinpoint high-CPU queries.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Install pg_stat_statements extension and query it.

    Why it's wrong here

    pg_stat_statements requires prior installation and is not available by default; Performance Insights is easier to enable and provides similar information.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often choose Option E (pg_stat_statements) thinking it is the only way to get query-level details, but Performance Insights (Option D) provides the same data with less effort and is the recommended AWS-native approach for this scenario.

Trap categories for this question

  • Similar concept trap

    pg_stat_statements requires prior installation and is not available by default; Performance Insights is easier to enable and provides similar information.

  • Command / output trap

    Enhanced Monitoring shows OS-level metrics like memory and disk I/O, but not query-level CPU usage.

Detailed technical explanation

How to think about this question

Performance Insights uses a built-in PostgreSQL extension (pg_stat_statements) under the hood to collect query metrics, but it presents them in a managed, easy-to-analyze dashboard with a database load chart (Average Active Sessions). The slow query log captures queries exceeding a configurable threshold (e.g., log_min_duration_statement), which is critical for identifying queries that run for seconds or minutes, often correlating with CPU spikes. In real-world scenarios, a single missing index or a suboptimal join can cause a query to consume 100% of a vCPU, and these tools help pinpoint that query without guesswork.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

An e-commerce site experiences heavy traffic on Black Friday and near-zero traffic during off-peak weeks. Rather than provisioning permanent large VMs, the team uses auto-scaling groups that add capacity automatically under load and reduce it overnight. Questions like this test whether you understand elasticity, availability zones, and cloud compute scaling patterns.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related DBS-C01 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free DBS-C01 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this DBS-C01 question test?

Monitoring and Troubleshooting — This question tests Monitoring and Troubleshooting — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Review the slow query log to identify long-running queries. — Option B is correct because reviewing the slow query log directly identifies long-running queries that can cause sustained high CPU usage on RDS for PostgreSQL. Option D is correct because Performance Insights provides a visual dashboard of database load and top SQL queries, making it easy to pinpoint which queries are consuming the most CPU resources.

What should I do if I get this DBS-C01 question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Keep practising

More DBS-C01 practice questions

Last reviewed: Jun 11, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

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.