Question 395 of 509
Java I/O API and Securing ApplicationsmediumMultiple SelectObjective-mapped

Quick Answer

The answer is to validate and sanitize all user input before processing, and to use PreparedStatement with parameterized queries to prevent SQL injection. This is correct because PreparedStatement separates SQL logic from user-supplied data, causing the database driver to automatically escape special characters so that input is treated as literal values rather than executable SQL code. On the Oracle Certified Professional Java SE 17 Developer 1Z0-829 exam, this concept tests your understanding of secure coding practices for user input in Java, often appearing in questions that ask you to identify which two of several options prevent injection attacks. A common trap is choosing string concatenation or Statement objects, which leave your application vulnerable. Remember the mnemonic “PSVP” — PreparedStatement, Validate, Parameterize — to recall that parameterized queries plus input validation form the core defense against SQL injection when handling user 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 secure coding practices should be followed when developing a Java application that handles user input? (Choose two.)

Question 1mediummulti select
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 PreparedStatement for database queries with user input.

Option A is correct because using PreparedStatement with parameterized queries prevents SQL injection by separating SQL logic from user input. The database driver automatically escapes special characters in the input, ensuring that user-supplied data is treated as literal values, not executable SQL code.

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 PreparedStatement for database queries with user input.

    Why this is correct

    Prevents SQL injection.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Serialize sensitive data without encryption for performance.

    Why it's wrong here

    Unencrypted serialization exposes data.

  • Grant java.security.AllPermission to the application's codebase.

    Why it's wrong here

    Defeats security; grant only required permissions.

  • Validate and sanitize all user input before processing.

    Why this is correct

    Prevents injection and malformed data.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Use java.util.Random for generating session tokens.

    Why it's wrong here

    Not cryptographically strong; use SecureRandom.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Oracle often tests the distinction between predictable random generators (java.util.Random) and cryptographically secure ones (SecureRandom), expecting candidates to know that session tokens require unpredictability, not just randomness.

Detailed technical explanation

How to think about this question

PreparedStatement precompiles the SQL statement with placeholders (?), so the database engine knows the structure in advance and treats user input strictly as data, not as part of the SQL command. This is defined in the JDBC specification (JSR 221) and is the recommended defense against SQL injection, which remains one of the OWASP Top 10 vulnerabilities. In contrast, Statement concatenation creates a new SQL string each time, opening the door for injection attacks.

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.

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 PreparedStatement for database queries with user input. — Option A is correct because using PreparedStatement with parameterized queries prevents SQL injection by separating SQL logic from user input. The database driver automatically escapes special characters in the input, ensuring that user-supplied data is treated as literal values, not executable SQL code.

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

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