Question 560
At the Ashbourne hospital IT infrastructure group, an application expects S3 bucket access but its ONTAP SVM is configured only for NFS and SMB. What follow-up practice would reduce this risk over time?
Explanation
Correct Answer
The needed prevention is to review protocol enablement and endpoint configuration when onboarding object applications. It directly sustains the original change to configure a supported ONTAP S3 object store server on the intended SVM and reachable data endpoint. This result addresses the stated challenge at the Ashbourne hospital IT infrastructure group.
Incorrect Answers
The option would have the team audit bucket ownership and lifecycle settings during application rollout. For this situation, the preventive control should instead be to review protocol enablement and endpoint configuration when onboarding object applications. For the Ashbourne hospital IT infrastructure group, the direct corrective action is to configure a supported ONTAP S3 object store server on the intended SVM and reachable data endpoint.
“Review SMB domain trust and DNS health after directory upgrades” checks a different ongoing risk rather than the reported failure: at the Ashbourne hospital IT infrastructure group, an application expects S3 bucket access but its ONTAP SVM is configured only for NFS and SMB. The relevant mechanism is a file-serving SVM does not automatically provide an S3-compatible object API. The directly matched preventive control is “Review protocol enablement and endpoint configuration when onboarding object applications”.
That routine supports lun mapping and lun id, but the relevant ongoing risk requires the team to review protocol enablement and endpoint configuration when onboarding object applications. For the Ashbourne hospital IT infrastructure group, the direct corrective action is to configure a supported ONTAP S3 object store server on the intended SVM and reachable data endpoint.