What options are available in ePO when creating a client task?

What options are available in ePO when creating a client task?

• A. The task runs on all endpoints
• B. The task can be configured with defined criteria
• C. The task requires a pre-created policy
• D. The task cannot be customized

Answer: (B)

When creating a client task in ePO, you define targeting criteria to decide exactly which endpoints should receive and run the task, and you can customize how it runs and what it does. This means the key capability is to configure the task with defined criteria so you can scope it to specific machines, groups, OS versions, installed software, or other conditions, rather than applying it to every endpoint by default. That targeting through defined criteria is what makes the task adaptable and useful in real-world environments. It also doesn’t require a pre-created policy—tasks and policies are separate concepts, and a task can be created and scheduled with its own package or action. The option stating the task can be configured with defined criteria best captures this flexibility.

When creating a client task in ePO, you define targeting criteria to decide exactly which endpoints should receive and run the task, and you can customize how it runs and what it does. This means the key capability is to configure the task with defined criteria so you can scope it to specific machines, groups, OS versions, installed software, or other conditions, rather than applying it to every endpoint by default.

That targeting through defined criteria is what makes the task adaptable and useful in real-world environments. It also doesn’t require a pre-created policy—tasks and policies are separate concepts, and a task can be created and scheduled with its own package or action. The option stating the task can be configured with defined criteria best captures this flexibility.