The answer is to enable log compression and increase the batch size in the CloudWatch Logs agent configuration. During peak traffic, a batch size of only 1 MB fills quickly, causing the agent to drop new log entries before they can be transmitted; increasing it to 5 MB allows the agent to buffer more data per API call, reducing the frequency of requests and preventing overflow. Enabling compression shrinks the payload size, so more log events fit within each batch, further lowering the risk of missing entries. On the AWS Certified SysOps Administrator Associate SOA-C02 exam, this scenario tests your understanding of the CloudWatch Logs agent’s `batch_size` and `compress_logs` parameters—common traps include focusing only on the batch timeout or assuming the agent auto-scales. A useful memory tip: think “Bigger Batch, Compress to Catch” to remember that both increasing the batch size and enabling compression work together to prevent log loss during high-volume periods.
SOA-C02 Monitoring, Logging, and Remediation Practice Question
This SOA-C02 practice question tests your understanding of monitoring, logging, and remediation. 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 company uses CloudWatch Logs to collect application logs from EC2 instances. The logs are critical for troubleshooting. The operations team notices that some log entries are missing during peak hours. The CloudWatch Logs agent is configured with a batch size of 1 MB and a batch timeout of 10 seconds. Which TWO actions should the administrator take to reduce the chance of missing log events?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Increase the batch size to 5 MB.
Option C is correct because increasing the batch size from 1 MB to 5 MB allows the CloudWatch Logs agent to buffer more log data before sending a request. During peak hours, log volume spikes can cause the agent to drop events if the batch fills up faster than it can be transmitted. A larger batch size reduces the frequency of API calls and helps ensure that all log entries are successfully delivered.
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.
✗
Use PutLogEvents directly from the application.
Why it's wrong here
This bypasses the agent's buffering and retry logic, likely making the problem worse.
✗
Reduce the retry count for failed requests.
Why it's wrong here
Reducing retries increases data loss if transient failures occur.
✓
Increase the batch size to 5 MB.
Why this is correct
Larger batches reduce the number of API calls, lowering the chance of hitting rate limits.
Related concept
Read the scenario before looking for a memorised answer.
✗
Increase the batch timeout to 30 seconds.
Why it's wrong here
Longer timeouts increase the risk of buffer overflow and data loss if logs are generated rapidly.
✓
Enable log compression in the agent configuration.
Why this is correct
Compression reduces the size of data sent per call, helping avoid throttling.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often think increasing the batch timeout (Option D) will help, but in reality, a longer timeout increases the risk of buffer overflow during peak traffic, whereas increasing batch size and enabling compression directly address throughput and payload limits.
Detailed technical explanation
How to think about this question
The CloudWatch Logs agent uses a producer-consumer model where log events are placed into a buffer and flushed based on either batch size or batch timeout, whichever occurs first. The default batch size limit is 1 MB (up to 1,048,576 bytes) and the maximum batch size is 5 MB. Enabling log compression (Option E) reduces the payload size over the wire, allowing more log data to fit within the batch size limit and reducing the likelihood of exceeding the 5 MB PutLogEvents API limit, which would cause request rejection.
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 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. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. 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.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Monitoring, Logging, and Remediation — This question tests Monitoring, Logging, and Remediation — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Increase the batch size to 5 MB. — Option C is correct because increasing the batch size from 1 MB to 5 MB allows the CloudWatch Logs agent to buffer more log data before sending a request. During peak hours, log volume spikes can cause the agent to drop events if the batch fills up faster than it can be transmitted. A larger batch size reduces the frequency of API calls and helps ensure that all log entries are successfully delivered.
What should I do if I get this SOA-C02 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 SOA-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 SOA-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.