Question 70
During a multisite network cutover, an HPE Juniper Networking engineer investigates this situation: IPv4 OSPFv2 adjacency is healthy, but IPv6 prefixes are absent after adding IPv6 to an access interface. Which operational control would best prevent a recurrence of this exact failure mode?
- Verify summary coverage and black-hole risk whenever component routes change.
- Track IPv4 and IPv6 adjacencies and RIB entries as separate acceptance checks.
- Record permitted LSA types and verify the default route before converting an area to stub.
- Validate area IDs for both link endpoints in change prechecks.
Explanation
Correct Answer
B:Track IPv4 and IPv6 adjacencies and RIB entries as separate acceptance checks. The control limits repetition of the described root condition: OSPFv2 and OSPFv3 have different address-family and protocol mechanics, so an OSPFv2 neighbor alone proves nothing about IPv6 routing. During audits, confirm: An OSPFv3 neighbor and expected IPv6 routes are visible in the appropriate routing table.
Incorrect Answers
A:Verify summary coverage and black-hole risk whenever component routes change. This is a plausible preventive practice for a different OSPF condition, specifically Route summarization at ABR. Interarea aggregation is performed by a suitable ABR; setting an unrelated import filter does not itself produce the expected summary. In this scenario, however, the distinguishing issue is OSPFv3 address-family enablement and the confirming observation is: An OSPFv3 neighbor and expected IPv6 routes are visible in the appropriate routing table.
C:Record permitted LSA types and verify the default route before converting an area to stub. This is a plausible preventive practice for a different OSPF condition, specifically Stub-area external reachability. A stub area excludes AS-external type 5 LSAs and relies on ABR-supplied reachability rather than importing individual external routes. In this scenario, however, the distinguishing issue is OSPFv3 address-family enablement and the confirming observation is: An OSPFv3 neighbor and expected IPv6 routes are visible in the appropriate routing table.
D:Validate area IDs for both link endpoints in change prechecks. This is a plausible preventive practice for a different OSPF condition, specifically Area ID mismatch. An OSPF adjacency requires consistent area identity on the shared link. In this scenario, however, the distinguishing issue is OSPFv3 address-family enablement and the confirming observation is: An OSPFv3 neighbor and expected IPv6 routes are visible in the appropriate routing table.
Question 71
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: A loopback network should be advertised into OSPF but a standard interface template has started sending protocol Hellos where no neighbor should ever form. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Compare authentication type, key identifier and accepted keys during the rollover window.
- Inspect OSPFv3 participation and IPv6 link-local neighbor formation instead of assuming OSPFv2 carries IPv6.
- Inspect whether the loopback or host-facing interface is passive while its prefix remains in OSPF.
- Compare directional interface costs and run shortest-path calculations from each router's own LSDB view.
Explanation
Correct Answer
C:Inspect whether the loopback or host-facing interface is passive while its prefix remains in OSPF. This check examines the decisive condition for Passive interface on OSPF LAN before any unrelated changes are made. The underlying mechanism is: A passive interface can contribute reachability without initiating routing adjacencies on a nontransit segment. The confirming observation is: The prefix is advertised while no OSPF Hello exchange or neighbor appears on the host-facing interface.
Incorrect Answers
A:Compare authentication type, key identifier and accepted keys during the rollover window. This is a plausible diagnostic check for a different OSPF condition, specifically OSPF authentication key rollover. Incompatible OSPF authentication settings cause received packets to be rejected before neighbor state can progress. In this scenario, however, the distinguishing issue is Passive interface on OSPF LAN and the confirming observation is: The prefix is advertised while no OSPF Hello exchange or neighbor appears on the host-facing interface.
B:Inspect OSPFv3 participation and IPv6 link-local neighbor formation instead of assuming OSPFv2 carries IPv6. This is a plausible diagnostic check for a different OSPF condition, specifically OSPFv3 address-family enablement. OSPFv2 and OSPFv3 have different address-family and protocol mechanics, so an OSPFv2 neighbor alone proves nothing about IPv6 routing. In this scenario, however, the distinguishing issue is Passive interface on OSPF LAN and the confirming observation is: The prefix is advertised while no OSPF Hello exchange or neighbor appears on the host-facing interface.
D:Compare directional interface costs and run shortest-path calculations from each router's own LSDB view. This is a plausible diagnostic check for a different OSPF condition, specifically SPF metric asymmetry. OSPF SPF uses each router's outbound link metrics, so directional cost differences can yield asymmetric paths. In this scenario, however, the distinguishing issue is Passive interface on OSPF LAN and the confirming observation is: The prefix is advertised while no OSPF Hello exchange or neighbor appears on the host-facing interface.
Question 72
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: A loopback network should be advertised into OSPF but a standard interface template has started sending protocol Hellos where no neighbor should ever form. Which routing or service mechanism best explains the reported behavior?
- Incompatible OSPF authentication settings cause received packets to be rejected before neighbor state can progress.
- OSPFv2 and OSPFv3 have different address-family and protocol mechanics, so an OSPFv2 neighbor alone proves nothing about IPv6 routing.
- OSPF SPF uses each router's outbound link metrics, so directional cost differences can yield asymmetric paths.
- A passive interface can contribute reachability without initiating routing adjacencies on a nontransit segment.
Explanation
Correct Answer
D:A passive interface can contribute reachability without initiating routing adjacencies on a nontransit segment. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The prefix is advertised while no OSPF Hello exchange or neighbor appears on the host-facing interface. The targeted correction is: Make the host-facing advertisement passive and preserve active routing on real transit links.
Incorrect Answers
A:Incompatible OSPF authentication settings cause received packets to be rejected before neighbor state can progress. This is a plausible protocol explanation for a different OSPF condition, specifically OSPF authentication key rollover. Incompatible OSPF authentication settings cause received packets to be rejected before neighbor state can progress. In this scenario, however, the distinguishing issue is Passive interface on OSPF LAN and the confirming observation is: The prefix is advertised while no OSPF Hello exchange or neighbor appears on the host-facing interface.
B:OSPFv2 and OSPFv3 have different address-family and protocol mechanics, so an OSPFv2 neighbor alone proves nothing about IPv6 routing. This is a plausible protocol explanation for a different OSPF condition, specifically OSPFv3 address-family enablement. OSPFv2 and OSPFv3 have different address-family and protocol mechanics, so an OSPFv2 neighbor alone proves nothing about IPv6 routing. In this scenario, however, the distinguishing issue is Passive interface on OSPF LAN and the confirming observation is: The prefix is advertised while no OSPF Hello exchange or neighbor appears on the host-facing interface.
C:OSPF SPF uses each router's outbound link metrics, so directional cost differences can yield asymmetric paths. This is a plausible protocol explanation for a different OSPF condition, specifically SPF metric asymmetry. OSPF SPF uses each router's outbound link metrics, so directional cost differences can yield asymmetric paths. In this scenario, however, the distinguishing issue is Passive interface on OSPF LAN and the confirming observation is: The prefix is advertised while no OSPF Hello exchange or neighbor appears on the host-facing interface.
Question 73
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: A loopback network should be advertised into OSPF but a standard interface template has started sending protocol Hellos where no neighbor should ever form. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The prefix is advertised while no OSPF Hello exchange or neighbor appears on the host-facing interface.
- Authentication counters and logs stop showing rejects and the existing adjacency returns to Full.
- An OSPFv3 neighbor and expected IPv6 routes are visible in the appropriate routing table.
- The calculated shortest paths match measured next hops after directional costs are accounted for.
Explanation
Correct Answer
A:The prefix is advertised while no OSPF Hello exchange or neighbor appears on the host-facing interface. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: A passive interface can contribute reachability without initiating routing adjacencies on a nontransit segment.
Incorrect Answers
B:Authentication counters and logs stop showing rejects and the existing adjacency returns to Full. This is a plausible observed evidence for a different OSPF condition, specifically OSPF authentication key rollover. Incompatible OSPF authentication settings cause received packets to be rejected before neighbor state can progress. In this scenario, however, the distinguishing issue is Passive interface on OSPF LAN and the confirming observation is: The prefix is advertised while no OSPF Hello exchange or neighbor appears on the host-facing interface.
C:An OSPFv3 neighbor and expected IPv6 routes are visible in the appropriate routing table. This is a plausible observed evidence for a different OSPF condition, specifically OSPFv3 address-family enablement. OSPFv2 and OSPFv3 have different address-family and protocol mechanics, so an OSPFv2 neighbor alone proves nothing about IPv6 routing. In this scenario, however, the distinguishing issue is Passive interface on OSPF LAN and the confirming observation is: The prefix is advertised while no OSPF Hello exchange or neighbor appears on the host-facing interface.
D:The calculated shortest paths match measured next hops after directional costs are accounted for. This is a plausible observed evidence for a different OSPF condition, specifically SPF metric asymmetry. OSPF SPF uses each router's outbound link metrics, so directional cost differences can yield asymmetric paths. In this scenario, however, the distinguishing issue is Passive interface on OSPF LAN and the confirming observation is: The prefix is advertised while no OSPF Hello exchange or neighbor appears on the host-facing interface.
Question 74
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: A loopback network should be advertised into OSPF but a standard interface template has started sending protocol Hellos where no neighbor should ever form. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Coordinate compatible key-chain or key settings across both peers with an overlap period where supported.
- Make the host-facing advertisement passive and preserve active routing on real transit links.
- Configure and verify the intended OSPFv3 IPv6 operation on both peers.
- Normalize planned costs or explicitly accept asymmetry based on tested service requirements.
Explanation
Correct Answer
B:Make the host-facing advertisement passive and preserve active routing on real transit links. The change addresses the root behavior described here: A passive interface can contribute reachability without initiating routing adjacencies on a nontransit segment. Verify success with: The prefix is advertised while no OSPF Hello exchange or neighbor appears on the host-facing interface.
Incorrect Answers
A:Coordinate compatible key-chain or key settings across both peers with an overlap period where supported. This is a plausible configuration or operational fix for a different OSPF condition, specifically OSPF authentication key rollover. Incompatible OSPF authentication settings cause received packets to be rejected before neighbor state can progress. In this scenario, however, the distinguishing issue is Passive interface on OSPF LAN and the confirming observation is: The prefix is advertised while no OSPF Hello exchange or neighbor appears on the host-facing interface.
C:Configure and verify the intended OSPFv3 IPv6 operation on both peers. This is a plausible configuration or operational fix for a different OSPF condition, specifically OSPFv3 address-family enablement. OSPFv2 and OSPFv3 have different address-family and protocol mechanics, so an OSPFv2 neighbor alone proves nothing about IPv6 routing. In this scenario, however, the distinguishing issue is Passive interface on OSPF LAN and the confirming observation is: The prefix is advertised while no OSPF Hello exchange or neighbor appears on the host-facing interface.
D:Normalize planned costs or explicitly accept asymmetry based on tested service requirements. This is a plausible configuration or operational fix for a different OSPF condition, specifically SPF metric asymmetry. OSPF SPF uses each router's outbound link metrics, so directional cost differences can yield asymmetric paths. In this scenario, however, the distinguishing issue is Passive interface on OSPF LAN and the confirming observation is: The prefix is advertised while no OSPF Hello exchange or neighbor appears on the host-facing interface.
Question 75
During a new PE-router service turn-up, an HPE Juniper Networking engineer investigates this situation: A loopback network should be advertised into OSPF but a standard interface template has started sending protocol Hellos where no neighbor should ever form. Which operational control would best prevent a recurrence of this exact failure mode?
- Stage authentication rollovers on both sides and confirm control-plane acceptance before retiring old keys.
- Validate area IDs for both link endpoints in change prechecks.
- Audit passive-interface exceptions to prevent unintended neighbor formation.
- Track IPv4 and IPv6 adjacencies and RIB entries as separate acceptance checks.
Explanation
Correct Answer
C:Audit passive-interface exceptions to prevent unintended neighbor formation. The control limits repetition of the described root condition: A passive interface can contribute reachability without initiating routing adjacencies on a nontransit segment. During audits, confirm: The prefix is advertised while no OSPF Hello exchange or neighbor appears on the host-facing interface.
Incorrect Answers
A:Stage authentication rollovers on both sides and confirm control-plane acceptance before retiring old keys. This is a plausible preventive practice for a different OSPF condition, specifically OSPF authentication key rollover. Incompatible OSPF authentication settings cause received packets to be rejected before neighbor state can progress. In this scenario, however, the distinguishing issue is Passive interface on OSPF LAN and the confirming observation is: The prefix is advertised while no OSPF Hello exchange or neighbor appears on the host-facing interface.
B:Validate area IDs for both link endpoints in change prechecks. This is a plausible preventive practice for a different OSPF condition, specifically Area ID mismatch. An OSPF adjacency requires consistent area identity on the shared link. In this scenario, however, the distinguishing issue is Passive interface on OSPF LAN and the confirming observation is: The prefix is advertised while no OSPF Hello exchange or neighbor appears on the host-facing interface.
D:Track IPv4 and IPv6 adjacencies and RIB entries as separate acceptance checks. This is a plausible preventive practice for a different OSPF condition, specifically OSPFv3 address-family enablement. OSPFv2 and OSPFv3 have different address-family and protocol mechanics, so an OSPFv2 neighbor alone proves nothing about IPv6 routing. In this scenario, however, the distinguishing issue is Passive interface on OSPF LAN and the confirming observation is: The prefix is advertised while no OSPF Hello exchange or neighbor appears on the host-facing interface.
Question 76
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: A locally originated static service prefix is visible in a Junos table but remote OSPF routers never learn it as an external route. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Compare the area's stub configuration and its LSA types with the missing external destinations.
- Inspect external route types and compare the internal cost to each advertising ASBR.
- Inspect the external LSA forwarding-address field and route resolution to that address.
- Compare the source route's active state with the OSPF export policy and resulting external LSAs.
Explanation
Correct Answer
D:Compare the source route's active state with the OSPF export policy and resulting external LSAs. This check examines the decisive condition for OSPF route export policy missing before any unrelated changes are made. The underlying mechanism is: Junos OSPF does not automatically redistribute arbitrary static prefixes; an export policy must explicitly permit the route. The confirming observation is: The originating ASBR generates the expected external advertisement and remote routers install the authorized prefix.
Incorrect Answers
A:Compare the area's stub configuration and its LSA types with the missing external destinations. This is a plausible diagnostic check for a different OSPF condition, specifically Stub-area external reachability. A stub area excludes AS-external type 5 LSAs and relies on ABR-supplied reachability rather than importing individual external routes. In this scenario, however, the distinguishing issue is OSPF route export policy missing and the confirming observation is: The originating ASBR generates the expected external advertisement and remote routers install the authorized prefix.
B:Inspect external route types and compare the internal cost to each advertising ASBR. This is a plausible diagnostic check for a different OSPF condition, specifically External E1 versus E2 selection. An external E2 metric primarily represents the advertised external cost, whereas E1 accounts for internal cost toward the ASBR plus external cost. In this scenario, however, the distinguishing issue is OSPF route export policy missing and the confirming observation is: The originating ASBR generates the expected external advertisement and remote routers install the authorized prefix.
C:Inspect the external LSA forwarding-address field and route resolution to that address. This is a plausible diagnostic check for a different OSPF condition, specifically OSPF external forwarding address. An advertised external destination can require reachable resolution of a nonzero forwarding address before the path is usable. In this scenario, however, the distinguishing issue is OSPF route export policy missing and the confirming observation is: The originating ASBR generates the expected external advertisement and remote routers install the authorized prefix.
Question 77
During an overnight NOC investigation, an HPE Juniper Networking engineer investigates this situation: A locally originated static service prefix is visible in a Junos table but remote OSPF routers never learn it as an external route. Which routing or service mechanism best explains the reported behavior?
- Junos OSPF does not automatically redistribute arbitrary static prefixes; an export policy must explicitly permit the route.
- A stub area excludes AS-external type 5 LSAs and relies on ABR-supplied reachability rather than importing individual external routes.
- Link-state routes depend on consistent current LSAs and completed SPF processing, not solely on neighbor Full status.
- An external E2 metric primarily represents the advertised external cost, whereas E1 accounts for internal cost toward the ASBR plus external cost.
Explanation
Correct Answer
A:Junos OSPF does not automatically redistribute arbitrary static prefixes; an export policy must explicitly permit the route. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The originating ASBR generates the expected external advertisement and remote routers install the authorized prefix. The targeted correction is: Add a narrow export policy for the correct source protocol and approved prefix.
Incorrect Answers
B:A stub area excludes AS-external type 5 LSAs and relies on ABR-supplied reachability rather than importing individual external routes. This is a plausible protocol explanation for a different OSPF condition, specifically Stub-area external reachability. A stub area excludes AS-external type 5 LSAs and relies on ABR-supplied reachability rather than importing individual external routes. In this scenario, however, the distinguishing issue is OSPF route export policy missing and the confirming observation is: The originating ASBR generates the expected external advertisement and remote routers install the authorized prefix.
C:Link-state routes depend on consistent current LSAs and completed SPF processing, not solely on neighbor Full status. This is a plausible protocol explanation for a different OSPF condition, specifically LSDB sequence-age mismatch. Link-state routes depend on consistent current LSAs and completed SPF processing, not solely on neighbor Full status. In this scenario, however, the distinguishing issue is OSPF route export policy missing and the confirming observation is: The originating ASBR generates the expected external advertisement and remote routers install the authorized prefix.
D:An external E2 metric primarily represents the advertised external cost, whereas E1 accounts for internal cost toward the ASBR plus external cost. This is a plausible protocol explanation for a different OSPF condition, specifically External E1 versus E2 selection. An external E2 metric primarily represents the advertised external cost, whereas E1 accounts for internal cost toward the ASBR plus external cost. In this scenario, however, the distinguishing issue is OSPF route export policy missing and the confirming observation is: The originating ASBR generates the expected external advertisement and remote routers install the authorized prefix.
Question 78
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: A locally originated static service prefix is visible in a Junos table but remote OSPF routers never learn it as an external route. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The local LSDB lacks type 5 LSAs while an ABR-provided default can still be installed.
- The originating ASBR generates the expected external advertisement and remote routers install the authorized prefix.
- Both routers hold the current LSA instance and SPF results match the intended next-hop behavior.
- The calculated path ranking changes as predicted when an E1 policy considers internal cost to each exit.
Explanation
Correct Answer
B:The originating ASBR generates the expected external advertisement and remote routers install the authorized prefix. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Junos OSPF does not automatically redistribute arbitrary static prefixes; an export policy must explicitly permit the route.
Incorrect Answers
A:The local LSDB lacks type 5 LSAs while an ABR-provided default can still be installed. This is a plausible observed evidence for a different OSPF condition, specifically Stub-area external reachability. A stub area excludes AS-external type 5 LSAs and relies on ABR-supplied reachability rather than importing individual external routes. In this scenario, however, the distinguishing issue is OSPF route export policy missing and the confirming observation is: The originating ASBR generates the expected external advertisement and remote routers install the authorized prefix.
C:Both routers hold the current LSA instance and SPF results match the intended next-hop behavior. This is a plausible observed evidence for a different OSPF condition, specifically LSDB sequence-age mismatch. Link-state routes depend on consistent current LSAs and completed SPF processing, not solely on neighbor Full status. In this scenario, however, the distinguishing issue is OSPF route export policy missing and the confirming observation is: The originating ASBR generates the expected external advertisement and remote routers install the authorized prefix.
D:The calculated path ranking changes as predicted when an E1 policy considers internal cost to each exit. This is a plausible observed evidence for a different OSPF condition, specifically External E1 versus E2 selection. An external E2 metric primarily represents the advertised external cost, whereas E1 accounts for internal cost toward the ASBR plus external cost. In this scenario, however, the distinguishing issue is OSPF route export policy missing and the confirming observation is: The originating ASBR generates the expected external advertisement and remote routers install the authorized prefix.
Question 79
During an edge-to-core validation, an HPE Juniper Networking engineer investigates this situation: A locally originated static service prefix is visible in a Junos table but remote OSPF routers never learn it as an external route. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Use a normal area if individual external LSAs are required, or explicitly design default-route reachability through the ABR.
- Correct LSA synchronization or update flooding causes, then allow the SPF process to converge.
- Add a narrow export policy for the correct source protocol and approved prefix.
- Use an E1 policy when internal path cost to an external exit must influence the selection.
Explanation
Correct Answer
C:Add a narrow export policy for the correct source protocol and approved prefix. The change addresses the root behavior described here: Junos OSPF does not automatically redistribute arbitrary static prefixes; an export policy must explicitly permit the route. Verify success with: The originating ASBR generates the expected external advertisement and remote routers install the authorized prefix.
Incorrect Answers
A:Use a normal area if individual external LSAs are required, or explicitly design default-route reachability through the ABR. This is a plausible configuration or operational fix for a different OSPF condition, specifically Stub-area external reachability. A stub area excludes AS-external type 5 LSAs and relies on ABR-supplied reachability rather than importing individual external routes. In this scenario, however, the distinguishing issue is OSPF route export policy missing and the confirming observation is: The originating ASBR generates the expected external advertisement and remote routers install the authorized prefix.
B:Correct LSA synchronization or update flooding causes, then allow the SPF process to converge. This is a plausible configuration or operational fix for a different OSPF condition, specifically LSDB sequence-age mismatch. Link-state routes depend on consistent current LSAs and completed SPF processing, not solely on neighbor Full status. In this scenario, however, the distinguishing issue is OSPF route export policy missing and the confirming observation is: The originating ASBR generates the expected external advertisement and remote routers install the authorized prefix.
D:Use an E1 policy when internal path cost to an external exit must influence the selection. This is a plausible configuration or operational fix for a different OSPF condition, specifically External E1 versus E2 selection. An external E2 metric primarily represents the advertised external cost, whereas E1 accounts for internal cost toward the ASBR plus external cost. In this scenario, however, the distinguishing issue is OSPF route export policy missing and the confirming observation is: The originating ASBR generates the expected external advertisement and remote routers install the authorized prefix.
Question 80
During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: A locally originated static service prefix is visible in a Junos table but remote OSPF routers never learn it as an external route. Which operational control would best prevent a recurrence of this exact failure mode?
- Record permitted LSA types and verify the default route before converting an area to stub.
- Monitor LSDB freshness and SPF processing during periods of churn.
- Test external metric-type assumptions after an ASBR topology or cost change.
- Review policy matches against a fixed allowlist after each redistribution change.
Explanation
Correct Answer
D:Review policy matches against a fixed allowlist after each redistribution change. The control limits repetition of the described root condition: Junos OSPF does not automatically redistribute arbitrary static prefixes; an export policy must explicitly permit the route. During audits, confirm: The originating ASBR generates the expected external advertisement and remote routers install the authorized prefix.
Incorrect Answers
A:Record permitted LSA types and verify the default route before converting an area to stub. This is a plausible preventive practice for a different OSPF condition, specifically Stub-area external reachability. A stub area excludes AS-external type 5 LSAs and relies on ABR-supplied reachability rather than importing individual external routes. In this scenario, however, the distinguishing issue is OSPF route export policy missing and the confirming observation is: The originating ASBR generates the expected external advertisement and remote routers install the authorized prefix.
B:Monitor LSDB freshness and SPF processing during periods of churn. This is a plausible preventive practice for a different OSPF condition, specifically LSDB sequence-age mismatch. Link-state routes depend on consistent current LSAs and completed SPF processing, not solely on neighbor Full status. In this scenario, however, the distinguishing issue is OSPF route export policy missing and the confirming observation is: The originating ASBR generates the expected external advertisement and remote routers install the authorized prefix.
C:Test external metric-type assumptions after an ASBR topology or cost change. This is a plausible preventive practice for a different OSPF condition, specifically External E1 versus E2 selection. An external E2 metric primarily represents the advertised external cost, whereas E1 accounts for internal cost toward the ASBR plus external cost. In this scenario, however, the distinguishing issue is OSPF route export policy missing and the confirming observation is: The originating ASBR generates the expected external advertisement and remote routers install the authorized prefix.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests