C_CPI Integration Suite Development Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Use a Content Modifier step to set a header with the filter condition, then reference that header in the mapping.

  Why it's wrong here

  A Content Modifier step manipulates message headers or properties at the exchange level, not the internal structure of a repeating node during mapping. Headers are not evaluated as node filters inside the graphical mapping editor. This approach cannot selectively map only active items; it would require additional scripting or a different mapping construct to achieve the filtering.

• ✗

  Apply a Filter step in the integration flow before the Message Mapping step to remove inactive items.

  Why it's wrong here

  A Filter step in the integration flow operates on the entire message exchange and routes or discards whole messages based on XPath conditions; it cannot selectively remove individual repeating node instances inside a payload. Using it here would either pass or drop the whole message, not filter individual <Items> entries, so it does not satisfy the requirement to filter within the mapping.

• ✗

  Use a standard user-defined function in the Message Mapping that returns a boolean and apply it as a condition on the target repeating node.

  Why it's wrong here

  Standard user-defined functions in the graphical message mapping editor return values, not boolean filters for repeating nodes. They cannot be attached as a condition to a target repeating node. While you can write logic inside a function, the mapping editor does not support using a UDF as a node filter; this would require a different mechanism such as a Filter node inside the mapping.

• ✓

  Use the Filter node in the Message Mapping editor on the source repeating node and define an XPath condition such as Status = 'ACTIVE'.

  Why this is correct

  The Filter node available in the graphical Message Mapping editor allows you to apply a condition directly to a repeating source node. You can specify an XPath expression like Status = 'ACTIVE' so that only matching occurrences are mapped to the target. This filters within the mapping itself, leaving the original source message unchanged and meeting the scenario requirement precisely.