The answer is a type mismatch: the flatMap method requires a function that returns a Stream, but String::chars returns an IntStream. This fails because flatMap on a Stream<String> expects a Stream<?> return type, while IntStream is a primitive specialization and not a subtype of Stream<?>, causing a compilation error. On the Oracle Certified Professional Java SE 17 Developer 1Z0-829 exam, this tests your understanding of the distinction between object streams and primitive streams, a common trap where candidates assume chars() returns a Stream<Character>. Remember that chars() yields an IntStream of Unicode code points, not a stream of Character objects. To fix it, you must map each int to a char or use mapToObj. Memory tip: “chars gives ints, not Chars.”
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. 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.
Exhibit
Refer to the exhibit.
Error log:
Exception in thread "main" java.lang.Error: Unresolved compilation problem:
The method flatMap(Function<? super String,? extends Stream<? extends String>>) in the type Stream<String> is not applicable for the arguments (String::chars)
Code snippet:
List<String> words = List.of("hello", "world");
List<Character> letters = words.stream()
.flatMap(String::chars)
.mapToObj(c -> (char) c)
.collect(Collectors.toList());
Refer to the exhibit.
Error log:
Exception in thread "main" java.lang.Error: Unresolved compilation problem:
The method flatMap(Function<? super String,? extends Stream<? extends String>>) in the type Stream<String> is not applicable for the arguments (String::chars)
Code snippet:
List<String> words = List.of("hello", "world");
List<Character> letters = words.stream()
.flatMap(String::chars)
.mapToObj(c -> (char) c)
.collect(Collectors.toList());
A
The collect method is not applicable for a Stream<Character>.
Why wrong: Collectors.toList() works fine on Stream<Character>.
B
The method reference String::chars is not a valid method reference.
Why wrong: String::chars is a valid method reference; it returns an IntStream.
C
The chars() method returns a Stream<Character>, but flatMap requires a function that returns a Stream<Integer>.
Why wrong: chars() returns IntStream, not Stream<Character>.
D
The flatMap method requires a function that returns a Stream, but String::chars returns an IntStream.
flatMap expects a Function returning a Stream<? extends R>, but chars() returns IntStream, which is not a Stream.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The flatMap method requires a function that returns a Stream, but String::chars returns an IntStream.
Option D is correct because the `chars()` method on `String` returns an `IntStream`, not a `Stream<Character>`. The `flatMap` method on a `Stream<String>` expects a function that returns a `Stream<?>`, but `String::chars` returns an `IntStream`, which is a primitive stream and not a subtype of `Stream<?>`. This type mismatch causes a compilation error.
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.
✗
The collect method is not applicable for a Stream<Character>.
Why it's wrong here
Collectors.toList() works fine on Stream<Character>.
✗
The method reference String::chars is not a valid method reference.
Why it's wrong here
String::chars is a valid method reference; it returns an IntStream.
✗
The chars() method returns a Stream<Character>, but flatMap requires a function that returns a Stream<Integer>.
Why it's wrong here
chars() returns IntStream, not Stream<Character>.
✓
The flatMap method requires a function that returns a Stream, but String::chars returns an IntStream.
Why this is correct
flatMap expects a Function returning a Stream<? extends R>, but chars() returns IntStream, which is not a Stream.
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 assume `String::chars` returns a `Stream<Character>` because it deals with characters, but it actually returns an `IntStream`, leading to a type mismatch when used with `flatMap`.
Detailed technical explanation
How to think about this question
Under the hood, `String.chars()` returns an `IntStream` because it represents the Unicode code points of the characters as primitive `int` values. The `flatMap` method on `Stream<T>` is generic and expects a `Function<? super T, ? extends Stream<? extends R>>`, so passing a method reference that returns an `IntStream` violates the type constraint. To fix this, you would need to call `.boxed()` on the `IntStream` to convert it to a `Stream<Integer>`, or use `flatMapToInt` instead of `flatMap`.
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: The flatMap method requires a function that returns a Stream, but String::chars returns an IntStream. — Option D is correct because the `chars()` method on `String` returns an `IntStream`, not a `Stream<Character>`. The `flatMap` method on a `Stream<String>` expects a function that returns a `Stream<?>`, but `String::chars` returns an `IntStream`, which is a primitive stream and not a subtype of `Stream<?>`. This type mismatch causes a compilation error.
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 →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A developer is converting legacy for loops to streams. The legacy code: List<Integer> list = new ArrayList<>(); for (String s : strings) { if (s.length() > 5) { list.add(s.length()); } } They write: List<Integer> list = strings.stream() .filter(s -> s.length() > 5) .map(s -> s.length()) .collect(Collectors.toList()); But it doesn't compile. The error is: 'cannot find symbol: method collect(Collector<Object,?,List<Object>>)'. What is the likely issue?
easy
A.The lambda in filter is incorrectly written; it should be s.length > 5.
✓ B.The map operation returns an IntStream, which does not have a collect method. Use map(s -> s.length()).boxed().collect(...) or mapToInt(...).boxed().
C.The stream should be made unordered to allow the collector to function.
D.Use parallelStream() to enable the collect method.
Why B: Option B is correct because the stream's type is String, but the pipeline returns an int (or Integer) after map; however, the error suggests the compiler cannot infer the collector type. The problem is that filter returns a Stream<String>, then map returns IntStream because s.length() returns int, and collect is not available on IntStream; they need to box it or use mapToInt then boxed. Option A is false because the lambda is valid. Option C is false because unordered would not affect compilation. Option D is false because the issue is not parallel.
Last reviewed: Jun 11, 2026
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.
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.