HAT-680 · Question #65
A storage administrator is planning to issue multiple Hitachi Device Manager CLI commands to the same storage system. What is the name of the file which can be used to prevent repetitive typing of…
The correct answer is C. HiCommandCLI.properties. HiCommandCLI.properties is the correct answer because Hitachi's Device Manager CLI tool was originally branded as "HiCommand CLI," and the properties file retains that legacy name. This file stores default parameters (such as server host, port, username, and password)…
Question
A storage administrator is planning to issue multiple Hitachi Device Manager CLI commands to the same storage system. What is the name of the file which can be used to prevent repetitive typing of CLI command parameters?
Options
- ADeviceManager.properties
- BDeviceManagerCLI.properties
- CHiCommandCLI.properties
- DHiCommandCLI.parameter
How the community answered
(27 responses)- B4% (1)
- C93% (25)
- D4% (1)
Explanation
HiCommandCLI.properties is the correct answer because Hitachi's Device Manager CLI tool was originally branded as "HiCommand CLI," and the properties file retains that legacy name. This file stores default parameters (such as server host, port, username, and password), eliminating the need to type them repeatedly with each command.
Why the distractors are wrong:
- A (DeviceManager.properties) - This file doesn't exist in the HiCommand/Device Manager CLI toolset; the name omits the "CLI" portion entirely.
- B (DeviceManagerCLI.properties) - Plausible-sounding but incorrect; it uses the current product branding ("Device Manager") rather than the legacy CLI name.
- D (HiCommandCLI.parameter) - The file name is right but the extension is wrong; standard Java-based tools like this use
.properties, not.parameter.
Memory tip: The key is the legacy name mismatch - even though the product is now called "Hitachi Device Manager," the CLI properties file kept the old HiCommand branding. If you remember "the CLI was born as HiCommand," option C becomes the obvious pick.
Topics
Community Discussion
No community discussion yet for this question.