The answer is to enable checkpointing with a state backend like RocksDB and configure the S3 sink to use exactly-once delivery semantics. Checkpointing is the core mechanism in Flink for fault tolerance, as it periodically captures the entire state of the streaming application to durable storage; in the event of a failure, Flink restarts from the last completed checkpoint, avoiding reprocessing large amounts of data. RocksDB is the ideal state backend here because it stores large state on disk with memory caching, enabling fast recovery even with high throughput. On the AWS Certified Machine Learning Specialty MLS-C01 exam, this scenario tests your understanding of streaming fault tolerance patterns, often appearing as a trap where candidates mistakenly choose a "reprocessing from the stream's earliest offset" option, which would defeat the purpose of checkpointing. Remember the key pairing: checkpointing for state durability plus exactly-once sinks for output consistency. A useful mnemonic is "Checkpoint and Commit" — Flink checkpoints the state, and the S3 sink commits exactly once.
MLS-C01 Data Engineering Practice Question
This MLS-C01 practice question tests your understanding of data engineering. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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 data engineer is designing a streaming pipeline using Amazon Kinesis Data Analytics for Apache Flink. The pipeline reads from a Kinesis data stream and writes to a S3 bucket. The job must recover quickly from failures without reprocessing large amounts of data. Which TWO configurations should be used? (Choose TWO)
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Enable checkpointing with a state backend like RocksDB.
Option A is correct because enabling checkpointing with a state backend like RocksDB allows Apache Flink to periodically save the state of the streaming application to durable storage. In the event of a failure, Flink can restart from the last completed checkpoint, avoiding the need to reprocess large amounts of data from the beginning of the stream. RocksDB is specifically designed for large state and provides fast recovery by storing state on disk with memory caching, making it ideal for production streaming pipelines.
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 checkpointing with a state backend like RocksDB.
Why this is correct
Checkpointing enables state recovery after failure.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use in-memory state backend for low latency.
Why it's wrong here
In-memory state is lost on failure.
✓
Configure the S3 sink to use exactly-once delivery semantics.
Why this is correct
Exactly-once prevents duplicate writes during recovery.
Related concept
Read the scenario before looking for a memorised answer.
✗
Set the parallelism to the maximum number of shards.
Why it's wrong here
Parallelism affects throughput, not recovery.
✗
Increase the retention period of the Kinesis stream to 365 days.
Why it's wrong here
Retention does not help with recovery.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse parallelism or stream retention settings with fault-tolerance mechanisms, mistakenly believing that increasing parallelism or retention alone can prevent data reprocessing, when in fact only checkpointing with a durable state backend ensures fast recovery.
Detailed technical explanation
How to think about this question
Under the hood, Flink checkpointing works by taking a consistent snapshot of the entire distributed state and storing it in a durable location (e.g., S3, HDFS). RocksDBStateBackend uses a log-structured merge-tree (LSM tree) to manage state on local disk, with asynchronous writes to the configured durable store, enabling incremental checkpoints that reduce overhead. In real-world scenarios, if a Flink job processes millions of events per second, a failure without checkpointing could require hours of reprocessing, whereas checkpointing with RocksDB can recover in seconds to minutes.
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
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
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.
Data Engineering — This question tests Data Engineering — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Enable checkpointing with a state backend like RocksDB. — Option A is correct because enabling checkpointing with a state backend like RocksDB allows Apache Flink to periodically save the state of the streaming application to durable storage. In the event of a failure, Flink can restart from the last completed checkpoint, avoiding the need to reprocess large amounts of data from the beginning of the stream. RocksDB is specifically designed for large state and provides fast recovery by storing state on disk with memory caching, making it ideal for production streaming pipelines.
What should I do if I get this MLS-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 →
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.
This MLS-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 MLS-C01 exam.
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.
Sign in to join the discussion.