Salesforce-Platform-Administrator Practice Test Questions

Explanation:

Universal Containers needs to count open cases per account and update the account every Friday evening. This is a scheduled aggregation requirement across a parent-child relationship (Account → Case), with a specific timing trigger.

Let’s evaluate each option:

A. Use a record trigger flow
Incorrect. A record-triggered flow runs when a record is created, updated, or deleted — not on a schedule. It cannot automatically run every Friday evening without an external trigger (e.g., a scheduled Apex job or Process Builder, which is being retired).

B. Use a scheduled process builder
Incorrect. Process Builder does not support scheduling. It is event-driven (record changes) and is being retired in favor of Flows. Even if it weren’t, it lacks native scheduling.

C. Use a Roll-Up summary
Incorrect. Roll-Up Summary fields can count child records (like open Cases), but only work when the child record is a Master-Detail relationship with the parent. Case → Account is a Lookup, not Master-Detail → Roll-Up Summary is not available. Also, Roll-Up Summary updates in real-time or near real-time — not on a weekly schedule.

D. Use a scheduled flow
Correct. Salesforce Scheduled Flows (introduced in Flow Builder) allow you to:

Run on a defined schedule (e.g., every Friday at 8 PM)
Query records (e.g., all open Cases)
Aggregate data (e.g., count Cases per Account)
Update parent records (Accounts) with the count

This is the only native, declarative tool that supports scheduled batch updates on Lookup relationships.

How to Implement (High-Level):
Create a Scheduled Flow
Set schedule: Weekly → Friday → Desired time
Get Records: All Case records where Status != Closed
Loop through Cases, use a Collection Variable or Assignment to count per AccountId
Update Accounts with a custom field (e.g., Open_Cases_Count__c)

Tip:
Use "Get Records" → Group by AccountId → Count with Aggregate Functions in Flow (available in SP25).

Reference:
Salesforce Help: Schedule a Flow
Flow Builder – Scheduled Flows (Supported in SP25)

Explanation:

A. Add a Path for Stage to the Opportunity Record Page
Why it’s correct:
Salesforce Path is designed to make stage-based processes faster and more intuitive. It allows users to view, update, and move through Opportunity Stages directly from the top of the record page—without scrolling or opening the full record details.
Key benefits:
Users can click once to change the Stage instead of editing the whole record.
Guidance for Success can display helpful tips or reminders for each Stage.
Key Fields can be shown inline for quick edits when changing Stages.
Implementation:
Go to Setup → Path Settings → Enable Path.
Create a new Path for the Opportunity object, based on the Stage field.
Add Key Fields and Guidance for Success for each Stage.
Activate it and add the Path component to the Opportunity Lightning page.

B. Use a Kanban List View for Opportunity
Why it’s correct:
The Kanban view is a visual representation of records, grouped by a picklist field—typically Stage for Opportunities. It lets users drag and drop cards between stages, which automatically updates the Stage field.
Key benefits:
No need to open records—users can move Opportunities between Stages with one action.
Displays totals and counts (e.g., pipeline amount per Stage).
Improves visibility of the sales pipeline and reduces clicks.
Implementation:
On the Opportunity tab, create or open a List View (e.g., “My Open Opportunities”).
Click the Display as Kanban icon (board view).
In Kanban Settings, group by Stage and summarize by Amount or other metrics.

Why not the others

C) Configure an autolaunched Flow for Opportunity editing — Not a good fit here Core mismatch:
Autolaunched flows have no screens (no UI). They’re designed to run in the background (invoked by a process, record-triggered flow, subflow, or an action), not for quick, ad-hoc user edits. For an interactive experience, you’d need a Screen Flow, not an autolaunched flow—still more clicks than Path/Kanban.
More clicks, more friction:
Users would need a button/quick action to call the flow, then confirm inputs—even if the only change is Stage. Path (on record) and Kanban (across many records) let users change Stage in-line with fewer steps.
Performance & scale considerations:
A flow run opens a full transaction: it evaluates entry criteria, runs before/after save logic, validation rules, triggers, etc. For dozens of changes, Kanban drag-and-drop is faster and lighter for the user.
Flows add maintenance overhead (versioning, testing, deployment) just to update one picklist field.
Operational risk:
If admin later changes Stage values or the Sales Process, the flow may need updates; otherwise you risk faults or incorrect logic.
Error handling (fault screens, subflow errors) introduces complexity not present with native Path/Kanban updates.
When it might be justified (but not this scenario):
If changing Stage must enforce extra automation (e.g., create tasks, send approvals) and you want a controlled, guided wizard—then a Screen Flow could make sense. Even then, it’s solving a different problem (guided orchestration), not “make it quick to edit Stage.”

