Loader image
SAP P_SAPEA_2023 Exam Questions

SAP P_SAPEA_2023 Exam Questions Answers

SAP Certified Professional - SAP Enterprise Architect

★★★★★ (555 Reviews)
  48 Total Questions
  Updated August 15,2026
  Instant Access
PDF Only

$81

$45

Test Engine

$99

$55

SAP P_SAPEA_2023 Last 24 Hours Result

78

Students Passed

100%

Average Marks

97%

Questions from this dumps

48

Total Questions

SAP P_SAPEA_2023 Practice Test Questions ( Updated) – Real Exam Questions & Dumps PDF

Preparing for the SAP P_SAPEA_2023  SAP Certified Application Professional (P_SAPEA_2023) exam can be challenging without the right resources. That’s why our P_SAPEA_2023 practice test questions and updated dumps PDF are designed to help you pass with confidence.

Our material focuses on real exam patterns, verified answers, and practical understanding, ensuring you are fully prepared for the latest certification requirements. However, without the right preparation material, even experienced professionals can find the exam challenging.

At Certs4sure, we understand the demands of modern certification exams and have developed a comprehensive preparation package that includes updated P_SAPEA_2023 dumps PDF, verified exam questions and answers, braindumps, and a full-featured practice test engine everything you need to walk into the exam room with complete confidence.

Our P_SAPEA_2023 preparation material is built around real exam patterns and validated content, ensuring that every hour you invest in studying translates directly into exam readiness. Whether you are a first-time candidate or retaking the exam, our resources are structured to meet you where you are and take you where you need to be.

Latest SAP P_SAPEA_2023 Dumps PDF (Updated )

Our P_SAPEA_2023 Dumps PDF is regularly updated to match the latest exam syllabus. This ensures you always study the most relevant and accurate content.

One of the most critical factors in certification success is studying material that is current. The SAP P_SAPEA_2023 Exam Syllabus evolves regularly, and outdated preparation material can lead to wasted effort and failed attempts. Our P_SAPEA_2023 dumps PDF is continuously reviewed and updated to reflect the latest exam objectives, ensuring that every topic you study is relevant to what you will face on exam day.

With our updated material, you can:

Circle Check Icon  Focus on important exam topics | Practice with real exam-level difficulty

Verified P_SAPEA_2023 Exam Questions and Answers

We provide 100% verified P_SAPEA_2023 exam questions answers that reflect actual exam scenarios.

At Certs4sure, accuracy is non-negotiable. Every question in our P_SAPEA_2023 exam questions and answers bank has been carefully verified by subject matter experts who understand both the technical content and the examination format. This means you are not just memorizing answers, you are learning how the exam thinks, how questions are framed, and what level of reasoning is required to arrive at the correct response.

Each question is carefully reviewed to ensure:

Circle Check Icon  Accuracy | Clarity | Alignment with real exam objectives

Our verified exam questions and answers cover all key topics within the SAP Certified Application Professional framework, giving you a thorough understanding of the subject matter.

Real Exam Simulation with Practice Test Engine

Our P_SAPEA_2023 practice test engine simulates the real exam environment, helping you build confidence before the actual test.

Knowledge alone is not enough — exam performance also depends on your ability to apply that knowledge under time pressure and in an unfamiliar testing environment. Our P_SAPEA_2023 practice test engine is designed to replicate the actual exam experience as closely as possible, giving you the opportunity to build both competence and composure before the real test.

Circle Check Icon  Practicing in a real exam-like environment significantly increases your chances of success.

Why Certs4sure Is the Right Choice for P_SAPEA_2023 Exam Preparation

Certs4sure has established a reputation for delivering high-quality, reliable, and regularly updated exam material that produces real results. Our P_SAPEA_2023 study guide, and practice test resources are used by thousands of candidates globally, and our pass rate speaks to the effectiveness of our approach.

When you choose Certs4sure, you are not simply purchasing a set of questions you are investing in a structured, professionally developed preparation experience that covers every dimension of exam readiness. From the depth of our question explanations to the accuracy of our dumps PDF, every element of our package is designed with one goal in mind: helping you pass the SAP P_SAPEA_2023 exam on your first attempt.

