An administrator manages several FortiGate units that all ship with the same default hostname, making it hard to tell devices apart in monitoring tools and on the CLI prompt. During initial configuration, which change gives each device a distinct identifier shown at the CLI prompt and in the GUI dashboard?
- ASet a unique system hostname on each FortiGate under the global system settings. Correct
- BSet a unique local-in alias on the management interface of each FortiGate.
- CSet a unique administrator profile name on each FortiGate so logins identify the device.
- DSet a unique SSL certificate common name on each FortiGate to label the device.
Why A is correct: The system hostname is the device name displayed in the CLI prompt and the GUI dashboard, so assigning a unique hostname to each unit directly distinguishes them as the scenario requires.
Why B is wrong: Interface aliases are descriptive labels for individual ports and appear beside those interfaces, but they do not change the device-wide name shown at the prompt or dashboard, so they do not solve the identification problem.
Why C is wrong: Profile names organise access permissions and are easy to confuse with device naming, but they describe privilege sets rather than the unit itself, so renaming a profile does not alter how the device identifies itself.
Why D is wrong: A certificate common name appears during secure session negotiation and can carry a device name, but it is not what the CLI prompt or dashboard displays, so changing it does not meet the stated need.