When is a GET workflow action needed?
When is a GET workflow action needed?
A GET workflow action is needed to retrieve information from an external resource. The GET method is specifically designed for retrieving data. It does not modify any resources on the server, making it suitable for retrieving information without making any changes. This contrasts with the POST method, which is primarily used to send data to a server to create or update a resource.
See Page 218 PDF: retrieve information from an external resource
B. To retrieve information from an external resource.
Why do the revealed answers have so many mistakes? It's clearly B.
Because the people answering them don't know what they are doing, they just get them online from someone else
Page 218 PDF: retrieve information from an external resource
See Page 218 PDF: retrieve information from an external resource
B -> pg 218 -> retrieve info from external source
I see the confusion. A GET request does SEND information to the external resource in order to perform a retrieve action.
It's B, A is POST not GET
It's clearly B. when you send information to external resource, use POST<.
B for Sure
Its B- and is correct
How are these simple answers so wrong all the time!?
B is answer
Definitely B.
B it gets ip info or do google search
when you post, same thing as you send answer is A.
https://docs.splunk.com/Documentation/Splunk/8.1.1/Knowledge/SetupaGETworkflowaction
https://docs.splunk.com/Documentation/Splunk/8.1.1/Knowledge/SetupaGETworkflowaction GET link workflow actions drop one or more values into an HTML link. Clicking that link performs an HTTP GET request in a browser, allowing you to pass information to an external web resource, such as a search engine or IP lookup service. -->A
B, For A you can use POST too