D) Create a simplified Opportunity page layout — Helpful in general, but not the best answer for this use case
Doesn’t directly target the bottleneck:
The complaint is: “It takes a long time to edit Stage.” A trimmed layout reduces page clutter, but users still open the record and click Edit (or hunt for the Stage field).
Path puts Stage front-and-center with one click; Kanban enables drag-and-drop across many records—both are a bigger speedup than simply removing fields/related lists.
Still page-load dependent:
Even a simplified layout must load the record page (components, related lists, charts, dynamic bits). If users only need Stage changes, staying in a Kanban view avoids full record-page loads entirely.
Maintenance tradeoffs:
Multiple profiles/record types often lead to layout sprawl. You can simplify, but keeping the page clean over time requires ongoing governance. Path/Kanban provide speed without multiplying layouts.
When layout simplification is valuable:
If Opportunity pages are genuinely sluggish due to too many components, heavy related lists, or embedded report charts, simplifying (or using Dynamic Forms/visibility rules) improves general usability. It’s just not as targeted as Path/Kanban for rapid Stage edits.

Bottom line:
C (Autolaunched Flow): Wrong tool for quick, user-driven edits; adds clicks and maintenance; no native UI.
D (Simplified Layout): Good hygiene, but it doesn’t beat Path or Kanban for fast Stage-only updates—those two eliminate the need to open/edit the record in the first place.

Best Practice:
Use Path for guided stage progression inside records, and Kanban view for quick pipeline management across records. Together, they streamline Opportunity management and reduce edit time significantly.

Reference:
Salesforce Help: Create a Path in Lightning Experience
Salesforce Help: Use Kanban Views in Lightning Experience

Explanation:

D. Einstein Opportunity Scoring:
This AI-powered tool is designed specifically to help sales reps prioritize and close deals. It analyzes historical data and assigns a score (1–99) to each opportunity based on its likelihood of being won. By focusing on high-scoring opportunities, reps can more effectively allocate their time and resources, leading to a higher win rate and more closed deals. The tool also provides insights into the factors that most influence the score, whether positive or negative.

Incorrect answer explanations
A. Einstein Lead Scoring:
This feature is used to score leads based on their likelihood of converting into opportunities, not for prioritizing deals that are already in the opportunity pipeline. B. Einstein Search Personalization: This feature uses AI to learn how a user works and search for records. It personalizes search results to show the most relevant information but does not help with deal management or prioritization.
C. Einstein Activity Capture:
This tool helps sales reps by automatically logging emails and events to related Salesforce records. While it helps streamline the sales process by reducing data entry, it does not provide predictive scoring for deals.

Explanation:

The requirement is to identify and fix potential session vulnerabilities in Salesforce. Session security includes settings like session timeout, login IP ranges, password policies, and remote site settings. Salesforce provides a dedicated tool to scan the org’s security posture, highlight risks (especially session-related), and offer one-click fixes.

C. Security Health Check
The Security Health Check is the only native tool designed specifically to evaluate and remediate security vulnerabilities, including session-based risks. It analyzes over 40 security settings, assigns a health score, and flags issues such as weak session timeouts, missing IP restrictions, or insecure API access. Admins can view detailed risk levels and apply recommended fixes directly from the interface.

Incorrect Answers

A. Field History Tracking:
This tracks changes to field values on records (e.g., Stage changed from "Prospect" to "Negotiation"). It has no relation to session security or vulnerability detection.
B. Setup Audit Trail:
This logs administrative actions (e.g., who modified a profile or enabled a permission). It is useful for compliance and change tracking but does not assess or fix session vulnerabilities.
D. Organization-Wide Defaults (OWD):
This controls record-level sharing access (e.g., Private, Public Read/Write). It governs data visibility, not login sessions or authentication security.

