Courseiva
Data Operations and SupporthardMultiple ChoiceObjective-mapped

DEA-C01 Data Operations and Support Practice Question

A data pipeline uses Amazon Kinesis Data Firehose to deliver data to an Amazon S3 bucket. The delivery stream is configured with a buffer size of 5 MB and a buffer interval of 60 seconds. The team notices that the S3 objects are much smaller than 5 MB. What is the most likely explanation?

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 incoming data volume is low, so the 60-second buffer interval triggers delivery before the 5 MB buffer is filled.

If the incoming data rate is low, the buffer interval (60 seconds) expires before the buffer size (5 MB) is reached, causing small objects. Option B is incorrect because S3 event notifications do not split objects; they are triggered by events but do not affect object size. Option C is incorrect because S3 lifecycle policies transition objects to Glacier, which does not affect object size during delivery. Option D is incorrect because GZIP compression reduces the object size after batching, but the buffer interval can still trigger delivery before the buffer is full, so it is not the most likely explanation.

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 incoming data volume is low, so the 60-second buffer interval triggers delivery before the 5 MB buffer is filled.

    Why this is correct

    Because if the incoming data rate is low, the buffer interval (60 seconds) expires before the buffer size (5 MB) is reached, causing small S3 objects.

  • The S3 bucket has event notifications that split the objects.

    Why it's wrong here

    S3 event notifications do not split objects; they trigger actions when objects are created. This is not related to object size.

  • The S3 bucket has a lifecycle policy that transitions objects to Glacier.

    Why it's wrong here

    An S3 lifecycle policy can transition objects to Glacier or delete them, but it does not cause objects to be small on delivery. This is unrelated to the observed objects being smaller than expected.

  • The delivery stream is using GZIP compression, which reduces the object size.

    Why it's wrong here

    GZIP compression reduces the size of data in transit and at rest, but it does not cause the S3 objects themselves to be smaller than the buffer size; the buffer size refers to the uncompressed data volume.

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 DEA-C01 question is part of Courseiva's 1,711-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 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.