What type of task requires a parameter?

• A. A task that integrates with an external application and requires a year and month input.
• B. A simple data entry task.
• C. A notification task.
• D. A data import task.

Answer: (A)

The main idea is that a parameter is a value supplied to a task at run time to define its scope. When a task integrates with an external application, it often needs dynamic input to know exactly what to operate on, such as the year and month to pull or push data for. That runtime value drives the external call and ensures the task processes the correct period in coordination with FCCS.

For a simple data entry task, you provide values directly into fields as you go, not through a run-time parameter that alters the task’s behavior. A notification task is about sending messages and doesn’t require a time-based parameter to function. A data import task usually uses predefined sources or configurations and does not inherently need a year-month parameter for its execution. Therefore, the external integration task requiring a year and month input best fits a parameter-driven operation.