Refer to the exhibit.

Comprehensive and Detailed Explanation From FortiOS 7.6, FortiWeb 7.4 Exact Extract study guide:

According to theFortiOS 7.6 AWS Administration Guideand thePublic Cloud Securitydocumentation regarding AWS CloudFormation templates:

YAML Format and Comments (Option D):The exhibit provided (image_dce708.png) displays an AWS CloudFormation template inYAML(YAML Ain't Markup Language) format. Unlike JSON, YAML natively supports inline and block comments using the#character. An administrator can simply add # followed by the instruction next to the InstanceType line, and the CloudFormation parser will ignore it during stack creation.

Infrastructure as Code (IaC) Best Practices:In a multinational deployment environment, using comments in YAML templates is a critical best practice for documentation. It allows the lead administrator to provide context for regional teams (e.g., "Change t2.large to a supported instance type in your region") directly within the code.

Why other options are incorrect:

Option A:The aws cloudformation update-stack command is used to apply changes to an existing stack. While you can provide a "Description" for the stack, it does not allow you to inject comments into the source template file itself.

Option B:The AWSTemplateFormatVersion "2010-09-09" is the only currently supported version for CloudFormation. Changing this would not impact comment functionality, as comment support is a property of the YAML file format, not the template version.

Option C:Converting the template toJSONwould be counterproductive because the standard JSON specificationdoes not support comments. If the template were in JSON, the administrator would actually need to convert ittoYAML to add comments.