Only one theme can be active at a time, and a theme applies to the entire org.

Chatter external users see the built-in Lightning theme only.

Explanation:

When branding Salesforce with Themes in Lightning Experience, it's crucial to understand their scope and limitations to set the correct expectations. Themes are a powerful tool for applying a custom color scheme and logo, but they are not as flexible as full-page layouts.

A. Only one theme can be active at a time, and a theme applies to the entire org.
This is a fundamental characteristic of Lightning Themes. An administrator can create and customize multiple themes, but only a single theme can be activated for the entire organization. When you set an active theme, it is visible to all internal users who are on Lightning Experience. You cannot, for example, have one theme for the Sales team and a different theme for the Service team.

D. Chatter external users see the built-in Lightning theme only.
Chatter External Users (also known as Customer Community Plus users or High-Volume Community users from a sharing perspective) have a limited view of Salesforce. A key limitation is that they cannot see custom themes. They will always see the standard, out-of-the-box Salesforce Lightning theme, regardless of what theme the administrator has activated for internal users. This is a critical consideration if your branding strategy includes external collaborators.

Incorrect Answers:

B. Themes apply to salesforce classic and to the salesforce mobile app.
This statement is false.
Salesforce Classic: Themes are a feature exclusive to Lightning Experience. They have no effect on the user interface in Salesforce Classic.
Salesforce Mobile App: The Salesforce mobile app has its own distinct UI and does not inherit the branding from a custom Lightning Theme. Branding for the mobile app is configured separately, if at all.
C. Upto 150 custom themes can be created, modified, or cloned from the built-in themes.
This number is incorrect and a common distractor. While an administrator can create and work with multiple themes, the limit is not 150. You can create a much smaller number of custom themes. The precise limit can change, but it is in the range of a handful (e.g., 5-10), not hundreds. The key point is that you are limited to only activating one of them at a time.

References:
Salesforce Help - Brand Your Org with Themes - This document outlines the capabilities and limitations of Lightning Themes.
Salesforce Help - User Types - Provides context on different user types, like Chatter external users, and their capabilities.

Explanation:

Why this is correct:
Salesforce won’t let you change a custom field’s data type if that field is referenced by other metadata, and formula fields are one of the explicit blockers. If a formula anywhere (on the same object or a related one) uses that picklist, Salesforce will prevent the type change until you remove or update the formula reference.

Why the others are not correct (in this context):
B. Record types:
Record types can restrict which values of a picklist are available, but their usage doesn’t by itself block converting the field type. You may need to clean up picklist assignments after a conversion, but record type usage isn’t one of the hard “reference” blockers listed by Salesforce.
C. Visualforce:
A Visualforce page referencing the field may break functionally after a change, but Visualforce references aren’t listed as a system-level blocker to changing field type (unlike formulas/flows/Apex).
D. JavaScript:
Client-side JavaScript isn’t a Salesforce metadata dependency and won’t prevent the change (though your scripts might need updates afterward).

References
Salesforce Help: Considerations for Converting the Field Type of a Custom Field (lists what references block data-type changes, including formulas).
Salesforce Help: Error “Cannot change type due to existing data” when field is referenced by a Formula field.

Explanation:

The business requirement is to provide a "self-serve option" for customers to generate cases. This means creating channels where customers can initiate a case without directly interacting with a DreamHouse Realty employee.

Why A is Correct (Web-to-Case):
Web-to-Case allows a company to embed a case submission form directly on its public website or a customer portal. A customer can visit the webpage, fill out the form (e.g., with their contact info, warranty details, and description of the problem), and submit it. This action automatically creates a new case in Salesforce. This is a classic and powerful self-service solution.

Why D is Correct (Email-to-Case):
Email-to-Case allows customers to generate a new case simply by sending an email to a designated email address (e.g., warranty@dreamhousereality.com). The content of the email is automatically converted into a new case record in Salesforce. This is another very common and convenient self-service channel that leverages a tool (email) that customers already use regularly.

Why B is Incorrect (Case Escalation):
Case Escalation is an internal process automation tool. It is used to automatically reassign a case or send notifications if a case is not closed within a specified time frame or meets certain criteria. It is a mechanism for handling existing cases, not for allowing customers to create them.