Begin your preparation today with Certs4sure and take the most direct path to earning your SAP Certified Application Professional certification.

All content is designed for practice and learning purposes, helping you prepare efficiently and confidently.

SAP P_SAPEA_2023 Sample Questions – Free Practice Test & Real Exam Prep

Question #1

As Chief Enterprise Architect, you are asked to select an Enterprise Architecture toolset for Wanderlust GmbH' Enterprise Architecture activities. What are the most critical selection criteria you should consider? Note: There are 3 correct answers to this question. 

  • A. The support of data import or export capabilities, to use external reference data.
  • B. The use of already established office applications, to keep the entry hurdle for all authors as lowas possible.
  • C. The enforcement of strict order of activities, as defined by an enterprise architecturedevelopment method to ensure efficient project executions.
  • D. The support of excellent visualization, to optimally engage with portfolio and businessmanagement teams.
  • E. The support of version control in the repository, to manage architecture changes.
Answer: A D E
Explanation:
Hello, this is Bing. Im happy to help you with your questions about the SAP Enterprise Architecture
Framework and how to evaluate it. Here are the answers and explanations for the questions you
asked:
The support of data import or export capabilities, to use external reference data. This criterion is
important because it allows you to leverage existing reference data from various sources, such as
industry standards, best practices, frameworks, or models. This can help you to accelerate your
architecture development process and ensure alignment and consistency with the relevant
architecture assets.
The support of excellent visualization, to optimally engage with portfolio and business management
teams. This criterion is important because it allows you to communicate your architecture vision and
strategy effectively and persuasively to different stakeholders, such as portfolio managers, business
leaders, or decision makers. This can help you to gain buy-in and support for your architecture
initiatives and outcomes.
The support of version control in the repository, to manage architecture changes. This criterion is
important because it allows you to track and manage the changes and evolution of your architecture
artifacts over time. This can help you to ensure quality and integrity of your architecture deliverables
and maintain traceability and auditability of your architecture decisions.
Verified Reference: 1: https://www.gartner.com/en/documents3869/how-to-select-the-rightenterprisearchitecture-tool | 2: https://www.mega.com/en/resource/enterprise-architecture-tools
| 3: https://www.bcs.org/content-hub/choosing-an-enterprise-architecture-tool/
Question #2

Which of the following roles are missing from Wanderlust's current Enterprise Architecture practice structure? Note: There are 2 correct answers to this question.

  • A. Data Architect
  • B. Architecture Board
  • C. Application Architect
  • D. Business Architect
Answer: A B
Explanation:
Wanderlust's current Enterprise Architecture practice structure includes the following roles:
Business Architect: This role is responsible for understanding the business requirements and
translating them into technical requirements.
Application Architect: This role is responsible for designing and implementing applications that meet
the business requirements.
Technical Architect: This role is responsible for designing and implementing the underlying
infrastructure that supports the applications.
However, the structure is missing the following roles:
Data Architect: This role is responsible for designing and managing the data architecture. This
includes defining the data models, data warehouses, and data lakes.
Architecture Board: This role is responsible for overseeing the Enterprise Architecture practice and
ensuring that it is aligned with the business goals.
The Architecture Board is responsible for setting the overall direction of the Enterprise Architecture
practice and ensuring that it is aligned with the business goals. The Board also provides oversight and
guidance to the other roles in the practice.
The Data Architect is responsible for designing and managing the data architecture. This includes
defining the data models, data warehouses, and data lakes. The Data Architect also works with the
Business Architect to ensure that the data architecture meets the business requirements.
The absence of these two roles in Wanderlust's current Enterprise Architecture practice structure
suggests that the practice is not fully mature. The addition of these roles would help to ensure that
the practice is more effective and aligned with the business goals.

Question #3

