Practice Free JN0-664 Exam Online Questions
Question #31
Exhibit
Referring to the exhibit, which statement is correct?
- A . The vrf-target configuration will allow routes to be shared between CE-1 and CE-2.
- B . The vrf-target configuration will stop routes from being shared between CE-1 and CE-2.
- C . The route-distinguisher configuration will allow overlapping routes to be shared between CE-1 and CE-2.
- D . The route-diatinguisher configuration will stop routes from being shared between CE-1 and CE-2.
Correct Answer: A
A
Explanation:
This is because the vrf-target configuration is used in MPLS VPNs to control the import and export of routes between different VPN routing and forwarding (VRF) instances. If both CE-1 and CE-2 have routing instances configured with matching vrf-target statements, this will allow them to share routes as the routes will be tagged with the same extended community value, which allows for the correct import and export of the routes into each VRF on the PE routers.
A
Explanation:
This is because the vrf-target configuration is used in MPLS VPNs to control the import and export of routes between different VPN routing and forwarding (VRF) instances. If both CE-1 and CE-2 have routing instances configured with matching vrf-target statements, this will allow them to share routes as the routes will be tagged with the same extended community value, which allows for the correct import and export of the routes into each VRF on the PE routers.
Question #31
Exhibit
Referring to the exhibit, which statement is correct?
- A . The vrf-target configuration will allow routes to be shared between CE-1 and CE-2.
- B . The vrf-target configuration will stop routes from being shared between CE-1 and CE-2.
- C . The route-distinguisher configuration will allow overlapping routes to be shared between CE-1 and CE-2.
- D . The route-diatinguisher configuration will stop routes from being shared between CE-1 and CE-2.
Correct Answer: A
A
Explanation:
This is because the vrf-target configuration is used in MPLS VPNs to control the import and export of routes between different VPN routing and forwarding (VRF) instances. If both CE-1 and CE-2 have routing instances configured with matching vrf-target statements, this will allow them to share routes as the routes will be tagged with the same extended community value, which allows for the correct import and export of the routes into each VRF on the PE routers.
A
Explanation:
This is because the vrf-target configuration is used in MPLS VPNs to control the import and export of routes between different VPN routing and forwarding (VRF) instances. If both CE-1 and CE-2 have routing instances configured with matching vrf-target statements, this will allow them to share routes as the routes will be tagged with the same extended community value, which allows for the correct import and export of the routes into each VRF on the PE routers.
Question #31
Exhibit
Referring to the exhibit, which statement is correct?
- A . The vrf-target configuration will allow routes to be shared between CE-1 and CE-2.
- B . The vrf-target configuration will stop routes from being shared between CE-1 and CE-2.
- C . The route-distinguisher configuration will allow overlapping routes to be shared between CE-1 and CE-2.
- D . The route-diatinguisher configuration will stop routes from being shared between CE-1 and CE-2.
Correct Answer: A
A
Explanation:
This is because the vrf-target configuration is used in MPLS VPNs to control the import and export of routes between different VPN routing and forwarding (VRF) instances. If both CE-1 and CE-2 have routing instances configured with matching vrf-target statements, this will allow them to share routes as the routes will be tagged with the same extended community value, which allows for the correct import and export of the routes into each VRF on the PE routers.
A
Explanation:
This is because the vrf-target configuration is used in MPLS VPNs to control the import and export of routes between different VPN routing and forwarding (VRF) instances. If both CE-1 and CE-2 have routing instances configured with matching vrf-target statements, this will allow them to share routes as the routes will be tagged with the same extended community value, which allows for the correct import and export of the routes into each VRF on the PE routers.
Question #31
Exhibit
Referring to the exhibit, which statement is correct?
- A . The vrf-target configuration will allow routes to be shared between CE-1 and CE-2.
- B . The vrf-target configuration will stop routes from being shared between CE-1 and CE-2.
- C . The route-distinguisher configuration will allow overlapping routes to be shared between CE-1 and CE-2.
- D . The route-diatinguisher configuration will stop routes from being shared between CE-1 and CE-2.
Correct Answer: A
A
Explanation:
This is because the vrf-target configuration is used in MPLS VPNs to control the import and export of routes between different VPN routing and forwarding (VRF) instances. If both CE-1 and CE-2 have routing instances configured with matching vrf-target statements, this will allow them to share routes as the routes will be tagged with the same extended community value, which allows for the correct import and export of the routes into each VRF on the PE routers.
A
Explanation:
This is because the vrf-target configuration is used in MPLS VPNs to control the import and export of routes between different VPN routing and forwarding (VRF) instances. If both CE-1 and CE-2 have routing instances configured with matching vrf-target statements, this will allow them to share routes as the routes will be tagged with the same extended community value, which allows for the correct import and export of the routes into each VRF on the PE routers.
Question #31
Exhibit
Referring to the exhibit, which statement is correct?
- A . The vrf-target configuration will allow routes to be shared between CE-1 and CE-2.
- B . The vrf-target configuration will stop routes from being shared between CE-1 and CE-2.
- C . The route-distinguisher configuration will allow overlapping routes to be shared between CE-1 and CE-2.
- D . The route-diatinguisher configuration will stop routes from being shared between CE-1 and CE-2.
Correct Answer: A
A
Explanation:
This is because the vrf-target configuration is used in MPLS VPNs to control the import and export of routes between different VPN routing and forwarding (VRF) instances. If both CE-1 and CE-2 have routing instances configured with matching vrf-target statements, this will allow them to share routes as the routes will be tagged with the same extended community value, which allows for the correct import and export of the routes into each VRF on the PE routers.
A
Explanation:
This is because the vrf-target configuration is used in MPLS VPNs to control the import and export of routes between different VPN routing and forwarding (VRF) instances. If both CE-1 and CE-2 have routing instances configured with matching vrf-target statements, this will allow them to share routes as the routes will be tagged with the same extended community value, which allows for the correct import and export of the routes into each VRF on the PE routers.
Question #36
Exhibit
Click the Exhibit button-Referring to the exhibit, which two statements are correct about BGP routes on R3 that are learned from the ISP-A neighbor? (Choose two.)
- A . By default, the next-hop value for these routes is not changed by ISP-A before being sent to R3.
- B . The BGP local-preference value that is used by ISP-A is not advertised to R3.
- C . All BGP attribute values must be removed before receiving the routes.
- D . The next-hop value for these routes is changed by ISP-A before being sent to R3.
Correct Answer: A,B
A,B
Explanation:
BGP is an exterior gateway protocol that uses path vector routing to exchange routing information among autonomous systems. BGP uses various attributes to select the best path to each destination and to propagate routing policies. Some of the common BGP attributes are AS path, next hop, local preference, MED, origin, weight, and community. BGP attributes can be classified into four categories: well-known mandatory, well-known discretionary, optional transitive, and optional nontransitive. Well-known mandatory attributes are attributes that must be present in every BGP update message and must be recognized by every BGP speaker. Well-known discretionary attributes are attributes that may or may not be present in a BGP update message but must be recognized by every BGP speaker. Optional transitive attributes are attributes that may or may not be present in a BGP update message and may or may not be recognized by a BGP speaker. If an optional transitive attribute is not recognized by a BGP speaker, it is passed along to the next BGP speaker. Optional nontransitive attributes are attributes that may or may not be present in a BGP update message and may or may not be recognized by a BGP speaker. If an optional nontransitive attribute is not recognized by a BGP speaker, it is not passed along to the next BGP speaker. In this question, we have four routers (R1, R2, R3, and R4) that are connected in a full mesh topology and running IBGP. R3 receives the 192.168.0.0/16 route from its EBGP neighbor and advertises it to R1 and R4 with different BGP attribute values. We are asked which statements are correct about the BGP routes on R3 that are learned from the ISP-A neighbor.
Based on the information given, we can infer that the correct statements are:
✑ By default, the next-hop value for these routes is not changed by ISP-A before being sent to R3. This is because the default behavior of EBGP is to preserve the next-hop attribute of the routes received from another EBGP neighbor. The next-hop attribute indicates the IP address of the router that should be used as the next hop to reach the destination network.
✑ The BGP local-preference value that is used by ISP-A is not advertised to R3. This is because the local-preference attribute is a well-known discretionary attribute that is used to influence the outbound traffic from an autonomous system. The local-preference attribute is only propagated within an autonomous system and is not advertised to external neighbors.
References:
https://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/13753-25.html:
https://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/13762-40.html:
https://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/13759-37.html
A,B
Explanation:
BGP is an exterior gateway protocol that uses path vector routing to exchange routing information among autonomous systems. BGP uses various attributes to select the best path to each destination and to propagate routing policies. Some of the common BGP attributes are AS path, next hop, local preference, MED, origin, weight, and community. BGP attributes can be classified into four categories: well-known mandatory, well-known discretionary, optional transitive, and optional nontransitive. Well-known mandatory attributes are attributes that must be present in every BGP update message and must be recognized by every BGP speaker. Well-known discretionary attributes are attributes that may or may not be present in a BGP update message but must be recognized by every BGP speaker. Optional transitive attributes are attributes that may or may not be present in a BGP update message and may or may not be recognized by a BGP speaker. If an optional transitive attribute is not recognized by a BGP speaker, it is passed along to the next BGP speaker. Optional nontransitive attributes are attributes that may or may not be present in a BGP update message and may or may not be recognized by a BGP speaker. If an optional nontransitive attribute is not recognized by a BGP speaker, it is not passed along to the next BGP speaker. In this question, we have four routers (R1, R2, R3, and R4) that are connected in a full mesh topology and running IBGP. R3 receives the 192.168.0.0/16 route from its EBGP neighbor and advertises it to R1 and R4 with different BGP attribute values. We are asked which statements are correct about the BGP routes on R3 that are learned from the ISP-A neighbor.
Based on the information given, we can infer that the correct statements are:
✑ By default, the next-hop value for these routes is not changed by ISP-A before being sent to R3. This is because the default behavior of EBGP is to preserve the next-hop attribute of the routes received from another EBGP neighbor. The next-hop attribute indicates the IP address of the router that should be used as the next hop to reach the destination network.
✑ The BGP local-preference value that is used by ISP-A is not advertised to R3. This is because the local-preference attribute is a well-known discretionary attribute that is used to influence the outbound traffic from an autonomous system. The local-preference attribute is only propagated within an autonomous system and is not advertised to external neighbors.
References:
https://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/13753-25.html:
https://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/13762-40.html:
https://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/13759-37.html
Question #36
Exhibit
Click the Exhibit button-Referring to the exhibit, which two statements are correct about BGP routes on R3 that are learned from the ISP-A neighbor? (Choose two.)
- A . By default, the next-hop value for these routes is not changed by ISP-A before being sent to R3.
- B . The BGP local-preference value that is used by ISP-A is not advertised to R3.
- C . All BGP attribute values must be removed before receiving the routes.
- D . The next-hop value for these routes is changed by ISP-A before being sent to R3.
Correct Answer: A,B
A,B
Explanation:
BGP is an exterior gateway protocol that uses path vector routing to exchange routing information among autonomous systems. BGP uses various attributes to select the best path to each destination and to propagate routing policies. Some of the common BGP attributes are AS path, next hop, local preference, MED, origin, weight, and community. BGP attributes can be classified into four categories: well-known mandatory, well-known discretionary, optional transitive, and optional nontransitive. Well-known mandatory attributes are attributes that must be present in every BGP update message and must be recognized by every BGP speaker. Well-known discretionary attributes are attributes that may or may not be present in a BGP update message but must be recognized by every BGP speaker. Optional transitive attributes are attributes that may or may not be present in a BGP update message and may or may not be recognized by a BGP speaker. If an optional transitive attribute is not recognized by a BGP speaker, it is passed along to the next BGP speaker. Optional nontransitive attributes are attributes that may or may not be present in a BGP update message and may or may not be recognized by a BGP speaker. If an optional nontransitive attribute is not recognized by a BGP speaker, it is not passed along to the next BGP speaker. In this question, we have four routers (R1, R2, R3, and R4) that are connected in a full mesh topology and running IBGP. R3 receives the 192.168.0.0/16 route from its EBGP neighbor and advertises it to R1 and R4 with different BGP attribute values. We are asked which statements are correct about the BGP routes on R3 that are learned from the ISP-A neighbor.
Based on the information given, we can infer that the correct statements are:
✑ By default, the next-hop value for these routes is not changed by ISP-A before being sent to R3. This is because the default behavior of EBGP is to preserve the next-hop attribute of the routes received from another EBGP neighbor. The next-hop attribute indicates the IP address of the router that should be used as the next hop to reach the destination network.
✑ The BGP local-preference value that is used by ISP-A is not advertised to R3. This is because the local-preference attribute is a well-known discretionary attribute that is used to influence the outbound traffic from an autonomous system. The local-preference attribute is only propagated within an autonomous system and is not advertised to external neighbors.
References:
https://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/13753-25.html:
https://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/13762-40.html:
https://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/13759-37.html
A,B
Explanation:
BGP is an exterior gateway protocol that uses path vector routing to exchange routing information among autonomous systems. BGP uses various attributes to select the best path to each destination and to propagate routing policies. Some of the common BGP attributes are AS path, next hop, local preference, MED, origin, weight, and community. BGP attributes can be classified into four categories: well-known mandatory, well-known discretionary, optional transitive, and optional nontransitive. Well-known mandatory attributes are attributes that must be present in every BGP update message and must be recognized by every BGP speaker. Well-known discretionary attributes are attributes that may or may not be present in a BGP update message but must be recognized by every BGP speaker. Optional transitive attributes are attributes that may or may not be present in a BGP update message and may or may not be recognized by a BGP speaker. If an optional transitive attribute is not recognized by a BGP speaker, it is passed along to the next BGP speaker. Optional nontransitive attributes are attributes that may or may not be present in a BGP update message and may or may not be recognized by a BGP speaker. If an optional nontransitive attribute is not recognized by a BGP speaker, it is not passed along to the next BGP speaker. In this question, we have four routers (R1, R2, R3, and R4) that are connected in a full mesh topology and running IBGP. R3 receives the 192.168.0.0/16 route from its EBGP neighbor and advertises it to R1 and R4 with different BGP attribute values. We are asked which statements are correct about the BGP routes on R3 that are learned from the ISP-A neighbor.
Based on the information given, we can infer that the correct statements are:
✑ By default, the next-hop value for these routes is not changed by ISP-A before being sent to R3. This is because the default behavior of EBGP is to preserve the next-hop attribute of the routes received from another EBGP neighbor. The next-hop attribute indicates the IP address of the router that should be used as the next hop to reach the destination network.
✑ The BGP local-preference value that is used by ISP-A is not advertised to R3. This is because the local-preference attribute is a well-known discretionary attribute that is used to influence the outbound traffic from an autonomous system. The local-preference attribute is only propagated within an autonomous system and is not advertised to external neighbors.
References:
https://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/13753-25.html:
https://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/13762-40.html:
https://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/13759-37.html
Question #38
Exhibit.
Referring to the exhibit, which path would traffic passing through R1 take to get to R4?
- A . R1 -> R3 -> R4
- B . R1 -> R2 -> R3 -> R4
- C . R1 -> R2 -> R4
- D . R1 -> R4
Correct Answer: C
C
Explanation:
The OSPF cost is carried in the LSAs that are exchanged within an OSPF area. When a router calculates the cost to a destination it uses the cost of the exit interface of each router in the path to the destination.
C
Explanation:
The OSPF cost is carried in the LSAs that are exchanged within an OSPF area. When a router calculates the cost to a destination it uses the cost of the exit interface of each router in the path to the destination.
Question #39
Exhibit
Which two statements are true about the OSPF adjacency displayed in the exhibit? (Choose two.)
- A . There is a mismatch in the hello interval parameter between routers R1 and R2
- B . There is a mismatch in the dead interval parameter between routers R1 and R2.
- C . There is a mismatch in the OSPF hold timer parameter between routers R1 and R2.
- D . There is a mismatch in the poll interval parameter between routers R1 and R2.
Correct Answer: A,B
A,B
Explanation:
The hello interval is the time interval between two consecutive hello packets sent by an OSPF router on an interface. The dead interval is the time interval after which a neighbor is declared down if no hello packets are received from it. These parameters must match between two OSPF routers for them to form an adjacency. In the exhibit, router R1 has a hello interval of 10 seconds and a dead interval of 40 seconds, while router R2 has a hello interval of 30 seconds and a dead interval of 120 seconds. This causes a mismatch and prevents them from becoming neighbors23.
A,B
Explanation:
The hello interval is the time interval between two consecutive hello packets sent by an OSPF router on an interface. The dead interval is the time interval after which a neighbor is declared down if no hello packets are received from it. These parameters must match between two OSPF routers for them to form an adjacency. In the exhibit, router R1 has a hello interval of 10 seconds and a dead interval of 40 seconds, while router R2 has a hello interval of 30 seconds and a dead interval of 120 seconds. This causes a mismatch and prevents them from becoming neighbors23.
Question #39
Exhibit
Which two statements are true about the OSPF adjacency displayed in the exhibit? (Choose two.)
- A . There is a mismatch in the hello interval parameter between routers R1 and R2
- B . There is a mismatch in the dead interval parameter between routers R1 and R2.
- C . There is a mismatch in the OSPF hold timer parameter between routers R1 and R2.
- D . There is a mismatch in the poll interval parameter between routers R1 and R2.
Correct Answer: A,B
A,B
Explanation:
The hello interval is the time interval between two consecutive hello packets sent by an OSPF router on an interface. The dead interval is the time interval after which a neighbor is declared down if no hello packets are received from it. These parameters must match between two OSPF routers for them to form an adjacency. In the exhibit, router R1 has a hello interval of 10 seconds and a dead interval of 40 seconds, while router R2 has a hello interval of 30 seconds and a dead interval of 120 seconds. This causes a mismatch and prevents them from becoming neighbors23.
A,B
Explanation:
The hello interval is the time interval between two consecutive hello packets sent by an OSPF router on an interface. The dead interval is the time interval after which a neighbor is declared down if no hello packets are received from it. These parameters must match between two OSPF routers for them to form an adjacency. In the exhibit, router R1 has a hello interval of 10 seconds and a dead interval of 40 seconds, while router R2 has a hello interval of 30 seconds and a dead interval of 120 seconds. This causes a mismatch and prevents them from becoming neighbors23.