Last Updated On : 18-Nov-2026
Salesforce Platform Administrator II - Plat-Admn-301 Practice Test
Prepare with our free Salesforce Platform Administrator II - Plat-Admn-301 sample questions and pass with confidence. Our Salesforce-Platform-Administrator-II practice test is designed to help you succeed on exam day.
Salesforce 2026
Cloud Kicks (CK) has deployed several new custom apps that use Lightning Web
components. The administrator is now concerned that they may need to make some
adjustments to CK’s org to make it more secure.
Which tools should the administrator use to expose possible security risks within a
Lightning web component?
A. Health Check
B. Master Encryption Keys
C. Salesforce Optimizer
D. Self-signed Certificates
Explanation:
To identify and address security risks in a Salesforce org — especially those related to custom apps and Lightning Web Components (LWCs) — the Health Check tool is the most appropriate choice.
🔹 Why Option A Is Correct:
Health Check evaluates your org’s security settings against Salesforce’s recommended baseline.
It helps uncover vulnerabilities such as:
Weak password policies
Insecure session settings
Unrestricted IP ranges
While it doesn’t scan LWCs directly, it ensures the org-level security posture is strong enough to support secure component behavior.
❌ Why the Other Options Are Incorrect:
B. Master Encryption Keys
Used for Shield Platform Encryption, not for detecting security risks.
Doesn’t analyze or expose vulnerabilities in LWCs.
C. Salesforce Optimizer
Focuses on performance and usage insights (e.g., unused fields, page layouts).
Not designed to detect security risks in components or org settings.
D. Self-signed Certificates
Used for authentication and secure communication, not for security auditing.
Doesn’t help expose risks in Lightning components.
🔗 Reference:
Health Check Overview
Secure Coding for LWCs
Cloud Kicks wants to implement multi-factor authentication (MFA) to help better secure its
Salesforce org.
Which two options should the administrator consider to use MFA?
Choose 2 answers
A. An Authentication App
B. A Username and Password
C. A Security Token
D. An Encryption Key
B. A Username and Password
Explanation:
Multi-Factor Authentication (MFA) requires a user to provide two or more distinct forms of verification to prove their identity. These factors are typically categorized as:
Something you know (e.g., a password or PIN).
Something you have (e.g., a physical device or an app on your phone).
Something you are (e.g., a fingerprint or facial recognition).
Let's analyze the options:
A. An Authentication App (Correct)
This represents the "something you have" factor. An authentication app (like Salesforce Authenticator, Google Authenticator, or Microsoft Authenticator) generates a time-based, one-time password (TOTP) that is tied to the user's specific device. This is a standard and highly recommended method for the second factor in MFA.
B. A Username and Password (Correct)
The username and password combination represents the "something you know" factor. This is the first, foundational layer of authentication. MFA builds upon this by requiring a second, different type of factor.
C. A Security Token (Incorrect)
A security token is a long, case-sensitive alphanumeric code that is appended to a user's password when logging in via the API or from an untrusted network. It is a form of two-factor authentication, but it is not the same as the modern, user-friendly MFA that Salesforce recommends and promotes. Salesforce is moving towards phasing out security tokens in favor of verification codes from authenticator apps.
D. An Encryption Key (Incorrect)
An encryption key is used to encrypt and decrypt data at rest. It is a tool for data security, not for user authentication. It is not a factor used in the MFA process.
Reference:
Multi-Factor Authentication (MFA): A security enhancement that requires two or more verification factors to gain access to a resource. In the context of Salesforce login, this is typically a password ("something you know") and a verification code from an authenticator app or a built-in authenticator ("something you have").
Salesforce Authenticator: The recommended and most integrated method for implementing MFA in Salesforce. It provides a push notification approval for a seamless user experience.
Universal Containers wants to assign a task due date on one of two fields. Estimated
Shipping Date or Client Need By Date, which is further in the future. Which two combined automation tools should the administrator use to create the task
record and assign based on date criteria?
(Choose 2 answers)
A. Create a formula capture the MAX date.
B. Make a Process Builder to create the task.
C. Design an approval process to capture the furthest date.
D. Configure a workflow to create the task.
B. Make a Process Builder to create the task.
Explanation:
✅ Option A is correct because a formula field is the most efficient and declarative way to calculate and store the maximum (further in the future) of two dates on the record itself. You can create a custom formula field (e.g., "Task Due Date") using the MAX function (e.g., MAX(Estimated_Shipping_Date__c, Client_Need_By_Date__c)). This field will dynamically evaluate to the later of the two dates, providing a single, reliable value for any downstream automation to use.
✅ Option B is correct because, once the formula field exists, Process Builder is the modern and powerful automation tool ideal for creating related records, such as Tasks. A process can be triggered when a record is created or edited (meeting the requirement to "assign a task"). It can use the pre-calculated formula field value to directly set the Task's Due Date without needing complex logic, making the process simple, maintainable, and efficient.
❌ Option C is incorrect. An approval process is designed to manage record submission and approval workflows, not to perform date calculations or create task records. It is the wrong tool for this specific functional requirement and would add unnecessary complexity.
❌ Option D is incorrect. While a workflow rule could technically create a task, workflow rules are a legacy automation tool. Their functionality for creating tasks has been largely superseded by Process Builder and Flow. More importantly, workflow rules have severe limitations; they cannot reference formula fields in cross-object criteria and cannot perform the complex logic required to evaluate two dates and choose the maximum value at the moment of record creation or update. Relying on a workflow rule for this would be unreliable and not a best practice.
Reference: This solution follows the standard Salesforce best practice of using a formula field to simplify complex logic for use in other parts of the platform. The use of Process Builder for record-triggered automation and related record creation is a core objective for the Platform App Builder and Platform Administrator II certifications. Salesforce recommends using these more modern and capable tools over legacy workflow rules.
Sales management wants a small subset of users with different profiles and roles to be able to view all data for compliance purposes. How can an administrator meet this requirement?
A. Assign delegated administrator to the subset of users to View All Data.
B. Create a new profile and role for the subset of users with the View All Data permission.
C. Enable the View All Data permission for the roles of the subset of users.
D. Create a permission set with the View All Data permission for the subset of users
Explanation:
The goal is to grant a small, specific group of users the ability to View All Data across the organization for compliance purposes, regardless of their standard profiles and roles. Using a Permission Set is the most flexible, secure, and modern approach to meet this requirement.
Permission Set
A Permission Set is a collection of settings and permissions that extend a user's functional access without changing their profile.
Configuration: The administrator can create a new Permission Set (e.g., "Compliance Data Access") and enable the "View All Data" system permission within it.
Assignment: The Permission Set is then assigned only to the small subset of users who require this specific, high-level access.
Benefit: This approach follows the Principle of Least Privilege, ensuring that these users retain their existing profiles and roles for their day-to-day work, while only gaining the special "View All Data" permission where necessary. It's easy to audit and revoke the permission instantly by removing the Permission Set assignment.
Why the Other Options are Incorrect
A. Assign delegated administrator to the subset of users to View All Data:
Delegated Administration is designed to allow a user to manage user creation, reset passwords, and manage specific custom objects. It does not automatically grant "View All Data" across all standard and custom objects.
B. Create a new profile and role for the subset of users with the View All Data permission:
Creating a new Profile is often unnecessary and overly complex for granting a single, specific permission. If these users already have roles and profiles that govern their other access (like Object and Field Permissions), moving them to a new Profile could inadvertently change or break their existing, necessary access. Permission Sets are designed specifically to layer permissions on top of existing profiles.
C. Enable the View All Data permission for the roles of the subset of users:
Permissions are not assigned to Roles. Permissions are assigned through Profiles and Permission Sets. Roles primarily manage the record visibility hierarchy (for sharing rules and Organization-Wide Defaults). Therefore, this option is technically impossible to configure in Salesforce.
Users at Northern Trail Outfitters have a lot of fields on their new account records because they track their accounts and competitors on the Account object. For accounts created for customers, they need access to different fields than the accounts used to track competitors. For partner accounts, they need different values in the Industry field. What should the administrator use to resolve the issues?
A. Business Processes
B. Required Fields
C. Flow Builder
D. Record Types
Explanation:
Summary 📝
The administrator should use Record Types to resolve these issues. This is the correct choice because Record Types are specifically designed to address these requirements by providing different page layouts for various user groups and different picklist values for specific record categories. By creating separate record types for customers, competitors, and partners, the administrator can control the fields visible on the page and the picklist values available in the Industry field.
⚙️ Detailed Explanation
D. Record Types (Correct)
A Record Type is the ideal solution because it is the fundamental tool for providing different user experiences for different business purposes on the same object. The administrator can create three separate record types on the Account object: one for Customers, one for Competitors, and one for Partners. Each of these record types can then be assigned a unique page layout, which controls which fields are visible to users, directly addressing the need for different fields for customer and competitor accounts. Furthermore, a Record Type can be associated with a specific business process, which in turn controls the available picklist values for fields like Industry. This allows for different Industry picklist values to be displayed for partner accounts. This declarative, out-of-the-box feature is the standard and most efficient way to handle all parts of this requirement.
A. Business Processes (Incorrect)
Business Processes are used to track the lifecycle of specific standard objects by controlling the available picklist values for a given Record Type. While a business process would be used in conjunction with a Record Type to handle the different Industry picklist values, it cannot by itself control which fields are visible on the page. Therefore, it is an incomplete solution to the overall problem.
B. Required Fields (Incorrect)
Making fields Required is a setting that ensures users must enter a value before saving a record. This does not address the need to show different fields or different picklist values to various user groups. This feature would be used after the fields are already on the page layout, not as a means to differentiate the layout itself.
C. Flow Builder (Incorrect)
Flow Builder is a powerful automation tool used to build complex business logic, automate tasks, and create guided user experiences. While a screen flow could be built to dynamically control field visibility or picklist values, it is not the standard, declarative, and most straightforward method for this common scenario. The requirements are best met by the foundational platform feature designed for this exact purpose, which is Record Types.
Reference:
For more information on how Record Types are used, you can refer to the official Salesforce documentation: Record Types
| Salesforce-Platform-Administrator-II Exam Questions - Home | Previous |
| Page 5 out of 44 Pages |