Question 76 of 509
Java I/O API and Securing ApplicationshardMultiple SelectObjective-mapped

Quick Answer

The correct answer includes the statement that AccessController.doPrivileged() allows code to temporarily escalate privileges, as this method remains a core part of the legacy security framework that the deprecated SecurityManager relied upon. In Java 17, the SecurityManager is deprecated for removal under JEP 411 because its architecture is considered outdated and difficult to maintain, signaling that developers should move away from relying on it for security policies. On the Oracle Certified Professional Java SE 17 Developer 1Z0-829 exam, this topic tests your understanding of deprecation mechanics and the shift toward modern alternatives like the Java Platform Module System (JPMS) for access control. A common trap is assuming deprecation means immediate removal—remember that deprecated classes still compile and run, but their use is strongly discouraged. Memory tip: think “doPrivileged = temporary keys to the castle” to recall that it grants a short-lived privilege escalation within a trusted code block.

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 THREE statements about the SecurityManager and security policies in Java 17 are true? (Choose three.)

Question 1hardmulti 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

The SecurityManager class is deprecated in Java 17.

The SecurityManager class is deprecated for removal in Java 17 (JEP 411). This deprecation means that while the class still exists for compatibility, it is no longer recommended for use and may be removed in a future release. The core reasoning is that the SecurityManager architecture is considered legacy and difficult to maintain, so Oracle has deprecated it to encourage developers to adopt alternative security mechanisms.

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.

  • System.setProperty("java.security.policy", "policy.url") loads a new policy.

    Why it's wrong here

    Only sets the property; explicit Policy refresh needed.

  • The SecurityManager class is deprecated in Java 17.

    Why this is correct

    Deprecated since Java 18? Actually Java 17 already marks it deprecated.

    Related concept

    Read the scenario before looking for a memorised answer.

  • By default, Java 17 applications run with a SecurityManager installed.

    Why it's wrong here

    No default SecurityManager; must be enabled manually.

  • A security policy file can contain grant entries for code sources.

    Why this is correct

    Policy files define permissions per code source.

    Related concept

    Read the scenario before looking for a memorised answer.

  • AccessController.doPrivileged() allows code to temporarily escalate privileges.

    Why this is correct

    Enables privileged code blocks with limited permissions.

    Related concept

    Read the scenario before looking for a memorised answer.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often confuse setting a system property with actually loading a policy, and they assume the SecurityManager is active by default in modern Java versions, when in fact it is deprecated and disabled by default since Java 17.

Detailed technical explanation

How to think about this question

The SecurityManager works with the AccessController and Policy classes to enforce sandbox security. The AccessController.doPrivileged() method (option E) allows a privileged code block to temporarily bypass the current security context's permissions, which is useful when trusted code needs to access a protected resource on behalf of untrusted code. The security policy file uses grant entries (option D) to specify permissions for code sources based on codebase URLs, signers, or principal names, following the syntax defined in the Java Security Architecture specification.

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 small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.

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: The SecurityManager class is deprecated in Java 17. — The SecurityManager class is deprecated for removal in Java 17 (JEP 411). This deprecation means that while the class still exists for compatibility, it is no longer recommended for use and may be removed in a future release. The core reasoning is that the SecurityManager architecture is considered legacy and difficult to maintain, so Oracle has deprecated it to encourage developers to adopt alternative security mechanisms.

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

Same concept, more angles

1 more ways this is tested on 1Z0-829

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. Which TWO statements are true about securing a Java application?

medium
  • A.A security policy file can grant specific permissions to code from a particular codebase.
  • B.Enabling the security manager is required for all Java applications.
  • C.The Java Cryptography Extension (JCE) is deprecated and should not be used.
  • D.Using code signing guarantees that the application is secure.
  • E.The SecurityManager class can be used to set a security policy for the application.

Why A: Option A is correct because a Java security policy file can use a codebase URL (e.g., `codeBase "file:/path/to/jar"`) to grant specific permissions, such as `java.io.FilePermission`, to code loaded from that location. This is a core feature of the Java security model, allowing fine-grained access control based on where the code originates.

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.