10 free sample questions from a bank of 57, with the correct answers and explanations. No signup required — start practising right now.
Answer: A
Use insert (with before or after) at the NAT rule-set level to put the new rule where you want it.
[edit security nat ... rule-set].insert is the configuration-mode command that positions a member of a list.before / after name the rule you want to sit next to.Junos always appends a newly configured rule to the bottom of its rule-set, which is why a freshly added NAT rule lands last. Because NAT evaluation is strictly top to bottom, the position decides which rule wins, and the only command that repositions an existing member of a list is insert combined with before or after. insert security nat source rule-set trust rule ftp rule before rule2 is the shape of the command.
run is an operational-mode wrapper for operational-mode commands; it has no effect on the order of a NAT rule-set.top moves the configuration cursor to the top of the hierarchy; it does not move a rule inside a rule-set.up steps one level higher in the configuration hierarchy, from rule to rule-set; it is not a list-ordering command.insert = reposition within a list, and it always comes with before or after. If an option is a hierarchy-navigation command, it is wrong.
Answer: AB
Junos OS is Juniper's network operating system, and it runs on both physical and virtual devices.
The two true statements are the plain description and its deployment breadth. Junos OS is the operating system that runs on Juniper network devices, and Juniper ships the same code for hardware and for virtual instances, which is why one training path covers both. The other two options describe different things entirely: a management system configures devices from outside, and "an operating system for IoT devices" is not something Junos is.
Junos OS = the device's own OS, physical or virtual. If an option calls it a management system, it is describing Junos Space or Security Director instead.
Answer: AB
Flow mode and packet mode. Route mode belongs to the MX/PTX forwarding architecture.
Junos gives the SRX two processing models. Flow mode is the default and is the stateful design in which a session is created on the first packet and every later packet follows it. Packet mode is the stateless per-packet model. Route mode is a different concept entirely - it describes the route-based forwarding architecture on MX and PTX - and wireless mode is not an SRX operating mode at all, so neither can be part of the answer.
Two SRX modes: flow and packet. "Route mode" always means MX/PTX route-based forwarding, so it is a distractor.
Answer: B
Static NAT first, then destination NAT; source NAT comes last, after the security policy lookup.
The order is fixed by what each stage needs. Static NAT has to be translated first because it creates both directions of a mapping. Destination NAT is next, because the routing table must be searched with the address the client actually dialled. Only after route lookup and the security policy lookup does source NAT run - and that is deliberate, so the policy matches the client's real address rather than the translated pool address.
Mnemonic: S-D-R-P-S. Static first, destination before routing, source last. Knowing that source NAT is last eliminates two options on its own.
Answer: B
Static NAT is the bi-directional form: one rule creates the matching reverse translation.
With set security nat static rule-set, the device builds the pair of translations automatically: untrust-to-trust traffic to the public address is rewritten to the internal address, and traffic from that internal address is rewritten back to the public one. That automatic reverse rule is exactly what "bi-directional" means, and it is why static NAT is the standard way to publish a server. The other three forms each translate in one direction only.
Static NAT is bi-directional; everything else is one-way. If an option mentions a one-way rule or "without PAT", it is not the answer.
Answer: BD
host-inbound-traffic controls the protocols and system services accepted by the zone, on both physical interfaces and logical units.
... host-inbound-traffic protocols <proto> except... host-inbound-traffic system-services <service>ge-0/0/1.0.The parameter has two sub-hierarchies, protocols for management protocols such as ssh, https, snmp and icmp, and system-services for Junos system services. Both are enforced on the interfaces bound to the zone, and a zone can hold physical ports as well as logical units, so the same control covers the port and its .0 unit. That is why B and D are selected together. The remaining two options describe traffic that this parameter never sees.
host-inbound-traffic.Two-part answer: protocols and system-services, both applying to physical ports and logical units. Anything describing through-traffic belongs to policies.
Answer: BD
Junos OS is built from independent processes, and each can be restarted on its own.
Junos was deliberately built as a set of independent processes. The routing daemon, the layer 2 daemon, the forwarding daemon and the management daemon each hold their own state and are supervised separately, so a crash in one is recovered by restarting that process alone. The two false options describe a monolithic design in which components are tangled together and one restart cascades - the failure mode Junos modularity exists to avoid.
Learn the phrase: independent, individually restartable processes. That single fact answers the "which two statements about Junos OS architecture" question every time.
Answer: AB
Install the AppID feature licence and put dynamic application objects in the policy.
Two things have to be true before a policy can act on a nested HTTP application. The firewall needs the AppID feature licence, because the identification database and engine ship with it. And the policy has to actually match dynamic application objects, otherwise it falls back to broad applications such as junos-http and the nested function is invisible. The other two options are optional practices, not requirements: unified policies work perfectly well as zone-based policies, and nothing forces you to remove the default policy.
Licence plus policy object. "Global zone" and "delete the default policy" are choices, not prerequisites.
Answer: A
Enable proxy ARP so the SRX answers ARP requests for the source-NAT pool addresses.
If the pool shares a subnet with the egress interface, upstream devices send their ARP requests straight at the firewall interface for the translated address. The firewall answers only when proxy ARP is enabled; otherwise the neighbour caches no MAC address, the reply never comes back, and the session cannot be established. That is why proxy ARP is the mandatory companion to this kind of pool and why the answer is A.
Pool in the same subnet as the egress interface means proxy ARP. Pool off-subnet behind a router means you do not need it.
Answer: B
Zone-based security policies are defined by a from-zone and a to-zone, so both zones appear in every policy.
[edit security policies from-zone X to-zone Y policy <name>].The structure of the configuration hierarchy is the proof: a policy cannot exist without both zone names, because the pair is the path through the hierarchy. The other three options each contradict a documented behaviour. Screens run before policies, not after. Policy evaluation happens once, on the first packet, so it is not part of fast path processing. And zone-based policies exist precisely to control traffic crossing between zones, which is transit traffic, not traffic confined to one zone.
Policy lookup happens once, on the first packet, after screens and after the route lookup. Any option that puts policies earlier or in both paths is wrong.
Want the full bank of 57 questions for Security, Associate (JNCIA-SEC)? See all practice exams.