You are using Ansible to modify the configuration of several FortiGate VMs.

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

Based on the FortiOS 7.6 Automation Guide and the provided documentation for Ansible workflows, the following structure is required for managing multiple FortiGate nodes:

Inventory File (The Target List): The inventory is a single file that defines the list of managed nodes. It specifies critical information such as hostnames, connection details, and specifically the IP addresses of the target devices. According to the study guide, this inventory is a text file that lists all the systems you want to manage.

Playbook File (The Task List): You create and edit a separate file that acts as the playbook. This file is written in YAML format and contains the series of tasks that Ansible performs on the managed nodes to reach a desired state.

Minimum File Count: A basic Ansible workflow consists of exactly two files: one inventory file (text) and one playbook file (YAML). By listing the target IP address (e.g., 10.0.206.131) within the inventory text file, the administrator can manage the FortiGate device without needing individual files for every target.

Why other options are incorrect:

Option A & C: Creating a separate playbook or inventory file for each target is inefficient and contradicts the core Ansible workflow, which uses a single inventory to manage multiple hosts.

Option B: While the playbook is a .yaml file, the study guide specifically defines the inventory (where IP addresses are configured) as a text file in the context of the basic workflow.