JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
During provider troubleshooting at Keystone Industrial, this symptom is observed: An IS-IS design uses extended metrics on some routers but a legacy metric setting prevents uniform interpretation of path cost. Which targeted inspection should precede remediation?
Inspect configured metric styles, LSP reachability TLVs and computed route costs at the same IS-IS level. The mismatch concerns IS-IS metric encoding and SPF cost, not Junos route preference between static and BGP.
The check diagnoses a different layer of service. Its source issue is: An IS-IS point-to-point peer stays down after interface provisioning while interface counters increment and other routed protocols can use the link. The relevant initial check is: Inspect configured metric styles, LSP reachability TLVs and computed route costs at the same IS-IS level.
This check may help with another root cause, for example: A new higher-priority router joins an IS-IS LAN but the team expects OSPF's DR/BDR rules and cannot explain the pseudonode origin. It does not test the first failed condition; start with: Inspect configured metric styles, LSP reachability TLVs and computed route costs at the same IS-IS level.
That evidence could be normal while the reported defect persists. It is aimed at: A transit core forms stable IS-IS adjacencies but one router's link-state PDU database lacks a refreshed neighbor record. Instead inspect: Inspect configured metric styles, LSP reachability TLVs and computed route costs at the same IS-IS level.
A production change request at Brookport Finance includes this finding: A Level 1 branch needs a selected prefix from Level 2 but a restrictive policy leaves it unaware of the destination. What should the engineer change to address it?
That would address a separate configuration fault: Two core routers join different IS-IS areas but are expected to exchange Level 1 routes directly as if they share an area identifier. This stem identifies a different cause, corrected by: Implement a narrowly scoped IS-IS interlevel route-leaking policy and validate that selected prefixes are advertised in the intended area and level.
This action may apply to a different problem, for example: An access-area router continues to calculate an obsolete SPF route because its LSP sequence version differs from adjacent routers after a change. It does not repair the stated failure boundary. The case-specific reason is: Interlevel reachability is controlled by L1/L2 advertisement policy and levels, not by adding an OSPF area summary.
Implement a narrowly scoped IS-IS interlevel route-leaking policy and validate that selected prefixes are advertised in the intended area and level. The case-specific reason is: Interlevel reachability is controlled by L1/L2 advertisement policy and levels, not by adding an OSPF area summary. A direct acceptance test is: Only approved interlevel prefixes appear in the target Level 1 database and route table, preserving reachability without a wholesale route leak.
That would address a separate configuration fault: A policy change accidentally distributes infrastructure static routes into IS-IS and expands the link-state database beyond approved scope. This stem identifies a different cause, corrected by: Implement a narrowly scoped IS-IS interlevel route-leaking policy and validate that selected prefixes are advertised in the intended area and level.
After Brookport Finance applies its proposed fix to this problem — A Level 1 branch needs a selected prefix from Level 2 but a restrictive policy leaves it unaware of the destination. — which observation best proves the specific failure has been resolved?
That check proves something else, such as: An IS-IS point-to-point peer stays down after interface provisioning while interface counters increment and other routed protocols can use the link. It could pass while the stated problem remains. The targeted evidence here is: Only approved interlevel prefixes appear in the target Level 1 database and route table, preserving reachability without a wholesale route leak.
Only approved interlevel prefixes appear in the target Level 1 database and route table, preserving reachability without a wholesale route leak. Interlevel reachability is controlled by L1/L2 advertisement policy and levels, not by adding an OSPF area summary.
The observation confirms a different component's behavior. Its source context is: A new high-capacity transit link stays unattractive in IS-IS despite the physical upgrade because an oversized intended metric cannot be represented in the current metric style. In this case the success criterion is: Only approved interlevel prefixes appear in the target Level 1 database and route table, preserving reachability without a wholesale route leak.
That check proves something else, such as: A new higher-priority router joins an IS-IS LAN but the team expects OSPF's DR/BDR rules and cannot explain the pseudonode origin. It could pass while the stated problem remains. The targeted evidence here is: Only approved interlevel prefixes appear in the target Level 1 database and route table, preserving reachability without a wholesale route leak.
An architecture review at Brookport Finance examines the following symptom: A Level 1 branch needs a selected prefix from Level 2 but a restrictive policy leaves it unaware of the destination. What Junos or protocol mechanism is most directly responsible?
That principle belongs to a different service stage: Two IS-IS devices have matching area identifiers but the configured interface level and authentication parameters prevent Hello acceptance. The directly relevant mechanism is: IS-IS route leaking intentionally advertises selected reachability between Level 2 and Level 1 rather than treating all interarea prefixes as native L1 routes.
That principle belongs to a different service stage: An access-area router continues to calculate an obsolete SPF route because its LSP sequence version differs from adjacent routers after a change. The directly relevant mechanism is: IS-IS route leaking intentionally advertises selected reachability between Level 2 and Level 1 rather than treating all interarea prefixes as native L1 routes.
This explains a separate protocol behavior: A new high-capacity transit link stays unattractive in IS-IS despite the physical upgrade because an oversized intended metric cannot be represented in the current metric style. In the current facts, the controlling mechanism is: IS-IS route leaking intentionally advertises selected reachability between Level 2 and Level 1 rather than treating all interarea prefixes as native L1 routes.
IS-IS route leaking intentionally advertises selected reachability between Level 2 and Level 1 rather than treating all interarea prefixes as native L1 routes. The key distinction is: Interlevel reachability is controlled by L1/L2 advertisement policy and levels, not by adding an OSPF area summary. Accordingly the remedy is: Implement a narrowly scoped IS-IS interlevel route-leaking policy and validate that selected prefixes are advertised in the intended area and level.
The team at Brookport Finance defers a fix for this condition: A Level 1 branch needs a selected prefix from Level 2 but a restrictive policy leaves it unaware of the destination. What failure is most likely if no targeted control is applied?
The concern could occur elsewhere when Two core routers join different IS-IS areas but are expected to exchange Level 1 routes directly as if they share an area identifier. For the stated scenario, the immediate risk is: Overly broad leaking bloats a constrained L1 area or exposes route reachability contrary to the topology plan.
Overly broad leaking bloats a constrained L1 area or exposes route reachability contrary to the topology plan. The direct mitigation is: Implement a narrowly scoped IS-IS interlevel route-leaking policy and validate that selected prefixes are advertised in the intended area and level.
It is a risk in another topology or protocol state: A connected service subnet must be injected into IS-IS but is absent even though the router's connected route is active. Here the most direct failure path is: Overly broad leaking bloats a constrained L1 area or exposes route reachability contrary to the topology plan.
The concern could occur elsewhere when Two IS-IS devices have matching area identifiers but the configured interface level and authentication parameters prevent Hello acceptance. For the stated scenario, the immediate risk is: Overly broad leaking bloats a constrained L1 area or exposes route reachability contrary to the topology plan.
During provider troubleshooting at Brookport Finance, this symptom is observed: A Level 1 branch needs a selected prefix from Level 2 but a restrictive policy leaves it unaware of the destination. Which targeted inspection should precede remediation?
This check may help with another root cause, for example: A parser discards useful IS-IS reachability information because the team mistakes an extended reachability TLV for a Hello timer field. It does not test the first failed condition; start with: Inspect level-specific import/export policy and L1 versus L2 routes for the exact prefix before changing interface metric values.
Inspect level-specific import/export policy and L1 versus L2 routes for the exact prefix before changing interface metric values. Interlevel reachability is controlled by L1/L2 advertisement policy and levels, not by adding an OSPF area summary.
The check diagnoses a different layer of service. Its source issue is: A transit core forms stable IS-IS adjacencies but one router's link-state PDU database lacks a refreshed neighbor record. The relevant initial check is: Inspect level-specific import/export policy and L1 versus L2 routes for the exact prefix before changing interface metric values.
This check may help with another root cause, for example: An IS-IS design uses extended metrics on some routers but a legacy metric setting prevents uniform interpretation of path cost. It does not test the first failed condition; start with: Inspect level-specific import/export policy and L1 versus L2 routes for the exact prefix before changing interface metric values.
At Seawood Media, a service provider router shows this failure: An operator leaks the entire Level 2 table into a small Level 1 area when only a single approved service prefix was required. What is the best targeted configuration or operations action?
The other action is relevant when A policy change accidentally distributes infrastructure static routes into IS-IS and expands the link-state database beyond approved scope. The current case instead requires: Implement a narrowly scoped IS-IS interlevel route-leaking policy and validate that selected prefixes are advertised in the intended area and level. The distinction is: Interlevel reachability is controlled by L1/L2 advertisement policy and levels, not by adding an OSPF area summary.
That would address a separate configuration fault: An IS-IS point-to-point peer stays down after interface provisioning while interface counters increment and other routed protocols can use the link. This stem identifies a different cause, corrected by: Implement a narrowly scoped IS-IS interlevel route-leaking policy and validate that selected prefixes are advertised in the intended area and level.
Implement a narrowly scoped IS-IS interlevel route-leaking policy and validate that selected prefixes are advertised in the intended area and level. The case-specific reason is: Interlevel reachability is controlled by L1/L2 advertisement policy and levels, not by adding an OSPF area summary. A direct acceptance test is: Only approved interlevel prefixes appear in the target Level 1 database and route table, preserving reachability without a wholesale route leak.
The other action is relevant when A new high-capacity transit link stays unattractive in IS-IS despite the physical upgrade because an oversized intended metric cannot be represented in the current metric style. The current case instead requires: Implement a narrowly scoped IS-IS interlevel route-leaking policy and validate that selected prefixes are advertised in the intended area and level. The distinction is: Interlevel reachability is controlled by L1/L2 advertisement policy and levels, not by adding an OSPF area summary.
A change auditor at Seawood Media must validate remediation of this finding: An operator leaks the entire Level 2 table into a small Level 1 area when only a single approved service prefix was required. Which test outcome is the strongest acceptance evidence?
The observation confirms a different component's behavior. Its source context is: A new higher-priority router joins an IS-IS LAN but the team expects OSPF's DR/BDR rules and cannot explain the pseudonode origin. In this case the success criterion is: Only approved interlevel prefixes appear in the target Level 1 database and route table, preserving reachability without a wholesale route leak.
That check proves something else, such as: Two core routers join different IS-IS areas but are expected to exchange Level 1 routes directly as if they share an area identifier. It could pass while the stated problem remains. The targeted evidence here is: Only approved interlevel prefixes appear in the target Level 1 database and route table, preserving reachability without a wholesale route leak.
Only approved interlevel prefixes appear in the target Level 1 database and route table, preserving reachability without a wholesale route leak. Interlevel reachability is controlled by L1/L2 advertisement policy and levels, not by adding an OSPF area summary.
The observation confirms a different component's behavior. Its source context is: A transit core forms stable IS-IS adjacencies but one router's link-state PDU database lacks a refreshed neighbor record. In this case the success criterion is: Only approved interlevel prefixes appear in the target Level 1 database and route table, preserving reachability without a wholesale route leak.
The operations training team at Seawood Media discusses this issue: An operator leaks the entire Level 2 table into a small Level 1 area when only a single approved service prefix was required. Which technical explanation matches the intended correction?
This explains a separate protocol behavior: An IS-IS design uses extended metrics on some routers but a legacy metric setting prevents uniform interpretation of path cost. In the current facts, the controlling mechanism is: IS-IS route leaking intentionally advertises selected reachability between Level 2 and Level 1 rather than treating all interarea prefixes as native L1 routes.
The statement can be true when A connected service subnet must be injected into IS-IS but is absent even though the router's connected route is active. But it does not explain the reported failure. Here: Interlevel reachability is controlled by L1/L2 advertisement policy and levels, not by adding an OSPF area summary.
That principle belongs to a different service stage: Two IS-IS devices have matching area identifiers but the configured interface level and authentication parameters prevent Hello acceptance. The directly relevant mechanism is: IS-IS route leaking intentionally advertises selected reachability between Level 2 and Level 1 rather than treating all interarea prefixes as native L1 routes.
IS-IS route leaking intentionally advertises selected reachability between Level 2 and Level 1 rather than treating all interarea prefixes as native L1 routes. The key distinction is: Interlevel reachability is controlled by L1/L2 advertisement policy and levels, not by adding an OSPF area summary. Accordingly the remedy is: Implement a narrowly scoped IS-IS interlevel route-leaking policy and validate that selected prefixes are advertised in the intended area and level.
At Seawood Media, a service acceptance review considers the unresolved issue: An operator leaks the entire Level 2 table into a small Level 1 area when only a single approved service prefix was required. Which operational exposure follows most directly?
It is a risk in another topology or protocol state: A policy change accidentally distributes infrastructure static routes into IS-IS and expands the link-state database beyond approved scope. Here the most direct failure path is: Overly broad leaking bloats a constrained L1 area or exposes route reachability contrary to the topology plan.
The concern could occur elsewhere when A new high-capacity transit link stays unattractive in IS-IS despite the physical upgrade because an oversized intended metric cannot be represented in the current metric style. For the stated scenario, the immediate risk is: Overly broad leaking bloats a constrained L1 area or exposes route reachability contrary to the topology plan.
Overly broad leaking bloats a constrained L1 area or exposes route reachability contrary to the topology plan. The direct mitigation is: Implement a narrowly scoped IS-IS interlevel route-leaking policy and validate that selected prefixes are advertised in the intended area and level.
It is a risk in another topology or protocol state: Routers on an IS-IS broadcast LAN show a different designated intermediate system than the operations diagram predicts. Here the most direct failure path is: Overly broad leaking bloats a constrained L1 area or exposes route reachability contrary to the topology plan.
Before changing configuration at Seawood Media, an engineer investigates: An operator leaks the entire Level 2 table into a small Level 1 area when only a single approved service prefix was required. Which first diagnostic most directly tests the suspected cause?
Inspect level-specific import/export policy and L1 versus L2 routes for the exact prefix before changing interface metric values. Interlevel reachability is controlled by L1/L2 advertisement policy and levels, not by adding an OSPF area summary.
This check may help with another root cause, for example: A transit core forms stable IS-IS adjacencies but one router's link-state PDU database lacks a refreshed neighbor record. It does not test the first failed condition; start with: Inspect level-specific import/export policy and L1 versus L2 routes for the exact prefix before changing interface metric values.
That evidence could be normal while the reported defect persists. It is aimed at: Two IS-IS devices have matching area identifiers but the configured interface level and authentication parameters prevent Hello acceptance. Instead inspect: Inspect level-specific import/export policy and L1 versus L2 routes for the exact prefix before changing interface metric values.
The check diagnoses a different layer of service. Its source issue is: Routers on an IS-IS broadcast LAN show a different designated intermediate system than the operations diagram predicts. The relevant initial check is: Inspect level-specific import/export policy and L1 versus L2 routes for the exact prefix before changing interface metric values.
Please check your mailbox for a message from support@examlabs.com and follow the directions.