Quick Answer
The answer is false. This is because BigDecimal’s equals method compares both the numeric value and the scale, meaning the number of digits after the decimal point, so “1.00” (scale 2) and “1.0” (scale 1) are not equal even though they represent the same mathematical value. On the Oracle Certified Professional Java SE 17 Developer 1Z0-829 exam, this distinction between BigDecimal equals vs compareTo scale is a classic trap: while equals checks scale, compareTo ignores scale and compares only the numeric value, returning zero for these two numbers. The exam frequently tests this nuance to see if you remember that equals is stricter than compareTo. A common memory tip is to think of equals as “exact match” (value and precision) and compareTo as “mathematical match” (value only).
This 1Z0-829 practice question tests your understanding of handling date, time, text, numeric and boolean values. 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.
What is the result of executing the following code snippet?
BigDecimal d1 = new BigDecimal("1.00"); BigDecimal d2 = new BigDecimal("1.0"); System.out.println(d1.equals(d2));
false
Correct: d1.equals(d2) returns false due to scale mismatch.
compile error
Why wrong: Incorrect: The code compiles and runs without error.
true
Why wrong: Incorrect: equals() returns false because scales are different (2 vs 1).
1
Why wrong: Incorrect: The output is a boolean, not an integer.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
false
The `equals` method of `BigDecimal` compares both the numeric value and the scale (number of digits after the decimal point). Since `new BigDecimal("1.00")` has a scale of 2 and `new BigDecimal("1.0")` has a scale of 1, they are not considered equal by `equals`, even though they represent the same mathematical value. Therefore, the output is `false`.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
false
Why this is correct
Correct: d1.equals(d2) returns false due to scale mismatch.
Related concept
Read the scenario before looking for a memorised answer.
compile error
Why it's wrong here
Incorrect: The code compiles and runs without error.
true
Why it's wrong here
Incorrect: equals() returns false because scales are different (2 vs 1).
1
Why it's wrong here
Incorrect: The output is a boolean, not an integer.
Common exam traps
The trap here is that candidates often assume `equals` behaves like `compareTo` or like primitive `==` for numeric values, forgetting that `BigDecimal.equals` enforces scale equality, so `1.00` and `1.0` are not equal.
Trap categories for this question
Command / output trap
Incorrect: The output is a boolean, not an integer.
Detailed technical explanation
Under the hood, `BigDecimal` stores an unscaled integer value and a scale. For `"1.00"`, the unscaled value is 100 and scale is 2; for `"1.0"`, unscaled value is 10 and scale is 1. The `equals` method checks both the unscaled value and the scale, so `100` vs `10` with different scales yields `false`. In contrast, `compareTo` ignores scale and would return 0, which is a common source of confusion in financial calculations where precision matters.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
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
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Handling Date, Time, Text, Numeric and Boolean Values — study guide chapter
Learn the concepts, then practise the questions
Handling Date, Time, Text, Numeric and Boolean Values practice questions
Targeted practice on this topic area only
All 1Z0-829 questions
509 questions across all exam domains
Oracle Certified Professional Java SE 17 Developer 1Z0-829 study guide
Full concept coverage aligned to exam objectives
1Z0-829 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise 1Z0-829 questions linked to Handling Date, Time, Text, Numeric and Boolean Values.
Practise 1Z0-829 questions linked to Controlling Program Flow.
Practise 1Z0-829 questions linked to Utilizing Java Object-Oriented Approach.
Practise 1Z0-829 questions linked to Handling Exceptions.
Practise 1Z0-829 questions linked to Working with Arrays and Collections.
Practise 1Z0-829 questions linked to Working with Streams and Lambda Expressions.
Practise 1Z0-829 questions linked to Java Platform Overview and Packaging.
Practise 1Z0-829 questions linked to Java I/O API and Securing Applications.
Practise 1Z0-829 questions linked to 1Z0-829 fundamentals.
Practise 1Z0-829 questions linked to 1Z0-829 scenario.
Practise 1Z0-829 questions linked to 1Z0-829 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Handling Date, Time, Text, Numeric and Boolean Values — This question tests Handling Date, Time, Text, Numeric and Boolean Values — Read the scenario before looking for a memorised answer..
The correct answer is: false — The `equals` method of `BigDecimal` compares both the numeric value and the scale (number of digits after the decimal point). Since `new BigDecimal("1.00")` has a scale of 2 and `new BigDecimal("1.0")` has a scale of 1, they are not considered equal by `equals`, even though they represent the same mathematical value. Therefore, the output is `false`.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 →
Last reviewed: Jun 25, 2026
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.