PDF C_CPE_2409 Study Guide

Comprehensive and Detailed Explanation

AMultitarget Application (MTA)is the SAP-recommended packaging format for complex applications that involve multiple modules (for example, CAP service, UI, XSUAA, destination service). MTAs are deployed as .mtar archives using theCloud MTA Build Tool (mbt)anddeploy service.

Correct Options:

C – Using SAP Business Application Studio

SAP Business Application Studio includes:

A graphical MTA builder

Built-in Cloud MTA Build Tool

Deployment integration with SAP BTP

Wizards for generating mta.yaml

Developers can simply right-click the project →Build MTA→Deploy MTA Archive.

D – Manually creating and deploying the mta.yaml file

Developers can:

Write or update the mta.yaml (the deployment descriptor).

Use the Cloud MTA Build Tool to build the .mtar.

Deploy using the Cloud Foundry deploy service (cf deploy .mtar).

This is a fully supported and widely used approach.

Why the Other Options Are Incorrect:

A – SAP HANA Cloud tools:

These tools manage HANA databases, not MTAs.

B – cf push:

cf push deploys asingle module.

MTAs must be deployed viadeploy service, not cf push.

Comprehensive and Detailed Explanation

Authorization flow in SAP BTP:

Scopesare defined in XSUAA.

Scopes are grouped intorole templates.

Role templates becomerolesin the subaccount.

Roles are assigned tousers.

Role collections group roles for easier assignment.

If a user cannot access an app:

The most common cause is:

C – Roles aren’t assigned to the user

Without receiving the required role, the user’s JWT tokendoes not contain the required scopes.

Even if:

Scopes exist

Role templates exist

Role collections exist

…the user mustexplicitlyhave the role (or role collection) assigned.

Why the Others Are Incorrect:

A:Client applications don’t require role assignments.

B:Role collections may be assigned, butroleassignment is the critical missing piece in this scenario.

D:Client applications do not need role collections.