When configuring a GRE tunnel interface on Junos, which two elements are mandatory for the tunnel to be operational?

Authentication key and checksum

Source and destination addresses

A network engineer is configuring a GRE tunnel between two routers. The tunnel is configured with a source of 192.168.1.1 and a destination of 192.168.2.1. The engineer commits the configuration, but the tunnel interface remains 'Down'. The engineer verifies that both addresses are reachable from each other. What is the most likely reason the tunnel is down?

The tunnel's destination address is not in the routing table.

The tunnel requires a GRE key to be configured on both ends.

The tunnel's source address is not a local interface address.

The tunnel interface has no IP address configured.

Which operational command displays the status and statistics of GRE tunnel interfaces on a Junos device?

show configuration interfaces gr-0/0/0

show interfaces gr-0/0/0 extensive

A network engineer is configuring a GRE tunnel between two routers. The engineer wants to ensure that the tunnel can carry both IPv4 and IPv6 traffic. What must be configured on the tunnel interface?

Both 'family inet' and 'family inet6' must be configured on the tunnel interface.

The tunnel must be configured with 'family inet6' only, as it is the newer protocol.

Only 'family inet' is needed, as IPv6 can be carried inside IPv4 GRE.

The tunnel interface does not need any family configuration, as it is a point-to-point link.

A service provider is setting up a GRE tunnel between two routers that are separated by a firewall. The firewall is configured to allow GRE protocol (IP protocol 47) between the two routers. The tunnel is configured correctly, but it does not come up. What is the most likely issue?

The firewall is also blocking ICMP, which is used by GRE keepalives.

The firewall is blocking UDP port 47.

The firewall is not configured to allow the tunnel's inner protocol.

The firewall is performing NAT on the GRE packets.

Juniper NetworksCertified Specialist, Service Provider Routing and Switching (JNCIS-SP)

Domain 9Objective 3

Configure, Monitor, or Troubleshoot GRE JN0-364 Practice Questions (Page 1)

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

14questions here

3free pages

3concepts

Questions 1–5

1foundation · medium
When configuring a GRE tunnel interface on Junos, which two elements are mandatory for the tunnel to be operational?
Select an answer first
2application · medium
A network engineer is configuring a GRE tunnel between two routers. The tunnel is configured with a source of 192.168.1.1 and a destination of 192.168.2.1. The engineer commits the configuration, but the tunnel interface remains 'Down'. The engineer verifies that both addresses are reachable from each other. What is the most likely reason the tunnel is down?
Select an answer first
3foundation · medium
Which operational command displays the status and statistics of GRE tunnel interfaces on a Junos device?
Select an answer first
4application · medium
A network engineer is configuring a GRE tunnel between two routers. The engineer wants to ensure that the tunnel can carry both IPv4 and IPv6 traffic. What must be configured on the tunnel interface?
Select an answer first
5application · medium
A service provider is setting up a GRE tunnel between two routers that are separated by a firewall. The firewall is configured to allow GRE protocol (IP protocol 47) between the two routers. The tunnel is configured correctly, but it does not come up. What is the most likely issue?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to JN0-364

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-364” is a trademark of its owner, used for identification only.