Certificate Associate Exam - Back-end Developer PT9

<Clean Core> What is the Clean Core principle in ABAP Cloud and why is it important?. The Clean Core principle ensures that custom enhancements are done without modifying the SAP standard code. It promotes the use of released and upgrade-safe objects. It allows the enhancement of SAP Standard code. It encourages the use of strictly coupled logic for better maintainability. It encourages decoupled architectures so the system stays stable and maintainable through upgrades.

<In-App Extensibility> What is in-app extensibility, and what are examples of what you can do with it?. In-app extensibility allows key users (not developers) to tailor standard SAP applications from within the system. In-app extensibility is often using Fiori-based no-code/low-code tools. It doesn't allow adding custom fields to BOs. It allows to add simple logic using BAdIs. You cannot add new buttons or UI changes thanks to the in-app extensibility.

<Side-by-Side Extensibility> What is side-by-side extensibility, and when would you choose it?. Side-by-side extensibility means creating custom apps or services on SAP BTP, which interact with S/4HANA via APIs or events — without changing the S/4HANA system itself. It’s the best choice when: - You need completely new functionality - You want to build independent apps. It’s the best choice when: - You do not want to scale or host logic outside the core system. Side-by-side extensibility is mostly used by key users (not developers).

<Released Objects> Why are you only allowed to use “released” objects in ABAP Cloud development?. Released objects (like released CDS views, APIs, classes, annotations) are officially approved by SAP for public use. Using them ensures that: - Your code is upgrade-safe - It won't break when SAP releases system updates. You do not need to stay compliant with clean core guidelines when using released objects. Released objects are not officially approved and should not be used in SAP.

<RAP & Extensibility> How does RAP help support extensibility while keeping the system clean?. by providing a flexible, layered architecture. by allowing developers to create released views and behaviors. by allowing key users to extend BOs via custom fields, logic, validations. by not allowing RAP to enable clean separation between data, logic, and consumption. by ensuring that everything stays upgrade-compliant when following clean core rules.