Salesforce-Platform-Administrator Practice Test Questions

Flow Builder

Explanation:

To launch a custom discount calculator screen when a sales rep clicks a button, the administrator should use Flow Builder to create a Screen Flow. Screen Flows allow you to present interactive UIs—such as calculators, forms, and wizards—directly within Salesforce. Unlike Workflow Rules, Process Builder, or Platform Events, Flow Builder’s Screen Flow element enables clicks-to-launch experiences with custom components and logic. You can embed the flow in a Lightning page or call it from a button or action, passing the Opportunity record ID so the flow can perform calculations and update fields. Flow Builder also supports conditional logic, input validation, and complex data manipulations, making it ideal for building a simple yet dynamic discount calculator screen without writing code.

Profile Assignment

Page layout Assignment.

Explanation:

To display a new record type to users, an administrator must (1) assign the record type to user profiles and (2) configure page layout assignments for that record type. Profile Assignment ensures that only selected profiles can create and view records of the new type. Page Layout Assignment lets you map specific page layouts to combinations of profiles and record types, controlling which fields and sections appear. Role Assignment is unrelated to record type visibility, and “App Manager Assignment” does not exist. Without both profile assignment and layout mapping, users either won’t see the record type option on the UI or will land on an inappropriate layout.

Use a conditional visibility to hide the unnecessary question

Explanation:

When only one of two questions on the same Screen Flow screen is needed at a time, leverage Conditional Visibility on individual components. This feature lets you set visibility rules based on prior inputs or record data, showing or hiding specific fields without adding extra screens or decision elements. Unlike creating multiple flow versions or branching screens manually, conditional visibility keeps the UI uncluttered and the flow logic centralized. It also improves maintainability by avoiding duplicate screens. Branching on the same screen isn’t supported directly; conditional visibility is the declarative way to implement dynamic, context-sensitive form fields in Flow Screens.

Explanation:

To streamline support agents’ access to documentation and past resolutions, enable Salesforce Knowledge. Populate Knowledge with articles that capture FAQs, troubleshooting steps, and case resolutions, then organize them with Data Categories. On the Case page layout, add the Knowledge component so agents can search and filter articles directly within the case context. This eliminates the need for a custom object or forcing agents to leave the case record for global search. Interview Flows (Screen Flows) and global search are suboptimal because they lack built-in article organization and presentation; Knowledge offers structured content management, versioning, and publishing workflows tailored for support scenarios.

Users’ profile requires permission to the Account object.

Explanation:

When new users cannot access the Account object at all, the most common cause is missing object-level permissions on their profile (or permission set). Even if roles, sharing rules, or organization-wide defaults are configured, a user must first have the “Read” (and optionally “Create”, “Edit”) permission on Accounts in their profile. Without it, the object doesn’t appear in the UI or API. Role hierarchy and sharing only control record-level visibility for objects the user already has permission to access. Therefore, granting the necessary object permissions on the profile immediately restores access to the Account tab and records.

Install in a sandbox

Check edition compatibility

Explanation:

Before installing an AppExchange package in production, administrators should verify its compatibility with their Salesforce edition and then install it in a sandbox. Sandboxes provide safe, isolated environments for testing functionality, data impacts, and user permissions without risking production data. Checking edition compatibility ensures the package supports required features (e.g., Lightning, Platform events) in your org. “Test Drive in a production org” is not possible, and Trailhead Playgrounds are intended only for training, not real org simulations.

Send email notifications.

Re-assign the Case.

Explanation:

Case Escalation Rules automate timely responses by evaluating cases against escalation criteria (e.g., age, priority) and triggering escalation actions. The two primary actions are sending email notifications to designated users or queues and reassigning the case to a higher-level support queue or user. You cannot use escalation rules to reopen cases; reopening is handled via case lifecycle settings or manual actions. Changing case priority requires a separate workflow or process builder action. Therefore, email alerts and owner changes are the correct pair of escalation actions.

Explanation:

To leverage a queue for Case management, first create a new queue and include “Case” as an available object. Then configure Case Assignment Rules to route incoming cases to that queue automatically based on criteria (e.g., case origin, type). This approach centralizes workload for the support team and ensures cases land in the queue instead of individual users. While a flow could also assign cases, standard assignment rules are simpler for predictable routing. You cannot add Cases to an existing task queue—each queue is object-specific.

Lookup field

Explanation:

To create a one-to-many relationship with optional and limited access to child records, use a Lookup field. Lookup relationships allow child records to exist independently of the parent and enforce access via sharing and profile permissions. Master-Detail relationships inherit parent sharing settings, making child records visible to anyone with access to the parent, which is unsuitable when you need to restrict child visibility. Roll-up summary and cross-object formulas require master-detail relationships, so a Lookup field is the correct choice for flexible, secure one-to-many links.

Outbound Message

Approval Process

Explanation:

To initiate expense reports from Salesforce to an external HR system with managerial review, combine an Approval Process with an Outbound Message. The Approval Process handles multi-level routing, notifications, and record locking for managers and directors to review and approve expense reports. Upon final approval (or rejection), an Outbound Message can send approved report data to the external HR system via SOAP, ensuring seamless integration. Quick Actions handle record creation but do not manage reviews; Email Alerts only send notifications without integration capabilities.