C_CPI Integration Suite Development Practice Question
An integration developer is configuring a JMS receiver adapter in SAP Cloud Integration. Messages must be consumed in the exact order they were produced, and the queue must survive a tenant restart without losing messages. Which JMS queue type and configuration should be used?
⚠ Common exam trap
The trap here is assuming that default JMS queues are always ordered or that retry logic can substitute for explicit ordering configuration.
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 a JMS queue configured with 'Ordered' processing and ensure the queue is persistent.
Ordered processing and persistence are distinct JMS queue attributes in SAP Cloud Integration. The ordered setting enforces FIFO consumption, while persistence ensures messages are not lost on restart. Selecting a queue with both attributes meets the scenario's dual requirements. Other options either ignore ordering or rely on mechanisms that do not provide sequence guarantees.
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 JMS queue with the default settings; ordering is not guaranteed but messages are persistent.
Why it's wrong here
Default JMS queue settings do not guarantee strict FIFO ordering because multiple consumer threads can process messages concurrently. While persistence is enabled by default, the lack of ordering makes this unsuitable for scenarios where sequence matters. The developer must explicitly configure the queue for ordered processing, not rely on defaults.
- ✗
Use a JMS queue with a large message threshold and enable retry on failure; ordering is maintained by the retry mechanism.
Why it's wrong here
Retry mechanisms handle transient failures but do not enforce message ordering. A large message threshold affects payload size handling, not sequence. This configuration may improve reliability but does not guarantee FIFO processing, so it fails the ordering requirement. The developer must select the ordered queue option specifically.
- ✗
Use a JMS topic with durable subscriptions; topics preserve order and persist messages across restarts.
Why it's wrong here
JMS topics implement publish-subscribe semantics where each subscriber receives a copy, not a single ordered stream. Durable subscriptions persist messages for offline subscribers, but they do not enforce global ordering across multiple consumers. The requirement is for a single ordered queue, not fan-out delivery, so a topic is the wrong messaging model here.
- ✓
Use a JMS queue configured with 'Ordered' processing and ensure the queue is persistent.
Why this is correct
Configuring the JMS queue for ordered processing ensures that messages are consumed in the exact sequence they were enqueued, which is critical when business logic depends on order. Persistence guarantees that messages survive a tenant restart. This combination directly satisfies both stated requirements without introducing unnecessary complexity.
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.