The answer is the `--previous` flag, used as in `kubectl logs api-pod --previous`. This flag is correct because when a container in a Pod crashes and restarts, Kubernetes preserves the logs from the terminated instance; without the `--previous` flag, `kubectl logs` only shows output from the currently running container, so the `--previous` flag is the only way to access the historical log data from the failed container for debugging the root cause of the crash. On the Google Associate Cloud Engineer exam, this question tests your understanding of Pod lifecycle and troubleshooting workflows, often appearing in scenarios where a deployment pipeline must capture crash output automatically. A common trap is assuming `kubectl logs` always shows all logs, but it defaults to the current container—so if the Pod has restarted, you will see only the new logs unless you explicitly add `--previous`. Memory tip: think of “previous” as “the container that was there before the restart”—like checking the “previous” version of a file.
Google ACE Deploying and implementing a cloud solution Practice Question
This ACE practice question tests your understanding of deploying and implementing a cloud solution. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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 deployment pipeline runs `kubectl logs` to capture output from a crashed Pod's previous container instance. Which flag retrieves logs from the previous (terminated) container instance rather than the current one?
Why wrong: `--since-crash` is not a valid flag. `--all-containers` shows logs from all containers in the Pod but doesn't target the previous instance.
D
kubectl describe pod api-pod | grep -A 50 'Last State'
Why wrong: `kubectl describe` shows metadata and events but not the full container logs. Use `kubectl logs --previous` for log content from the terminated container.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
kubectl logs api-pod --previous
The `--previous` flag in `kubectl logs` retrieves logs from the previous (terminated) container instance of a Pod. This is essential for debugging crashes where the current container has restarted, as the logs from the failed instance are preserved and accessible only with this flag.
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.
✗
kubectl logs api-pod --terminated
Why it's wrong here
`--terminated` is not a valid kubectl logs flag. Use `--previous` or `-p` for the previous container instance.
✓
kubectl logs api-pod --previous
Why this is correct
`--previous` (or `-p`) retrieves logs from the last terminated container instance — essential for debugging containers that crash on startup.
Related concept
Read the scenario before looking for a memorised answer.
`--since-crash` is not a valid flag. `--all-containers` shows logs from all containers in the Pod but doesn't target the previous instance.
✗
kubectl describe pod api-pod | grep -A 50 'Last State'
Why it's wrong here
`kubectl describe` shows metadata and events but not the full container logs. Use `kubectl logs --previous` for log content from the terminated container.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the `--previous` flag as the only way to access logs from a terminated container, and candidates mistakenly choose `--terminated` or `--since-crash` because they sound plausible but do not exist in the kubectl command syntax.
Trap categories for this question
Command / output trap
`--since-crash` is not a valid flag. `--all-containers` shows logs from all containers in the Pod but doesn't target the previous instance.
Detailed technical explanation
How to think about this question
Under the hood, `kubectl logs --previous` queries the kubelet API for the log file of the terminated container, which is stored on the node's filesystem (typically under `/var/log/pods/`). This flag works only if the container has previously run and exited, and the log file has not been rotated or cleaned up. In real-world scenarios, this is critical for debugging init container failures or application crashes that cause rapid restarts, as the current container's logs may not contain the error.
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 startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this ACE question in full detail.
Deploying and implementing a cloud solution — This question tests Deploying and implementing a cloud solution — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: kubectl logs api-pod --previous — The `--previous` flag in `kubectl logs` retrieves logs from the previous (terminated) container instance of a Pod. This is essential for debugging crashes where the current container has restarted, as the logs from the failed instance are preserved and accessible only with this flag.
What should I do if I get this ACE 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 ACE practice question is part of Courseiva's free Google Cloud 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 ACE 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.