Free SAP C_CPE_2601 Practice Questions: Backend Developer System Tasks [2026]

Step-by-Step Execution:

1. Open your application's manifest file (manifest.yml) in your code editor.
2. Set the health-check-type attribute to http.
3. Define the health-check-http-endpoint attribute to point to your application's specific health endpoint.
4. Increase the timeout attribute to 60 seconds to accommodate the slow database connection.
5. Apply the new configuration by executing cf push YOUR_APP_NAME.

Example Values:

• health-check-type: http
• health-check-http-endpoint: /health
• timeout: 60

Expected Result: Cloud Foundry uses the HTTP endpoint to verify application readiness. The router does not forward traffic until the /health endpoint returns an HTTP 200 status code, and instances are automatically restarted if the endpoint later fails.

Quick Mistakes:

• Using an endpoint that requires user authentication, causing the health check to constantly fail with a 401 Unauthorized status and mark the app as crashed.
• Forgetting that failing an ongoing liveness check forces a container restart, while a readiness check failure only temporarily removes the instance from the load balancer router.

Exam Insight:

• Tests understanding of Cloud Foundry health check mechanisms (port, process, HTTP).
• Highlights how custom HTTP checks ensure graceful deployments and robust application recovery by directly verifying application logic instead of just network availability.

Step-by-Step Execution:

1. Open the context menu for your CAP project and launch the SAP Fiori tools application generator.
2. Select the SAP Fiori Elements template to create your application and place it in the app folder.
3. Right-click the generated UI application folder and select the option to open the Page Map visual editor.
4. Configure the List Page by modifying the table fields and setting the Header to dynamically display the respective title value.
5. Save the configuration to automatically generate the required CDS UI annotation files in your project.

Example Values:

• UI Template: SAP Fiori Elements List Page and Object Page
• Target Folder: app

Expected Result: The app folder contains a new SAP Fiori Elements application with generated annotation files reflecting the Page Map configuration.

Quick Mistakes:

• Placing the UI files outside of the app folder, which prevents the CAP framework from serving them automatically.
• Assuming the UI must be built with raw JavaScript or HTML instead of leveraging SAP Fiori Elements out-of-the-box support and visual productivity tools.

Exam Insight:

• Tests your ability to use SAP Fiori Tools and the Page Map for rapid UI development in CAP.
• Understanding this is crucial because it abstracts the complexity of writing manual UI annotations and generates the required metadata documents automatically.

Step-by-Step Execution:

1. Navigate to the UI Applications tile in the Storyboard and select the + icon to add a new user interface.
2. Select the existing backend service as the Data source and proceed.
3. Choose Mobile-Centric, Freestyle Application as the UI Application Type to enable native mobile features.
4. Select CRUD as the UI Application Template to allow users to create, read, update, and delete data.
5. Select the target entities as Data Objects and specify a List Picker property for dropdown selections.
6. Navigate to the generated Page Map to configure captions and titles for the mobile application.

Example Values:

• Data source: RiskManagementService
• UI Application Template: CRUD
• Data Objects: Mitigations and Risks
• List Picker: BusinessPartnerFullName

Expected Result: A metadata-based mobile UI project is generated within the workspace, featuring a Page Map layout for SAP Mobile Development Kit (MDK) development.

Quick Mistakes:

• Choosing a standard responsive web template instead of the Mobile-Centric application type.
• Forgetting to map the correct List Picker property, which determines the display value for dropdown selections in the mobile app.

Exam Insight:

• Evaluates ability to generate multichannel applications running natively on mobile devices using the SAP BTP ecosystem.
• Tests familiarity with the SAP Mobile Development Kit (MDK) configuration options and Page Map editor within SAP Business Application Studio.

Step-by-Step Execution:

1. Open the JavaScript file associated with your CDS service.
2. Register an event handler to validate the incoming request.
3. Use the req.error() method within your handler logic to formulate a human-readable error message.
4. Pass the custom message and an appropriate HTTP status code to the method.
5. Restart the local server and trigger the condition to verify the new error output.

Example Values:

• Error HTTP Code: 400
• Custom Message: "Replacement date cannot be in the past."

Expected Result: The application cleanly rejects invalid requests and returns the custom error message in the payload instead of a generic or cryptic stack trace.

Quick Mistakes:

• Trying to catch unexpected programmer errors with generic try/catch blocks instead of fixing the root cause in the code.
• Hiding the root cause of an error by completely overwriting framework exceptions without logging them.
• Continuing to execute logic silently after an operational error occurs, risking data corruption.

Exam Insight:

• Tests the ability to manage operational errors and utilize the req.error() method in the CAP Node.js SDK.
• This is crucial for building robust APIs that provide clear, actionable feedback to frontend applications and avoid "failing silently."

Step-by-Step Execution:

1. Open the domain model .cds file containing the Books entity.
2. Add the @mandatory annotation to the title element to reject null or empty strings.
3. Add the @assert.target annotation to the author association to ensure the provided foreign key exists in the database.
4. Add the @assert.range: true annotation to the genre element (typed as an Enum) to restrict input to predefined valid values.
5. Send an HTTP POST request to create a new book with invalid values (e.g., missing title or a non-existent genre) to verify the validation logic.

Example Values:

• Title Annotation: @mandatory
• Author Annotation: @assert.target
• Genre Annotation: @assert.range: true

Expected Result: Attempting to create an invalid record bypasses execution and immediately returns an HTTP 400 (Bad Request) status code. The response body details the exact validation failure, such as indicating the invalid foreign key or highlighting the missing mandatory value.

Quick Mistakes:

• Testing the validations only via a web UI and forgetting to test direct HTTP POST requests where client-side validation is naturally bypassed.
• Forgetting to pass the : true property to @assert.range for enum elements, which might inadvertently allow users to pass numeric values outside the defined list.

Exam Insight:

• Tests your knowledge of built-in CAP declarative input validations via annotations like @mandatory, @assert.target, and @assert.range.
• Important for understanding how to secure database integrity generically without writing explicit custom validation logic in Node.js event handlers.