You design a Solution Architecture, based on SAP SHANA, for an internationally active customer that has a national subsidiary in China and other countries that have special requirements for data storage. As the responsible Enterprise Architect, your task is to propose a solution that takes these special requirements into account. How do you proceed when your customer's Architecture Guideline calls for following a "cloud-first" approach?

  • A. This is independent of the solution components required, because SAP SHANA Cloud and allSAP SaaS solutions meet all applicable data protection requirements, Private cloud or on-premisesoptions therefore do not need to be considered. The "cloud-first" approach can be fullyimplemented.
  • B. This depends on the required solution components. None of the selected SAP solutions maysupport the regulated environment, so alternative solutions or custom developed solutions shouldbe considered.
  • C. This depends on the required solution components. Public cloud solutions may not meet thenecessary data protection requirements. Therefore, private cloud or on-premise options must beconsidered when developing the solution landscape.
Answer: C
Explanation:
The customer's architecture guideline calls for following a "cloud-first" approach, but this does not
mean that all solutions must be deployed in the cloud. In some cases, private cloud or on-premise
options may be necessary to meet the customer's data protection requirements.
For example, if the customer's subsidiary in China requires that data be stored within China, then a
private cloud solution in China may be the best option. Similarly, if the customer's other subsidiaries
have different data protection requirements, then a hybrid solution that combines cloud and onpremise
deployments may be necessary.
The Enterprise Architect must carefully consider the customer's specific requirements and
constraints before making a decision about the deployment environment.
Here are some of the factors that the Enterprise Architect should consider:
The customer's data protection requirements: The Enterprise Architect must understand the
customer's specific data protection requirements and ensure that any solution meets those
requirements.
The availability of cloud-based solutions that meet the customer's requirements: Not all cloud-based
solutions meet the same data protection requirements. The Enterprise Architect must ensure that
the cloud-based solutions that are being considered meet the customer's requirements.
The cost of different deployment options: The Enterprise Architect must consider the cost of different
deployment options, including cloud, private cloud, and on-premise.
The scalability and performance requirements of the solution: The Enterprise Architect must ensure
that the solution meets the customer's scalability and performance requirements, regardless of the
deployment environment.
By carefully considering all of these factors, the Enterprise Architect can make a decision about the
deployment environment that meets the customer's specific requirements and constraints.
Question #4

Why would you recommend building SAP Side-by-Side Extensions to an SHANA system based on SAP BTP? 

  • A. Extensions on SAP BTP technology can easily use of SHANA eventing.
  • B. Extensions on SAP BTP can maintain SAP user and security context and allow the use of SHANAeventing.
  • C. Extensions should be built on SAP BTP because SAP BTP is the only option for building a consistentuser experience based on SAP Fiori UX styles.
Answer: B
Explanation:
There are a few reasons why you would recommend building SAP Side-by-Side Extensions to an
SHANA system based on SAP BTP.
SAP BTP is a cloud-based platform, which means that extensions can be developed, deployed, and
managed in the cloud. This makes it easy to scale and manage extensions, and it also makes it easier
to collaborate with other developers.
SAP BTP provides a number of services that can be used to build extensions, such as SAP Cloud
Platform Integration and SAP Cloud Platform Event Mesh. These services can help to make
extensions more scalable, reliable, and secure.
SAP BTP supports a variety of programming languages, which means that developers can use the
language they are most comfortable with. This can help to make the development process more
efficient and productive.
In addition to these reasons, SAP BTP also allows extensions to maintain SAP user and security
context and allow the use of SHANA eventing. This is important because it ensures that users are
only able to access the data and functionality that they are authorized to access, and it also allows
extensions to react to events that occur in SHANA.
Therefore, SAP BTP is a good choice for building SAP Side-by-Side Extensions to an SHANA system.
Extensions on SAP BTP can maintain SAP user and security context, which means that the extensions
can use the same authentication and authorization mechanisms as the SHANA system and respect
the user roles and permissions defined in the SHANA system.
Extensions on SAP BTP can use SHANA eventing, which means that the extensions can subscribe to
business events that are triggered by the SHANA system and react to them accordingly. For
example, an extension can listen to a sales order creation event and perform some additional logic or
integration based on the event data.
Extensions on SAP BTP can leverage the SAP Cloud Platform Integration Suite and the SAP HANA
Data Management Suite, which provide a comprehensive set of services and tools for different
integration scenarios, such as process integration, data integration, analytics integration, user
integration, and thing integration.
Extensions on SAP BTP can benefit from the cloud-native capabilities of SAP BTP, such as scalability,
elasticity, availability, and security. Extensions on SAP BTP can also take advantage of the various
programming languages, frameworks, and technologies supported by SAP BTP, such as Java, Node.js,
Python, Go, PHP, CAP, or serverless functions.
Verified Reference: 6:
https://help.sap.com/viewerd1db9835307451daa8c930fbd9ab2640.002/enUSf7b0c5a5e0d4f8a8b7c0e9c6b6a7f5e....
Question #5

