The correct answer is that peek is an intermediate operation used for debugging, not for production side effects. This is because the Stream API’s peek method is designed solely to observe elements as they flow through a pipeline, making it ideal for the "peek method stream debugging Java" use case. However, its execution is not guaranteed for every element—short-circuiting operations like findFirst or optimizations such as loop fusion can skip it entirely, so relying on peek for stateful changes leads to unpredictable behavior. On the Oracle Certified Professional Java SE 17 Developer 1Z0-829 exam, this question tests your understanding of intermediate vs. terminal operations and the pitfalls of side effects in streams. A common trap is assuming peek behaves like forEach, but remember: peek is a lazy, non-terminal observer. Memory tip: "Peek, don’t tweak"—use it to look, not to modify.
1Z0-829 Working with Streams and Lambda Expressions Practice Question
This 1Z0-829 practice question tests your understanding of working with streams and lambda expressions. 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 stream pipeline uses the peek method for debugging. Which statement about peek is correct?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
peek is an intermediate operation used for debugging; it is not suitable for production side effects.
Option C is correct because the `peek` method is an intermediate operation in the Stream API, designed primarily for debugging to observe elements as they flow through the pipeline. It is not intended for production side effects because its execution is not guaranteed for every element (e.g., due to short-circuiting or optimization), and relying on it for stateful operations can lead to unpredictable behavior.
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.
✗
peek is a terminal operation that prints elements.
Why it's wrong here
Peek is intermediate.
✗
peek can only be used with parallel streams.
Why it's wrong here
It can be used with any stream.
✓
peek is an intermediate operation used for debugging; it is not suitable for production side effects.
Why this is correct
Correct: Peek is intended for debugging and should not be used for production side effects because its execution is not guaranteed.
Related concept
Read the scenario before looking for a memorised answer.
✗
peek is an intermediate operation, and it is guaranteed to be executed for each element.
Why it's wrong here
Not guaranteed; the Java documentation says it exists mainly for debugging and may not be executed if the pipeline is optimized.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume `peek` is a terminal operation or that it always executes for every element, confusing it with `forEach` or ignoring the Stream API's lazy evaluation and optimization guarantees.
Detailed technical explanation
How to think about this question
Under the hood, `peek` is a non-interfering, stateless intermediate operation that applies a consumer to each element as it passes through the pipeline, but the Java runtime may elide `peek` calls if the stream is optimized (e.g., when using `count()` or `forEach()` after `peek`). A real-world scenario is debugging a complex pipeline where `peek` helps trace element flow, but relying on it for logging in production can fail because short-circuiting operations like `findFirst()` may not invoke `peek` on all elements. The Javadoc explicitly warns that `peek` exists solely to support debugging and should not be used for production side effects.
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 practitioner preparing for the 1Z0-829 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
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.
Working with Streams and Lambda Expressions — This question tests Working with Streams and Lambda Expressions — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: peek is an intermediate operation used for debugging; it is not suitable for production side effects. — Option C is correct because the `peek` method is an intermediate operation in the Stream API, designed primarily for debugging to observe elements as they flow through the pipeline. It is not intended for production side effects because its execution is not guaranteed for every element (e.g., due to short-circuiting or optimization), and relying on it for stateful operations can lead to unpredictable behavior.
What should I do if I get this 1Z0-829 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 1Z0-829 practice question is part of Courseiva's free Oracle 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 1Z0-829 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.