The correct answer is that marking sensitive fields as transient and implementing readObject() to validate and sanitize fields are the two practices that improve Java serialization security. Marking a field as transient prevents it from being written to the serialized byte stream, which directly protects confidential data like passwords or cryptographic keys from exposure. Implementing the readObject() method allows you to enforce validation and sanitization upon deserialization, guarding against crafted input that could corrupt object state or trigger malicious behavior. On the Oracle Certified Professional Java SE 17 Developer 1Z0-829 exam, this topic tests your understanding of secure coding practices within the serialization lifecycle, often appearing as a multiple-select question where distractors might suggest using defaultReadObject() alone or relying on writeReplace(). A common trap is assuming that transient only affects serialization, not deserialization—remember that transient blocks output, while readObject() controls input. Memory tip: “Transient for output, readObject for input.”
1Z0-829 Java I/O API and Securing Applications Practice Question
This 1Z0-829 practice question tests your understanding of java i/o api and securing applications. 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.
Which TWO practices improve the security of Java serialization?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Mark sensitive fields as transient to exclude them from serialization.
Option B is correct because marking sensitive fields as transient prevents them from being serialized, ensuring that confidential data (e.g., passwords, cryptographic keys) is not exposed through the serialized stream. Option D is correct because implementing readObject() allows you to validate and sanitize deserialized fields, protecting against deserialization attacks where crafted data could corrupt the object state or trigger malicious 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.
✗
Disable serialization by throwing NotSerializableException from writeObject().
Why it's wrong here
This prevents serialization but may break functionality; better to secure than disable.
✓
Mark sensitive fields as transient to exclude them from serialization.
Why this is correct
transient prevents sensitive data from being serialized.
Related concept
Read the scenario before looking for a memorised answer.
✗
Set a random serialVersionUID to prevent malicious serialization.
Why it's wrong here
serialVersionUID is for version compatibility, not security.
✓
Implement readObject() to validate and sanitize fields.
Why this is correct
Validation in readObject() can prevent malicious data from being used.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use Externalizable for full control over serialization format.
Why it's wrong here
Externalizable is a design choice, not specifically a security practice.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse serialVersionUID as a security mechanism when it is actually a versioning control for class compatibility, not a defense against malicious serialization.
Detailed technical explanation
How to think about this question
Under the hood, Java serialization uses ObjectOutputStream to write object state, and transient fields are simply skipped during the default serialization process, leaving them as default values (null for objects, 0 for primitives) upon deserialization. A real-world scenario is a banking application where an Account object contains a transient password field; without this, the password would be written to the serialized byte stream, potentially exposing it if the stream is intercepted. Additionally, implementing readObject() with validation (e.g., checking field ranges or rejecting nulls) is a key defense against deserialization attacks like those exploiting the 'gadget chain' vulnerability in libraries like Apache Commons Collections.
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.
Java I/O API and Securing Applications — This question tests Java I/O API and Securing Applications — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Mark sensitive fields as transient to exclude them from serialization. — Option B is correct because marking sensitive fields as transient prevents them from being serialized, ensuring that confidential data (e.g., passwords, cryptographic keys) is not exposed through the serialized stream. Option D is correct because implementing readObject() allows you to validate and sanitize deserialized fields, protecting against deserialization attacks where crafted data could corrupt the object state or trigger malicious 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.