• Cert++
  • Practice
  • Certle
  • Review
  • Tracks
  • Checklist
  • Guides
  • Upgrade
Cert++
  1. Home
  3. Platform Administrator II

Platform Administrator II

Checklist progress

0/215Learned

Platform Administrator II

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

Checklist progress

0/215Learned

  • Organization-wide defaults versus role hierarchy access
  • Field-level security versus page layout visibility
  • Grant Access Using Hierarchies on custom objects
  • Controlled by Parent access on child records
  • Sharing rules as additive record access
  • Owner-based versus criteria-based sharing rules
  • Manual sharing behavior on ownership transfer
  • Implicit sharing on parent-child records
  • Account team access versus consolidated record access
  • Report and dashboard folder sharing
  • Email template folder access
  • Territory Management default record access
  • Territory membership versus role hierarchy access
  • Standard versus custom profile editability
  • Additive permission set grants versus profile baseline
  • When to use a permission set instead of a new profile
  • Profile-only settings versus permission set capabilities
  • Permission set groups for job functions
  • Session-based permission sets for temporary access
  • When to use delegated administration
  • Delegated administration capabilities and limits
  • Organization versus profile password policies
  • Organization versus profile login hours
  • Trusted IP ranges versus profile login IP ranges
  • Identity verification and device activation
  • Multi-factor authentication requirements
  • Session security and high-assurance sessions
  • My Domain login policies
  • Freezing versus deactivating a user
  • SAML single sign-on as service provider
  • Delegated authentication versus SAML
  • Social sign-on versus single sign-on
  • Login flows after authentication
  • Certificate-based user authentication
  • Business accounts versus Person accounts
  • Person account enablement prerequisites
  • Business account to Person account conversion
  • Contacts to Multiple Accounts versus a single parent account
  • Contacts to Multiple Accounts setup
  • Direct versus indirect account-contact relationships
  • Contacts to Multiple Accounts considerations
  • Sharing implications of Person accounts and related contacts
  • Custom objects versus fields on standard objects
  • Master-detail versus lookup for object extension
  • Lookup field deletion behaviors
  • Converting master-detail relationships to lookups
  • Multilevel master-detail and subdetail records
  • Junction objects for many-to-many models
  • Junction object primary master and sharing
  • Related lists for related object data
  • Record types for picklists and business processes
  • Record type profile availability and defaults
  • Schema Builder for data model changes
  • Object Creator for extending objects
  • Lightning App Manager branding and navigation
  • Lightning page types in App Builder
  • Lightning App Builder versus page layout editor
  • Standard Lightning page components
  • Lightning page activation and assignment
  • Dynamic Forms versus Record Detail
  • Dynamic Forms migration and limitations
  • Dynamic related lists in Lightning App Builder
  • Lightning console apps versus standard apps
  • Lightning pages for console apps
  • Lightning page Analyze button
  • Setup Audit Trail for configuration change history
  • Debug logs for transaction and automation troubleshooting
  • Field data classification for compliance policies
  • Field Audit Trail for compliance retention
  • Shield Platform Encryption for data at rest
  • Deterministic versus probabilistic encryption
  • Platform Encryption key management
  • Sandbox data masking and anonymization
  • Data Mask masking types
  • Sandbox seeding versus full-copy masking
  • Security Health Check review and remediation
  • Reviewing effective user access
  • Release Updates affecting system access
  • Troubleshooting unexpected access from security settings
  • Products versus price books in the sales catalog
  • Standard Price Book versus custom price books
  • Opportunity price book and opportunity products
  • Quantity versus revenue product schedules
  • Quotes created from opportunities
  • Quote sync with opportunity products
  • Order Settings and enabling orders
  • Creating orders from quotes and opportunities
  • Activated orders versus reduction orders
  • Removing products and price books
  • Pipeline forecast types
  • Forecast categories and stage mapping
  • Forecast quotas, periods, and fiscal year
  • Forecasts hierarchy for role-based rollups
  • Manager judgments in pipeline forecasts
  • Pipeline forecast submissions
  • Territory types and hierarchy
  • Territory model states
  • Account assignment rules versus manual assignment
  • Opportunity assignment to territories
  • Territory hierarchy versus role hierarchy
  • Territory administration permissions
  • Role-based versus territory-based forecasts
  • Territory forecast manager assignment
  • Lightning Knowledge enablement
  • Lightning Knowledge user access
  • Knowledge article record types and page layouts
  • Data category groups and category hierarchy
  • Data category visibility
  • Knowledge article lifecycle
  • Knowledge article import
  • Entitlements versus entitlement processes versus milestones
  • Entitlement models for accounts, contacts, assets, and contracts
  • Entitlement Management enablement and lookup filters
  • Creating and maintaining entitlement records
  • Service contracts with related entitlements
  • Entitlement templates for products and assets
  • Entitlement process timelines, entry, and exit
  • Support milestones on entitlement processes
  • Milestone warning, violation, and success actions
  • Business hours in entitlement milestone timing
  • Case and work order movement through entitlement processes
  • Entitlement verification and Milestone Tracker on cases
  • Entitlement process versioning
  • Agentforce Service Console workspace
  • Case Feed actions for agent-customer communication
  • Chat and Enhanced Chat for customer conversations
  • Omni-Channel routing and agent capacity
  • Experience Cloud sites for customer self-service
  • Site Case Feed for Experience Cloud members
  • Sales, Service, Marketing, and Commerce product fit
  • Salesforce edition and suite implications
  • Salesforce Foundations bundled capabilities
  • Experience Cloud as a platform extension
  • Data quality assessment and management plans
  • Field data types for data quality
  • Picklist administration for data quality
  • Validation rules versus formula fields for data quality
  • Matching rules versus duplicate rules
  • Merging duplicate records
  • Duplicate jobs and duplicate record sets
  • Record data enrichment tools
  • In-org archival and mass delete
  • Custom report types versus standard report types
  • Cross filters versus field filters
  • Report bucket fields versus formula fields
  • Custom summary formulas versus row-level formulas
  • Complex report and dashboard charting
  • Joined reports versus a single report type
  • When to use reporting snapshots
  • Dashboard filters versus cloned dashboards
  • Dynamic dashboards versus specified running user
  • Data backup versus data archive
  • Native data export versus third-party backup
  • Data warehouses and data lakes for off-platform data
  • Big objects versus Salesforce Connect versus Heroku Connect
  • Salesforce Connect adapter selection
  • External lookup versus indirect lookup relationships
  • Salesforce Connect feature support and limitations
  • Data Import Wizard versus Data Loader
  • Data Import Wizard matching options
  • External ID matching for upserts
  • Relating imported records with External IDs
  • Sandbox types and what they copy from production
  • Sandbox refresh implications
  • Sandbox copy versus change set deployment
  • Managed versus unmanaged packages
  • Change sets versus packages for unrelated orgs
  • Deployment connections for change sets
  • Outbound versus inbound change sets
  • Permissions to upload and deploy change sets
  • Components available in change sets
  • Change set coverage for data and destructive changes
  • Dependent components in change sets
  • Profile settings and permission sets in change sets
  • Inbound change set validation versus deployment
  • Apex tests when deploying change sets

