Palo Alto Networks Certified Security Automation Engineer (PCSAE)PlaybooksHard
A security analyst is reviewing a playbook and notices that a particular script task, which queries a remote API, is configured with a 'Timeout' value of '0'. What is the practical implication of setting a task's 'Timeout' property to '0' in Cortex XSOAR?
- AThe task will execute immediately and complete without waiting.
- BThe task will run indefinitely, with no timeout enforced.
- CThe task will fail instantly upon execution attempt.
- DThe task will inherit the global playbook timeout setting.
Show answer & explanationAnswer & explanation
Correct answer: B. The task will run indefinitely, with no timeout enforced.
In Cortex XSOAR, setting a task's 'Timeout' property to '0' explicitly disables the timeout for that specific task. This means the task will continue to run until it naturally completes or encounters an error, without being forcibly terminated by a timeout.
Why the other options are wrong
- A. A timeout of '0' does not imply immediate execution or completion; it removes the time limit for execution.
- C. An instant failure would typically occur if there's an immediate error in the script or command, not as a direct result of a 'Timeout' of '0'.
- D. While some settings can be inherited, the 'Timeout: 0' setting is an explicit configuration that overrides any potential global or default timeout, effectively disabling it for that task.
Task Timeout: 0
Configuring a playbook task's 'Timeout' property with a value of '0' explicitly disables the timeout mechanism for that task, allowing it to run indefinitely.
- Disables timeout for the specific task.
- Task runs until completion or error.
- Can lead to stuck playbooks if not managed.
Memory trick: Zero timeout means 'go forever'!