SAP P_SAPEA_2023 Exam - 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?

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

BFollow SAP's Tier 1 to Tier 2 extension model, which enables different extension options: Cloud Extensibility Model and Cloud API Enablement. This allows the development of cloud- ready and upgrade-stable applications and extensions.

CUse 'Key User Extensibility' functions of S/4HANA for simple extensions. 'Developer Extensibility must comply with the rules for a Tier-1 or Tier-2 extension.

DUse of public local APIs or public remote APIs for 'Developer Extensibility.

Show Suggested 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.

by Lacey at Sep 14, 2024, 06:12 AM

Limited Time Offer

25%

Off

Get Premium P_SAPEA_2023 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Shawn

3 months ago

C is useful for quick fixes, but not for long-term strategy.

upvoted 0 times

...

Almeta

3 months ago

B is spot on! Cloud-ready is the future.

upvoted 0 times

...

Bettina

3 months ago

Wait, I thought Developer Extensibility was still an option?

upvoted 0 times

...

Anglea

4 months ago

I disagree, B has more flexibility for cloud apps.

upvoted 0 times

...

Malcolm

4 months ago

A is definitely the way to go for clean-core!

upvoted 0 times

...

Ivan

4 months ago

I feel like option D is related to the use of APIs, but I’m not sure if public local APIs are really aligned with the clean-core strategy. I need to double-check that part.

upvoted 0 times

...

Jesusita

4 months ago

I vaguely remember that 'Key User Extensibility' is for simpler extensions, but I'm confused about how it fits into the clean-core strategy. I might be mixing it up with 'Developer Extensibility' rules.

upvoted 0 times

...

Adell

4 months ago

I think option B sounds familiar because it mentions the Tier 1 to Tier 2 model. I practiced a question about cloud-ready applications, but I can't recall the specifics of the Cloud API Enablement.

upvoted 0 times

...

Remona

5 months ago

I remember studying the clean-core strategy, and I think 'Side-by-Side Extensibility' is crucial for keeping the core clean. But I'm not entirely sure if 'Developer Extensibility' is completely off the table.

upvoted 0 times

...

Dorothy

5 months ago

For simple extensions, I'd use the Key User Extensibility functions of S/4HANA, but for anything more complex, I need to make sure it complies with the Tier 1 or Tier 2 rules, so option C seems like a good approach.

upvoted 0 times

...

Kenneth

5 months ago

The key here is to follow the rules for Tier 1 or Tier 2 extensions, which means using the appropriate extensibility options like cloud extensibility or cloud API enablement. I think option B is the way to go.

upvoted 0 times

...

Hershel

5 months ago

Hmm, I'm a bit confused. I thought the clean-core strategy was about the Tier 1 to Tier 2 extension model, but I'm not sure if that's the whole story. I might need to review the details on that.

upvoted 0 times

...

Elly

5 months ago

I'm pretty confident about this one. The clean-core strategy requires using side-by-side extensibility on the SAP Business Technology Platform, so I'd go with option A.

upvoted 0 times

...

Adelina

1 year 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

1 year 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

Dyan

1 year ago

C) Use 'Key User Extensibility' functions of S/4HANA for simple extensions. 'Developer Extensibility must comply with the rules for a Tier-1 or Tier-2 extension.

upvoted 1 times

...

Talia

1 year ago

C) Use 'Key User Extensibility' functions of S/4HANA for simple extensions. 'Developer Extensibility must comply with the rules for a Tier-1 or Tier-2 extension.

upvoted 1 times

...

Alayna

1 year ago

B) Follow SAP's Tier 1 to Tier 2 extension model, which enables different extension options: Cloud Extensibility Model and Cloud API Enablement. This allows the development of cloud-ready and upgrade-stable applications and extensions.

upvoted 2 times

...

Margot

1 year ago

upvoted 2 times

...

Novella

1 year 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

...

Lashawna

1 year ago

upvoted 0 times

...

Dona

1 year 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

Bonita

1 year ago

Definitely, following the recommended extension models will make it easier to manage and upgrade the system in the future.

upvoted 1 times

...

Walton

1 year ago

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 1 times

...

Herminia

1 year ago

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

1 year 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

...

German

1 year 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 1 times

...

Hayley

1 year 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

1 year 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

1 year 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

1 year 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

1 year ago

I agree, option A seems like the best choice for following SAP's clean-core strategy.

upvoted 0 times

...

My

1 year 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 year 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 year 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

1 year 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 year ago

I agree, option B provides a good balance between flexibility and alignment with SAP's clean-core strategy.

upvoted 0 times

...