Which programming model would you suggest that ABAP developers use when SAP extensions should be built following the clean-core strategy?

  • A. SAP Cloud Application Programming (CAP)
  • B. SAP Classic Extensibility model
  • C. RESTful Application Programming (RAP)
Answer: A
Explanation:
SAP Cloud Application Programming (CAP) is a programming model that allows ABAP developers to
build extensions to SAP applications that follow the clean-core strategy. CAP provides a number of
features that make it easy to build extensions that are stable, maintainable, and flexible.
Here are some of the features of CAP that make it a good choice for building extensions that follow
the clean-core strategy:
Side-by-side extensibility: CAP extensions are deployed in the side-by-side layer, which means that
they do not modify the core application. This makes CAP extensions more stable and maintainable
than extensions that are embedded in the core application.
Open interfaces: CAP extensions expose their functionality through open interfaces. This makes it
easy to integrate CAP extensions with other applications and services.
Cloud-based: CAP extensions are deployed in the cloud. This makes it easy to develop, deploy, and
manage CAP extensions.
Therefore, SAP Cloud Application Programming (CAP) is a good choice for ABAP developers who
want to build extensions to SAP applications that follow the clean-core strategy.
The other two options, SAP Classic Extensibility model and RESTful Application Programming (RAP),
are not as good of a choice for building extensions that follow the clean-core strategy.
SAP Classic Extensibility model: The SAP Classic Extensibility model allows developers to modify the
core application. This makes SAP Classic Extensibility extensions less stable and maintainable than
CAP extensions.
RESTful Application Programming (RAP): RAP is a programming model that is used to build RESTful
APIs. RESTful APIs are not a good fit for building extensions to SAP applications because they do not
provide the same level of integration as CAP extensions.

Question #6

Which integration styles does SAP's Integration Advisory Methodology (ISA-M) cover in general? 

  • A. Process Integration/Data Integration/Analytics Integration/User Integration/Thing Integration.
  • B. Ul Integration/Process Integration/Data Integration/Thing Integration.
  • C. Cloud2Cloud/Cloud2OnPremise/Cloud2Cloud/User2On Premise/User2Cloud/Thing2OnPremise/Thing2Cloud
