SALESFORCE INTEGRATION CAPABILITIES ( Weighting 28% )
- In a given scenario, recommend when to use API-based integrations, such as SOAP, REST, Bulk, Streaming, Canvas, Workflow outbound, APEX (Callouts, @ future, etc.) and Lightning Connect to achieve business requirements.
- Compare and contrast the advantages and drawbacks (design trade-offs) of using API-based integrations such as SOAP, REST, Bulk, Streaming, Canvas, Workflow outbound, APEX (Callouts, @future, etc.) and Lightning Connect.
Integrating with Force.com Platform
Technical Library: Salesforce Integration
https://developer.salesforce.com/docs/atlas.en-us.api_asynch.meta/api_asynch/asynch_api_planning_guidelines.htm
Integration Architecture for the salesforce Platform
SALESFORCE INTEGRATION PATTERNS ( Weighting 17% )
- Provided an integration scenario, describe requirements and issues that the Architect must consider to select the right pattern (Layer, Timing, Direction, and Volume).
- In a customer scenario containing business requirements, summarize which implementation pattern will achieve those goals.
- Compare and contrast the advantages and drawbacks (design trade-offs) of using various patterns, such as: Remote Process Invocation—Request and Reply, Remote Process Invocation—Fire and Forget, Batch Data Synchronization, Remote Call-In, and UI Update Based on Data Changes.
Salesforce Backup and Restore Essentials Part 1
Salesforce Backup and Restore Essentials Part 2
ENTERPRISE INTEGRATION ARCHITECTURE CONCEPTS ( Weighting 15% )
- Given a customer scenario containing business requirements for integrating Salesforce with other enterprise back-office systems, recommend the appropriate integration architecture.
- Analyze and determine when and where to use data cleaning, standardization, deduplication, and data transformation as part of data integration.
- Analyze and determine the various considerations while performing data migration (including but not limited to: platform handle bulk data load vs SOAP data load, monitoring the data loads, and error handling).
Patterns of Enterprise Application Architecture
SALESFORCE INTEGRATION TESTING ( Weighting 10% )
- Given a software development lifecycle scenario, determine the timing, type, and sequence of testing activities that are needed for successful implementation.
- Given an integration scenario, determine the appropriate platform capability needed to meet the testing requirements.
INTEGRATING WITH FORCE.COM: SECURITY ( Weighting 15% )
- Given a scenario, determine the appropriate security strategy to meet the customer requirements.
TOOLS ( Weighting 10% )
- Given a scenario, determine the appropriate tools to meet the customer requirements.
- Given a scenario, analyze and recommend the appropriate tools by comparing the pros and cons to meet the business requirements.
MONITORING ( Weighting 5% )
- Given a scenario, identify, isolate, and recommend approaches for integration challenges.