The correct answer is to use Amazon Kinesis Data Streams with Lambda and a dead-letter queue. Kinesis Data Streams guarantees ordered processing within each shard, which is essential for maintaining the sequence of messages from each IoT device stream, while Lambda natively processes records from a shard in order. For the SAP-C02 exam, this scenario tests your understanding that SQS FIFO queues, though ordered, cannot be directly triggered by Lambda in a way that preserves per-device ordering across multiple shards, making Kinesis the only service that inherently ties ordering to a partition key. A common trap is choosing SQS FIFO because it offers ordering, but you must remember that Lambda triggers on SQS pull batches, not per-shard streams, breaking device-level sequence. Memory tip: think "Kinesis keeps the key order" — the partition key (device ID) ensures all messages from that device land in the same shard and are processed sequentially.
SAP-C02 Design for New Solutions Practice Question
This SAP-C02 practice question tests your understanding of design for new solutions. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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 company is designing a serverless data processing pipeline using AWS Lambda to process messages from an Amazon SQS queue. The messages are generated by thousands of IoT devices. The architect needs to ensure that messages are processed in order within each device's stream and that failures are handled without data loss. Which combination of services should the architect use?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use Amazon Kinesis Data Streams with Lambda function and a dead-letter queue
Amazon Kinesis Data Streams preserves the order of records within a shard, and Lambda can process records in order. For error handling, a DLQ captures failed records. Option A (SQS FIFO) provides ordering but does not support Lambda triggers with ordered processing per shard. Option B (Lambda with DLQ on SQS) does not guarantee ordering across multiple shards. Option D (Kinesis with SQS) adds unnecessary complexity.
Key principle: NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Use Amazon Kinesis Data Firehose with Lambda function and an SQS queue for error handling
Why it's wrong here
Firehose is for delivery to destinations, not for real-time ordered processing.
✗
Use Amazon SQS standard queues with Lambda function and a dead-letter queue
Why it's wrong here
Standard queues do not guarantee order.
✗
Use Amazon SQS FIFO queues with Lambda function
Why it's wrong here
SQS FIFO provides ordering but Lambda processes messages in batches, potentially reordering if multiple message groups are used.
✓
Use Amazon Kinesis Data Streams with Lambda function and a dead-letter queue
Why this is correct
Kinesis preserves order within shards; Lambda processes records sequentially; DLQ handles failures.
Related concept
Static NAT maps one inside address to one outside address.
Common exam traps
Common exam trap: NAT rules depend on direction and matching traffic
NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.
Detailed technical explanation
How to think about this question
NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.
KKey Concepts to Remember
Static NAT maps one inside address to one outside address.
PAT allows many inside hosts to share one public address using ports.
Inside local and inside global describe the private and translated addresses.
NAT ACLs identify traffic for translation, not always security filtering.
TExam Day Tips
→Identify inside and outside interfaces first.
→Check whether the scenario needs static NAT, dynamic NAT or PAT.
→Do not confuse NAT matching ACLs with normal packet-filtering intent.
Key takeaway
NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related SAP-C02 NAT questions on configuration and troubleshooting.
Design for New Solutions — This question tests Design for New Solutions — Static NAT maps one inside address to one outside address..
What is the correct answer to this question?
The correct answer is: Use Amazon Kinesis Data Streams with Lambda function and a dead-letter queue — Amazon Kinesis Data Streams preserves the order of records within a shard, and Lambda can process records in order. For error handling, a DLQ captures failed records. Option A (SQS FIFO) provides ordering but does not support Lambda triggers with ordered processing per shard. Option B (Lambda with DLQ on SQS) does not guarantee ordering across multiple shards. Option D (Kinesis with SQS) adds unnecessary complexity.
What should I do if I get this SAP-C02 question wrong?
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related SAP-C02 NAT questions on configuration and troubleshooting.
What is the key concept behind this question?
Static NAT maps one inside address to one outside address.
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 SAP-C02 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 SAP-C02 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.