SAP C_CPE_2409 - SAP Certified Associate - Backend Developer - SAP Cloud Application Programming Model

SAP BTP provides:

Integration (A): A full suite of integration services for apps, data, and processes.

Application Development (B): Tools and runtimes for building new extensions or applications.

Extensibility (C): Allows extending SAP S/4HANA Cloud, SuccessFactors, and on-premise systems side-by-side.

Incorrect option:

D – Build tightly coupled applications:

SAP BTP promotes loose coupling, modularity, and clean extension approaches.

In XSUAA security model:

Roles group multiple scopes.

Role collections group multiple roles, not scopes.

Scopes are the finest-grain authorization units.

Therefore, the entity that holds several scopes is the Role (B).

Incorrect options:

A: Role collections bundle roles, not scopes directly.

C: A scope is a single authorization unit.

D: User groups are not part of XSUAA authorization structures.

@cap-js/telemetry enhances CAP observability and automatically publishesruntimeanddatabasemetrics.

B – Memory Usage Metrics

Telemetry captures Node.js process metrics such as:

Heap usage

Resident Set Size (RSS)

Garbage collection metrics

Memory allocations and consumption patterns

These help diagnose memory leaks or heavy load conditions.

C – Database Pool Statistics

Telemetry gathers database-layer metrics such as:

Active/idle database connections

Pool usage and saturation

Connection acquisition time

Query execution statistics

These metrics are critical for diagnosing bottlenecks in SAP HANA Cloud or SQLite adapters.

Why the Others Are Incorrect:

A – Network latency and jitter:

Telemetry does not measure network latency at the protocol layer.

This requires external APM or monitoring tools.

D – CPU allocation / thread management:

CAP telemetry exposes basic CPU metrics only through Node.js process stats but does not provide deep OS-level CPU or thread-management metrics.

Pods in Kubernetes:

Are the smallest deployable unit (A).

Encapsulate one or more containers (C) that share network and storage namespaces.

Incorrect options:

B: Persistent storage is handled via volumes and claims, not pods.

D: Pods can wrap one or multiple containers; not limited to one.

cds add xsuaa adds authentication and authorization support to CAP applications. It updates:

package.json (C):Adds dependencies and configuration entries for XSUAA integration.

xs-security.json (D):Generates or updates the security descriptor defining scopes, role templates, attributes, etc.

Incorrect options:

A – .cdsrc.json:Not modified by this command.

B – xs-usertokens.json:Not used by CAP tooling.

When connecting from a CAP application to thesandboxof SAP API Business Hub (now SAP Business Accelerator Hub) for APIs such as theBusiness PartnerOData service, the learning content and examples describe that:

The sandbox environment is protected by anAPI keythat must be sent in a specific HTTP header (for example, APIKey or similar) with each request.

Tutorials for CAP/Cloud SDK and S/4HANA integration in a training context show configuration steps where developers obtain anAPI keyfrom the hub and configure it in a destination or in custom code for outbound calls.

This matches optionC – API key.

Why the other options are incorrect:

A – Client certificate:Client certificates are common for productive mutual TLS connections, not for the public sandbox.

B – Service principal:“Service principal” is an Azure-specific concept and not how the sandbox on SAP API Business Hub is accessed.

D – OAuth token:Many productive APIs use OAuth 2.0, but thesandboxin the official exercises is specifically accessed using an API key.

Comprehensive and Detailed Explanation

The SAP Cloud SDK enhances open-source frameworks for enterprise-grade side-by-side extensions.

B – Multi-tenant persistence

The SDK provides:

Multi-tenant database segregation

Tenant-specific configuration

Automatic resolution of tenant context

Support for SaaS extension scenarios

This feature is essential for SaaS applications built on SAP BTP.

C – Feature toggling

The SDK includes libraries that allow:

Dynamic enabling/disabling of features

Gradual rollout

Canary testing

Tenant-based feature control

This helps enterprise customers deploy new features safely.

Why the Others Are Incorrect:

A – Tightly coupled integration:

SAP strongly promotesloosely coupledarchitectures.

D – Code samples:

The SDK provides samples, but that's not an “enterprise adaptation feature.”

In CAP:

destinations.json (A):

Used during local development to define destinations mapped to external services. CAP automatically loads these destinations when running locally.

package.json (D):

Contains the requires section where CAP services declare dependencies on external services. This indicates how the destination should be consumed by CAP runtime (e.g., which kind of service is required and where to get credentials).

Incorrect options:

B – manifest.json: Not used in CAP backend runtime.

C – services.xml: Not part of CAP configuration.

SAP BTP Cloud Foundry runtime is amanaged PaaS platform.

B – Managed security and automatic updates

The platform handles:

Operating system patching

Buildpack updates

Security vulnerability patches

Scaling and monitoring infrastructure

Developers do not manage OS, VM, clusters, or security baselines.

C – High availability with load balancing

Cloud Foundry natively provides:

Multiple application instances

Route-based load balancing

Health checks

Automatic restart of unhealthy instances

This ensureshigh availabilityfor deployed apps.

Why the Others Are Incorrect:

A:Scaling isautomatic, not manual. Developers can set autoscaling rules.

D:Service mesh is not part of Cloud Foundry; it belongs to Kubernetes-based runtimes (e.g., Kyma).