Salesforce Integration Interview Questions and Answers Part-1

1) What are the main differences between REST and SOAP APIs in Salesforce, and when would you choose one over the other?

Differences between REST and SOAP APIs:

Format and Simplicity:

REST API: Supports both JSON and XML formats. It is lightweight, easy to use, and well-suited for modern web and mobile applications.

SOAP API: Supports only XML format, which can be more complex to handle.

Protocol and Methods:

REST API: Uses standard HTTP methods such as GET, POST, PUT, DELETE, etc.

SOAP API: Relies on a strict XML messaging protocol and includes a WSDL (Web Services Description Language) file for communication.

When to Choose:

Choose REST API when simplicity, speed, and modern formats like JSON are needed.

Choose SOAP API when integration demands more robust error handling, advanced security, or backward compatibility with older systems.

2) What is Salesforce Connect, and in what scenarios would you recommend using it for integration?

Salesforce Connect is a feature that allows users to access and display external data within Salesforce without storing it in Salesforce databases. It uses external objects to map to external data tables and accesses data on demand in real time.

Scenarios for Using Salesforce Connect:

1. Large Data Volumes: When you have large datasets that you don't want to replicate in Salesforce.

2. Real-Time Data Access: When you need real-time access to the latest external data instead of working with stale data copies.

3. Efficient Data Retrieval: When only small amounts of data are needed at a time, minimizing the need for storage and replication.

Advantages:

• Avoids data redundancy.
• Ensures up-to-date and accurate information.
• Simplifies integration with minimal data storage overhead.

Example Use Case: A company might use Salesforce Connect to access customer data stored in an external ERP system, ensuring sales teams always have the most up-to-date order and account details without duplicating that data in Salesforce.

3) What is the Bulk API in Salesforce, and when should it be used?

The Bulk API is designed for handling large-scale data operations asynchronously. It supports insert, update, delete, upsert, and query operations in batches, making it ideal for processing thousands or millions of records efficiently.

When to Use:

• When working with large data sets (e.g., over 2,000 records).
• For data migrations or regular bulk updates.
• To optimize performance and avoid API call limits.

4) What is the Streaming API, and give one example of use case?

The Streaming API enables real-time event streaming using push technology. It supports events like PushTopic, platform events, Change Data Capture, and generic events.

Use Case: A logistics company might use the Streaming API to push real-time updates about shipment status changes from Salesforce to a mobile app used by delivery drivers.

5) What is a Connected App in Salesforce, and why is it important for integration?

A connected app in Salesforce is designed to enable external applications to integrate with Salesforce APIs securely. For example:

• To use OAuth authorization for external apps, configure the connected app with appropriate OAuth settings.
• For SAML single sign-on (SSO) flows, configure SAML settings.

6) How to determine if your org is an owner or consumer of a Connected App?

As a connected app owner, your Salesforce organization built the app. You can edit the app’s characteristics and manage its access policies.

As a connected app consumer, your organization installed the app from the AppExchange Marketplace or as a managed package from a third-party vendor’s website. You can only edit the app’s access policies

7) What permissions are required to create, update, or delete a connected app in Salesforce?

To manage connected apps, a user needs the Customize Application permission, along with either:

• Modify All Data or
• Manage Connected Apps permissions.

8) What is callback URL?

A callback URL is the URL that is invoked after OAuth authorization for the consumer (connected app). In some contexts, the URL must be a real URL that the client’s web browser is redirected to. In others, the URL isn’t actually used, but the value between your client app and the server (the connected app definition) must be the same.

9) What does the "Token Valid for" setting in a Salesforce connected app define, and what are the configurable options for its duration?

The "Token Valid for" setting defines the duration for which an OAuth token(such as the access token) remains valid in Salesforce. The duration can be configured between 1 minute and 720 minutes (12 hours), with the default being 120 minutes (2 hours). Shorter durations enhance security by limiting token misuse, while longer durations provide convenience in trusted systems.

Gain a deep understanding of Salesforce integration, from creating and configuring Connected Apps to mastering advanced topics like OAuth flows, SAML-based Single Sign-On, and Streaming APIs. Our PDF course combines practical examples, real-time scenarios, and integration patterns to equip professionals with the skills needed to streamline processes and enhance productivity. Tailored for those with 2–8 years of experience, it’s your guide to unlocking seamless connectivity between Salesforce and other systems.

Link to course : Mastering Salesforce Integration