General

Question 1

What options are supported for integration at the Data layer?

Answer 1

• Native Rest and SOAP (Enterprise & Partner) web services.
• Bulk API (Rest based)
• Streaming API
• Change Data Capture
• Platform Events
• OData (2.0 & 4.0)

Question 2

Why SOAP over Rest for certain use cases?

Answer 2

• Support for more fine-grained security using WS-Security. It provides support identity verification through intermediaries rather than just point to point as provided by SSL which is available for both SOAP and Rest.
• SOAP offers a built-in retry mechanism.
• It can be used on all kinds of transport layer protocols such as HTTP, SMTP, FTP, etc.

Question 3

Does SOAP/Rest support both asynchronous calls to Salesforce?

Answer 3

No, SOAP/Rest only supports synchronous calls to Salesforce.

https://developer.salesforce.com/docs/atlas.en-us.integration_patterns_and_practices.meta/integration_patterns_and_practices/integ_pat_remote_call_in.htm

Question 4

What are the typical use-cases for APEX Web Services ( Alternative to SOAP API)?

Answer 4

• Full transactional support is required (for example, create an account, contact, and opportunity all in one transaction).
• Custom logic must be applied on the Salesforce side before committing.

Question 5

Which API can be used to Publish events onto Platform events?

Answer 5

1. SOAP
2. Rest
3. Bulk API

Question 6

What are the various security considerations for various integrations?

Answer 6

1. the platform uses the logged-in user’s access rights (for example, profile settings, sharing rules, permission sets, and so on).
2. profile IP restrictions can be used to restrict access to the API for a specific IP address range.
3. Salesforce support SSL, 2-way SSL and TLS protocols.

Question 7

What are the contents of a digital certificate?

Answer 7

• Information about the subject a.k.a. Subject Name - “subject” refers to the site represented by the cert.
• Information about the certificate issuer/certificate authority (CA) - The CA is the body that issued and signed the certificate. More about this shortly
• Serial number - this is the serial number assigned by the issuer to this certificate. Each issuer must make sure each certificate it issues has a unique serial number.
• Version - the X.509 version used by a given certificate. These days, you’ll usually find version 3.
• Validity period - certs aren’t meant to last forever. The validity period defines the period over which the cert can still be deemed trustworthy.
• Signature - This is the digital signature of the entire digital certificate, generated using the certificate issuer’s private key
• Signature algorithm - The cryptographic signature algorithm used to generate the digital signature (e.g. SHA-1 with RSA Encryption)
• Public key information - Information about the subject’s public key. This includes:
  
  • the algorithm (e.g. Elliptic Curve Public Key),
  • the key size (e.g. 256 bits),
  • the key usage (e.g. can encrypt, verify, derive), and
  • the public key itself

A digital certificate primarily acts like an identification card; something like a driver’s license, a passport, a company ID, or a school ID. It basically tells other people who you are. So that, for example, when a user arrives at your site looking for yourdomain.com, your site’s digital certificate (a.k.a. cert) will help that user confirm whether he actually landed at yourdomain.com.

In addition, a cert also holds a copy of your site’s public key, which is used in encrypting data transmitted between your site and the user’s web client (in most cases, a web browser).

Question 8

When to use continution object for Request and Reply pattern?