Free Salesforce Certified Platform App Builder practice test: 30 questions with answers

Formula fields are read-only and recalculate from the fields they reference. Users cannot type over the value, the value is not stored as a fixed copy, and formula fields cannot be used as External IDs.

A text formula can evaluate the Close Date and the IsClosed flag with IF logic and return Overdue automatically. A roll-up summary only aggregates child records, and a manually updated picklist or an auto-number field cannot evaluate dates.

Roll-up summary fields are available only on the parent side of a master-detail relationship. Lookup and external lookup relationships do not support them, and the hierarchical relationship exists only on User records.

A validation rule blocks the save when its formula evaluates to TRUE, so the formula must be TRUE for the invalid case. Returning FALSE for the invalid case would let the bad record save, and the other options do not express the condition.

Validation rules are evaluated on save, and they display their error message when the formula is TRUE. They do not correct data, do not fire on each field exit, and do not replace field-level security.

A before-save record-triggered flow changes the triggering record directly as part of the save, so no extra DML is needed. Screen flows need a user, scheduled flows run on a timetable, and platform event flows respond to event messages rather than record saves.

A master-detail relationship cascades deletes from the parent and inherits sharing from it, which matches the requirements. A lookup does not cascade deletes, a junction object is for many-to-many links, and an external lookup points to data stored outside the org.

A lookup is loosely coupled, so the child field can be left empty and the child saved without a parent. Lookup parents do not cascade deletes, the child requirement describes master-detail, and roll-up summary fields are not created automatically on lookups.

A many-to-many relationship is modeled with a junction object that has two master-detail relationships. A picklist or a text field cannot create real relationships, and two lookups on Student would only allow one course per field.

An External ID field can be used to match incoming rows during an upsert. Formula fields are read-only, and picklists and checkboxes cannot be marked as External IDs.

Data Loader can upsert in bulk, using an External ID to decide whether each row updates an existing record or creates a new one. Manual editing does not scale, and mass transfer changes record ownership rather than field values.

Master-detail relationships cascade deletes to children and allow roll-up summary fields on the parent. A master-detail child always needs a parent, a child has one master only, and child sharing follows the parent.

Object Manager lets administrators define custom objects declaratively with clicks. The Apex trigger, the Lightning web component and the Visualforce page with a controller all require programming.

Dashboards display the results of reports, so a report grouped by owner and stage is the declarative fit. The list view, the Apex page and the flow do not produce a grouped dashboard view of the data.

Field-level security controls whether a user can see or edit an individual field. Organization-wide defaults, the role hierarchy and sharing rules control access to whole records, so they would hide the entire Account rather than one field.

Organization-wide defaults and sharing rules both determine record-level access to Accounts. Field-level security affects only one field, while page layouts and tab visibility change what is displayed, not who can access the record.

A Private default restricts reps to their own records, and the role hierarchy extends visibility upward to managers. Public Read/Write exposes every account, Modify All Data gives far more than needed, and a broad public group grants edit access to everyone in it.

AgentExchange is the Salesforce marketplace for apps, agents and components that can be added to an org. Trailhead is a learning platform, the Organization Information page shows org settings, and the Recycle Bin holds deleted records.

Lightning App Builder is the declarative tool for designing Lightning pages by dragging components into regions. The Developer Console and Visual Studio Code are code tools, and Setup Audit Trail only records configuration changes.

Dynamic Forms lets an administrator set visibility rules on individual fields based on other field values. A record type switches layouts by category rather than by field value, and a static page layout cannot change field visibility based on Industry.

Record types determine which page layouts and picklist values users see for a record. Storage, sharing and list view sort order are controlled by other settings.

The compact layout sets the handful of fields that appear at the top of a record in the highlights panel and in the mobile record summary. Search results layouts control search output, Path shows sales or process stages, and list views filter record lists.

A quick action of type Flow runs a screen flow from a button on the record page. JavaScript buttons are not supported in Lightning Experience, a web tab does not open a flow, and an email template only drafts messages.

Lightning Web Components are the recommended framework for new custom Lightning components and use standard modern JavaScript. Aura components are older, Visualforce is a legacy page technology, and S-Controls are a retired technology.

A full sandbox replicates the production metadata and all of its data. Developer and Developer Pro sandboxes copy metadata without production data, and a Partial Copy sandbox includes only a sample of the data.

Change sets package metadata in a source org and deploy it to a connected target org. They do not delete components, do not move record data, and require a connection between the two orgs.

Managed packages protect intellectual property, support upgrades and are used for distribution to other customers. Unmanaged packages expose their code and do not upgrade, and change sets are for moving components between an organization's own orgs.

A Developer sandbox copies metadata only, which keeps production data out of development work. A full sandbox copies all production data, a Partial Copy sandbox includes a sample of it, and the production org is the live environment that should not be used for development.

A sandbox rehearsal exposes missing dependencies and configuration errors while the change is still contained. Copying records into production, skipping acceptance testing and skipping production tests all increase risk rather than reduce it.

Managed packages can be upgraded by subscribers as the developer releases new versions. Subscribers cannot edit the packaged Apex, and managed packages are meant for distribution to other customers rather than for internal sandbox moves.