1. Evaluate the Current System Landscape Evaluate the Current System Landscape
8%
- 1.1Given a set of business requirements, identify the current system landscape and determine what standards, limitations, boundaries, and protocols exist.
- 1.2Given an existing system landscape, analyze for constraints and/or pain-points to satisfy a business requirement(s).
- 1.3Given a set of requirements, evaluate the authentication and authorization needs based on the system landscape.
2. Evaluate Business Needs Evaluate Business Needs
11%
- 2.1Given a use case, identify functional and non-functional requirements needed for integration.
- 2.2Based on a given integration requirement, identify and classify data into Confidential/Secure/Public.
- 2.3Given a use case, identify key factors for CRM success that should be included as integration requirements.
- 2.4Given a use case, identify the business growth and regulatory factors that can impact choice of integration solutions.
3. Translate Needs to Integration Requirements Translate Needs to Integration Requirements
22%
- 3.1Given an existing system landscape diagram, create an inventory of the systems and integration patterns.
- 3.2Given a use case and business process, evaluate system and process constraints.
- 3.3Given a use case, identify integration security/authentication/authorization requirements.
- 3.4Given a use case, identify performance needs (volumes, response times, latency) and propose appropriate integration solutions that will meet business requirements.
4. Design Integration Solutions Design Integration Solutions
28%
- 4.1Given a use case, identify the integration pattern that meets business requirements.
- 4.2Given a use case, define the components which create a solution that meets business requirements.
- 4.3Given a use case, identify the trade-offs, limitations, and constraints that meet the proposed solution.
- 4.4Given a use case that includes technical requirements, constraints, or drivers, specify the appropriate Salesforce application programming interface(s) (API) for the proposed solution.
- 4.5Given a use case that includes technical requirements, constraints, or drivers, determine the standards, components, techniques, and security mechanism that should be used.
5. Build Solution Build Solution
23%
- 5.1Given a use case that includes technical requirements, constraints, or drivers, identify the considerations when designing and implementing an API(s), both Salesforce as an API provider and Salesforce as an API consumer.
- 5.2Given a use case, identify the considerations when choosing the right option in making an outbound call to an external system.
- 5.3Given a use case, describe what should be considered when building a scalable solution.
- 5.4Given a use case, determine error handling for different integration options.
- 5.5Given a use case, create a security solution for inbound or outbound integrations.
- 5.6Given a use case, identify the factors needed to build resilience in an integration solution for system updates.
6. Maintain Integration Maintain Integration
8%
- 6.1Given an integration maintenance use case, identify performance monitoring needs for integration requirements.
- 6.2Given a use case, identify the appropriate error handling, escalation, and recovery procedures for a failed integration.
- 6.3Given a use case, identify reporting needs for integration monitoring.