Juniper JN0-664 Practice Test 40
Question 390
A Junos service-provider routing engineer investigates this service-provider network scenario. A customer OSPF network prefers a higher-cost interarea VPN route over a backdoor link and needs a design review of sham-link and metric conditions. Which TWO complementary steps combine a suitable technical action and its direct verification? Select TWO answers.
- Review CE dual-homing advertisements, SoO community tags, OSPF route type/cost, sham-link endpoint reachability and import/export policy.
- Inspect hub and spoke import/export communities, default-route presence, return routes, firewall/NAT policy and VPN-specific forwarding table entries.
- Use Site of Origin controls and supported OSPF sham-link design where required to prevent multihomed customer loops or preserve intended intra-area OSPF path selection.
- Use BGP communities as controlled signals for provider routing policies instead of confusing tagging with guaranteed remote traffic behavior.
- Design an eBGP multihop session with explicit remote loopback reachability and appropriate TTL/session transport settings when directly connected peering is not used.
Explanation
Correct Answers
A:The direct discriminating observation is: Review CE dual-homing advertisements, SoO community tags, OSPF route type/cost, sham-link endpoint reachability and import/export policy.
C:The case-specific routing and services action is: Use Site of Origin controls and supported OSPF sham-link design where required to prevent multihomed customer loops or preserve intended intra-area OSPF path selection.
Incorrect Answers
B:This alternative proposes: Inspect hub and spoke import/export communities, default-route presence, return routes, firewall/NAT policy and VPN-specific forwarding table entries. It concerns a different Junos engineering issue Layer 3 VPN hub spoke topology and controlled Internet breakout, not the directly tested provider-network issue Site of Origin and OSPF sham-link loop control.
D:This alternative proposes: Use BGP communities as controlled signals for provider routing policies instead of confusing tagging with guaranteed remote traffic behavior. It concerns a different Junos engineering issue BGP communities and selective transit routing policy, not the directly tested provider-network issue Site of Origin and OSPF sham-link loop control.
E:This alternative proposes: Design an eBGP multihop session with explicit remote loopback reachability and appropriate TTL/session transport settings when directly connected peering is not used. It concerns a different Junos engineering issue BGP external multihop and loopback peer reachability, not the directly tested provider-network issue Site of Origin and OSPF sham-link loop control.
Question 391
A Junos service-provider routing engineer investigates the following routing and service incident: Two carriers negotiate an L3VPN interconnect but their ASBRs disagree about Option A versus VPNv4 signaling, leaving site prefixes absent. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Verify the transport and service label roles in an MPLS Layer 3 VPN before attributing a forwarding failure to the customer routing protocol.
- Select the supported inter-AS or carrier-of-carriers VPN interconnection model according to trust, labels, MP-BGP signaling and administrative boundary requirements.
- Check OSPFv3 adjacency and IPv6 reachability through supported Junos ospf3 operational commands rather than assuming an IPv4 OSPFv2 adjacency proves IPv6 is working.
- Implement intended full-mesh or hub-and-spoke VPN reachability with precise route-target and policy behavior, including explicitly approved Internet access.
Explanation
Correct Answer
B:The case-specific routing and services action is: Select the supported inter-AS or carrier-of-carriers VPN interconnection model according to trust, labels, MP-BGP signaling and administrative boundary requirements. The governing Junos routing/service principle is: Interprovider options vary in whether adjacent ASBRs exchange VRF routes or labeled VPN/transport routes; carrier-of-carriers provides specialized labeled connectivity, not free unrestricted access.
Incorrect Answers
A:This alternative proposes: Verify the transport and service label roles in an MPLS Layer 3 VPN before attributing a forwarding failure to the customer routing protocol. It concerns a different Junos engineering issue MPLS VPN transport label stack and next hop, not the directly tested provider-network issue Interprovider Layer 3 VPN options and carrier of carriers.
C:This alternative proposes: Check OSPFv3 adjacency and IPv6 reachability through supported Junos ospf3 operational commands rather than assuming an IPv4 OSPFv2 adjacency proves IPv6 is working. It concerns a different Junos engineering issue OSPFv3 IPv6 neighbor and IPv4 separation, not the directly tested provider-network issue Interprovider Layer 3 VPN options and carrier of carriers.
D:This alternative proposes: Implement intended full-mesh or hub-and-spoke VPN reachability with precise route-target and policy behavior, including explicitly approved Internet access. It concerns a different Junos engineering issue Layer 3 VPN hub spoke topology and controlled Internet breakout, not the directly tested provider-network issue Interprovider Layer 3 VPN options and carrier of carriers.
Question 392
A provider routing design review considers this situation. Two carriers negotiate an L3VPN interconnect but their ASBRs disagree about Option A versus VPNv4 signaling, leaving site prefixes absent. A colleague proposes: Select the supported inter-AS or carrier-of-carriers VPN interconnection model according to trust, labels, MP-BGP signaling and administrative boundary requirements. Which technical principle BEST supports that action? Select ONE best answer.
- VPN topology is shaped by which prefixes are imported/exported between sites, and a shared service or Internet breakout must be explicitly engineered rather than assumed by one RT value.
- IS-IS hello compatibility requires suitable circuit level, area relation for Level 1, supported MTU/parameters and authentication; physical link Up alone is insufficient.
- The bgp.l3vpn.0 table holds VPNv4 routes; a selected VRF import policy determines which eligible VPN routes appear in that customer's routing-instance inet.0.
- Interprovider options vary in whether adjacent ASBRs exchange VRF routes or labeled VPN/transport routes; carrier-of-carriers provides specialized labeled connectivity, not free unrestricted access.
Explanation
Correct Answer
D:The relevant Junos service-provider networking principle is: Interprovider options vary in whether adjacent ASBRs exchange VRF routes or labeled VPN/transport routes; carrier-of-carriers provides specialized labeled connectivity, not free unrestricted access. In the described provider-network case (Two carriers negotiate an L3VPN interconnect but their ASBRs disagree about Option A versus VPNv4 signaling, leaving site prefixes absent.), it supports the planned action: Select the supported inter-AS or carrier-of-carriers VPN interconnection model according to trust, labels, MP-BGP signaling and administrative boundary requirements.
Incorrect Answers
A:This alternative proposes: VPN topology is shaped by which prefixes are imported/exported between sites, and a shared service or Internet breakout must be explicitly engineered rather than assumed by one RT value. It concerns a different Junos engineering issue Layer 3 VPN hub spoke topology and controlled Internet breakout, not the directly tested provider-network issue Interprovider Layer 3 VPN options and carrier of carriers.
B:This alternative proposes: IS-IS hello compatibility requires suitable circuit level, area relation for Level 1, supported MTU/parameters and authentication; physical link Up alone is insufficient. It concerns a different Junos engineering issue IS-IS adjacency NET and interface mismatch troubleshooting, not the directly tested provider-network issue Interprovider Layer 3 VPN options and carrier of carriers.
C:This alternative proposes: The bgp.l3vpn.0 table holds VPNv4 routes; a selected VRF import policy determines which eligible VPN routes appear in that customer's routing-instance inet.0. It concerns a different Junos engineering issue VPNv4 bgp.l3vpn.0 versus customer VRF route tables, not the directly tested provider-network issue Interprovider Layer 3 VPN options and carrier of carriers.
Question 393
A Juniper service-provider engineer needs decisive verification evidence for this situation. Two carriers negotiate an L3VPN interconnect but their ASBRs disagree about Option A versus VPNv4 signaling, leaving site prefixes absent. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Inspect customer IGMP/PIM membership, MVPN route state, provider tunnel or data-plane transport, RP/SSM mode, RPF and egress PE forwarding.
- Review CE dual-homing advertisements, SoO community tags, OSPF route type/cost, sham-link endpoint reachability and import/export policy.
- Inspect show ospf3 neighbor, show ospf3 interface, IPv6 link-local addresses, area association, LSDB and inet6 routes independently of OSPFv2.
- Compare ASBR/PE roles, VPN route exchange, BGP family negotiation, label stack transport, import/export RT policy and inter-provider fault boundaries.
Explanation
Correct Answer
D:The direct discriminating observation is: Compare ASBR/PE roles, VPN route exchange, BGP family negotiation, label stack transport, import/export RT policy and inter-provider fault boundaries. In the stated situation (Two carriers negotiate an L3VPN interconnect but their ASBRs disagree about Option A versus VPNv4 signaling, leaving site prefixes absent.), the intended acceptance outcome is: The intended remote VPN site can reach its authorized peer across the AS boundary without transferring unrelated tenants' routes or losing required label resolution.
Incorrect Answers
A:This alternative proposes: Inspect customer IGMP/PIM membership, MVPN route state, provider tunnel or data-plane transport, RP/SSM mode, RPF and egress PE forwarding. It concerns a different Junos engineering issue Multicast VPN provider and customer traffic separation, not the directly tested provider-network issue Interprovider Layer 3 VPN options and carrier of carriers.
B:This alternative proposes: Review CE dual-homing advertisements, SoO community tags, OSPF route type/cost, sham-link endpoint reachability and import/export policy. It concerns a different Junos engineering issue Site of Origin and OSPF sham-link loop control, not the directly tested provider-network issue Interprovider Layer 3 VPN options and carrier of carriers.
C:This alternative proposes: Inspect show ospf3 neighbor, show ospf3 interface, IPv6 link-local addresses, area association, LSDB and inet6 routes independently of OSPFv2. It concerns a different Junos engineering issue OSPFv3 IPv6 neighbor and IPv4 separation, not the directly tested provider-network issue Interprovider Layer 3 VPN options and carrier of carriers.
Question 394
A service-provider acceptance team reviews the result of a provider-service change. Two carriers negotiate an L3VPN interconnect but their ASBRs disagree about Option A versus VPNv4 signaling, leaving site prefixes absent. The intended verification is: Compare ASBR/PE roles, VPN route exchange, BGP family negotiation, label stack transport, import/export RT policy and inter-provider fault boundaries. Which outcome BEST demonstrates success? Select ONE best answer.
- The customer contract rate is enforced with predictable handling of permitted bursts and no unintended control-plane traffic drops.
- Customer multicast subscribers receive their authorized streams through the VPN without flooding other tenants or depending on unavailable default multicast underlay features.
- Spokes exchange only approved traffic through the hub and optional shared Internet access follows inspected security and return-path controls.
- The intended remote VPN site can reach its authorized peer across the AS boundary without transferring unrelated tenants' routes or losing required label resolution.
Explanation
Correct Answer
D:The verified success outcome is: The intended remote VPN site can reach its authorized peer across the AS boundary without transferring unrelated tenants' routes or losing required label resolution. Confirm this by: Compare ASBR/PE roles, VPN route exchange, BGP family negotiation, label stack transport, import/export RT policy and inter-provider fault boundaries.
Incorrect Answers
A:That option concerns CoS policers traffic-shaping and committed-rate contracts. The related controlled intervention is: Select the supported inter-AS or carrier-of-carriers VPN interconnection model according to trust, labels, MP-BGP signaling and administrative boundary requirements.
B:That option concerns Multicast VPN provider and customer traffic separation. The related controlled intervention is: Select the supported inter-AS or carrier-of-carriers VPN interconnection model according to trust, labels, MP-BGP signaling and administrative boundary requirements.
C:This alternative proposes: Spokes exchange only approved traffic through the hub and optional shared Internet access follows inspected security and return-path controls. It concerns a different Junos engineering issue Layer 3 VPN hub spoke topology and controlled Internet breakout, not the directly tested provider-network issue Interprovider Layer 3 VPN options and carrier of carriers.
Question 395
A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. Two carriers negotiate an L3VPN interconnect but their ASBRs disagree about Option A versus VPNv4 signaling, leaving site prefixes absent. Which assumption is MOST DIRECTLY dangerous or unsupported? Select ONE best answer.
- Add a customer access interface to the provider's global inet.0 table and expect its overlapping RFC1918 subnet to remain isolated from every other tenant.
- Import every spoke RT into all customer VRFs when the design explicitly requires isolation except for a controlled central inspection service.
- Assume every inter-provider VPN can be connected by advertising raw customer private addresses on an unsecured global peering session with no labels or VPN policy.
- Rewrite every customer's packet to the highest-priority DSCP and set all drop-profile thresholds to zero to eliminate congestion entirely.
Explanation
Correct Answer
C:That conflicts with the edge-to-cloud principle: Interprovider options vary in whether adjacent ASBRs exchange VRF routes or labeled VPN/transport routes; carrier-of-carriers provides specialized labeled connectivity, not free unrestricted access.
Incorrect Answers
A:This alternative proposes: Add a customer access interface to the provider's global inet.0 table and expect its overlapping RFC1918 subnet to remain isolated from every other tenant. It concerns a different Junos engineering issue PE to CE routing and customer route redistribution, not the directly tested provider-network issue Interprovider Layer 3 VPN options and carrier of carriers.
B:This alternative proposes: Import every spoke RT into all customer VRFs when the design explicitly requires isolation except for a controlled central inspection service. It concerns a different Junos engineering issue Layer 3 VPN hub spoke topology and controlled Internet breakout, not the directly tested provider-network issue Interprovider Layer 3 VPN options and carrier of carriers.
D:This alternative proposes: Rewrite every customer's packet to the highest-priority DSCP and set all drop-profile thresholds to zero to eliminate congestion entirely. It concerns a different Junos engineering issue CoS RED drop profiles and rewrite-marking validation, not the directly tested provider-network issue Interprovider Layer 3 VPN options and carrier of carriers.
Question 396
A Junos service-provider routing engineer investigates the following routing and service incident: A carrier-of-carriers customer expects its labeled core connectivity through the provider but the border exchange strips the label-related information needed by the negotiated model. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Validate EVPN multihoming Ethernet segment identifiers and designated-forwarder behavior before activating redundant customer links.
- Verify IPv6 customer prefixes across a supported L3VPN by checking VPNv6 MP-BGP family, route targets and IPv6 customer forwarding independently of IPv4 VPNv4 behavior.
- Implement intended full-mesh or hub-and-spoke VPN reachability with precise route-target and policy behavior, including explicitly approved Internet access.
- Select the supported inter-AS or carrier-of-carriers VPN interconnection model according to trust, labels, MP-BGP signaling and administrative boundary requirements.
Explanation
Correct Answer
D:The case-specific routing and services action is: Select the supported inter-AS or carrier-of-carriers VPN interconnection model according to trust, labels, MP-BGP signaling and administrative boundary requirements. The governing Junos routing/service principle is: Interprovider options vary in whether adjacent ASBRs exchange VRF routes or labeled VPN/transport routes; carrier-of-carriers provides specialized labeled connectivity, not free unrestricted access. Verify the decision through: Compare ASBR/PE roles, VPN route exchange, BGP family negotiation, label stack transport, import/export RT policy and inter-provider fault boundaries.
Incorrect Answers
A:This alternative proposes: Validate EVPN multihoming Ethernet segment identifiers and designated-forwarder behavior before activating redundant customer links. It concerns a different Junos engineering issue EVPN Ethernet segment multihoming and designated forwarder, not the directly tested provider-network issue Interprovider Layer 3 VPN options and carrier of carriers.
B:This alternative proposes: Verify IPv6 customer prefixes across a supported L3VPN by checking VPNv6 MP-BGP family, route targets and IPv6 customer forwarding independently of IPv4 VPNv4 behavior. It concerns a different Junos engineering issue IPv6 Layer 3 VPN VPNv6 route families and forwarding, not the directly tested provider-network issue Interprovider Layer 3 VPN options and carrier of carriers.
C:This alternative proposes: Implement intended full-mesh or hub-and-spoke VPN reachability with precise route-target and policy behavior, including explicitly approved Internet access. It concerns a different Junos engineering issue Layer 3 VPN hub spoke topology and controlled Internet breakout, not the directly tested provider-network issue Interprovider Layer 3 VPN options and carrier of carriers.
Question 397
A provider routing design review considers this situation. A carrier-of-carriers customer expects its labeled core connectivity through the provider but the border exchange strips the label-related information needed by the negotiated model. A colleague proposes: Select the supported inter-AS or carrier-of-carriers VPN interconnection model according to trust, labels, MP-BGP signaling and administrative boundary requirements. Which technical principle BEST supports that action? Select ONE best answer.
- MVPN carries customer multicast across provider networks using supported control-plane membership and provider transport mechanisms; unicast VRF reachability alone does not prove multicast distribution.
- The bgp.l3vpn.0 table holds VPNv4 routes; a selected VRF import policy determines which eligible VPN routes appear in that customer's routing-instance inet.0.
- Interprovider options vary in whether adjacent ASBRs exchange VRF routes or labeled VPN/transport routes; carrier-of-carriers provides specialized labeled connectivity, not free unrestricted access.
- On an OSPF broadcast network a DR and BDR reduce full-adjacency fanout; elections depend on eligible interface priorities and router IDs, and are not always preemptive.
Explanation
Correct Answer
C:The relevant Junos service-provider networking principle is: Interprovider options vary in whether adjacent ASBRs exchange VRF routes or labeled VPN/transport routes; carrier-of-carriers provides specialized labeled connectivity, not free unrestricted access. In the described provider-network case (A carrier-of-carriers customer expects its labeled core connectivity through the provider but the border exchange strips the label-related information needed by the negotiated model.), it supports the planned action: Select the supported inter-AS or carrier-of-carriers VPN interconnection model according to trust, labels, MP-BGP signaling and administrative boundary requirements.
Incorrect Answers
A:This alternative proposes: MVPN carries customer multicast across provider networks using supported control-plane membership and provider transport mechanisms; unicast VRF reachability alone does not prove multicast distribution. It concerns a different Junos engineering issue Multicast VPN provider and customer traffic separation, not the directly tested provider-network issue Interprovider Layer 3 VPN options and carrier of carriers.
B:This alternative proposes: The bgp.l3vpn.0 table holds VPNv4 routes; a selected VRF import policy determines which eligible VPN routes appear in that customer's routing-instance inet.0. It concerns a different Junos engineering issue VPNv4 bgp.l3vpn.0 versus customer VRF route tables, not the directly tested provider-network issue Interprovider Layer 3 VPN options and carrier of carriers.
D:This alternative proposes: On an OSPF broadcast network a DR and BDR reduce full-adjacency fanout; elections depend on eligible interface priorities and router IDs, and are not always preemptive. It concerns a different Junos engineering issue OSPF designated router election on a multiaccess segment, not the directly tested provider-network issue Interprovider Layer 3 VPN options and carrier of carriers.
Question 398
A Juniper service-provider engineer needs decisive verification evidence for this situation. A carrier-of-carriers customer expects its labeled core connectivity through the provider but the border exchange strips the label-related information needed by the negotiated model. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Compare PE routing-instance configuration, RD values, RT export/import communities, received VPN routes and per-instance inet.0 population.
- Compare ASBR/PE roles, VPN route exchange, BGP family negotiation, label stack transport, import/export RT policy and inter-provider fault boundaries.
- Inspect show ospf3 neighbor, show ospf3 interface, IPv6 link-local addresses, area association, LSDB and inet6 routes independently of OSPFv2.
- Inspect show route table bgp.l3vpn.0, instance.inet.0, accepted RT communities, next-hop resolution and label information at both PEs.
Explanation
Correct Answer
B:The direct discriminating observation is: Compare ASBR/PE roles, VPN route exchange, BGP family negotiation, label stack transport, import/export RT policy and inter-provider fault boundaries. In the stated situation (A carrier-of-carriers customer expects its labeled core connectivity through the provider but the border exchange strips the label-related information needed by the negotiated model.), the intended acceptance outcome is: The intended remote VPN site can reach its authorized peer across the AS boundary without transferring unrelated tenants' routes or losing required label resolution.
Incorrect Answers
A:This alternative proposes: Compare PE routing-instance configuration, RD values, RT export/import communities, received VPN routes and per-instance inet.0 population. It concerns a different Junos engineering issue Layer 3 VPN route distinguishers versus route targets, not the directly tested provider-network issue Interprovider Layer 3 VPN options and carrier of carriers.
C:This alternative proposes: Inspect show ospf3 neighbor, show ospf3 interface, IPv6 link-local addresses, area association, LSDB and inet6 routes independently of OSPFv2. It concerns a different Junos engineering issue OSPFv3 IPv6 neighbor and IPv4 separation, not the directly tested provider-network issue Interprovider Layer 3 VPN options and carrier of carriers.
D:This alternative proposes: Inspect show route table bgp.l3vpn.0, instance.inet.0, accepted RT communities, next-hop resolution and label information at both PEs. It concerns a different Junos engineering issue VPNv4 bgp.l3vpn.0 versus customer VRF route tables, not the directly tested provider-network issue Interprovider Layer 3 VPN options and carrier of carriers in the stated situation (A carrier-of-carriers customer expects its labeled core connectivity through the provider but the border exchange strips the label-related information needed by the negotiated model.). A better case-specific check is: Compare ASBR/PE roles, VPN route exchange, BGP family negotiation, label stack transport, import/export RT policy and inter-provider fault boundaries. The more targeted action is: Select the supported inter-AS or carrier-of-carriers VPN interconnection model according to trust, labels, MP-BGP signaling and administrative boundary requirements.
Question 399
A service-provider acceptance team reviews the result of a provider-service change. A carrier-of-carriers customer expects its labeled core connectivity through the provider but the border exchange strips the label-related information needed by the negotiated model. The intended verification is: Compare ASBR/PE roles, VPN route exchange, BGP family negotiation, label stack transport, import/export RT policy and inter-provider fault boundaries. Which outcome BEST demonstrates success? Select ONE best answer.
- Two customers may use the same internal subnet without conflated control-plane identities and only authorized VPNs import each others' prefixes.
- The intended remote VPN site can reach its authorized peer across the AS boundary without transferring unrelated tenants' routes or losing required label resolution.
- Subscribers receive the intended group from approved sources and traffic continues after a tested RP or upstream path change.
- Spokes exchange only approved traffic through the hub and optional shared Internet access follows inspected security and return-path controls.
Explanation
Correct Answer
B:The verified success outcome is: The intended remote VPN site can reach its authorized peer across the AS boundary without transferring unrelated tenants' routes or losing required label resolution. Confirm this by: Compare ASBR/PE roles, VPN route exchange, BGP family negotiation, label stack transport, import/export RT policy and inter-provider fault boundaries. The related controlled intervention is: Select the supported inter-AS or carrier-of-carriers VPN interconnection model according to trust, labels, MP-BGP signaling and administrative boundary requirements.
Incorrect Answers
A:That option concerns Layer 3 VPN route distinguishers versus route targets. The related controlled intervention is: Select the supported inter-AS or carrier-of-carriers VPN interconnection model according to trust, labels, MP-BGP signaling and administrative boundary requirements.
C:That option concerns PIM sparse mode rendezvous point and shared tree operation. The related controlled intervention is: Select the supported inter-AS or carrier-of-carriers VPN interconnection model according to trust, labels, MP-BGP signaling and administrative boundary requirements.
D:This alternative proposes: Spokes exchange only approved traffic through the hub and optional shared Internet access follows inspected security and return-path controls. It concerns a different Junos engineering issue Layer 3 VPN hub spoke topology and controlled Internet breakout, not the directly tested provider-network issue Interprovider Layer 3 VPN options and carrier of carriers.
Question 400
A provider change-review board examines this Junos service case. A carrier-of-carriers customer expects its labeled core connectivity through the provider but the border exchange strips the label-related information needed by the negotiated model. Which THREE statements together give an appropriate corrective action, supporting diagnostic check and success outcome? Select THREE answers.
- Check CE neighbor health, routing-instance interface membership, customer prefixes in instance.inet.0, VRF export policy and remote import results.
- Separate Level 1 intra-area and Level 2 inter-area IS-IS forwarding responsibilities when building a multi-area service-provider IGP.
- The intended remote VPN site can reach its authorized peer across the AS boundary without transferring unrelated tenants' routes or losing required label resolution.
- Verify service MTU and any supported pseudowire encapsulation/control-word expectations when a pseudowire is signaled Up but customer frames fail.
- Compare ASBR/PE roles, VPN route exchange, BGP family negotiation, label stack transport, import/export RT policy and inter-provider fault boundaries.
- Select the supported inter-AS or carrier-of-carriers VPN interconnection model according to trust, labels, MP-BGP signaling and administrative boundary requirements.
Explanation
Correct Answers
C:Confirm this by: Compare ASBR/PE roles, VPN route exchange, BGP family negotiation, label stack transport, import/export RT policy and inter-provider fault boundaries.
E:The direct discriminating observation is: Compare ASBR/PE roles, VPN route exchange, BGP family negotiation, label stack transport, import/export RT policy and inter-provider fault boundaries.
F:The case-specific routing and services action is: Select the supported inter-AS or carrier-of-carriers VPN interconnection model according to trust, labels, MP-BGP signaling and administrative boundary requirements.
Incorrect Answers
A:That option concerns PE to CE routing and customer route redistribution. Confirm this by: Compare ASBR/PE roles, VPN route exchange, BGP family negotiation, label stack transport, import/export RT policy and inter-provider fault boundaries.
B:That option concerns IS-IS level one level two hierarchy and area boundaries. Confirm this by: Compare ASBR/PE roles, VPN route exchange, BGP family negotiation, label stack transport, import/export RT policy and inter-provider fault boundaries.
D:That option concerns Layer 2 pseudowire MTU and control-word interworking. Confirm this by: Compare ASBR/PE roles, VPN route exchange, BGP family negotiation, label stack transport, import/export RT policy and inter-provider fault boundaries.