Fortinet
NSE8_812 · Question #15
An automation stitch was configured using an incoming webhook as the trigger named 'my_incoming_webhook'. The action is configured to execute the CLI script shown: config firewall address edit…
The correct answer is A. data: "{ \"params\": { \"hostname\": \"Bad_host_1\", \"ip\": \"1.1.1.1\" } }" url: http://192.168.226.129/api/v2/monitor/system/automation-stitch/webhook/my_incoming_webhook. See the full explanation below for the reasoning.
Question
An automation stitch was configured using an incoming webhook as the trigger named 'my_incoming_webhook'. The action is configured to execute the CLI script shown: config firewall address edit %%results.hostname%% set subnet %%results.ip.1%%/32 next end config firewall addrgrp edit Bad-Hosts append member %%results.hostname%% next end The base Curl command starts with: curl -k -X POST -H 'Authorization: Bearer ' --data '<data>' <url> Which Curl command will successfully work with the configured automation stitch?
Options
- Adata: "{ "params": { "hostname": "Bad_host_1", "ip": "1.1.1.1" } }" url: http://192.168.226.129/api/v2/monitor/system/automation-stitch/webhook/my_incoming_webhook
- Bdata: "{ "hostname": "Bad_host_1", "ip": "1.1.1.1" }" url: http://192.168.226.129/api/v2/monitor/system/automation-stitch/webhook/my_incoming_webhook
- Cdata: "{ "hostname": "Bad_host_1", "ip": "1.1.1.1" }" url: http://192.168.226.129/api/v2/cmd/system/automation-stitch/webhook/my_incoming_webhook
- Ddata: "{ "params": { "hostname": "Bad_host_1", "ip": "1.1.1.1" } }" url: http://192.168.226.129/api/v2/cmd/system/automation-stitch/webhook/my_incoming_webhook
How the community answered
(28 responses)- A79% (22)
- B4% (1)
- C4% (1)
- D14% (4)
Community Discussion
No community discussion yet for this question.