Why C is Incorrect (Case Queues):
Case Queues are a way to group and assign cases to teams of agents, rather than to a single user. They help in managing the workload of existing cases that have been created. Like Case Escalation, this is an internal routing and management tool, not a customer-facing self-service channel for case creation.

Reference:
Salesforce Help articles on "Set Up Web-to-Case" and "Set Up Email-to-Case" describe these as the primary methods for creating cases from external sources, enabling customer self-service.

Explanation:

Case Escalation Rules are designed specifically to re-route cases and/or send notifications if they are not resolved or updated within a specified time frame (age over a certain number of hours/minutes) based on defined criteria and business hours.

B. Case Escalation Rule:
This feature allows an administrator to define criteria (e.g., case status equals 'New', case has no response from an agent) and an "age over" time threshold (2 hours in this case) after which the case can be automatically reassigned (e.g., to a manager's queue or directly to the manager) and an email notification sent to the manager.

A. Assignment Rule:
Assignment rules are used when a case is first created to automatically route it to the correct user or queue based on its initial criteria. They do not monitor cases over a period of time after creation.

C. Omni-Channel Supervisor:
This is a real-time monitoring tool for supervisors to view agent workloads, queue backlogs, and work items. It helps supervisors manually intervene, but it does not automatically trigger actions or notifications based on predefined time limits.

D. Formula Field: A formula field performs calculations or displays data based on other fields. It cannot initiate time-based actions like sending notifications or reassigning records.

Explanation:

Why:
In Flow, a checkbox field evaluates to a Boolean. To branch when High_Value_Customer__c = TRUE, configure the Decision outcome with:
Resource: {!High_Value_Customer__c}
Operator: Equals
Value: {!$GlobalConstant.True}
If true, route to the second screen (skip the first).

Why the others are wrong:

B. “Use the equals operator and “High Value Customer” as the value.”
Type mismatch: A checkbox stores True/False, not text. Comparing a Boolean resource to a Text literal like "High Value Customer" is invalid.
Wrong operand meaning: "High Value Customer" is the field label, not a value the field ever contains. A checkbox doesn’t hold the words “High Value Customer”—it’s either checked (True) or unchecked (False).

C. “Use the contains operator and {!$GlobalConstant.False} as the value.”
Operator not applicable: Contains is for Text or Collections (e.g., “Does this string include that substring?” or “Does this collection include that item?”). It doesn’t apply to Boolean fields.
Wrong logic anyway: The requirement is “skip the first screen when the checkbox is True.” Checking for False would do the opposite—even if the operator were valid (it isn’t).

D. “Use the contains operator and “High Value Customer” as the value.”
Operator not applicable (again): Contains doesn’t work with Boolean fields—only text or collections.
Meaningless comparison: You’d be looking for the string "High Value Customer" inside something. A checkbox doesn’t contain text; it’s just True/False. Also, using the field’s label string in a decision is never how you evaluate a checkbox’s value.

Explanation:

C. Default Language:
This setting, found in the Company Information page, determines the default language for the organization. For a global team, setting a clear default is essential. While individual users can set their personal language preference, the org-wide default acts as the fallback for all new users, system messages, and certain text fields that are not translated by the individual user setting.

D. Currency Local:
For a global company operating in multiple regions, the Currency Local (also known as Default Locale or Organization Locale) is critical. It determines the format for:

Date and Time (e.g., DD/MM/YYYY vs. MM/DD/YYYY).
Number formatting (e.g., comma as a decimal separator vs. period).

Currency display symbols. This ensures that data is displayed in a consistent, regionally appropriate format for all global users, which is essential for minimizing confusion and data entry errors.

❌ Incorrect Answers and Why They Are Wrong

A. Login Hours:
This setting is configured at the Profile level, not in the Company Information settings. It is used to restrict when a specific group of users can log in, which is a security control, not a fundamental global configuration for language or locale.

B. Password Policy:
This setting is configured under Security Controls (or Identity in Lightning), not in the Company Information settings. It defines rules like password length, history, and expiration for all users in the org, which is a global security setting, but not one of the primary localization or company detail settings requested.

Reference
Salesforce Help Documentation: Manage Information About Your Company
This resource confirms that settings for Default Language and Default Locale (which affects currency display, date, and time formats) are configured under Company Information and are essential for global user support.