Salesforce Platform Administrator II

Least privilege is easier to keep when permissions are modular. You build custom profiles, compose permission sets and groups, mute permissions where needed, and secure fields so each user holds only what their work requires.

• Minimum-access profiles
• Permission sets and permission set groups
• Muting permissions inside a group
• Field-level security and its limits
• Object and system permissions in practice
• Auditing who holds a permission

You build A permission model built from permission set groups, with a report of who holds what.

Who may log in, and how, matters as much as what they see. You configure single sign-on, multi-factor authentication, login policies and sessions, and troubleshoot logins for a business with several identity needs.

• My Domain and login configuration
• Single sign-on with SAML
• Multi-factor authentication policies
• Login IP ranges, hours and session settings
• Login flows for extra checks
• Diagnosing a failed login

You build A login policy for three user groups, with single sign-on and multi-factor rules.

A weak data model makes everything else harder. You choose between relationship types, model many-to-many links, add formulas and roll-ups, and use validation to keep data right as the business grows.

• Lookup and master-detail relationships compared
• Junction objects for many-to-many data
• Roll-up summary and formula fields
• Validation rules that help rather than block
• Record types, picklists and page layouts
• Field history and its limits
• Documenting the model with Schema Builder

You build A data model for a subscription business, built and documented.

Complex requirements still need simple screens. You build Lightning apps and record pages that adapt to the user, add guidance for each stage of a process, and set up the console for people who work many records at once.

• Lightning apps and navigation
• Dynamic forms and dynamic actions
• Path and guidance for success
• Utility bar and console configuration
• Compact layouts and mobile considerations

You build A Lightning app with role-specific record pages and guided stages.

Flow handles most business logic without code. You build record-triggered, screen and scheduled flows that handle branching, loops and related records, and design them to stay inside platform limits as volume grows.

• Choosing the right flow type
• Record-triggered flows before and after save
• Screen flows for guided work
• Loops, collections and bulk-safe design
• Subflows and reuse
• Scheduled flows and approvals
• Fault paths and error messages

You build A set of flows that automate a multi-step approval and keep related records in sync.

When automation misfires, you need to find out why. You debug flows step by step, read error emails and logs, understand the order Salesforce runs its logic, and fix conflicts between automations that overlap.

• Debugging a flow in Flow Builder
• Reading flow errors and interview details
• Order of execution
• Finding conflicts between flows and validations
• Using debug logs
• Limits that surface as errors

You build A troubleshooting record for three failing automations, each traced to its cause.

After a change, someone will ask who did it and when. You use the setup audit trail, login history and field tracking to answer, check org health, and set up routines that catch problems before users report them.

• Setup audit trail
• Login history and user activity
• Field history and tracking
• Org health and security checks
• System overview and usage limits
• Alerts for org changes that matter

You build A monitoring routine with a one-page audit of a recent change.

The cloud applications are where advanced configuration shows. You set up sales processes, forecasting and products, then service channels, entitlements, routing and the service console to meet the needs of larger teams.

• Sales processes, teams and forecasting
• Products, price books and quotes
• Case management and routing
• Entitlements and milestones
• Knowledge and the service console
• Where Agentforce Sales and Service fit

You build A configured sales and service setup for one business scenario.

Reports are only as good as the data under them. You manage duplicates, volume and quality, then build reports and dashboards that answer business questions for different audiences without exposing the wrong records.

• Matching rules, duplicate rules and merge behavior
• Data quality checks and cleanup
• Working with large data volumes
• Custom report types and joined reports
• Dashboards with dynamic running users
• Bucketing, cross filters and formulas in reports

You build A data quality plan and a dashboard that answers one executive question.

Changes should reach production by a controlled route. You choose sandbox types, refresh and template them, and deploy with change sets and release tooling so every release is tested, reversible and recorded.

• Sandbox types and what each is for
• Refreshing and templating sandboxes
• Change sets and deployment connections
• DevOps tooling for administrators
• Testing a release before it ships
• Planning rollback

You build A release plan that moves a set of changes from sandbox to production.

Take a messy requirement and shape the answer. You choose the access model, data model, automation and release path, document the trade-offs, and defend the design to the people who must run it.

• Reading a complex set of requirements
• Choosing declarative approaches that scale
• Designing access, data and automation together
• Planning release and monitoring
• Presenting trade-offs to stakeholders

You build A design document for a complex org, with access, automation and release plans.