000-349 · Question #61
Which is the true statement about command line qualifiers? They must begin with:
The correct answer is A. a dash (-) and are case insensitive. Command line qualifiers use a dash (-) as their required prefix character and are treated as case insensitive, meaning uppercase and lowercase forms are interchangeable.
Question
Which is the true statement about command line qualifiers? They must begin with:
Options
- Aa dash (-) and are case insensitive.
- Ba dash (-) and are case sensitive
- Can ampersand (&) and are case insensitive.
- Dan ampersand (&) and are case sensitive.
How the community answered
(30 responses)- A77% (23)
- B13% (4)
- C7% (2)
- D3% (1)
Why each option
Command line qualifiers use a dash (-) as their required prefix character and are treated as case insensitive, meaning uppercase and lowercase forms are interchangeable.
Command line qualifiers are defined to begin with a dash (-) as the standard delimiter that separates them from positional arguments, and they are case insensitive so that '-Q' and '-q' are treated as identical by the parser.
While qualifiers do begin with a dash (-), the case sensitive claim is incorrect - qualifiers are case insensitive, making this choice only half correct.
An ampersand (&) is not the designated prefix for command line qualifiers; it is a shell operator used for background execution or logical AND operations.
An ampersand (&) is not used to introduce command line qualifiers, and qualifiers are case insensitive rather than case sensitive, making both parts of this answer incorrect.
Concept tested: Command line qualifier prefix and case sensitivity rules
Topics
Community Discussion
No community discussion yet for this question.