Cert++
  1. Home
  3. Platform Foundations

Platform Foundations

Checklist progressProgress

0/133Learned

Platform Foundations Study Checklist
  • Platform Administrator
  • Platform App Builder
  • Platform Foundations
  • Platform Developer
  • Platform Administrator II
  • Agentforce Sales Consultant
  • Agentforce Service Consultant
  • Platform Data Architect
  • Platform Development Lifecycle and Deployment Architect
  • Platform Identity and Access Management Architect
  • Platform Integration Architect
  • Platform Sharing and Visibility Architect
  • Heroku Architect
  • B2C Solution Architect
  • Experience Cloud Consultant
  • Agentforce Field Service and Operations Consultant
  • Agentforce Nonprofit Consultant
  • Data 360 Consultant
  • Omnistudio Consultant
  • CRM Analytics and Einstein Discovery Consultant
  • Platform User Experience Designer
  • Platform Strategy Designer
  • B2C Commerce Developer
  • JavaScript Developer
  • Omnistudio Developer
  • Platform Developer II
  • Marketing Cloud Engagement Administrator
  • Marketing Cloud Engagement Specialist
  • Marketing Cloud Engagement Consultant
  • Agentforce Sales Foundations
  • Business Analyst
  • Marketing Cloud Engagement Developer
  • Marketing Cloud Engagement Foundations
  • Agentforce Specialist
  • Agentforce Life Sciences Consultant
  • B2B Commerce Administrator AP
  • B2B Commerce Developer AP
  • Agentforce Consumer Goods AP
  • Agentforce Financial Services AP
  • Agentforce Health AP
  • Agentforce Manufacturing AP
  • MuleSoft Integration Foundations
  • MuleSoft Developer
  • MuleSoft Developer II
  • MuleSoft Platform Integration Architect
  • MuleSoft Platform Architect
  • Tableau Desktop Foundations
  • Tableau Data Analyst
  • Tableau Consultant
  • Tableau Server Administrator
  • Tableau Architect
  • Slack Administrator

Checklist progressProgress

0/133Learned

Given a scenario, describe various resources available to learn and apply in-demand Salesforce skills

0/10

  • Trailhead as the Salesforce learning platform
  • Trailhead badges, trails and trailmixes
  • Superbadges versus standard badges
  • Trailhead Playground for hands-on practice
  • Trailblazer Community and Community Groups
  • Salesforce Help and documentation as a skills resource
  • Salesforce certifications and what they validate
  • Trailhead Academy for expert-led training
  • myTrailhead versus public Trailhead content
  • Driving company-wide Salesforce adoption with Trailhead

Given a use case, identify which Salesforce Customer 360 product offerings could be used

0/13

  • Customer 360 as an integrated family of Salesforce solutions
  • Sales Cloud (Agentforce Sales) for leads, opportunities and pipeline
  • Service Cloud (Agentforce Service) for case management and support
  • Marketing Cloud for personalized customer journeys
  • Commerce Cloud for online storefronts and digital shopping
  • Experience Cloud for customer, partner and employee sites
  • Slack for team collaboration connected to Salesforce
  • Tableau versus in-app reports and dashboards for analytics
  • MuleSoft for integrating Salesforce with other business systems
  • Data Cloud (Data 360) for unifying customer data from many sources
  • Agentforce AI agents versus Prompt Builder for AI use cases
  • Nonprofit Cloud for fundraising and program management
  • AppExchange for extending Salesforce with prebuilt solutions

Describe how companies use Salesforce

0/11

  • CRM and Salesforce as a customer success platform
  • Real-time visibility and collaboration benefits of Salesforce
  • Connecting sales and service teams for a 360-degree customer view
  • Salesforce Platform custom apps for HR, IT and other departments
  • Multitenant cloud architecture and automatic upgrades
  • Salesforce orgs and types of instances
  • Salesforce core values
  • The 1-1-1 model and business as a platform for change
  • Makeup of the Salesforce ecosystem and Trailblazers
  • Salesforce partners and how they help customers
  • Customer success stories and industry guides for use-case research

Differentiate between various job roles and career paths in the Salesforce ecosystem

0/11

The Salesforce Economy and demand for Salesforce talent

Learn this concept
Unseen

In-house customer roles versus partner-hired roles

Learn this concept
Unseen

Salesforce administrator role and core responsibilities

Learn this concept
Unseen

Business analyst versus administrator role

Learn this concept
Unseen

Requirements gathering and user stories

Learn this concept
Unseen

Salesforce developer role versus declarative admin work

Learn this concept
Unseen

Salesforce architect role

Learn this concept
Unseen

Salesforce designer role

Learn this concept
Unseen

Sales and marketing career paths using Salesforce

Learn this concept
Unseen

Role-based Salesforce certifications

Learn this concept
Unseen

Resources for researching and building a Salesforce career path

