| Objective | Weighting |
| Application Design | 5% |
| List and describe components of an application | |
| Describe the model-view-controller design paradigm | |
| Given a scenario, determine whether sufficient information is available to plan/build/design an application | |
| Overview of Force.com Platform | 5% |
| List and describe the steps required to design and deploy a successful application built using the declarative
capabilities of the Force.com platform | |
| List and describe the building blocks of an application provided by the Force.com platform | |
| Data Model | 32% |
| Describe how to create a functional data model for a business application | |
| Given a scenario, select the features required to create a functional data model for a business application | |
| Describe the properties and implications of choosing one object relationship type over another and
distinguish among relationship types | |
| Given a scenario, distinguish among object relationship types, describe how to create relationships, and
determine which relationship should be recommended | |
| List and describe the features used to set permission and data access in a custom app | |
| Given a scenario, select the appropriate feature (e.g., profiles, defaults, roles) to provide appropriate
permissions and data access in a custom app | |
| List and describe optional (Salesforce-enabled) features for managing the application (e.g., create audit
fields, encrypted fields, multicurrency) | |
| User Interface | 15% |
| List and describe the components of any Force.com application user interface (e.g., tabs, applications, detail
pages, list views) | |
| Given a scenario, determine the capabilities and constraints of the declarative framework for building a user
interface (e.g., what can and can’t be done in a page layout) | |
| Describe use cases for how Visualforce can extend the user interface in the declarative framework and when
to do so | |
| Describe the capabilities and functionality of Force.com Sites | |
| Business Logic | 23% |
| List and describe how to create formulas, validation rules, and workflow rules | |
| Given a scenario, determine which Force.com feature to use to solve a business requirement and/or describe
how to apply the solution | |
| List and describe the capabilities of the Force.com approval processes | |
| Given a scenario, select the appropriate features of Force.com approval processes to satisfy business
requirements | |
| List and describe the features of the Force.com platform for debugging and monitoring automated business
processes | |
| Describe use cases for extending business logic through Apex | |
| Data Management | 10% |
| List and describe the capabilities and constraints of import wizards | |
| List and describe the capabilities and constraints of API-based tools for managing data | |
| List and describe the functions of the Force.com data loader | |
| Describe use cases and functions of external IDs and upsert | |
| Given a scenario, determine appropriate uses of the GUI and command-line interface for the data loader | |
| Describe the characteristics of Force.com record IDs | |
| Reporting and Analytics | 10% |
| List and describe capabilities and constraints of reports and analytics of the Force.com platform | |
| Given a scenario, determine methods for analyzing and displaying data | |