C_CPI Integration Suite Development Practice Question
An integration developer is building a flow that receives an XML order and must transform it to JSON for a downstream REST API. The XML contains an attribute on the root element that must appear as a JSON property named 'orderId'. The developer uses the XML-to-JSON converter but the attribute is missing from the output. What is the most appropriate action?
⚠ Common exam trap
The trap here is assuming the converter always includes attributes, when by default it drops them unless attribute conversion is explicitly turned on.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Enable the 'Convert Attributes' option in the XML-to-JSON converter so XML attributes are emitted as JSON properties.
The XML-to-JSON converter omits attributes unless attribute conversion is explicitly enabled. Enabling the convert attributes option causes each attribute to be emitted as a JSON property, which places the root attribute into the output as 'orderId'. Remapping the attribute into an element, using the wrong converter direction, or adjusting namespace handling do not address the underlying configuration that controls attribute emission.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Enable the 'Convert Attributes' option in the XML-to-JSON converter so XML attributes are emitted as JSON properties.
Why this is correct
By default the XML-to-JSON converter ignores attributes unless attribute conversion is enabled. Turning on the convert attributes option emits each attribute as a JSON property, so the root attribute appears as 'orderId'. This is the direct configuration change that addresses the missing attribute without altering the source XML or adding mapping logic.
- ✗
Set the converter's namespace handling to 'Ignore Namespaces' so attributes are treated as elements.
Why it's wrong here
Namespace handling controls how qualified names are rendered, not whether attributes are converted. Ignoring namespaces affects element and attribute prefixes but does not promote attributes to properties. The missing attribute is due to attribute conversion being disabled, so this setting does not resolve the issue.
- ✗
Add a Message Mapping step before the converter to move the attribute into a child element.
Why it's wrong here
Moving the attribute into a child element changes the XML structure and still requires the converter to handle the resulting element. It adds unnecessary mapping complexity when a single converter option suffices. The converter's attribute handling is the intended control point, so this workaround is not the most appropriate action.
- ✗
Replace the XML-to-JSON converter with a JSON-to-XML converter and reverse the flow direction.
Why it's wrong here
A JSON-to-XML converter performs the opposite transformation and cannot convert the incoming XML to JSON. Using it would require an additional reversal step and still would not address attribute handling. This option misidentifies the required converter and does not solve the missing attribute problem.
About these practice questions
Courseiva writes every C_CPI question from scratch — 218 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official SAP exam blueprint
This C_CPI practice question is part of Courseiva's free SAP certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the C_CPI exam.