Select Two (Multi-Select) Questions

show interfaces terse

Why wrong: Shows only a brief summary of interface status, not detailed statistics.

show interfaces ge-0/0/0

Why wrong: Shows a single snapshot of interface statistics, not continuous real-time monitoring.

monitor security log

Why wrong: Used for monitoring security events, not interface statistics.

The /altroot directory is a backup root filesystem.

Why wrong: There is no standard /altroot directory; backup root is /altroot on some systems but not common Junos.

The /kernel directory contains the operating system kernel.

Why wrong: The kernel is loaded from /boot, not a /kernel directory.

The root directory (/) is a RAM disk.

Why wrong: The root filesystem is stored on flash, not a RAM disk.

show log dcd

Why wrong: Shows a specific log, not the main messages.

show log file

Why wrong: Not a standard command; usually specifies a file.

show system messages

Why wrong: Not a valid command.

The 'commit confirmed' command immediately discards changes if not confirmed.

Why wrong: It schedules a rollback; changes are not immediately discarded.

The 'commit' command always requires 'commit synchronize' when using dual Routing Engines.

Why wrong: 'commit synchronize' is used only when you want to synchronize configurations; 'commit' alone commits only on the local RE.

A static route with a next-hop of 127.0.0.1 is an unreachable route.

Why wrong: A static route with a next-hop of 127.0.0.1 creates a reject route that sends ICMP unreachable messages, not an unreachable route.

Static routes can have a preference value of 0.

Why wrong: Incorrect. Preference 0 is reserved for directly connected routes; static routes cannot use it.

show route protocol static

Why wrong: The command 'show route protocol static' filters the routing table to display only routes that were learned through the static routing protocol, as identified by the protocol field for each route entry. It omits other IPv4 unicast routes, such as direct, OSPF, or BGP routes, so it is too narrow to show the current routing table in its entirety. While useful for verifying static route installation, it does not fulfill the requirement of viewing all IPv4 unicast routes.

show forwarding-table

Why wrong: The command 'show forwarding-table' displays the forwarding table (FIB), not the routing table (RIB). The forwarding table is derived from the routing table and contains only the routes that are active and selected for actual packet forwarding, along with next-hop and interface information optimized for the forwarding engine. It does not show all routes present in the routing table, such as inactive or backup paths, so it is not a valid way to view the current routing table itself.

show route table inet6.0

Why wrong: The command 'show route table inet6.0' explicitly selects the IPv6 unicast routing table, which is used for IPv6 routes only. Since the question asks about the current routing table (implied to be IPv4 unicast, as inet.0 is the default), this command would display a different address-family's routes and would not show IPv4 information. To view IPv4 routes, one must specify inet.0 or use the default 'show route'.

System uptime

Why wrong: System uptime is a counter that tracks how long the routing engine has been running; it is a candidate metric in BGP route selection (preferring older routes) but does not, by itself, cause the routing table to be rebuilt or updated. Routing table changes are driven by topology events, protocol messages, or explicit administrative actions, not by the passage of time or system restarts.

Log file rotation

Why wrong: Log file rotation is a housekeeping task performed by the system to archive or truncate log files (e.g., /var/log/messages). It has no connection to the routing protocol daemon (rpd) or the routing table because it neither alters interface states, receives routing updates, nor modifies active configuration that affects network reachability.

Configuration commit

Why wrong: A configuration commit only activates the candidate configuration into the active configuration. Unless that configuration change directly alters an interface address, enables or disables a routing protocol, or adds/removes a static route, committing it does not itself modify the existing routing table; the table changes only when the underlying protocol or interface state actually changes.

The preference of a route cannot be changed.

Why wrong: In Junos, route preference is not fixed; it can be modified through routing policy by using the 'preference' statement to override the default value for matched routes. This mechanism allows network administrators to influence path selection, for example, making a BGP route preferred over an OSPF route. Therefore, the claim that preference cannot be changed is incorrect.

Static routes have a default preference of 10.

Why wrong: Static routes in Junos actually have a default preference of 5, making them more preferred than OSPF's 10 and BGP's 170, but less preferred than direct routes at 0. A preference of 10 is the default for OSPF internal routes, so attributing it to static routes is a common misconception. The default preference can be overridden with routing policy, but the out-of-box value for static is 5.

BGP routes have a default preference of 200.

Why wrong: BGP routes in Junos are assigned a default preference of 170, not 200, and this value is used for both internal and external BGP routes unless overridden by policy. A preference of 200 does not represent any standard Junos route type, so this statement is incorrect. Adjusting BGP's preference via routing policy is a common way to manipulate route selection.

Archival stores the candidate configuration.

Why wrong: Archival stores the committed (active) configuration, not the candidate.

Archival only saves the rescue configuration.

Why wrong: Archival saves the active configuration, not specifically the rescue config.

Archival automatically archives after every commit without any configuration.

Why wrong: Archival must be explicitly configured; it is not automatic.

configure static

Why wrong: Not a valid Junos configuration mode.

configure dynamic

Why wrong: Not a valid Junos configuration mode.

The rollback configurations are stored in /config/juniper.conf.0.gz, .1.gz, etc.

Why wrong: Rollback files are in /var/db/config/rollback-*.

The candidate configuration is stored in /config/.

Why wrong: Candidate is stored in /var/db/config.

The factory default configuration is stored in /etc/config/.

Why wrong: Factory default is in /etc/config/, but the rescue config is different.

show log messages | last 100

Why wrong: This command shows the last 100 lines of the log file, but it is a one-time snapshot, not real-time monitoring.

show system log messages

Why wrong: This is not a valid command. Real-time monitoring is done with 'monitor start'.

show configuration system syslog

Why wrong: This command shows the syslog configuration, not live log messages.

monitor start interactive-commands

Why wrong: The 'monitor start interactive-commands' command displays real-time output of user commands logged to the interactive-commands log file. It is another real-time monitoring option.

Type 'cli' at the operational mode prompt.

Why wrong: Incorrect: The 'cli' command is not a valid method to enter configuration mode; it is used to access the CLI from the shell.

Type 'expert' at the operational mode prompt.

Why wrong: Incorrect: The 'expert' command is not a valid method to enter configuration mode; it enables expert mode in the J-Web interface, not CLI configuration mode.

Metric

Why wrong: Metric is only compared within the same routing protocol.

Route origin

Why wrong: Route origin is a BGP attribute and is not used in cross-protocol comparison.

Local preference

Why wrong: Local preference is a BGP-specific attribute and is not used across all protocols.

The 'commit full' command activates the configuration without performing any validation.

Why wrong: Commit full forces a full check.

The 'commit' command can only be issued when no other users are in configuration mode.

Why wrong: Multiple users can commit in private mode.

show configuration | display inheritance

Why wrong: Shows inherited configuration values, not the full configuration.

show configuration | match

Why wrong: Filters configuration output, but the base command is still 'show configuration'.

show configuration | compare

Why wrong: Shows differences between candidate and active configuration, not the full configuration.

Configuration groups are stored in separate files that are imported using the 'file' statement.

Why wrong: Configuration groups are part of the configuration hierarchy, not separate files.

The 'replace' tag is used to reference a configuration group.

Why wrong: The 'replace' tag is used in other contexts, not to reference groups; 'apply-groups' is used.

Configuration groups are applied only at the [edit interfaces] hierarchy level.

Why wrong: Configuration groups can be applied at any hierarchy level, not just interfaces.

You can run multiple commit scripts during a single commit operation.

Why wrong: Only one commit script can be active at a time.

The rollback command reverts to the current active configuration.

Why wrong: Rollback reverts to a previously committed configuration, not the current one.