Practice Test Geeks(SLM) Salesforce Loyalty Management Certification Practice Test
← All SLM Flashcard Decks

Integration Design Flashcards

7 cards from real SLM practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.

Read the first 7 Integration Design flashcards as text

  1. A nightly batch job must sync 500,000 loyalty transaction records from an external data warehouse into Salesforce. Which integration approach is most appropriate?

    Answer: Bulk API with batch data synchronization pattern

    The Bulk API is optimized for high-volume data loads and the batch synchronization pattern is ideal for nightly large-scale data transfers.

  2. Which Salesforce Loyalty Management API endpoint is used by an external POS system to accrue points for a member transaction?

    Answer: /services/data/vXX.0/loyalty-programs/{programName}/members/{membershipNumber}/transaction-journals

    The Transaction Journals resource under a specific member and program is the standard endpoint for recording point accrual events via the Loyalty Management API.

  3. An integration must handle cases where the external loyalty partner API is temporarily unavailable. Which Apex pattern best addresses this?

    Answer: Exponential backoff retry logic using Queueable Apex

    Queueable Apex supports chaining and retry logic, and exponential backoff prevents overwhelming the external system during recovery.

  4. Change Data Capture (CDC) for LoyaltyMemberCurrency records is enabled. What can an external system use to receive these change notifications?

    Answer: Subscribing to the /data/LoyaltyMemberCurrencyChangeEvent channel via CometD

    CDC publishes change events to a channel that external systems subscribe to via CometD or Bayeux protocol, enabling near real-time data sync.

  5. A loyalty integration uses MuleSoft as the middleware layer. What is the primary architectural benefit of this approach over direct Salesforce-to-external API calls?

    Answer: It provides a centralized integration layer for protocol transformation, routing, and error handling

    MuleSoft acts as an ESB/iPaaS layer providing centralized transformation, orchestration, and error handling that decouples Salesforce from external systems.

  6. What is the maximum number of callouts allowed within a single Salesforce transaction, which affects loyalty integration design?

    Answer: 100 callouts per transaction

    Salesforce enforces a limit of 100 callouts per transaction, which must be considered when designing bulk loyalty point accrual integrations.

  7. When designing a loyalty integration that calls out from an Apex trigger, which critical restriction must the architect consider?

    Answer: Callouts cannot be made from triggers that fire synchronously within a DML operation

    Salesforce does not allow HTTP callouts directly from synchronous Apex triggers; instead, @future or Queueable Apex must be used for asynchronous callouts.