Jobs in XSOAR run playbooks or scripts automatically at scheduled intervals. According to the Job Execution section of the Admin Guide, if a job encounters an error during playbook execution, its continued operation depends on whether“Continue on Error”is enabled. When this checkbox is selected, the job will not terminate due to an exception or integration failure. Instead, it logs the error and proceeds to the next scheduled execution as normal.

Queue handling settings (A) apply to indicators/job queues within feeds, not job failure behavior. RBAC changes (C) do not influence job execution continuity. Ensuring the last task closes the investigation (D) is unrelated and may even disrupt job workflows, since jobs often do not require incident-based models.

By contrast, enablingContinue on Erroris the documented mechanism that prevents scheduled jobs from halting due to transient or recurring errors. It ensures operational resilience, especially during integration outages or API rate limits.

Thus, optionBis the correct and fully documented answer.

The XSOAR Playbook Editor allows engineers to manipulate and transform context data dynamically. According to the XSOAR Admin and Playbook Development Guides,“Extend Context”is the dedicated mechanism that enables a task to save output values into new or existing context keys, including keys that correspond to incident fields. By defining a key under the “Extend Context” section, the playbook task can map specific outputs—such as JSON fields, strings, arrays, or nested objects—to a structured location within the incident context. These keys can then be used to populate incident fields through further playbook tasks, field mappings, or automated incident field updates.

Classification (option A) applies only during ingestion and cannot assign task outputs to incident fields. Inputs (option B) define what data a task receives, not how it is stored afterward. Mapping (option D) belongs to the ingestion pipeline and determines how event fields become incident fields during creation, not during playbook execution.

Therefore,Extend Contextis the correct feature that allows a task to associate its output with incident fields, making optionCthe correct answer based on documentation.