C_C4H45_2408 SAP Certified Associate - Integration Consultant - SAP Sales and Service Cloud Questions and Answers

Request and upload a new client certificate from the certificate authority

Upload the client certificate to the communication arrangement

Change the URL to use HTTPS

Upload the root certificates to the SAP Sales and Service Cloud trust store

By any CA provided in the server list

By any CA that is in the trust list of the client system

By every CA provided in the server list

By the same CA that signed the server's client certificate

Replication model

Logical web service port

Receiver system hostname

Outbound implementation

The SAP S/ 4 HANA client certificate needs to be signed by a certificate authority trusted by SAP Sales and Service Cloud.

The SAP S/4HANA client certificate needs to be signed by a certificate authority trusted by the SAP Cloud Integration load balancer

The SAPS/4HANA server certificate needs to be signed by a certificate authority trusted by SAP Sales and Service Cloud

The SAP S/4HANA client certificate needs to be signed by a certificate authority trusted by the SAP Sales and Service Cloud load balancer

SAP S/4HANA SSL client PSE

SAP Sales and Service Cloud certificate trust list

SAP Web Dispatcher trust store

SAPS/ 4HANA SSL server PSE

No changes to inbound firewall settings necessary

No installation inside the on-premise network necessary

Built-in malware detection engine

Fine grained access control to multiple systems and resources

When you need to integrate employees

When you need to integrate sales pricing

When you need to integrate products

When you need to integrate organizational structures

When you need to integrate campaigns

When the initial deploy fails and a new version of the WSDL needs to be exported

When using a reduced IDoc, for example, MATMAS_CFS

When fields required for the integration scenario have been added to the service

When using a synchronous web service

Protection of sensitive customer data

Uniform implementation independent of the back-end system

No BAdl implementation needed in source or target system

Performance enhancement independent from increased data loads

Attachments

E-mails

Pricing

Notes

User-defined status

Timestamps

Direction

XML payload

Service interface

Service Request to Service Request

Sales Quote to Sales Quote

Opportunity to Opportunity

Ticket to Ticket

Only filtering by BAdl is secure and allows enforced consistency

Reduced load on the middleware (eg SAP Process Orchestration or SAP Cloud Integration)

Data protection, which ensures that sensitive data NOT intended for external systems never leaves SAP S/4HANA

Automatic update of WSDL structure in the target system

Internet

Forward proxy

Reverse proxy

On-Premise

Create new facets in SAP Sales and Service Cloud objects using SAP Cloud Integration

Create extension fields in SAP Sales and Service Cloud via the adaptation mode

Include extension fields in SAP Sales and Service Cloud web services

Create extension fields in SAP Sales and Service Cloud using SAP Cloud Integration

Forward proxy

Client certificate authentication

HTTPS communication

Reverse proxy

Deploy a user credential artifact on SAP Cloud Integration containing the user credential of the SAP Sales and Service Cloud communication user

Deploy a user credential artifact on SAP Cloud Integration containing the user credential of the SAP S/4HANA communication user

Update the integration flow parameters with the host and path of the SAP S/4HANA web service

Update the integration flow parameters with the host of SAP Sales and Service Cloud and the relevant credential name.

Identify custom fields early in the project

Include functional, integration, basis, and networking experts on the project team

Set the expectation that prepaclra.ged integration requires configuration

Create extension fields across all systems from the BTP subaccount

Align business processes after setting up prepackaged integration

In the basic authentication artifact

In the 0Auth2 authentication artifact

In the keystore artifact

In the PGP secret keyring artifact

1. Add the "ENVIRONMENT RISK field to the target message WSDL in SAP Cloud Integration. 2. Map the "ENVIRONMENT RISK target field with source field "EnvironmentRelevancelndicator" in the message mapping 3. Activate the new mapping.

1. Download the extended WSDL from SAP Sales and Service Cloud.2. Import the WSDL into SAP Cloud Integration.3. Map the "ENVIRONMENT RISK target field with source field "EnvironmentRelevancelndicator" in the message mapping,

1. Export the WSDL from SAP S/4HANA.2. Import the WSDL into the communication arrangement in SAP Sales and Service Cloud.3. Update the mapping with the new WSDL from SAP Sales and Service Cloud

1. Create an "ENVIRONMENT RISK variable in externalized parameters in SAP Cloud Integration 2. Update the externalized parameters with the variable for the "ENVIRONMENT _RISK" field.3. Save and activate the updated externalized parameters.

Maintain Logon Data Management

Maintain Communication Arrangement

Maintain Provider System

Maintain Profile

Maintain Security Artifact