Salesforce Platform Administrator — Practice Questions and Mock Exam

The Setup menu as a discipline. Company-level settings (business hours, fiscal year, currency, defaults); the declarative user-interface layer — UI/UX settings, list views, the app menu, global actions and the Lightning App Builder; and the whole user lifecycle, where the exam repeatedly rewards knowing that a user is deactivated and never deleted. The security half is the heavier half: org-level controls such as the Setup Audit Trail, session settings, login hours and identity verification, then the sharing model itself — org-wide defaults, the role hierarchy, sharing rules, public groups, teams and report/dashboard folder access — and finally the profile-versus-permission-set judgement call, including permission set groups and muting.

The data model as an administrator builds it. Standard objects and the relationship types between them — lookup, master-detail and the junction object that turns two master-details into a many-to-many — plus record types and Schema Builder. Then page layouts and fields, on custom objects as much as standard ones, and, in the part candidates most often under-read, the consequences of deleting a field that a roll-up summary, a cross-object formula, a picklist dependency or a relationship still depends on. It closes on assigning layouts, Lightning page visibility, business processes and record types.

Sales Cloud from the administrator's side. The sales process end to end — leads, opportunities and path — and the productivity layer around opportunities: forecasting, territory management, opportunity scoring and grading, lead scoring, the home-page assistant and the Einstein features for sales. The marketing half is lead automation and campaign management: lead assignment rules, lead conversion and the mapping it performs, campaigns and campaign members.

Service Cloud at administrator depth rather than agent depth. What case management can do — the case object, queues and case assignment rules — and how to automate it: support processes, auto-response rules, escalation rules and the Einstein features for service. Small in weight, but it shares its machinery with the Automation section, and the same assignment-rule engine drives both leads and cases.

The features end users touch every day and administrators configure. Activity management (tasks and events); Chatter, including groups, who may access them and how internal and external users differ; the Salesforce mobile app, from the Lightning pages it renders through the app menu, visibility and branding to building a launchpad; and AppExchange, at awareness level — managed versus unmanaged packages, who may publish, and what appears on AgentExchange.

The largest section on the exam. First, moving data: importing and updating, transferring and mass-deleting, exporting, archiving and backing up, and knowing when the Import Wizard is the right tool and when Data Loader is. Then keeping it clean, with duplicate and matching rules and validation rules. Then reporting: report and report-type options, joined objects, records with and without a matching related record, formulas, buckets, grouping and chart settings — followed by the point that separates administrators from report builders, namely how the org's sharing model and folder structure decide what a report actually shows. Dashboards close it out, including dynamic dashboards, running-user settings, subscriptions, refresh schedules and per-edition limits.

Choosing the automation tool and then configuring it. The choice comes first — escalation rules, case and lead assignment rules, the default automation user, and the AI options — and only then Flow itself — record-triggered flows, screen flows and autolaunched flows — plus the order of execution that decides when each one runs relative to validation rules, triggers and roll-up summaries. Approval processes finish the section: approver criteria, approvals and rejections.

The newest section of the blueprint and the reason the credential was rebuilt. What Agentforce is and when an agent is the right answer at all, plus the security and permission questions an administrator has to answer before one runs — including how to troubleshoot an agent that cannot see what it needs. The second objective is Agent Builder as a maintenance surface: installing, updating and maintaining prompts and instructions, light testing, and the conversation preview.

Select the single answer that best meets the question’s requirements.