Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

SAP Exam P_SAPEA_2023 Topic 1 Question 33 Discussion

Actual exam question for SAP's P_SAPEA_2023 exam
Question #: 33
Topic #: 1
[All P_SAPEA_2023 Questions]

As Chief Enterprise Architect, you want to select an extension option that follows SAP's clean-core strategy. What are your recommendations to implement the clean-core strategy best?

Show Suggested Answer Hide Answer
Suggested Answer: A

The clean-core strategy is a SAP initiative to keep the core of SAP S/4HANA as clean as possible by moving customizations and extensions to the side-by-side layer. This allows SAP to more easily deliver new releases of S/4HANA without having to worry about breaking custom code.

There are two main ways to extend SAP S/4HANA:

Developer Extensibility:This allows developers to extend the core of SAP S/4HANA by modifying the source code. This is not allowed under the clean-core strategy.

Side-by-Side Extensibility:This allows developers to extend SAP S/4HANA by creating new applications that run alongside the core system. These applications can communicate with the core system using public APIs.

The following are the benefits of using Side-by-Side Extensibility:

Flexibility:Side-by-Side Extensibility allows developers to extend SAP S/4HANA in any way they see fit.

Scalability:Side-by-Side Extensibility can be scaled to meet the needs of any organization.

Maintainability:Side-by-Side Extensibility is easier to maintain than Developer Extensibility, because custom code is not embedded in the core system.

Therefore, the best way to implement the clean-core strategy is to use Side-by-Side Extensibility. This will allow you to extend SAP S/4HANA in a flexible, scalable, and maintainable way.


Contribute your Thoughts:

Adelina
13 days ago
I'm sorry, but I'm too busy trying to figure out how to make my coffee machine work with SAP to worry about this question. Anyone know a good API for that?
upvoted 0 times
...
Walton
14 days ago
I'm a bit confused by all these extension options. I just want to get my job done! Can we get a simpler answer, please?
upvoted 0 times
Lashawna
3 days ago
A) To follow the clean-core strategy, the so-called 'Developer Extensibility' of S/4HANA isn't allowed. Extensions must use 'Side-by-Side Extensibility' on the SAP Business Technology Platform. These extensions use corresponding public remote APIs of the S/4HANA backend system.
upvoted 0 times
...
...
Dona
25 days ago
Option C looks good to me. Using the 'Key User Extensibility' for simple extensions and following the Tier-1 or Tier-2 rules for 'Developer Extensibility' seems like a solid strategy.
upvoted 0 times
Walton
3 days ago
User 3: I think sticking to the rules for Tier-1 or Tier-2 extensions will help maintain system stability and compatibility in the long run.
upvoted 0 times
...
Herminia
12 days ago
User 2: I agree, it's important to ensure that the extensions are in line with SAP's guidelines for a clean-core strategy.
upvoted 0 times
...
Maryann
16 days ago
User 1: Option C looks good to me. Using the 'Key User Extensibility' for simple extensions and following the Tier-1 or Tier-2 rules for 'Developer Extensibility' seems like a solid strategy.
upvoted 0 times
...
...
German
1 months ago
I prefer option B. Following SAP's Tier 1 to Tier 2 extension model allows for different extension options like Cloud Extensibility Model and Cloud API Enablement, which can lead to cloud-ready and upgrade-stable applications.
upvoted 0 times
...
Hayley
1 months ago
I'm leaning towards option A. Keeping extensions on the SAP Business Technology Platform and using public remote APIs is the cleanest approach in my opinion.
upvoted 0 times
Rupert
13 days ago
I'm not sure about option D, using public local APIs or public remote APIs for Developer Extensibility seems less clean compared to the other options.
upvoted 0 times
...
Virgina
16 days ago
Option C might be simpler for basic extensions, but I see the appeal of using public remote APIs in option A.
upvoted 0 times
...
Maira
23 days ago
I think option B could also be a good option, as it allows for cloud-ready and upgrade-stable applications.
upvoted 0 times
...
Janey
27 days ago
I agree, option A seems like the best choice for following SAP's clean-core strategy.
upvoted 0 times
...
...
My
1 months ago
I agree with Whitney. Option A ensures that extensions use corresponding public remote APIs of the S/4HANA backend system, which is important for maintaining a clean-core strategy.
upvoted 0 times
...
Whitney
1 months ago
I think option A is the best choice. It follows SAP's clean-core strategy and uses Side-by-Side Extensibility on the SAP Business Technology Platform.
upvoted 0 times
...
Lettie
1 months ago
I think option B is the way to go. The Tier 1 to Tier 2 extension model seems to offer the most flexibility and alignment with SAP's clean-core strategy.
upvoted 0 times
Gertude
27 days ago
I think option B is the best choice as well. It allows for cloud-ready and upgrade-stable applications.
upvoted 0 times
...
Gertude
1 months ago
I agree, option B provides a good balance between flexibility and alignment with SAP's clean-core strategy.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77