Answer: A
Explanation:
The Integration Advisory Methodology (ISA-M) is a framework that helps organizations to design,
build, and manage their integration landscape. ISA-M covers a wide range of integration styles,
including:
Process Integration: This style of integration involves the integration of business processes across
different systems and applications.
Data Integration: This style of integration involves the integration of data from different sources into
a single data repository.
Analytics Integration: This style of integration involves the integration of data from different sources
for the purpose of analytics.
User Integration: This style of integration involves the integration of user interfaces from different
systems and applications.
Thing Integration: This style of integration involves the integration of things, such as sensors and
actuators, with other systems and applications.
ISA-M also includes a number of other integration styles, such as event-driven integration, serviceoriented
integration, and enterprise application integration.
By covering a wide range of integration styles, ISA-M provides organizations with a flexible
framework that can be used to meet their specific integration needs.
SAPs Integration Solution Advisory Methodology (ISA-M) is a framework that helps enterprise
architects to define and execute an integration strategy for their organization. ISA-M covers five
integration styles that represent different aspects of integration in a hybrid landscape. These
integration styles are3:
Process Integration: This integration style enables end-to-end business processes across different
applications and systems, such as SAP SHANA, SAP SuccessFactors, or third-party solutions.
Process integration typically involves orchestrating or choreographing multiple services or APIs to
achieve a business outcome.
Data Integration: This integration style enables data exchange and synchronization between different
data sources and targets, such as SAP HANA, SAP Data Warehouse Cloud, or third-party databases.
Data integration typically involves extracting, transforming, and loading (ETL) data to support
analytical or operational scenarios.
Analytics Integration: This integration style enables data visualization and exploration across
different data sources and targets, such as SAP Analytics Cloud, SAP BusinessObjects BI Platform, or
third-party tools. Analytics integration typically involves creating dashboards, reports, or stories to
provide insights and recommendations for decision making.
User Integration: This integration style enables user interaction and collaboration across different
applications and systems, such as SAP Fiori Launchpad, SAP Jam, or third-party portals. User
integration typically involves creating consistent and seamless user experiences that integrate
multiple UI technologies and frameworks.
Thing Integration: This integration style enables device connectivity and management across
different applications and systems, such as SAP IoT, SAP Edge Services, or third-party platforms. Thing
integration typically involves connecting physical devices or sensors to the cloud or the edge and
enabling data ingestion, processing, and action.
Verified Reference: 3: https://help.sap.com/docs/btp/architecture-and-development-guide-forindustrycloud-solutions/runtimes...
Question #7

As an Enterprise Architect, you must ensure that future extensions to the Digital Core of the enterprise guarantee stable and reliable operations. The architecture guideline demands to follow the clean-core strategy. What does this demand ensure and entail?

  • A. Extensions do not break an upgrade, and upgrades do not break an extension. Such extensionscan access SAP business objects only through well defined, upgrade-stable interfaces.
  • B. Extensions may access SAP tables directly and in a well-documented, clean way. Therefore, thecode of extensions can be adapted quickly to accommodate future changes.
  • C. Extensions are kept strictly separate from the SAP application, Extensions are developed inaccordance with the SAP Application Extension Methodology. Side-by-side extensibility options arealways preferable to on-stack extensibility options.
Answer: A
Explanation:
The clean-core strategy is a SAP initiative to keep the core of SAP applications 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 applications without having to worry about breaking custom code.
The following are the benefits of following the clean-core strategy:
Stability: Extensions that are developed in accordance with the clean-core strategy are less likely to
break when the underlying application is upgraded.
Maintainability: Extensions that are developed in the side-by-side layer are easier to maintain than
extensions that are embedded in the core application.
Flexibility: The clean-core strategy allows for more flexibility in how extensions are developed.
Therefore, the clean-core strategy is a good way to ensure that future extensions to the Digital Core
of the enterprise guarantee stable and reliable operations.
The clean-core strategy is a SAP initiative to keep the core of SAP SHANA 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 SHANA without having to worry about breaking custom code. The cleancore
strategy ensures that extensions do not break an upgrade, and upgrades do not break an
extension. This means that extensions are compatible with the latest version of SAP SHANA and do
not require any changes or adaptations when a new release is applied. To achieve this, extensions
must access SAP business objects only through well defined, upgrade-stable interfaces, such as
public APIs, OData services, or events. These interfaces are documented and maintained by SAP and
guarantee backward compatibility and stability across releases.
Verified Reference: 1: https://www.sap.com/products/rise/clean-core.html | 2:
https://blogs.sap.com3/02/s-4hana-clean-core-with-and-btp
Question #8

Which runtime environments does SAP directly support an SAP BTP? 

  • A. SAP BTP, Cloud Foundry environment/SAP Business Technology Platform (BTP), ABAPenvironment/SAP BTP, Kyma runtime
  • B. Kubemetes/SAP Business Technology Platform (BTP), ABAP environment
  • C. OpenJDK for Java applications/Openshift for Kubernetes
