Free Salesforce Certified Platform Administrator practice test: 30 questions with answers

Duplicate rules use matching rules to compare new or edited records with existing ones and warn or block the user. Sharing rules control access, record types control page and picklist options, and approval processes route records for decisions.

Data Loader handles large bulk jobs and supports upserts keyed on an external ID, so existing contacts are updated and new ones inserted. A report export is for reading data, email-to-case creates cases, and the home page displays records without loading any.

A Partial Copy sandbox includes the metadata plus a sample of production records, which suits realistic testing without the cost of a full copy. The developer sandboxes contain no production records, and a full sandbox copies everything rather than a sample.

The Accounts with or without opportunities report type includes accounts that have no related opportunities, so they appear with a zero total. An opportunities-based report would drop accounts that have none, and the other report types do not report opportunity amounts.

A bucket field groups values into labelled ranges inside the report, leaving the stored data unchanged. A formula field stores or displays a calculation on the record, a roll-up summary totals child records, and a validation rule checks values at save time.

A Private org-wide default restricts access to owners, and the role hierarchy automatically gives managers access to records owned by users below them. Public access exposes every record, the System Administrator profile bypasses sharing for every user, and per-user sharing rules need constant upkeep.

Field-level security on a profile or permission set controls whether a field is visible and editable for that group of users. Page layouts only arrange fields on screen, record types control picklists, and validation rules check data at save time rather than controlling who can see a field.

Field-level security set to read-only on the profile or permission set is the control that makes the field visible but not editable across the platform. A page layout only changes what is displayed, the organisation-wide default works at record level, and a validation rule blocks values rather than controlling access.

Login IP ranges on a profile restrict the addresses users can log in from. Session timeouts and password policies are other security settings, and trusted IP ranges for a connected app control API access rather than user login locations.

Permission sets add access on top of a user's profile, and they can be grouped into permission set groups for easier assignment. They do not replace profiles, they can be assigned to any user rather than only administrators, and login does not depend on holding one.

A master-detail relationship supports roll-up summary fields and makes the child inherit sharing from the parent. A lookup relationship cannot roll up values, an external lookup links to data outside Salesforce, and the hierarchical relationship exists only on User.

A junction object with two master-detail relationships is the standard model for many-to-many relationships, and each side can report on the other. Storing lists of IDs in a lookup or a text field cannot be queried or related properly, and a formula concatenating names is only a display.

A validation rule with a formula that checks the stage and close date blocks the save and shows an error when the condition is met. Changing the date silently, requiring the field, or comparing duplicates does not enforce the rule.

Dynamic Forms let administrators set visibility rules for individual fields on a Lightning record page, so one page serves several groups. Visualforce pages, duplicate objects and custom Apex each add maintenance the requirement does not need.

A record-triggered flow runs automatically when the stage changes, so the related Account is updated without anyone starting it. A screen flow needs a user action, a nightly schedule would be late, and an Apex-started flow adds code the administrator does not need.

Flow Builder is the declarative automation tool Salesforce recommends, and Process Builder is being retired in favour of it, so new work should be built in flows. Workflow rules are a legacy tool, and declarative automation has not been removed.

The Loop element runs the same steps for each item in a collection, which is what creating a task for every contact requires. Pause and Wait control timing rather than repetition, and a Decision branches once without repeating.

A scheduled flow runs at a set time, so it can process large groups of records overnight without user action. Record-triggered flows fire per record change, screen flows need a user, and platform event flows run on published messages.

Opportunity stages and forecast categories track progress through the sales process and feed the forecast. Campaign influence, quotes and price books support other sales processes but do not track stage progress or produce the forecast.

Case assignment rules route each new case to the correct queue or user based on criteria such as product or region. Escalation rules, entitlements and milestones each support a different part of service delivery, but they do not assign new cases.

Omni-Channel routes many kinds of work item, including cases and chats, to agents based on capacity, and presence status tells the router who is available. It does not route only chats, it does not need a separate org per queue, and it works within the Service Console rather than replacing it.

A price book holds the prices for products, including the standard price book and custom ones, and opportunities use it to set line item prices. A quote template formats documents, product families group products, and campaign members track responses.

Topics group the instructions and actions an agent uses for a subject, such as order status or returns, which helps it choose the right behaviour. Session policy, reporting and licensing are different administrative settings.

Grounding the agent in trusted knowledge and data sources means its answers come from approved content the user is allowed to see. Higher creativity makes answers less predictable, removing permissions limits what the agent can use, and deleting knowledge removes the source the answers should come from.

An action is a defined function the agent can call, such as looking up an order, which lets it do work rather than only answer. Topics group instructions, knowledge articles provide reference content, and permission sets control access for users.

Running the agent's actions with the permissions of the user it serves means it cannot reveal records that user is not allowed to see. Administrator access, disabled audit trails and org-wide read access each widen what the agent can expose.

Activity list views show a user's open tasks and events across records in one list, with filters for due dates and status. The recycle bin restores deleted records, duplicate rules check for matches, and paths guide a single record through its stages.

Path shows a record's stages as a guided sequence, with key fields and guidance for each stage. The recycle bin, Chatter groups and activity timeline support other needs and do not guide the user through a process.

Chatter groups give a team a shared space for posts and files around a topic, independent of any single record. A notes field holds text for one record, the recycle bin restores deleted items, and a dashboard filter limits chart data.

Events hold meeting details with start and end times, can send reminders, and can be related to the account. Tasks are for to-do items rather than time-bound meetings, while reports and dashboards summarise data and do not remind users.