Examers.io
ExamsOrganizationsHow it worksPricingHelp & FAQ
Juniper Networks logo

Juniper NetworksCertified Professional, Service Provider Routing and Switching (JNCIP-SP)

Domain 6Objective 3

Layer 3 VPN Configuration and Monitoring JN0-664 Practice Questions (Page 6)

Part of the Layer 3 VPNs domain, which makes up ~8% of our current practice bank. Juniper Networks does not publish an official question count, but from its 90-minute exam (~35–60 total, ~3–5 in this domain), expect 1–2 from this objective — we provide 28 practice questions to prepare you well beyond it. (estimate)

28questions here
6free pages
7concepts

Questions 26–28

  1. 26foundation · easy

    In a hub-and-spoke Layer 3 VPN, which route target configuration would prevent spoke VRFs from exchanging routes directly with each other?

    Select an answer first
  2. 27application · medium

    A provider is implementing a Layer 3 VPN where two different customers, Customer X and Customer Y, share the same PE router. Customer X has two sites that need to communicate, and Customer Y has two sites that need to communicate. The engineer configures VRF instances for each customer. What route target configuration will ensure that Customer X's sites can communicate with each other but not with Customer Y's sites?

    Select an answer first
  3. 28expert · hard

    A service provider has a Layer 3 VPN with multiple customers. One customer, Customer D, has two sites that need to communicate. The engineer configures the VRF on both PE routers with the same route distinguisher and route targets. However, the sites cannot communicate. The engineer checks the MP-BGP sessions and finds they are up. The engineer also verifies that the VPN-IPv4 routes are present in the BGP table. What should the engineer check next?

    Select an answer first
Finished these 3 questions?

Review the revealed explanations, or continue through the curriculum.

No more pagesBack to JN0-664

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Juniper Networks. “JN0-664” is a trademark of its owner, used for identification only.