JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
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.
At Copperwick Markets, a service provider router shows this failure: A connected service subnet must be injected into IS-IS but is absent even though the router's connected route is active. What is the best targeted configuration or operations action?
Correct and constrain the relevant IS-IS export policy to originate only approved non-IS-IS route sources with valid active contributors. The case-specific reason is: Redistributing a connected or static route is an export-policy decision; a healthy adjacency alone does not originate every RIB entry. A direct acceptance test is: The intended subnet appears with the expected IS-IS advertisement attributes and disallowed connected/static routes remain absent.
The other action is relevant when An operator leaks the entire Level 2 table into a small Level 1 area when only a single approved service prefix was required. The current case instead requires: Correct and constrain the relevant IS-IS export policy to originate only approved non-IS-IS route sources with valid active contributors. The distinction is: Redistributing a connected or static route is an export-policy decision; a healthy adjacency alone does not originate every RIB entry.
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: Correct and constrain the relevant IS-IS export policy to originate only approved non-IS-IS route sources with valid active contributors.
This action may apply to a different problem, for example: A provider cannot decide whether IS-IS is losing Hello packets or receiving LSDB updates but failing to process them. It does not repair the stated failure boundary. The case-specific reason is: Redistributing a connected or static route is an export-policy decision; a healthy adjacency alone does not originate every RIB entry.
A change auditor at Copperwick Markets must validate remediation of this finding: A connected service subnet must be injected into IS-IS but is absent even though the router's connected route is active. Which test outcome is the strongest acceptance evidence?
The observation confirms a different component's behavior. Its source context is: A provider redesigns two areas and loses expected interarea reachability because a border router is no longer participating in Level 2 routing. In this case the success criterion is: The intended subnet appears with the expected IS-IS advertisement attributes and disallowed connected/static routes remain absent.
The intended subnet appears with the expected IS-IS advertisement attributes and disallowed connected/static routes remain absent. Redistributing a connected or static route is an export-policy decision; a healthy adjacency alone does not originate every RIB entry.
That check proves something else, such as: A transit core forms stable IS-IS adjacencies but one router's link-state PDU database lacks a refreshed neighbor record. It could pass while the stated problem remains. The targeted evidence here is: The intended subnet appears with the expected IS-IS advertisement attributes and disallowed connected/static routes remain absent.
This would be valid for another situation: An IS-IS design uses extended metrics on some routers but a legacy metric setting prevents uniform interpretation of path cost. It does not establish that the failing boundary in this scenario works; verify: The intended subnet appears with the expected IS-IS advertisement attributes and disallowed connected/static routes remain absent.
The operations training team at Copperwick Markets discusses this issue: A connected service subnet must be injected into IS-IS but is absent even though the router's connected route is active. Which technical explanation matches the intended correction?
Junos IS-IS export policy controls origination or redistribution of selected route sources into IS-IS advertisements. The key distinction is: Redistributing a connected or static route is an export-policy decision; a healthy adjacency alone does not originate every RIB entry. Accordingly the remedy is: Correct and constrain the relevant IS-IS export policy to originate only approved non-IS-IS route sources with valid active contributors.
This explains a separate protocol behavior: An operator leaks the entire Level 2 table into a small Level 1 area when only a single approved service prefix was required. In the current facts, the controlling mechanism is: Junos IS-IS export policy controls origination or redistribution of selected route sources into IS-IS advertisements.
The statement can be true when A parser discards useful IS-IS reachability information because the team mistakes an extended reachability TLV for a Hello timer field. But it does not explain the reported failure. Here: Redistributing a connected or static route is an export-policy decision; a healthy adjacency alone does not originate every RIB entry.
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: Junos IS-IS export policy controls origination or redistribution of selected route sources into IS-IS advertisements.
At Copperwick Markets, a service acceptance review considers the unresolved issue: A connected service subnet must be injected into IS-IS but is absent even though the router's connected route is active. Which operational exposure follows most directly?
That consequence is more closely associated with another deficiency, such as: A transit core forms stable IS-IS adjacencies but one router's link-state PDU database lacks a refreshed neighbor record. The described fault instead exposes: Missing source routes isolate services, while a broad export can introduce undesirable extra prefixes into the domain.
Missing source routes isolate services, while a broad export can introduce undesirable extra prefixes into the domain. The direct mitigation is: Correct and constrain the relevant IS-IS export policy to originate only approved non-IS-IS route sources with valid active contributors.
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: Missing source routes isolate services, while a broad export can introduce undesirable extra prefixes into the domain.
That consequence is more closely associated with another deficiency, such as: An operator leaks the entire Level 2 table into a small Level 1 area when only a single approved service prefix was required. The described fault instead exposes: Missing source routes isolate services, while a broad export can introduce undesirable extra prefixes into the domain.
Before changing configuration at Copperwick Markets, an engineer investigates: A connected service subnet must be injected into IS-IS but is absent even though the router's connected route is active. Which first diagnostic most directly tests the suspected cause?
Inspect the source route's active state, ordered IS-IS policy terms, and the advertised prefix in local and remote IS-IS tables. Redistributing a connected or static route is an export-policy decision; a healthy adjacency alone does not originate every RIB entry.
The check diagnoses a different layer of service. Its source issue is: An operator leaks the entire Level 2 table into a small Level 1 area when only a single approved service prefix was required. The relevant initial check is: Inspect the source route's active state, ordered IS-IS policy terms, and the advertised prefix in local and remote IS-IS tables.
This check may help with another root cause, for example: 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 does not test the first failed condition; start with: Inspect the source route's active state, ordered IS-IS policy terms, and the advertised prefix in local and remote IS-IS tables.
That evidence could be normal while the reported defect persists. It is aimed at: 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. Instead inspect: Inspect the source route's active state, ordered IS-IS policy terms, and the advertised prefix in local and remote IS-IS tables.
During a Junos network change at Ironcrest Payments, the engineer observes: A policy change accidentally distributes infrastructure static routes into IS-IS and expands the link-state database beyond approved scope. Which remediation most directly fixes the described problem?
That would address a separate configuration fault: An IS-IS design uses extended metrics on some routers but a legacy metric setting prevents uniform interpretation of path cost. This stem identifies a different cause, corrected by: Correct and constrain the relevant IS-IS export policy to originate only approved non-IS-IS route sources with valid active contributors.
Correct and constrain the relevant IS-IS export policy to originate only approved non-IS-IS route sources with valid active contributors. The case-specific reason is: Redistributing a connected or static route is an export-policy decision; a healthy adjacency alone does not originate every RIB entry. A direct acceptance test is: The intended subnet appears with the expected IS-IS advertisement attributes and disallowed connected/static routes remain absent.
The other action is relevant when A provider redesigns two areas and loses expected interarea reachability because a border router is no longer participating in Level 2 routing. The current case instead requires: Correct and constrain the relevant IS-IS export policy to originate only approved non-IS-IS route sources with valid active contributors. The distinction is: Redistributing a connected or static route is an export-policy decision; a healthy adjacency alone does not originate every RIB entry.
That would address a separate configuration fault: A remote system appears reachable by IP but intermittent IS-IS adjacency loss correlates with wrong MTU or mismatched circuit configuration. This stem identifies a different cause, corrected by: Correct and constrain the relevant IS-IS export policy to originate only approved non-IS-IS route sources with valid active contributors.
The Junos team at Ironcrest Payments needs a success criterion for this defect: A policy change accidentally distributes infrastructure static routes into IS-IS and expands the link-state database beyond approved scope. Which observed result most precisely confirms the intended repair?
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: The intended subnet appears with the expected IS-IS advertisement attributes and disallowed connected/static routes remain absent.
This would be valid for another situation: A remote system appears reachable by IP but intermittent IS-IS adjacency loss correlates with wrong MTU or mismatched circuit configuration. It does not establish that the failing boundary in this scenario works; verify: The intended subnet appears with the expected IS-IS advertisement attributes and disallowed connected/static routes remain absent.
The observation confirms a different component's behavior. Its source context is: An IS-IS design uses extended metrics on some routers but a legacy metric setting prevents uniform interpretation of path cost. In this case the success criterion is: The intended subnet appears with the expected IS-IS advertisement attributes and disallowed connected/static routes remain absent.
The intended subnet appears with the expected IS-IS advertisement attributes and disallowed connected/static routes remain absent. Redistributing a connected or static route is an export-policy decision; a healthy adjacency alone does not originate every RIB entry.
While analyzing a service failure at Ironcrest Payments, the following is observed: A policy change accidentally distributes infrastructure static routes into IS-IS and expands the link-state database beyond approved scope. Which mechanism best explains the underlying control-plane or forwarding behavior?
The statement can be true when An access-area router continues to calculate an obsolete SPF route because its LSP sequence version differs from adjacent routers after a change. But it does not explain the reported failure. Here: Redistributing a connected or static route is an export-policy decision; a healthy adjacency alone does not originate every RIB entry.
That principle belongs to a different service stage: Two core routers join different IS-IS areas but are expected to exchange Level 1 routes directly as if they share an area identifier. The directly relevant mechanism is: Junos IS-IS export policy controls origination or redistribution of selected route sources into IS-IS advertisements.
This explains a separate protocol behavior: Two IS-IS devices have matching area identifiers but the configured interface level and authentication parameters prevent Hello acceptance. In the current facts, the controlling mechanism is: Junos IS-IS export policy controls origination or redistribution of selected route sources into IS-IS advertisements.
Junos IS-IS export policy controls origination or redistribution of selected route sources into IS-IS advertisements. The key distinction is: Redistributing a connected or static route is an export-policy decision; a healthy adjacency alone does not originate every RIB entry. Accordingly the remedy is: Correct and constrain the relevant IS-IS export policy to originate only approved non-IS-IS route sources with valid active contributors.
The following provider defect remains uncorrected at Ironcrest Payments: A policy change accidentally distributes infrastructure static routes into IS-IS and expands the link-state database beyond approved scope. What is the most direct service or security risk of leaving it unresolved?
The concern could occur elsewhere when An operator leaks the entire Level 2 table into a small Level 1 area when only a single approved service prefix was required. For the stated scenario, the immediate risk is: Missing source routes isolate services, while a broad export can introduce undesirable extra prefixes into the domain.
Missing source routes isolate services, while a broad export can introduce undesirable extra prefixes into the domain. The direct mitigation is: Correct and constrain the relevant IS-IS export policy to originate only approved non-IS-IS route sources with valid active contributors.
It is a risk in another topology or protocol state: Two IS-IS devices have matching area identifiers but the configured interface level and authentication parameters prevent Hello acceptance. Here the most direct failure path is: Missing source routes isolate services, while a broad export can introduce undesirable extra prefixes into the domain.
The concern could occur elsewhere when A parser discards useful IS-IS reachability information because the team mistakes an extended reachability TLV for a Hello timer field. For the stated scenario, the immediate risk is: Missing source routes isolate services, while a broad export can introduce undesirable extra prefixes into the domain.
A support escalation at Ironcrest Payments describes: A policy change accidentally distributes infrastructure static routes into IS-IS and expands the link-state database beyond approved scope. Where should the Junos operator look first for decisive evidence?
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 the source route's active state, ordered IS-IS policy terms, and the advertised prefix in local and remote IS-IS tables.
That evidence could be normal while the reported defect persists. It is aimed at: Routers on an IS-IS broadcast LAN show a different designated intermediate system than the operations diagram predicts. Instead inspect: Inspect the source route's active state, ordered IS-IS policy terms, and the advertised prefix in local and remote IS-IS tables.
The check diagnoses a different layer of service. Its source issue is: A provider changes wide metrics in IS-IS but monitoring reads only legacy narrow reachability data and reports no topology effect. The relevant initial check is: Inspect the source route's active state, ordered IS-IS policy terms, and the advertised prefix in local and remote IS-IS tables.
Inspect the source route's active state, ordered IS-IS policy terms, and the advertised prefix in local and remote IS-IS tables. Redistributing a connected or static route is an export-policy decision; a healthy adjacency alone does not originate every RIB entry.
Please check your mailbox for a message from support@examlabs.com and follow the directions.