To import a server task from a remote ePO server, which file extension is required?

To import a server task from a remote ePO server, which file extension is required?

• A. Xml
• B. Json
• C. Csv
• D. Txt

Answer: (A)

The import mechanism for a server task relies on an XML-serialized representation of the task. XML is the format ePO uses to capture all the task details—its name, actions, schedule, deployment settings, and other metadata—in a structured way that the server can parse and recreate the task on the remote system. Because of this, the required file extension is XML. JSON, CSV, and TXT do not carry the full, structured configuration needed for a task import, so they’re not suitable for this purpose.

The import mechanism for a server task relies on an XML-serialized representation of the task. XML is the format ePO uses to capture all the task details—its name, actions, schedule, deployment settings, and other metadata—in a structured way that the server can parse and recreate the task on the remote system. Because of this, the required file extension is XML. JSON, CSV, and TXT do not carry the full, structured configuration needed for a task import, so they’re not suitable for this purpose.