C_CPI Integration Suite Development Practice Question
An integration developer is troubleshooting an integration flow that uses a Groovy script step. The script must read a message header named 'CustomerID' and write its value into the message body. The script currently throws a NullPointerException when the header is absent. Which approach correctly handles the missing header while preserving the script's intent?
⚠ Common exam trap
The trap here is assuming that a missing header returns an empty string rather than null, which leads to an unhandled NullPointerException.
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
✓
Use message.getHeaders().get('CustomerID') and check for null before assigning, defaulting to an empty string if absent
When a header may be absent, retrieving it with get('CustomerID') returns null. The script must explicitly check for null and provide a fallback value before using the result. Defaulting to an empty string avoids the NullPointerException and maintains the script's purpose of writing the header value to the body. Other approaches either call methods on null or use an invalid API, so they fail to handle the missing header safely.
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 message.getHeaders().get('CustomerID').toString() and assign the result to the body
Why it's wrong here
Calling toString() on a null value throws a NullPointerException immediately. This approach does not handle the missing header case; it actually guarantees the exception when the header is absent. The developer must check for null before calling any method on the retrieved value, so this does not resolve the issue.
- ✓
Use message.getHeaders().get('CustomerID') and check for null before assigning, defaulting to an empty string if absent
Why this is correct
Retrieving the header with get('CustomerID') returns null when the header is missing. Adding a null check and defaulting to an empty string prevents the NullPointerException while preserving the intent to write the header value to the body. This is the correct defensive programming approach in a Groovy script step within SAP Cloud Integration.
- ✗
Use message.getHeader('CustomerID') and assign the result to the body without further processing
Why it's wrong here
The Message interface in SAP Cloud Integration does not provide a getHeader method; headers are accessed through getHeaders(). Using a non-existent method would cause a compilation or runtime error. Even if a similar method existed, assigning without a null check would not handle the absent header case and could still result in a NullPointerException.
- ✗
Use message.getHeaders().get('CustomerID') and assign the result directly to the body without a null check
Why it's wrong here
Directly assigning the result of get('CustomerID') to the body does not handle the null case. If the header is absent, the value is null and any subsequent operation on it, or the body assignment itself in some contexts, can trigger a NullPointerException. The script must explicitly check for null or provide a default value to avoid the exception.
About these practice questions
This C_CPI question is part of Courseiva's 218-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.