JNCIA-SEC Junos OS Security Objects Practice Question
Which TWO objects can be referenced inside a Junos OS security policy? (Choose two)
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
✓
Address book entries / Address sets
Security policies reference source/destination addresses (from address books) and applications.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Functional zone names directly as match criteria for payload inspection
Why it's wrong here
Functional zones are routing context / host traffic constructs, not policy application match criteria.
- ✓
Address book entries / Address sets
Why this is correct
Policies use address objects for matching source and destination traffic.
- ✗
SCREEN option profiles
Why it's wrong here
SCREEN options are applied under security zones, not security policies.
- ✓
Application / Application sets
Why this is correct
Policies use application objects for protocol matching.
- ✗
Hardware crypto processor allocation maps
Why it's wrong here
Hardware allocation is automatic and not referenced in security policies.
About these practice questions
One of 513 original JNCIA-SEC practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed August 2026 · checked against the official Juniper Networks exam blueprint
This JNCIA-SEC practice question is part of Courseiva's free Juniper Networks 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 JNCIA-SEC exam.