A technician at a rural fiber cooperative is unsure what keywords can legally follow show interfaces ge-0/0/0 on an aggregation switch and types a question mark at that point in the command line. What should Junos do in response?
Select an answer to reveal the explanation.
Short Explanation
The question mark is your built-in cheat sheet: type it anywhere in a command and Junos shows you exactly what's allowed to come next. It's context-sensitive too, so the list changes depending on where in the command you ask.
Full Explanation
Junos CLI help is context-sensitive, meaning a question mark entered at any point in a partially typed command causes the CLI to display the set of keywords, options, or variable types that are syntactically valid at that exact position, without requiring the command to be finished or submitted. Claiming the command executes as-is misreads the purpose of the character entirely; a question mark is a help request, not a terminator like the Enter key, and Junos does not treat it as one. Opening an external browser is incorrect because context-sensitive help is served entirely from within the CLI session using the device's own command tree, with no dependency on a network connection to a documentation site. Silently ignoring the character is also wrong, since the whole design intent of the feature is immediate, visible feedback rather than no response at all. A practical habit worth building on unfamiliar commands is asking for help at each token rather than guessing and pressing Enter, since a malformed operational command is harmless to retype, but the same instinct in configuration mode prevents staging a statement that does not do what was intended.