Advanced Integration Patterns Flashcards

1
Q

Q. What are advanced integration patterns in Salesforce?

A

A. Advanced integration patterns define structured approaches to connecting Salesforce with external systems for scalability, efficiency, and maintainability.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Q. What are the key objectives of advanced integrations?

A
  • Ensure data consistency across systems
  • Optimize real-time and batch processing
  • Minimize API call limits and performance issues
  • Implement secure and scalable architectures
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Q. What are the main types of integration patterns in Salesforce?

A
  • Remote Process Invocation – Request & Reply
  • Remote Process Invocation – Fire & Forget
  • Batch Data Synchronization
  • Remote Call-In
  • UI Update Based on Data Changes
  • Event-Driven Architecture
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Q. What is the Request & Reply integration pattern?

A

A. A synchronous pattern where Salesforce sends a request to an external system and waits for a response before proceeding.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Q. When should you use Request & Reply?

A
  • Real-time interactions with external systems
  • When Salesforce needs immediate confirmation of a transaction
  • Payment processing & stock availability checks
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Q. What are the common technologies used in Request & Reply?

A
  • REST & SOAP APIs
  • OAuth & JWT for authentication
  • Named Credentials in Salesforce
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Q. What are the challenges of using Request & Reply?

A
  • High response time may slow down user interactions
  • Increased API call consumption
  • Error handling complexities
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Q. What is the Fire & Forget integration pattern?

A

A. A synchronous or asynchronous pattern where Salesforce sends a request to an external system but does not wait for a response.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Q. When should you use Fire & Forget?

A
  • Logging system events
  • Background data synchronization
  • Sending transactional emails to external systems
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Q. What are the advantages of Fire & Forget?

A
  • Faster processing time
  • Lower dependency on external system availability
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Q. What are the risks of Fire & Forget?

A
  • No immediate error handling
  • Data consistency issues if messages fail
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Q. What is Batch Data Synchronization?

A

A. A pattern that moves large volumes of data between Salesforce and external systems at scheduled intervals.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Q. When should you use Batch Data Synchronization?

A
  • When data consistency is required across systems
  • For nightly batch jobs or mass data migrations
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Q. What are common tools for batch synchronization?

A
  • Bulk API
  • ETL tools (MuleSoft, Informatica, Jitterbit)
  • Apex Batch Jobs
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Q. What are best practices for batch processing?

A
  • Use indexed fields for SOQL queries
  • Break large jobs into smaller batches
  • Monitor governor limits
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Q. What is the Remote Call-In pattern?

A

A. A pattern where an external system calls Salesforce APIs to fetch or modify Salesforce data.

17
Q

Q. When should you use Remote Call-In?

A
  • When external systems act as a data source
  • When integrating with ERP systems (SAP, Oracle, NetSuite)
18
Q

Q. What APIs are commonly used for Remote Call-In?

A
  • REST API (preferred for lightweight data retrieval)
  • SOAP API (used in legacy integrations)
  • GraphQL API (flexible data fetching)
19
Q

Q. What are best practices for Remote Call-In?

A
  • Use API rate limiting strategies
  • Implement OAuth authentication
  • Enable API logging & monitoring
20
Q

Q. What is the UI Update pattern?

A

A. A pattern where Salesforce UI automatically updates based on real-time data changes.

21
Q

Q. When should you use UI Update based on data changes?

A
  • Live dashboards
  • Real-time case updates in Service Cloud
22
Q

Q. What technologies enable UI updates in Salesforce?

A
  • Platform Events
  • Change Data Capture (CDC)
  • Streaming API
  • Lightning Message Service (LMS)
23
Q

Q. What is an event-driven architecture in Salesforce?

A

A. An asynchronous integration pattern where systems react to events instead of direct API calls.

24
Q

Q. What are common event-driven integration tools in Salesforce?

A
  • Platform Events (for cross-system communication)
  • Change Data Capture (CDC) (real-time data updates)
  • Streaming API (event subscriptions)
  • Pub/Sub API (scalable event messaging)
25
Q

Q. What are best practices for implementing event-driven architecture?

A
  • Minimize API polling by using event subscriptions
  • Use durable event subscriptions to avoid data loss
  • Implement error handling for message reprocessing
26
Q

Q. What is middleware in Salesforce integration?

A

A. A third-party platform that facilitates data exchange between Salesforce and external systems.

27
Q

Q. What are common middleware tools for Salesforce?

A
  • MuleSoft (Salesforce-owned)
  • Dell Boomi
  • Jitterbit
  • Zapier (lightweight automation)
28
Q

Q. What is message queueing in Salesforce integrations?

A

A. A buffering mechanism where messages are queued and processed asynchronously.

29
Q

Q. What message queuing systems integrate with Salesforce?

A
  • Amazon SQS (AWS Simple Queue Service)
  • Kafka (real-time event streaming)
  • RabbitMQ (message broker)
30
Q

Q. What is an API Gateway?

A

A. A centralized entry point for managing API requests between Salesforce and external systems.

31
Q

Q. What are the benefits of using an API Gateway?

A
  • Security enforcement (OAuth, JWT)
  • Rate limiting & traffic management
  • Caching for performance optimization
32
Q

Q. What is microservices architecture in Salesforce?

A

A. A design pattern where business logic is split into small, independent services communicating via APIs.

33
Q

Q. When should you use microservices with Salesforce?

A
  • When integrating multiple enterprise applications
  • For scalable, modular architectures
34
Q

Q. What are best practices for Salesforce integrations?

A
  • Choose the right integration pattern for the use case
  • Optimize API usage to stay within limits
  • Use event-driven architecture where possible
  • Implement robust error handling & logging
35
Q

Q. How can you monitor Salesforce integration performance?

A
  • Use Event Monitoring to track API usage
  • Enable Debug Logs for troubleshooting
  • Implement real-time alerts for API failures