Select Two (Multi-Select) Questions

Protocol type

Why wrong: Protocol type is factored into preference.

Next hop address

Why wrong: Next hop is not used for selection.

AS path length

Why wrong: AS path is used in BGP but not in general route selection.

The default confirmation timeout is 5 minutes.

Why wrong: Incorrect: The default timeout is 10 minutes.

It requires a reboot to revert to the previous configuration.

Why wrong: Incorrect: No reboot is required; rollback is immediate.

It stages the configuration in the candidate configuration but does not apply it until confirmed.

Why wrong: Incorrect: The configuration is applied immediately upon commit.

The 'deactivate' command permanently removes a configuration statement from the candidate.

Why wrong: 'deactivate' disables the statement but keeps it in the candidate; it can be reactivated.

The 'set' command in configuration mode directly modifies the active configuration.

Why wrong: 'set' modifies the candidate configuration, not the active one.

In operational mode, the 'show' command displays the candidate configuration.

Why wrong: Operational mode 'show configuration' displays the active configuration, not candidate.

Command options are enclosed in curly braces { }.

Why wrong: Curly braces are for configuration display, not CLI options.

Commands must be entered in full; abbreviation is not allowed.

Why wrong: Commands can be abbreviated to a unique prefix.

You can commit configuration changes directly.

Why wrong: Commit is done in configuration mode, not operational mode.

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.

It captures packets from the Routing Engine only.

Why wrong: Wrong: It captures packets on the forwarding plane, not just the RE.

It requires a reboot to start capturing packets.

Why wrong: Wrong: No reboot is needed; the command runs immediately.

It reads packets from a previously saved pcap file.

Why wrong: Wrong: 'monitor traffic' captures live traffic; to read a file, use 'monitor traffic file <filename>'.

Static routes have a default preference value of 10.

Why wrong: The default preference for static routes is 5, not 10.

Static routes require a routing protocol to be activated.

Why wrong: Static routes are configured directly and do not need a routing protocol.

Static routes are automatically updated if the network topology changes.

Why wrong: Static routes are manually configured and do not dynamically update.

Each change is applied incrementally to the active configuration.

Why wrong: Commits are atomic; all changes are applied together.

The candidate configuration is stored in a separate file from the active configuration.

Why wrong: Both are stored in the same database; the candidate is a copy that becomes active upon commit.

After a commit, the candidate configuration is automatically discarded.

Why wrong: After commit, the candidate becomes the active configuration; it is not discarded.

Static routes always have a metric of 1.

Why wrong: Static routes do not have a metric by default; metric is used by dynamic protocols.

Static routes are automatically redistributed into OSPF.

Why wrong: Redistribution requires explicit policy configuration.

The default preference for static routes is 170.

Why wrong: 170 is the default preference for OSPF external routes, not static routes.

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.

show configuration

Why wrong: Used to view configuration, not a diagnostic command.

request system reboot

Why wrong: System control command, not diagnostic.

The 'edit' command is used in operational mode to navigate the hierarchy.

Why wrong: 'edit' is used in configuration mode.

The 'set' command is used in operational mode to set parameters.

Why wrong: 'set' is used in configuration mode.

The 'rollback 0' command discards the candidate configuration.

Why wrong: 'rollback 0' reverts to active config.

commit check

Why wrong: Does not exit configuration mode.

quit

Why wrong: Not a standard command.

The 'routing-options' hierarchy is used to configure interface IP addresses.

Why wrong: Interface IPs are under 'interfaces'.

Firewall filters are configured under 'policy-options'.

Why wrong: Firewall filters are under 'firewall'.

The 'protocols' hierarchy includes system-level settings like hostname.

Why wrong: System settings are under 'system'.

show interfaces terse

Why wrong: Shows interface status, not protocol.

show arp

Why wrong: Shows ARP cache, not routing protocol.

Configuration changes are activated immediately upon entering the 'set' command.

Why wrong: Changes are not activated until commit.

The 'commit check' command activates the candidate configuration if syntax is valid.

Why wrong: 'commit check' only checks syntax, does not activate.

The 'commit confirmed' command automatically commits changes permanently.

Why wrong: 'commit confirmed' requires confirmation within timeout; otherwise rollback.

It schedules the configuration to be applied at a later time.

Why wrong: Commit applies immediately; to schedule, use 'commit at'.

It discards the candidate configuration after saving.

Why wrong: The candidate becomes the active; it is not discarded.

It automatically reboots the device to apply the changes.

Why wrong: Commit does not reboot; changes are applied immediately.

show log

Why wrong: Shows log messages.

show configuration interfaces

Why wrong: Shows configuration, not operational state.

show route

Why wrong: Shows routing table.

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.

The preference of a static route cannot be changed.

Why wrong: Preference can be changed using the 'preference' statement.

Static routes automatically update if the next hop becomes unreachable.

Why wrong: Static routes do not update automatically.