Salesforce Certified Platform Integration Architect Free Sample Questions

Evaluate the Current System Landscape · System landscape standards, limitations, boundaries, and protocols

1. A

   Generate the WSDL from the ERP, import it into Salesforce using 'Generate from WSDL', and use the auto-generated Apex classes to make the callout.

2. B

   Implement Salesforce Connect with a custom OData 4.0 adapter to map the ERP XML to External Objects.

3. C

   Use Apex HttpRequest to construct the raw XML envelope manually, set the required headers, and send the request to the ERP endpoint.

4. D

   Use Outbound Messaging to send the SOAP request and configure a callback listener in Salesforce to handle the response.

Evaluate the Current System Landscape · Constraints and pain points analysis

1. A

   Pain Point: Lack of Middleware; Solution: Introduce an ETL tool to batch process closed Opportunities nightly.

2. B

   Pain Point: Low timeout thresholds; Solution: Increase the Apex callout timeout to 120 seconds in the trigger.

3. C

   Pain Point: Governor Limits; Solution: Move the logic to a @future method to ensure the callout happens eventually.

4. D

   Pain Point: Tightly coupled systems; Solution: Implement a Fire and Forget pattern using Platform Events to decouple the transaction.

Evaluate the Current System Landscape · Authentication and authorization evaluation

1. A

   Connected App with the 'API Only' scope and IP Relaxation.

2. B

   Shield Platform Encryption to encrypt the password field in a custom object.

3. C

   Custom Metadata Types to store the Client ID and Secret, using Apex to generate the JWT.

4. D

   Named Credentials with a JWT/Client Credentials Auth Provider and a certificate stored in Certificate and Key Management.

Evaluate Business Needs · Data classification (Confidential/Secure/Public)

1. A

   Implement Shield Platform Encryption for the PII fields and ensure the custom integration log object is also encrypted.

2. B

   Classify the data as 'Public' in the Data Classification metadata to bypass security checks.

3. C

   Use Field-Level Security to hide PII fields from the Integration User profile.

4. D

   Use an MD5 hash function in Apex to hash PII data before writing it to the logs.

Evaluate Business Needs · Functional and non-functional requirements for integration

1. A

   Non-Functional Requirements

2. B

   Compliance Requirements

3. C

   Data Governance Requirements

4. D

   Functional Requirements

Evaluate Business Needs · CRM success factors for integration

1. A

   Selecting the middleware with the lowest licensing cost.

2. B

   Ensuring all developers have System Administrator access to production.

3. C

   Defining clear data stewardship and ownership for the customer master data.

4. D

   Establishing a Center of Excellence (CoE) to oversee integration standards and changes.