SAP Updated C_CPI_2506 Exam Questions and Answers by ameerah

For an asynchronous integration architecture, the best design pattern is Event-Driven Architecture (EDA):

Events (notifications) are published by producers and consumed by interested partners asynchronously.

Enables decoupled, scalable, and resilient communication.

Other options:

Serverless design → A runtime execution model, not a messaging pattern.

Request-driven design → Synchronous, not asynchronous.

Hexagonal design → A software architecture pattern, not messaging-driven.

Thus, for exchanging asynchronous notifications between partners, the correct design is Event-driven design.

In a microservices architecture, applications are decomposed into multiple smaller services communicating via APIs. This results in:

Increased API traffic due to inter-service communication.

Higher need for governance: enforcing policies, security, throttling, and quotas.

Comprehensive monitoring required to trace calls across multiple distributed services to ensure performance, reliability, and compliance.

SAP Integration Suite’s API Management provides these capabilities:

Traffic management (quotas, rate limiting).

Security policies (OAuth, API keys).

End-to-end monitoring & analytics for distributed calls.

Thus, the correct answer highlights the need for more robust API management and monitoring in high-volume, microservices-driven landscapes.

In API Management (Integration Suite), when you configure an API provider of type Internet, the system checks connectivity by sending a request to the backend.

HTTP 200 → Success (OK). The endpoint is reachable and functioning.

401 (Unauthorized) → Authentication failure.

403 (Forbidden) → Authorization failure.

502 (Bad Gateway) → Network or proxy error.

Therefore, the successful response code indicating proper connection is 200.

For a synchronous call to a remote HTTP API in an integration flow:

The OData adapter (or HTTP adapter) is used to perform synchronous request-reply communication with REST-based services.

AMQP → Messaging protocol, not synchronous.

SFTP → File-based transfer, asynchronous.

Mail → For SMTP/IMAP, not synchronous API calls.

Thus, the correct adapter for a synchronous remote API call is OData (or HTTP adapter, depending on configuration).