The correct answer is that static fields are not serialized during serialization, and constructors are not invoked during deserialization. This is because Java serialization captures only the instance state of an object, writing the values of non-static, non-transient fields to the stream; static fields belong to the class, not the instance, so they are excluded by design. During deserialization, the object is reconstructed directly from the stream data without calling any constructor of the serialized class—instead, the no-arg constructor of the first non-serializable superclass is used, and the serialized fields are populated via reflection or custom readObject() methods. On the Oracle Certified Professional Java SE 17 Developer 1Z0-829 exam, this concept tests your understanding of serialization internals and often appears as a trap where candidates assume constructors run normally or that static values persist. A reliable memory tip: “Static is class-wide, not stream-wide; constructors are for new objects, not restored ones.”
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 statements about Java serialization are true?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
During deserialization, the constructor of the serialized class is not invoked.
Option B is correct because during deserialization, Java does not invoke the constructor of the class being deserialized. Instead, the object is reconstructed from the serialized stream data using the no-arg constructor of the first non-serializable superclass (if any), and the serialized class's fields are populated via reflection or readObject() methods. This avoids re-executing initialization logic that may have side effects or depend on runtime state.
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 serialVersionUID must be explicitly declared in every serializable class.
Why it's wrong here
If not declared, Java computes one automatically.
✓
During deserialization, the constructor of the serialized class is not invoked.
Why this is correct
Deserialization uses special mechanism without constructor.
Related concept
Read the scenario before looking for a memorised answer.
✗
A class that implements Externalizable does not need to implement Serializable.
Why it's wrong here
Externalizable extends Serializable.
✓
Static fields are not serialized during serialization.
Why this is correct
Static fields belong to class, not instance.
Related concept
Read the scenario before looking for a memorised answer.
✗
Fields marked as transient are serialized by default.
Why it's wrong here
Transient fields are excluded from serialization.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume constructors are always called during object creation, but Java serialization bypasses constructors for the serialized class, which can lead to unexpected behavior if initialization logic is missing.
Detailed technical explanation
How to think about this question
Under the hood, serialization uses ObjectOutputStream to write object graphs by traversing fields and writing class metadata, while deserialization uses ObjectInputStream to reconstruct objects without calling constructors—relying on the no-arg constructor of the first non-serializable ancestor (e.g., Object). A subtle behavior: if a serializable class has a finalizer, deserialization can resurrect objects, and the readResolve() method can replace the deserialized instance (e.g., for singletons). In real-world scenarios, this constructor-skipping is critical for frameworks like RMI or distributed caching, where object state must be restored exactly as saved.
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: During deserialization, the constructor of the serialized class is not invoked. — Option B is correct because during deserialization, Java does not invoke the constructor of the class being deserialized. Instead, the object is reconstructed from the serialized stream data using the no-arg constructor of the first non-serializable superclass (if any), and the serialized class's fields are populated via reflection or readObject() methods. This avoids re-executing initialization logic that may have side effects or depend on runtime state.
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.