Given a complex scenario, determine the solution using the best tool or combination of tools to solve a business problem

0/11

Flow versus Process Builder and Workflow Rules

Learn this concept
Unseen

Flow versus Apex for business automation

Learn this concept
Unseen

Screen Flow versus record-triggered Flow

Learn this concept
Unseen

Record-triggered versus scheduled Flow

Learn this concept
Unseen

Formula fields versus Flow

Learn this concept
Unseen

Formula fields combined with Flow

Learn this concept
Unseen

Approval processes versus Flow for record review

Learn this concept
Unseen

Classic approval processes versus Flow approvals

Learn this concept
Unseen

Approval processes combined with Flow

Learn this concept
Unseen

Flow Orchestration versus Flow Builder

Learn this concept
Unseen

Migrate to Flow versus rebuilding automation

Learn this concept
Unseen

Given a scenario, identify the appropriate tool or method for troubleshooting declarative automation

0/10

  • Flow tests versus Flow Debugger
  • Flow fault paths and error emails
  • Monitoring flow and orchestration runs
  • Debug logs for declarative automation
  • Declarative automation that never ran
  • Delayed and waiting automation diagnosis
  • Process Builder and workflow failure diagnosis
  • Classic approval process troubleshooting
  • Flow approval process troubleshooting
  • Orchestration run details and debug modes

Given a scenario, explain the capabilities and limitations of each declarative automation tool

0/8

  • Screen flow input, navigation, and Lightning page placement
  • Before-save versus after-save record-triggered flow capabilities
  • Flow create update and delete versus Workflow and Process Builder
  • Scheduled paths versus time-dependent workflow actions
  • Workflow rule remaining actions and limitations
  • Classic approval process steps actions and record locking
  • Flow approval processes versus Classic approval processes
  • Flow interview bulkification and transaction limits

Understand the implications of the order of execution when using automation tools

0/10

  • System validation versus custom validation in the save order
  • Before-save versus after-save record-triggered Flow timing
  • Duplicate-rule block actions versus later automation
  • Assignment and auto-response rules versus later automation
  • Record-triggered Flow trigger order on one object
  • Process Builder and after-save flows in the late save window
  • Workflow field updates re-entering the save order
  • Roll-up summary parent updates re-entering the save order
  • Approval field updates re-entering the save order
  • After-commit emails and scheduled paths versus in-save automation

Prepare for the Exam

Play Today's Certle
Back to track

Study Community

Ask questions and get the latest info from other Platform Administrator II studiers. 593 members and growing.

Go to Discord

Formula fields combined with Flow

Explainer

Learn More

Practice Question

Keep going

Next conceptApproval processes versus Flow for record review

Checklist progress

0/215 (0%)

0 of 215 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 Administrator II studiers. 593 members and growing.

Go to Discord

Explainer

A formula field calculates its value from other fields, expressions, or values instead of storing something a user typed. Flow can use formulas of its own to decide whether a record-triggered flow starts, to filter a collection, or as a reusable Formula resource, and it can also read formula fields already on the record. Use that pairing when you need a calculated value plus automation, but Flow evaluates record formula fields the way Salesforce Classic does, and a formula field that shows new data because another object was updated does not always start the flow.

Core information
  • A formula is an algorithm that derives its value from other fields, expressions, or values, so a formula field automatically calculates a result rather than storing a value someone entered.
More details and nuances
  • Record formula fields are evaluated in flows exactly as they are in Salesforce Classic. When a record formula field checks NOT(null/blank), it evaluates to FALSE.