In Junos OS, the ? command modifier is used to display all possible completions for a specific command. This helps users understand the available options and syntax for a command they are trying to use.

After increasing the MTU size of an interface and committing the configuration, the command to verify the applied MTU change is D, " show interfaces ge-0/0/0. " This command displays detailed information about the interface, including the current MTU size, making it the best choice for verifying the applied changes.

When an interface on a router is configured with an IPv4 address and is in an up state, two types of routes are automatically created in the routing table: a local route and a direct route, making B and D the correct answers. The local route represents the interface ' s IP address itself, indicating that the router can directly receive packets addressed to this IP. The direct route represents the subnet or network segment to which the interface is connected, indicating that the router can directly forward packets to destinations within this subnet.

In the given telnet command, " telnet 10.10.10.1 source 192.168.100.1, " the destination address of the telnet session is 10.10.10.1, and the source address of the session is specified as 192.168.100.1, making C and D the correct answers. This command instructs the telnet client to use the specified source IP address when establishing the connection to the destination.

Transit traffic that traverses the forwarding plane of a Layer 3 router includes both unicast and multicast traffic types. Unicast traffic is directed from a single source to a single destination, while multicast traffic is sent from one source to multiple destinations that are part of a multicast group. These types of traffic are efficiently routed through the network by leveraging the router ' s forwarding plane capabilities. Exception traffic, which requires special handling by the control plane, and broadcast traffic, which is typically limited to a single broadcast domain and not usually forwarded by Layer 3 routers, are not considered standard types of transit traffic for the forwarding plane of a router.

The Packet Forwarding Engine (PFE) in Juniper Networks devices is the heart of the data plane, handling the actual forwarding of packets based on pre-computed forwarding tables. It provides several critical services to manage and control traffic flow, including policing (to enforce bandwidth limits for certain traffic types), stateless firewall filtering (to permit or deny traffic based on predefined criteria), and Class of Service (CoS) (to prioritize traffic to ensure quality of service for critical applications). The PFE utilizes both Layer 2 (MAC addresses) and Layer 3 (IP addresses) forwarding tables to make intelligent forwarding decisions, ensuring that packets are efficiently routed toward their final destination.

The routing table and forwarding table play distinct roles in a Junos OS device. The correct answers are A and D. The routing table (A) is used by the Routing Engine (RE) to select the best route among all the learned routes, while the routing table (D) stores all routes and prefixes learned from all routing protocols. The forwarding table, in contrast, contains only the active routes chosen by the RE and is used by the Packet Forwarding Engine for actual packet forwarding.

In Junos OS, there are two main configuration databases:

Candidate configuration : a working copy of the configuration that holds any uncommitted changes. All configuration edits are made here.

Active configuration : the running configuration that the system currently uses.

When you issue a commit command, the candidate configuration is promoted to active, replacing the previous configuration. Until that happens, all changes remain in the candidate configuration and do not affect device operation.

From Junos Fundamentals Guide :

“The candidate configuration is a separate copy of the configuration database. All changes are made to the candidate configuration and do not take effect until they are committed.”

In Junos OS, the management daemon (mgd) is responsible for handling all the device management tasks, including processing CLI commands and handling commit operations. The mgd daemon interacts with the Junos OS configuration database and provides the necessary logic to ensure that configuration changes are syntactically correct and do not conflict with each other. When a user commits a configuration, mgd validates the changes, applies them to the running configuration, and ensures that the necessary daemons are notified of the changes to apply them accordingly.

In Junos OS, route preference (also known as administrative distance) is used to determine the preferred route among multiple routes to the same destination learned via different routing protocols. Direct and local routes, which represent directly connected networks and interfaces, typically share the same low preference value, indicating high trustworthiness because they are directly connected to the router. OSPF internal routes (routes within the same OSPF area) and OSPF AS external routes (routes that are external to the OSPF autonomous system but redistributed into OSPF) also share the same preference value, although this value is higher (indicating less trust) than for direct and local routes. This distinction helps the routing engine decide which routes to use when multiple paths are available.