Refer to the exhibit.

The FortiWeb ingress controller requires credentials so it can authenticate to and manage FortiWeb. The study guide defines creation of a cluster secret as an explicit installation step. After installing the Fortinet Helm chart, administrators use the kubectl create secret command to create the Kubernetes secret containing the required FortiWeb authentication information. The ingress configuration then references that secret through the fortiweb-login annotation rather than embedding the FortiWeb administrator password directly in the manifest. The value is therefore not obtained from the pod deployment manifest or from EKS cluster deployment output. Using a Kubernetes secret also follows the intended security model by separating sensitive authentication information from ordinary application configuration. Therefore, the administrators must create the required Kubernetes secret and reference it in the ingress manifest.