During initial configuration an administrator must manage a FortiGate internal interface using only encrypted protocols, so that both the web GUI and the command-line interface are reachable while no credentials ever cross the wire in clear text. Which two protocols should be added to the interface allowaccess list to meet this requirement? Select TWO.
- AHTTP, so the administrator can reach the web-based GUI from a standard browser without certificate prompts.
- BHTTPS, so the administrator can reach the web-based GUI over a TLS-encrypted management session. Correct
- CTelnet, so the administrator can open a remote command-line session to the FortiGate over the network.
- DSSH, so the administrator can open a remote command-line session to the FortiGate over an encrypted channel. Correct
- EPING, so the administrator can confirm reachability to the interface before logging in to manage it.
Why A is wrong: HTTP does reach the GUI, but it carries the management session and credentials in clear text, which violates the encrypted-only requirement.
Why B is correct: HTTPS provides GUI access over TLS, so credentials and session data are encrypted in transit as required.
Why C is wrong: Telnet reaches the CLI but transmits the session, including the password, as clear text, so it fails the encryption requirement.
Why D is correct: SSH provides CLI access over an encrypted channel, meeting the requirement for command-line management without clear-text credentials.
Why E is wrong: PING only permits ICMP echo for reachability testing and provides no management plane, so it neither offers GUI nor CLI access.