SAP Integration Developer (C_CPI) Practice Exam

Correct: B — Publish-subscribe through SAP Event Mesh. The publisher emits the event and consumers subscribe independently, which is exactly what “without knowing who consumes them” requires — and it is why adding a consumer later changes nothing at the source.

Why not the others: synchronous calls to each system (A) and point-to-point iFlows per consumer (D) both couple the publisher to its audience; and a nightly batch (C) abandons the event-driven premise entirely.

Correct: D — Exception-handling subprocesses. They are the named construct: a special subprocess triggered when an error occurs during processing. The precision matters, because the wrong options here are all plausible-sounding near-misses.

Why not the others: status code checks (A) test an expected outcome rather than catching the unexpected; and try-catch subprocesses (B) and exception handler elements (C) borrow terminology from general programming and other tools — neither is what Cloud Integration calls this.

Correct: A — A queue that retains the message until the consumer can process it. That durability is the difference between a topic broadcast and a guaranteed delivery, and it is why queues exist alongside topics in the messaging model.

Why not the others: scheduled re-publishing (B) duplicates events and shifts the problem to the publisher; claiming events are always fire-and-forget (C) is precisely the misconception this area corrects; and publisher retries (D) reintroduce the coupling events remove.

Correct: D — When no immediate answer is needed and decoupling is wanted. Synchronous calls remain right when the caller genuinely needs the result before continuing — a payment authorization, say. The judgement is the point, not a blanket preference.

Why not the others: events for everything (A) forces asynchrony onto transactions that need an answer now; a data-centre condition (B) is not what drives the choice; and calling events unreliable for critical data (C) ignores queues and delivery guarantees.

Correct: B — A content modifier. It is the step for setting headers, properties, and the message body where needed — the workhorse for carrying values through a flow without transforming the structure.

Why not the others: message mapping (A) transforms structure between formats, which the requirement excludes; an adapter (C) handles connectivity at the flow’s edges; and an aggregator (D) combines multiple messages into one.

Correct: C — A standard description of a service and its metadata, consumable by other tools. That machine-readable contract is what lets a developer portal render documentation and client tooling generate code without anyone writing either by hand.

Why not the others: authentication (A), rate limiting (B), and transport encryption (D) are all runtime policies applied by API Management — a specification describes the API rather than enforcing anything about it.

Correct: A — A rate-limiting or quota policy on the API proxy. The policy sits in front of the backend and enforces the contract before the call reaches it, which is the whole reason API Management exists as a layer.

Why not the others: an exception subprocess (B) reacts after something has gone wrong; a queue (C) buffers messaging rather than throttling API callers; and a header set by a content modifier (D) records a count without enforcing anything.

Correct: C — The SAP Integration Solution Advisory Methodology. It is the named method for defining integration styles, mapping use-case patterns, and setting technology guidelines — strategy rather than tooling.

Why not the others: the Discovery Center (A) offers missions and services to explore, and the Business Accelerator Hub (B) publishes APIs and pre-built content — both useful, neither a methodology; and per-project definition (D) is the fragmentation the method prevents.

Correct: B — The SAP Business Accelerator Hub. It is SAP’s catalog of APIs and pre-built integration packages, self-service and named directly in this exam’s overview area — the first place to check before building anything.

Why not the others: a consulting engagement (A) is not required for self-service content; claiming SAP publishes none (C) is false; and the advisory methodology (D) shapes strategy rather than shipping content.

Correct: C — An XPath expression. XPath addresses a node inside an XML payload, which is how a router or content modifier reads the value it needs to decide on — SAP names XPath and payload access directly in the flow-modeling objectives.

Why not the others: an OpenAPI specification (A) describes a service rather than reading a message; a topic subscription (B) is how a consumer receives events; and a quota policy (D) throttles API calls.