Question 231 of 509
Java I/O API and Securing ApplicationsmediumMultiple ChoiceObjective-mapped

Quick Answer

The correct answer is to use an ObjectInputFilter to whitelist allowed classes during deserialization. This secure coding practice prevents deserialization attacks by defining a filter that rejects untrusted classes before they are instantiated, effectively blocking gadget chains that could lead to remote code execution. On the Oracle Certified Professional Java SE 17 Developer 1Z0-829 exam, this concept tests your understanding of the ObjectInputFilter interface introduced in Java 9, often appearing in questions about secure coding for the java.io package. A common trap is assuming that input validation alone is sufficient, but the filter must explicitly whitelist classes rather than blacklist them, as blacklists can be bypassed. Remember the memory tip: “Whitelist, don’t blacklist—filter first, deserialize last.”

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.

A financial application deserializes objects received over the network using ObjectInputStream. To prevent deserialization attacks, which secure coding practice should be implemented?

Question 1mediummultiple choice
Full question →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Use an ObjectInputFilter to whitelist allowed classes.

Option A is correct because ObjectInputFilter (introduced in Java 9) allows you to define a filter that whitelists only trusted classes during deserialization. By rejecting untrusted classes before they are deserialized, you prevent deserialization attacks such as remote code execution via gadget chains. This is the recommended secure coding practice per Oracle's secure coding guidelines for the Java I/O API.

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.

  • Use an ObjectInputFilter to whitelist allowed classes.

    Why this is correct

    ObjectInputFilter provides a declarative way to restrict class loading during deserialization.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Override readObject() in each serializable class to validate data.

    Why it's wrong here

    Overriding readObject() can help but is error-prone and not as comprehensive as a global filter.

  • Declare all fields as transient to prevent unwanted data exposure.

    Why it's wrong here

    Transient fields prevent serialization of that field, but do not protect against deserialization attacks.

  • Encrypt the serialized data with AES before transmission.

    Why it's wrong here

    Encryption protects confidentiality, not integrity of the deserialization process.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often confuse data validation (Option B) or encryption (Option D) with deserialization attack prevention, but the core issue is controlling which classes are allowed to be deserialized, which only an ObjectInputFilter can enforce at the stream level.

Detailed technical explanation

How to think about this question

ObjectInputFilter works by implementing the java.io.ObjectInputFilter interface, which is invoked during the deserialization process via ObjectInputStream.setObjectInputFilter(). The filter can reject classes based on patterns, package names, or custom logic, and it operates at the stream level before any objects are constructed, making it effective against gadget chain attacks like those exploiting the Commons Collections library. In a real-world scenario, a financial application might whitelist only classes from its own package (e.g., com.bank.*) and reject all others, blocking exploits that rely on third-party libraries.

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 security administrator must allow nursing staff to reach a patient records server while blocking access from the guest Wi-Fi VLAN. After applying an extended ACL, traffic is still blocked from nursing workstations. The ACL was applied outbound instead of inbound on the wrong interface. Questions like this test ACL direction and placement rules.

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.

Related practice questions

Related 1Z0-829 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free 1Z0-829 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this 1Z0-829 question test?

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: Use an ObjectInputFilter to whitelist allowed classes. — Option A is correct because ObjectInputFilter (introduced in Java 9) allows you to define a filter that whitelists only trusted classes during deserialization. By rejecting untrusted classes before they are deserialized, you prevent deserialization attacks such as remote code execution via gadget chains. This is the recommended secure coding practice per Oracle's secure coding guidelines for the Java I/O API.

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 →

How Courseiva writes practice questions · Editorial policy

Keep practising

More 1Z0-829 practice questions

Last reviewed: Jun 25, 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.

Loading comments…

Sign in to join the discussion.

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.