Courseiva
Management and OperationseasyMultiple ChoiceObjective-mapped

DBS-C01 Management and Operations Practice Question

Network Topology
namespace AWS/RDSmetric-name WriteLatencydimensions Name=DBInstanceIdentifierstart-time 2023-01-01T00:00:00Zend-time 2023-01-02T00:00:00Zperiod 300statistics Averageoutput jsonRefer to the exhibit."Datapoints": ["Timestamp": "2023-01-01T10:00:00Z","Average": 0.002},"Timestamp": "2023-01-01T10:05:00Z","Average": 0.025"Timestamp": "2023-01-01T10:10:00Z","Average": 0.001...

Refer to the exhibit. A database administrator runs the AWS CLI command to retrieve CloudWatch metrics for an Amazon RDS DB instance. The output shows a spike in WriteLatency at 10:05 UTC. What is the most likely cause of this spike?

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

The DB instance's gp2 volume has exhausted its burst credits.

A sudden spike in write latency often indicates that the storage volume has exhausted its burst credits and is now using baseline performance, which may be slower. Option B is incorrect because taking a snapshot causes I/O suspension, not necessarily a latency spike. Option C is incorrect because a large number of concurrent connections typically causes increased CPU and memory usage, not a latency spike. Option D is incorrect because a Multi-AZ failover would cause a brief downtime, not a latency spike.

Answer analysis

Option-by-option breakdown

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

  • The DB instance's gp2 volume has exhausted its burst credits.

    Why this is correct

    A sudden spike in write latency often indicates that the storage volume has exhausted its burst credits and is now using baseline performance, which may be slower.

  • The DB instance is in the process of taking a snapshot.

    Why it's wrong here

    A snapshot causes I/O suspension, not necessarily a write latency spike.

  • There is a large number of concurrent connections to the DB instance.

    Why it's wrong here

    A large number of connections typically causes increased CPU and memory usage, not necessarily a latency spike.

  • The DB instance experienced a Multi-AZ failover.

    Why it's wrong here

    A Multi-AZ failover would cause a brief downtime, not a latency spike.

Quick reference

AWS S3 Storage Class Comparison

Storage ClassMin DurationRetrievalUse Case
S3 StandardNoneImmediateFrequently accessed data
S3 Standard-IA30 daysImmediateInfrequent access, rapid retrieval
S3 One Zone-IA30 daysImmediateNon-critical infrequent data
S3 Intelligent-TieringNoneImmediate–hoursUnknown or changing access patterns
S3 Glacier Instant90 daysMillisecondsArchive with instant retrieval
S3 Glacier Flexible90 daysMinutes–hoursArchive, flexible retrieval
S3 Glacier Deep Archive180 daysHoursLong-term compliance archive

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 →

How Courseiva writes practice questions · Editorial policy

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.