Fortinet
NSE8_812 · Question #17
Refer to the exhibit. A customer has deployed a FortiGate 200F high-availability (HA) cluster that contains a TPM chip. The exhibit shows output from the FortiGate CLI session where the…
The correct answer is B. Configuration for TPM is not synchronized between FortiGate HA cluster members. E. The administrator needs to manually enter the hex private data encryption key in FortiManager. See the full explanation below for the reasoning.
Question
Refer to the exhibit. A customer has deployed a FortiGate 200F high-availability (HA) cluster that contains a TPM chip. The exhibit shows output from the FortiGate CLI session where the administrator enabled TPM. Following these actions, the administrator immediately notices that both FortiGate high availability (HA) status and FortiManager status for the FortiGate are negatively impacted. What are the two reasons for this behavior? (Choose two.)
Options
- AThe private-data-encryption key entered on the primary did not match the value that the TPM expected.
- BConfiguration for TPM is not synchronized between FortiGate HA cluster members.
- CThe FortiGate has not finished the auto-update process to synchronize the new configuration to FortiManager yet.
- DTPM functionality is not yet compatible with FortiGate HA.
- EThe administrator needs to manually enter the hex private data encryption key in FortiManager.
How the community answered
(37 responses)- A8% (3)
- B70% (26)
- C5% (2)
- D16% (6)
Community Discussion
No community discussion yet for this question.