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 an email parsing tool. CK wants to ensure that when certain field are
updated, the Case Owner is notified by email.
What should the administrator use to email the Case Owner?
A. Email-to-Case
B. Outbound Message
C. Before Save Flow
D. After Save Flow
Explanation:
Why it’s correct:
You need to email the Case Owner when certain fields are updated. That’s record-change automation plus an email action. A record-triggered Flow that runs after save can evaluate which fields changed and then send an email (via the Flow Send Email core action or an Email Alert). “After save” is required because email actions are supported after the record is committed.
Why the other options are not correct
A. Email-to-Case – Creates Cases from inbound emails; it’s not a notification mechanism for field updates.
B. Outbound Message – Sends a SOAP message to an external endpoint, not an email to a user.
C. Before Save Flow – Optimized for fast field updates only; it can’t send emails or perform actions that require the record to exist in the database. Use after-save for emails.
Exam tip
Remember: Before-save = fast field updates; After-save = actions (send email, create related records, etc.). If the requirement includes sending an email on a record change, pick After Save Flow.
References:
Record-Triggered Flow (After Save): trigger after record is saved.
Flow Core Action – Send Email: send emails from Flow; use templates if desired.
Before-Save updates: limited to updating fields on the triggering record.
Outbound Message (what it does): posts to external endpoints, not email.
Email-to-Case (purpose): turns emails into Cases, not notifications.
Cloud Kicks has o custom object called Membership Details that records information about
customers' preferences for their memberships. Depending, on the membership level,
different data needs to be displayed.
• when cue running user has the Market no profile, all data should be visible.
• When the running user has the Support profile, only the Support preference fields should
be visible.
• Both Marketing and Support users should be able to report on all data.
How should the administrator deliver this solution?
A. Create two record types und two page layouts.
B. Set up Dynamic forms to conditionally show data.
C. Make a permission set with a Muting permission.
D. Use Field-Level Security to control data access.
Explanation:
Why:
Use Dynamic Forms on the Membership Details Lightning record page to show/hide fields (or entire Field Sections) based on the running user’s profile: show all sections for Marketing; show only the “Support preferences” section for Support. This controls what appears on the page without changing data access. Keep Field-Level Security (FLS) with Read access for both profiles so both can report on all fields (reports rely on FLS, not page layout visibility).
Why not the others:
A. Two record types + two page layouts – Record types are unnecessary; the requirement is user-based display, not different business processes. Dynamic Forms handles conditional display per profile without new record types.
C. Permission set with Muting – Muting permissions are for Permission Set Groups, not a mechanism to conditionally show fields on a page. They don’t solve per-profile page display.
D. Field-Level Security – Using FLS to hide fields would also hide them from reports; the ask says both groups must be able to report on all data. Page/UI visibility should be handled with Dynamic Forms, not by removing FLS access.
Build tips:
Add “Support Preferences” as a Fields Section; set Visibility rule: Profile equals Support.
Leave other sections visible to Profile equals Marketing (or not restricted).
Ensure FLS “Read” on all fields for both profiles so reporting works as requested.
Northen trail Outfitters (NTO) wants to change the current master-detail relationship
between Shipments and Opportunity to a lookup relationship. The system administrator has
made the necessary changes in a full sandbox and has successfully tested them against
NTO’s data.
Now that the changes are ready to implement in production, what should the system
administrator do next?
A. Make the changes directly in the production org.
B. Create an Unmanaged Package to distribute to production.
C. Use Data Loader to export the changes to the production org.
D. Add the components to an outbound change set and deploy it to production.
Explanation:
To implement changes like modifying a master-detail relationship to a lookup relationship from a sandbox to a production org, Salesforce best practices recommend using a structured deployment process to ensure changes are tracked, tested, and applied safely. Here's a step-by-step breakdown:
Why Change Sets?
Change sets are Salesforce's native deployment tool for moving metadata (like object relationships, fields, and configurations) between orgs, such as from a full sandbox to production. They provide a controlled, auditable way to deploy changes, ensuring that only tested components are moved. In this scenario, the system administrator has already tested the change (converting the master-detail to a lookup relationship) in a full sandbox, so using an outbound change set is the appropriate next step to deploy this metadata change to production.
Why Not the Other Options?
A. Make the changes directly in the production org.
Making changes directly in production is risky and against Salesforce best practices. It bypasses testing, version control, and governance processes, potentially introducing errors or data inconsistencies, especially for significant changes like altering object relationships. This could also violate NTO’s change management policies.
B. Create an Unmanaged Package to distribute to production.
Unmanaged packages are typically used for sharing templates or apps with other orgs, not for deploying configuration changes within the same org ecosystem (e.g., from sandbox to production). They don’t provide the same level of control or dependency tracking as change sets and are not suitable for this use case.
C. Use Data Loader to export the changes to the production org.
Data Loader is designed for importing/exporting data (records), not metadata like object relationships. Changing a master-detail to a lookup relationship is a metadata change, not a data migration, so Data Loader is irrelevant here.
Process for Change Sets:
The administrator should create an outbound change set in the sandbox, including the modified object relationship (Shipment and Opportunity objects with the new lookup field).
Upload the change set to the production org.
In production, validate and deploy the inbound change set, ensuring all dependencies (e.g., fields, page layouts, or workflows referencing the relationship) are included and properly tested.
Note: When changing a master-detail to a lookup, the administrator must ensure no roll-up summary fields, sharing rules, or other dependencies rely on the master-detail relationship, as these could block the deployment or require additional configuration.
Additional Considerations:
Ensure the sandbox and production orgs are aligned in terms of metadata and data dependencies.
Validate the change set in production before final deployment to catch any issues.
Document the change for audit purposes and communicate with stakeholders, as altering relationships can impact reports, dashboards, or automation.
References:
Salesforce Help: Change Sets Best Practices
Explains how to use change sets for deploying metadata changes between orgs.
Salesforce Trailhead: Application Lifecycle and Development Models
Covers deployment strategies, including change sets for sandbox-to-production workflows.
Salesforce Help: Considerations for Relationships
Details considerations for changing master-detail to lookup relationships, including dependencies.
An administrator is creating a custom Opportunity record page for Sales users for new logo
opportunities. They need to control what fields display on the record when a sales user is
viewing the opportunity.
Where should the administrator edit what fields display in the details of the record page?
A. Record Detail Component
B. Custom Lightning Component
C. Record Types
D. Page Layout
Explanation:
Correct Option Explanation:
✅ Option D: Page Layout.
Page layouts in Salesforce determine which fields, sections, and related lists are visible to users on the record detail page. When a sales user opens an Opportunity record, the fields they see in the details section are controlled directly by the assigned page layout. By editing the page layout, the administrator can add or remove fields, reorder sections, and tailor the record view specifically for new logo opportunities. This ensures sales users only see the fields relevant to their process, which makes data entry faster and keeps the interface clean. Page layouts are the standard tool for managing field visibility within record details in Lightning record pages.
Incorrect Options Explanations:
❌ Option A: Record Detail Component.
The Record Detail component in a Lightning page acts as the container that displays record details, but it does not control which fields show up. It simply renders whatever is configured on the page layout. If you place the Record Detail component on a Lightning record page, it pulls its field configuration from the assigned page layout. Therefore, this component is not the place where you configure fields.
❌ Option B: Custom Lightning Component.
Creating a custom Lightning component would allow developers to design highly specific field displays, but this is unnecessary and overly complex for the requirement. Salesforce already provides point-and-click control through page layouts. Using a custom Lightning component would introduce unnecessary development work and complexity when page layouts can solve the problem directly.
❌ Option C: Record Types.
Record types control business processes, picklist values, and which page layout is assigned to a record, but they do not themselves define which fields display. A record type may assign a different page layout to sales users for new logo opportunities, but the actual field visibility is still configured at the page layout level. So while record types are related, they are not the tool to directly control fields in the record detail section.
🔗 Reference: Salesforce Help – Customize Page Layouts
✨ Key Takeaway:
If you need to control what fields users see in the record details section, always edit the Page Layout. Record types can assign layouts, and the Record Detail component displays them, but the actual field control comes from the page layout.
After setting up field history tracking on the Account object, the administrator for AW
Computing wants to retrieve the field history data for analysis.
how should the administrator acquire this data?
A. Create a report of Accounts and export it to Excel.
B. Query and export the Account History object using Data Loader.
C. Use the Data export service in setup.
D. Create a list view of Account History and print using the Printable View action.
Explanation:
Field History Tracking stores all changes to the tracked fields in a separate, dedicated object. For the standard Account object, this history is stored in the Account History object (API Name: AccountHistory).
Dedicated History Object:
Every standard object with history tracking enabled has a corresponding history object (e.g., AccountHistory, OpportunityHistory, CaseHistory).
Accessing History Data:
To retrieve the raw, comprehensive data from the history object for analysis (especially large volumes), the administrator must use an API-based tool like Data Loader to perform a query and export.
Data Loader Process:
The administrator would log into Data Loader, select Export (or Export All to include soft-deleted records), choose the Account History object, define the fields they want (like CreatedDate, Field, OldValue, NewValue, and AccountId), and run the export to get a CSV file for analysis.
Why the Other Options are Incorrect
A. Create a report of Accounts and export it to Excel:
A standard report on the Account object itself only shows the current state of the records. While you can create a report using the built-in Account History report type, this report type has limitations (e.g., typically a 2000-row limit on export of a formatted report, and it only shows history up to the last 18-24 months in the standard history table). Data Loader is the robust tool needed for a full data export for analysis.
C. Use the Data export service in Setup:
The Data Export service (Weekly/Monthly export) does include the history objects in the zip file (EntityHistory.csv or specific history object files like AccountHistory.csv), making it a viable option. However, Data Loader is a more direct and immediate way to query and retrieve only the specific history object data without waiting for a scheduled export or downloading a large zip file that contains all org data. Data Loader is generally considered the primary tool for targeted large-scale data manipulation (including exports for analysis) by administrators.
D. Create a list view of Account History and print using the Printable View action:
You cannot create a standard list view of the history objects like AccountHistory. The history is displayed in the History related list on the Account record page. Using "Printable View" on a list view is a basic feature not suitable for retrieving large amounts of structured data for detailed analysis.
| Salesforce-Platform-Administrator-II Exam Questions - Home |
| Page 2 out of 44 Pages |