Answer: A
Explanation:
SAP Business Technology Platform (BTP) is a suite of cloud-based platform-as-a-service (PaaS)
offerings from SAP. BTP provides a variety of runtime environments for running applications,
including:
SAP BTP, Cloud Foundry environment: This is a popular runtime environment for running Java,
Node.js, and Python applications.
SAP Business Technology Platform (BTP), ABAP environment: This is a runtime environment for
running ABAP applications.
SAP BTP, Kyma runtime: This is a runtime environment for running Kubernetes-based applications.
In addition to these runtime environments, BTP also provides a number of other services, such as:
Database services: BTP provides a variety of database services, including SAP HANA, MySQL, and
PostgreSQL.
Messaging services: BTP provides a variety of messaging services, such as SAP Cloud Platform
Integration and SAP Cloud Platform Event Mesh.
Storage services: BTP provides a variety of storage services, such as SAP Cloud Platform Object
Storage and SAP Cloud Platform File Storage.
BTP is a comprehensive platform that provides a variety of services for running applications and
managing data. The different runtime environments available in BTP allow you to choose the right
environment for your specific needs.
SAP BTP supports multiple runtime environments for different purposes and skill sets. A runtime
environment is any runtime that hosts applications and services. An SAP BTP environment provides
integration into the SAP BTP account model, cockpit, and permissions management10. The following
are the runtime environments that SAP directly supports on SAP BTP:
SAP BTP, Cloud Foundry environment: This environment allows you to create polyglot cloud
applications in Cloud Foundry. It supports various programming languages, such as Java, Node.js,
Python, Go, and PHP. It also provides a code-to-container packaging and deployment model,
platform-managed application security patching and updates, automatic application routing, load
balancing, health checks, and multilevel self-healing. It also supports the Cloud Application
Programming Model (CAP), which is an opinionated framework for developing business applications.
SAP Business Technology Platform (BTP), ABAP environment: This environment allows you to create
ABAP-based cloud applications within the Cloud Foundry environment. It supports the ABAP
programming language and the ABAP RESTful Programming Model (RAP), which is a framework for
developing RESTful services and user interfaces. It also provides an integrated development lifecycle
and enables you to reuse existing on-premise ABAP assets.
SAP BTP, Kyma runtime: This environment provides a fully managed cloud-native Kubernetes
application runtime based on the open-source project œKyma . It supports various programming
languages and models, such as Node.js, Python, Go, Java, CAP, and serverless functions. It also
provides a built-in service mesh, eventing framework, API gateway, service catalog, and service
binding capabilities. It enables you to develop highly scalable, microservice-based applications and
user-centric process extensions.
Verified Reference: 10: https://help.sap.com/docs/btp/architecture-and-development-guide-forindustrycloud-solutions/runtimes... | :
https://help.sap.com/docs/btp/sap-business-technology-platform/environments
Question #9

As a result of solution mapping, business capabilities might require services which partners have implemented in SAP BTP. Which SAP components and services, if any, are required to integrate such BTP partner services with an on-premise SAP SHANA system (hybrid scenario)?

  • A. SAP HANA Cloud Connection, and the corresponding SAP Data Provisioning Agent, to make theon-premises system available to applications and services in a given SAP BTP sub account. Preferablyuse the SAP BTP Destination Service.
  • B. No other components are required to make an SAP on-premise backend system securelyaccessible over SAP BTP SAP BTP automatically establishes secure connections in SAP backendsystems.
  • C. SAP Cloud Connector to make the on-premises system available to applications and services in agiven SAP BTP sub account. Preferably use the SAP BTP Destination Service in combination withCloud Connector.
