Free Practice Questions for SAP C_CPE_2409 Exam

A Kubernetes Deployment provides:

Declarative updates to pods

Rolling updates and rollbacks

Zero-downtime deployments when configured with suitable strategies

Incorrect options:

A: Databases are external or stateful sets, not deployments.

B: Network policies are configured via dedicated objects.

C: Deployments manage ReplicaSets, not pods "directly."

To expose a data model in CAP:

You needdata model entities (D)defined in CDS.

You must create aservice definitioncontainingservice entities (A)that expose selected data model entities.

Associations and aspects are optional modeling features and do not by themselves expose a model.

AMulti-Target Application (MTA)on SAP BTP is described by anMTA deployment descriptor:

This descriptor is stored in the filemta.yaml.

It defines the MTA’smodules(for example, CAP service, approuter, UI module) andresources(for example, XSUAA instance, destination service, database service).

Tools such as theCloud MTA Build Tool (mbt)read mta.yaml to create an .mtar archive that is deployed to Cloud Foundry.

Thus, the correct answer isA – mta.yaml.

Why the others are incorrect:

B – mta.json:Not used as the standard descriptor format in SAP BTP MTA scenarios.

C – mtad.yaml:In some older XS Advanced contexts, mtad.yaml is the deployment descriptor, but in the SAP BTP Cloud Foundry + CAP context the standard is mta.yaml.

D – manifest.json:This is often used for SAPUI5 applications (UI metadata), not for MTAs. Cloud Foundry deployment manifests use manifest.yml, not manifest.json.

OData plays a central role in CAP service exposure:

CRUD operations using HTTP verbs (A):CAP services expose entities over OData, supporting GET, POST, PATCH, PUT, and DELETE.

Define request/response behavior (C):OData standardizes request/response structures, headers, status codes, payload formats (JSON/XML), and protocol-level semantics.

Incorrect options:

B:UI generation is achieved by SAP Fiori Elements, not OData itself.

D:OData is not an analytics engine.

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.”

The Destination Service stores:

Endpoints

Authentication information

Configuration for external APIs or systems

This service is used by CAP applications to call external OData, REST, SOAP, or custom APIs.

Incorrect options:

A – Connectivity Service: Provides on-premise connectivity via Cloud Connector; does not store the metadata itself.

C – Core Data Service: CDS is a modeling language, not a BTP service.

In CAP, your services are typically exposed via OData, and SAP Fiori elements can generate UIs based purely on the service metadata ifUI-relevant semanticsare provided. This is done throughSAP Fiori (UI) annotationson CDS entities and services.

From the CAP and SAP Fiori elements guidance, UI annotations are used to:

Describe how fields aredisplayed in lists and object pages(for example, which properties are line items, identification fields, or facets).

Definevalue helps, grouping, sorting, and actionsin a way that SAP Fiori elements can interpret.

ProvideUI-specific semanticsto the generic OData service so that a UI can be rendered without additional UI coding.

In other words, the core purpose is toenrich the exposed service with UI-specific instructionsthat SAP Fiori elements consumes to render the application.

A: Real-time synchronization is handled via events/messaging, not annotations.

B: Schema migration is based on CDS models and deployment tools, not UI annotations.

C: Performance improvements are not the primary purpose of annotations; they are for semantics.

C – Define role templates in xs-security.json

xs-security.json is the core XSUAA configuration file. It defines:

Role templates

Scopes

Attributes

Authorization semantics

To secure the app, developers must definerole templates, which determine which scopes a role grants.

B – Use role names in application descriptors (web.xml in Java apps)

For Java web apps running via Tomcat/Servlet containers,web.xmldefines application-level roles and maps them to XSUAA role templates.

Thus, restricting access involves linking:

web.xml roles → XSUAA role templates → scopes → permissions

Why A and D Are Incorrect:

A:In xs-app.json, scopes define access rules forHTML5 apps via approuter, not Java applications.

D:Scopes belong to xs-security.json, but setting them alone does not restrict application access unless roles and mappings are defined. The question focuses onstepsto restrict access, and B + C describe the necessary actions.