Learn this concept
Unseen
  • Navigation vocabulary for apps, tabs, objects and records
  • App Launcher for switching apps and finding items
  • Navigation bar and console navigation menu within an app
  • Utility bar for quick access to productivity tools
  • Home page tools for daily priorities
  • Global search for finding records across objects
  • Recently viewed records and lists
  • Favorites as shortcuts to frequently used pages
  • Record page areas for locating record details and activity
  • Related lists for viewing associated records
  • Custom list views for filtering records
  • Private versus shared list views and record access
  • Kanban view for visual record tracking
  • Recycle Bin for finding and restoring deleted records
  • In-app Help and page-specific guidance
  • Setup and Setup Home as the org customization hub
  • Setup menu categories and the work each one covers
  • Quick Find versus browsing the Setup menu
  • Object Manager for standard and custom object settings
  • Custom fields versus custom objects for new business data
  • Lightning App Builder and the Lightning pages it customizes
  • Page layout editor versus Lightning App Builder
  • Compact layouts and the record highlights panel
  • App Manager and custom Lightning apps
  • Admin-defined app navigation versus personal navigation bar changes
  • Personal settings and profile page versus Setup
  • Key Setup pages for users, org details and history
  • Objects, fields, and records in the Salesforce data model
  • Standard objects versus custom objects
  • Core standard objects and the business records each one tracks
  • Lookup, master-detail and hierarchical relationships
  • Account and contact relationship
  • Contacts to Multiple Accounts
  • Leads versus opportunities in the sales process
  • Lead conversion and the records it creates
  • Opportunity contact roles and related Sales Cloud objects
  • Cases and their links to accounts and contacts
  • Account hierarchies and parent accounts
  • Account teams for coworker roles and access on an account
  • Business accounts versus person accounts
  • Schema Builder for viewing object relationships
  • Levels of data access control in Salesforce
  • Object permissions and object-level access
  • Profiles versus permission sets for granting access
  • Permission set groups for job-based access bundles
  • Field-level security versus page layouts for hiding fields
  • Org-wide default settings for baseline record access
  • Role hierarchy and access to subordinates' records
  • Sharing rules as automatic exceptions to org-wide defaults
  • Public groups versus personal groups in sharing
  • Manual sharing of individual records
  • Layering org-wide defaults with record sharing tools
  • Record types for process-specific picklist values and layouts
  • Dynamic Forms for field placement and visibility on record pages
  • Choosing a field data type to fit the data
  • Picklists for standardized field values
  • Dependent picklists and controlling fields
  • Default field values for new records
  • Validation rules and required fields for data entry standards
  • Formula fields for automatically calculated values
  • Lookup filters for limiting related record choices
  • Duplicate management with matching and duplicate rules
  • Purpose of a Salesforce report
  • Where users find, search and create reports
  • Role of the report type in a report
  • Standard versus custom report types
  • Report builder panes and report preview
  • Tabular, summary and matrix report formats
  • Joined reports for multiple views in one report
  • Report filters and filter options
  • Formula fields versus report formulas for calculated values
  • Drill-down and inline editing on the report run page
  • Report charts and embedded report charts
  • Report folders and who can see a report
  • Report subscriptions and scheduled email delivery
  • Exporting report data outside Salesforce
  • Turning a business question into report requirements
  • Purpose of a Salesforce dashboard
  • Where dashboards are created, found and displayed
  • Source reports behind dashboard widgets
  • Dashboard widget types and when to use each
  • Report charts versus dashboards
  • Dashboard filters versus report filters
  • Dashboard folders and sharing access
  • Dashboard running user and data visibility
  • Dynamic dashboards for per-viewer data
  • Refreshing dashboard data
  • Dashboard subscriptions and scheduled email delivery

Prepare for the Exam

Play Today's Certle
Back to track

Study Community

Ask questions and get the latest info from other Platform Foundations studiers.

Go to Discord
  1. Platform Foundations Checklist
  3. Salesforce Ecosystem

In-house customer roles versus partner-hired roles

Explainer

Learn More

Practice Question

Keep going

Next conceptSalesforce administrator role and core responsibilities

Checklist progress

0/133 (0%)

0 of 133 concepts learned

Tip: You can filter concepts by status.

Prepare for the Exam

Play Today's Certle
Back to track

Study Community

Ask questions and get the latest info from other Platform Foundations studiers.

Go to Discord
Close
  1. Platform Foundations Checklist
  3. Salesforce Ecosystem
In-house customer roles versus partner-hired roles

Explainer

Learn More

Practice Question

Keep going

Next conceptSalesforce administrator role and core responsibilities

Explainer

The Salesforce ecosystem is the team that makes Salesforce work: Salesforce itself, its customers, and its partners. Customers employ their own Salesforce professionals, such as administrators and developers, to manage and improve their Salesforce instance. Partners hire professionals such as business analysts, consultants, and architects to help customers get more out of Salesforce. Knowing which side a role usually sits on tells you where a company should turn for a given need.
Core information
  • The Salesforce ecosystem has three members: Salesforce (the company), customers (companies of all sizes that use Salesforce products), and partners (Salesforce-certified experts who work with customers across products and industries).
More details and nuances
  • In-house roles and partner roles complement each other rather than compete: customers need their own professionals to manage their instance, and more than 85% of customers also work with partners.

Explainer

The Salesforce ecosystem is the team that makes Salesforce work: Salesforce itself, its customers, and its partners. Customers employ their own Salesforce professionals, such as administrators and developers, to manage and improve their Salesforce instance. Partners hire professionals such as business analysts, consultants, and architects to help customers get more out of Salesforce. Knowing which side a role usually sits on tells you where a company should turn for a given need.
Core information
  • The Salesforce ecosystem has three members: Salesforce (the company), customers (companies of all sizes that use Salesforce products), and partners (Salesforce-certified experts who work with customers across products and industries).
More details and nuances
  • In-house roles and partner roles complement each other rather than compete: customers need their own professionals to manage their instance, and more than 85% of customers also work with partners.