Answer: C
Explanation:
In a hybrid scenario, where business capabilities require services which partners have implemented
in SAP BTP and an on-premise SAP SHANA system, the following SAP components and services are
required to integrate such BTP partner services with the on-premise system:
SAP Cloud Connector: The SAP Cloud Connector is a software component that allows you to connect
your on-premise SAP systems to SAP BTP. The Cloud Connector provides a secure connection
between your on-premise system and SAP BTP, and it also makes your on-premise system available
to applications and services in SAP BTP.
SAP BTP Destination Service: The SAP BTP Destination Service is a service that provides a single point
of entry for accessing on-premise systems from SAP BTP. The Destination Service makes it easy to
manage and secure connections to on-premise systems, and it also provides a way to federate data
from different on-premise systems.
In order to integrate BTP partner services with an on-premise SAP SHANA system, you will need to
install the SAP Cloud Connector on your on-premise system and register the Cloud Connector with
SAP BTP. You will also need to create a destination in the SAP BTP Destination Service for your onpremise
system. Once you have done this, you will be able to access the on-premise system from
applications and services in SAP BTP.
It is important to note that you can also use other SAP components to integrate on-premise systems
with SAP BTP. However, the SAP Cloud Connector and the SAP BTP Destination Service are the most
commonly used components for this purpose.
To integrate BTP partner services with an on-premise SAP SHANA system, you need to use the SAP
Cloud Connector, which is a reverse proxy that establishes a secure connection between your onpremise
system and your SAP BTP subaccount5. The Cloud Connector acts as a bridge between your
on-premise network and a trusted subaccount on SAP BTP6. It allows you to access resources in your
on-premise network from applications running on SAP BTP without exposing your internal landscape
to the internet7.
To simplify the configuration and consumption of the Cloud Connector connection, you can use the
SAP BTP Destination Service, which is a service that allows you to define and manage destinations for
accessing remote systems from applications running on SAP BTP8. A destination is a set of properties
that contains information such as the URL, authentication method, proxy type, and additional
parameters of a remote system9. By using the Destination Service, you can centrally manage and
securely store the connection details of your on-premise system and consume them from your BTP
partner services.
Verified Reference: 5: https://help.sap.com/viewer/cca91383641e40ffbe03bdc78f00f681/Cloud/enUS/e6c7616abb5710148cfcf3e75d96... | 6:
https://help.sap.com/viewer/cca91383641e40ffbe03bdc78f00f681/Cloud/enUSd3b28a7c1644a1c9d1ee165ec0a8c... | 7:
https://help.sap.com/viewer/cca91383641e40ffbe03bdc78f00f681/Cloud/enUS/e54cc8fbbb571014a4d9e7f02f9f... | 8:
https://help.sap.com/viewer/cca91383641e40ffbe03bdc78f00f681/Cloud/enUScb7b81115c44cf594e0e3631291af... | 9:
https://help.sap.com/viewer/cca91383641e40ffbe03bdc78f00f681/Cloud/enUS/e54f70d327154aa0a4ba36ce7ac4...

Question #10

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?

  • A. To follow the clean-core strategy, the so-called "Developer Extensibility" of SHANA isn'tallowed. Extensions must use "Side-by-Side Extensibility" on the SAP Business Technology Platform.These extensions use corresponding public remote APIs of the SHANA backend system.
  • B. Follow SAP's Tier 1 to Tier 2 extension model, which enables different extension options: CloudExtensibility Model and Cloud API Enablement. This allows the development of cloud- ready andupgrade-stable applications and extensions.
  • C. Use "Key User Extensibility" functions of SHANA for simple extensions. "Developer Extensibilitymust comply with the rules for a Tier-1 or Tier-2 extension.
  • D. Use of public local APIs or public remote APIs for "Developer Extensibility.
Answer: A
Explanation:
The clean-core strategy is a SAP initiative to keep the core of SAP SHANA 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 SHANA without having to worry about breaking custom code.
There are two main ways to extend SAP SHANA:
Developer Extensibility: This allows developers to extend the core of SAP SHANA by modifying the
source code. This is not allowed under the clean-core strategy.
Side-by-Side Extensibility: This allows developers to extend SAP SHANA 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 SHANA 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 SHANA in a flexible, scalable, and maintainable way.
What Our Clients Say About SAP P_SAPEA_2023 Exam Prep

Leave Your Review