When importing a server task from a remote ePO server, which file extension is used to transfer the task?

When importing a server task from a remote ePO server, which file extension is used to transfer the task?

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

Answer: (D)

Transferring a server task between ePO servers uses an XML representation because tasks include a hierarchical structure with schedule, actions, criteria, and related metadata that must be preserved and reconstructed on the remote server. XML is designed to encode complex, nested data and is the standard format used by ePO’s import/export mechanism, ensuring the task is transferred with all its details intact. Formats like JSON, CSV, or plain text don’t reliably capture the full task structure and metadata, so they aren’t used for this transfer.

Transferring a server task between ePO servers uses an XML representation because tasks include a hierarchical structure with schedule, actions, criteria, and related metadata that must be preserved and reconstructed on the remote server. XML is designed to encode complex, nested data and is the standard format used by ePO’s import/export mechanism, ensuring the task is transferred with all its details intact. Formats like JSON, CSV, or plain text don’t reliably capture the full task structure and metadata, so they aren’t used for this transfer.