C_CPI Integration Suite Development Practice Question
An integration developer needs to process a large payload of incoming JSON data from a partner system within SAP Cloud Integration. The pipeline must extract specific nodes dynamically while minimizing memory consumption during processing. Which step type is best suited to achieve this requirement efficiently?
⚠ Common exam trap
Candidates often try to parse large JSON files using Groovy or JavaScript, which consumes massive amounts of heap memory. They fail to realize that converting to XML allows for efficient stream-based processing.
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
✓
JSON to XML Converter step followed by an XML Modifier or XSLT mapping step.
The JSON to XML Converter step transforms incoming JSON payloads into standard XML format, enabling downstream integration flow steps like XML Modifier or XSLT to execute resource-efficient XPath evaluations. This approach leverages streaming capabilities in SAP Cloud Integration to handle large datasets effectively without triggering out-of-memory exceptions.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Write Variables step to persist individual JSON attributes into global variables.
Why it's wrong here
Global variables are stored in the runtime tenant memory and are strictly designed to persist small control values, not large chunks of payload data. Utilizing them for bulk JSON processing will severely degrade tenant performance and exhaust available heap space.
- ✓
JSON to XML Converter step followed by an XML Modifier or XSLT mapping step.
Why this is correct
Converting JSON to XML then applying XML Modifier or XSLT mapping enables streaming node extraction without loading the entire payload into memory, satisfying the low-memory constraint for large partner JSON payloads processed within SAP Cloud Integration.
- ✗
Content Modifier step configured with local parameters referencing JSON paths.
Why it's wrong here
Content Modifier local parameters evaluate JSON paths against the message body but cannot stream or split it, so the whole payload is still parsed in memory. It is tempting as a declarative, no-code extraction method, and would be correct for small payloads needing header or property enrichment.
- ✗
Groovy script step loading the complete payload into a custom Java HashMap object.
Why it's wrong here
Loading the entire payload into a HashMap holds all JSON in memory at once, defeating the streaming requirement. Groovy scripting is tempting because it offers full control over dynamic node extraction, and would be correct where payloads are small and complex transformations exceed standard mapping capabilities.
About these practice questions
One of 218 original C_CPI practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.