The answer is to use equals() instead of == for string comparison. The == operator in Java compares object references, not the actual content of the strings, so even when two hash strings are identical in value, they are distinct objects in memory, causing == to return false and denying valid users. This question tests your understanding of Java string equality with equals vs double equals, a core concept in the Oracle Java Foundations 1Z0-811 exam that frequently appears in scenarios involving user input validation or data retrieval. The common trap is assuming == works for strings because it works for primitives; remember that strings are objects, so reference comparison fails where content comparison succeeds. A reliable memory tip: think of == as checking "are they the same object?" while equals() asks "do they have the same characters?"—for login systems, you always want the latter.
1Z0-811 Primitives, Strings and Operators Practice Question
This 1Z0-811 practice question tests your understanding of primitives, strings and operators. 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 developer is implementing a login system where users enter a password that is then hashed using SHA-256. The system stores the hash as a String in the database. On login, the entered password is hashed and compared to the stored hash using the == operator. Occasionally, valid users are denied access, even though the hashes are identical when printed. The developer has confirmed that the hash algorithm is correctly implemented and that the stored hash is exactly the same string as the computed hash. What is the most likely cause and correct fix?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Change the comparison from == to equals().
The == operator compares object references, not string content. Even if the two hash strings are logically equal, they are different String objects in memory, so == returns false. The correct fix is to use the equals() method (or equalsIgnoreCase() for case-insensitive comparison, but hashes are case-sensitive). Option A directly fixes the issue. Option B (intern()) is not standard. Option C (compareTo()) could work but equals() is idiomatic. Option D (hashCode()) compares integers, not strings.
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.
✓
Change the comparison from == to equals().
Why this is correct
equals() compares the actual characters of the strings, which is appropriate for password hash comparison.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use hashCode() to compare integer representations.
Why it's wrong here
Hash codes can have collisions; two different strings can produce the same hash code, so this is unreliable.
✗
Call intern() on both hash strings before using ==.
Why it's wrong here
intern() can make == work for strings from the pool, but it is not a standard or reliable approach for this scenario.
✗
Use compareTo() which returns 0 if equal.
Why it's wrong here
compareTo() works, but equals() is the more idiomatic and clear method for equality checks.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.
Trap categories for this question
Scenario analysis trap
intern() can make == work for strings from the pool, but it is not a standard or reliable approach for this scenario.
Detailed technical explanation
How to think about this question
This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.
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.
Use explanations to understand the rule behind the answer.
TExam Day Tips
→Underline the problem statement mentally.
→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-811 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 1Z0-811 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
Primitives, Strings and Operators — This question tests Primitives, Strings and Operators — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Change the comparison from == to equals(). — The == operator compares object references, not string content. Even if the two hash strings are logically equal, they are different String objects in memory, so == returns false. The correct fix is to use the equals() method (or equalsIgnoreCase() for case-insensitive comparison, but hashes are case-sensitive). Option A directly fixes the issue. Option B (intern()) is not standard. Option C (compareTo()) could work but equals() is idiomatic. Option D (hashCode()) compares integers, not strings.
What should I do if I get this 1Z0-811 question wrong?
Identify which 1Z0-811 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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. Given: String s1 = "Java"; String s2 = new String("Java"); What does (s1 == s2) evaluate to?
medium
A.true if interned, false otherwise
✓ B.false
C.true
D.Compilation error
Why B: Option B is correct: s1 is a literal (interned), s2 is a new object, so == compares references and returns false. Option A is wrong because equals would be true. Option C is wrong because it doesn't compile. Option D is wrong because they are not the same object.
Variation 2. Refer to the exhibit. What is the output?
hard
A.false true false
B.true false true
C.true true true
✓ D.false true true
Why D: The code uses `String.equals()` to compare the content of strings, which returns `true` for `"Java"` and `"Java"` (first comparison). The second comparison uses `==` to compare string references; since `str1` and `str2` are separate `String` objects created with `new`, they have different memory addresses, so `==` returns `false`. The third comparison uses `String.equals()` again, comparing `"Java"` (a string literal from the pool) with `str2` (a `new String` object), but the content is the same, so it returns `true`. Thus the output is `false true true`.
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-811 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-811 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.