[Jun-2026] Salesforce Developer Plat-Admn-202 Exam Practice Dumps
2026 Plat-Admn-202 Premium Files Test pdf - Free Dumps Collection
Salesforce Plat-Admn-202 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
NEW QUESTION # 156
After utilizing the Lightning Object Creator to create a new object, its fields, and to insert all of the data, an app builder now needs to set up the Lightning Record Page.
Which component should the app builder have on their Lightning Record Page to see all of the fields from the page layout?
- A. Record Detail
- B. Highlights Panel
- C. Path
- D. Recommendations
Answer: A
Explanation:
For an app builder who needs to ensure all fields from the page layout are visible on a Lightning Record Page after using the Lightning Object Creator, the correct component to use is:
Record Detail (C). The Record Detail component automatically displays all fields that are included on the assigned page layout for the object. It is designed to reflect the layout configuration and is the simplest way to ensure all fields are presented as configured in the layout editor.
Highlights Panel (A) is used primarily to display key fields at the top of the record page, providing a summary view rather than full field visibility. Recommendations (B) is used for displaying prompts or suggestions and does not display record fields. Path (D) is useful for displaying stages in a process (like sales stages or service processes) and does not show field data directly.
Reference for setting up Lightning Record Pages and using components effectively:
Lightning Record Pages: https://help.salesforce.com/articleView?id=sf.lightning_page_components.htm&type=5
NEW QUESTION # 157
Universal Containers wants to track installation information once a container has been purchased on a custom object. Sales reps should have visibility of all the installations associated with their opportunities.
Which kind of relationship should this new object have to Opportunity?
- A. Lookup
- B. Master-Detail
- C. Many to Many
- D. Hierarchical
Answer: B
Explanation:
The new custom object ("Installation__c") must store installation details that are related to an Opportunity. Since each installation should be tied directly to a single opportunity, and inherit ownership and visibility from that opportunity (as per "sales reps should have visibility"), a Master-Detail relationship is appropriate.
Why B (Master-Detail) is correct:Exact Extract:"In a master-detail relationship, the detail record inherits the sharing and security settings of its master record." - Salesforce Help | Relationships OverviewBecause Opportunities already have ownership and sharing settings that determine sales reps' visibility, making Installation__c the detail record ensures that sales reps automatically see related installations.Exact Extract:"The master-detail relationship closely links objects so that the master record controls certain behaviors of the detail record, such as record ownership, sharing, and deletion." - Salesforce Help | Master-Detail Relationships Why B (Master-Detail) is correct:Exact Extract:"In a master-detail relationship, the detail record inherits the sharing and security settings of its master record." - Salesforce Help | Relationships OverviewBecause Opportunities already have ownership and sharing settings that determine sales reps' visibility, making Installation__c the detail record ensures that sales reps automatically see related installations.Exact Extract:"The master-detail relationship closely links objects so that the master record controls certain behaviors of the detail record, such as record ownership, sharing, and deletion." - Salesforce Help | Master-Detail Relationships Why not A (Many to Many):Many-to-many relationships are only used when multiple records on both sides need to relate (e.g., Opportunities linked to multiple Installations and vice versa). That is not described here.
Why not C (Hierarchical):Hierarchical relationships are only available on the User object.
Why not D (Lookup):Lookup relationships do not automatically grant visibility or inherit ownership, so sales reps might not see all related installations.
Reference (Salesforce Platform App Builder documentation / Study Guide topics):
Salesforce Help | Relationships Overview
Salesforce Help | Master-Detail Relationships
Salesforce Platform App Builder Exam Guide | Data Modeling and Management
NEW QUESTION # 158
An App Builder at UVC would like to prevent users from creating new records on an Account related list by overriding standard buttons. Which two should the App Builder consider before overriding standard buttons?
- A. Standard buttons can be changed on lookup dialogs, list views, and search result layouts
- B. Standard buttons that are not available for overrides can still be hidden on page layouts
- C. Standard buttons can be overridden with a Visualforce page
- D. Standard buttons can be overridden, relocated on the detail page, and relabeled
Answer: B,C
Explanation:
Standard buttons can be overridden with a Visualforce page to provide custom functionality or user interface. For example, you can override the New button on an object to display a custom Visualforce page instead of the standard page layout3. Standard buttons that are not available for overrides can still be hidden on page layouts to prevent users from accessing them. For example, you can hide the Delete button on an object to prevent users from deleting records
NEW QUESTION # 159
An app builder created multiple custom fields, page layouts, and reports in the sandbox and added them to a change set was deployed to production, the reports were NOT deployed.
What should the app builder do?
- A. Add the reports to an unmanaged package and install the unmanaged package into production.
- B. Move the reports to the Untried Public Reports folder and add them to a new change set.
- C. Move the reports from the Unfiled Public Reports folder and add them to a new change set
- D. Recreate the reports in production. Reports are not supported in change sets
Answer: C
Explanation:
Moving the reports from the Unfiled Public Reports folder and adding them to a new change set is what the app builder should do to deploy the reports to production. According to the Salesforce documentation, "Reports in the Unfiled Public Reports folder aren't available for deployment." Moving the reports to the Untried Public Reports folder, recreating the reports in production, and adding the reports to an unmanaged package are not necessary or recommended actions.
NEW QUESTION # 160
Universal Containers allows all employees to submit reviews for leadership using a custom object called Review. These Reviews should only be visible to the HR department and the employee who submitted the record.
Which three steps should an app builder take to properly control access to Reviews?
Choose 3 answers
- A. Add a Master-Detail (User; field on the Review object.
- B. Create a criteria-based Sharing Rule for the HR Department.
- C. Remove Review Read permission from non-HR Department user Profiles.
- D. Set organization-wide default to Private.
- E. Disable Grant Access Using Hierarchies.
Answer: B,D,E
Explanation:
To control access to the Review custom object such that only the HR department and the submitting employee can see the reviews, the following steps should be taken:
A . Disable Grant Access Using Hierarchies:By default, Salesforce allows users higher in the role hierarchy to access records owned by users lower in the hierarchy. Since reviews should only be visible to HR and the submitting employee, you need to disable Grant Access Using Hierarchies on the Review object to prevent anyone else in the hierarchy from automatically gaining access to these records.
Record Access and Role Hierarchies
C . Create a criteria-based Sharing Rule for the HR Department:With the organization-wide default (OWD) set to Private, you'll need to create a criteria-based sharing rule to ensure that HR users can view the Review records. This rule would give HR access to the records based on a specified condition, such as all records of the Review object.
Reference:
E . Set organization-wide default to Private:Setting the organization-wide default (OWD) for the Review object to Private ensures that no user, other than the record owner (the submitting employee) and those explicitly granted access (HR), can see the Review records by default.
Why the other options are incorrect:
Option B: Add a Master-Detail (User) field on the Review object:This is not necessary in this scenario because the primary relationship is about controlling access through sharing rules, not creating a master-detail relationship. Moreover, this would complicate access control, which is better managed via sharing settings.
Option D: Remove Review Read permission from non-HR Department user Profiles:This step is redundant if the organization-wide default is set to Private. Profile permissions control the general ability to access the object, while the visibility of specific records is controlled by sharing rules and OWD. Removing read access via profiles would block all users, including the ones submitting the reviews, from accessing the object.
In summary, by disabling Grant Access Using Hierarchies, setting OWD to Private, and implementing a criteria-based sharing rule for HR, you can ensure that only HR and the submitting employee can view Review records.
NEW QUESTION # 161
Universal Containers utilizes opportunities and a custom object called Detaited.Sales__c. The company would like to roll sales metrics up to an opportunity for only Detailed.Sales__c records that have their picklist status set to Active.
What is the recommended method for the app builder to achieve this request?
- A. Utilize the AppExchange to download a third-party application that can roll_up the sales dollars with the appropriate filter.
- B. Create a lookup relationship between the parent and child object with a roll-up summary held that filters on the status field.
- C. Utilize Apex code to roll up the desired amounts.
- D. Create a master-detail relationship between the parent and child object with a roll-up summary field that fitters on the status held.
Answer: D
Explanation:
Create a master-detail relationship between the parent and child object with a roll-up summary field that filters on the status field is the recommended method for the app builder to achieve the request of rolling up sales metrics to an opportunity for only Detailed.Sales__c records that have their picklist status set to Active. According to the Salesforce documentation, "Roll-up summary fields calculate values from related records, such as those in a master-detail relationship." A roll-up summary field can filter on a field value of the child records and sum up only those records that match the criteria. Utilize the AppExchange to download a third-party application that can roll up the sales dollars with the appropriate filter, create a lookup relationship between the parent and child object with a roll-up summary field that filters on the status field, and utilize Apex code to roll up the desired amounts are not valid or necessary methods for this request.
NEW QUESTION # 162
Universal Containers expects impacts to operations due to increased demand. The executive team will reach out to current customers and wants to see the number of open cases for the account and parent account.
What should an app builder use to display the number of open cases on the account page?
- A. Flow
- B. Roll-up summary
- C. Approval Process
- D. Cuctom object
Answer: B
Explanation:
Reference:
[Salesforce Help - Roll-up Summary Fields](https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up up_summary_fields.htm&type=5)
NEW QUESTION # 163
At Ursa Major Solar, there is a single Lightning record page for the Celestial Bodies custom object; however, there is a Lightning component the app builder wants to restrict to mobile app users.
Which feature on the Lightning app builder should be utilized?
- A. Chatter feed
- B. Highlights panel
- C. Related list quick links
- D. Component visibility filter
Answer: D
Explanation:
Component visibility filter is the feature on the Lightning app builder that should be utilized to restrict a Lightning component to mobile app users. According to the Salesforce documentation, "Use component visibility filters to show or hide components on a record page based on field values or user profile." Chatter feed, highlights panel, and related list quick links are not features for controlling component visibility, but standard components that can be added to a record page.
NEW QUESTION # 164
Universal Containers wants to deliver purchased containers to remote construction address. In these cases, the customers will supply UC with the coordinates to the location.
What type of field should the app builder use to capture this information?
- A. Text
- B. Number
- C. Geo location
- D. External Lookup
Answer: C
Explanation:
A geolocation field can be used to capture the coordinates of a location in latitude and longitude. This field type can also be used in reports, formulas, validation rules, and Apex
NEW QUESTION # 165
An app builder received a request to extend record access beyond the organization-wide defaults configured. Which two features satisfy this requirement?
Choose 2 answers
- A. Manual Sharing Rules
- B. Permission Set Groups
- C. Public Groups
- D. Sharing Rules
Answer: A,D
Explanation:
Sharing rules and manual sharing are two features that can extend record access beyond the organization-wide defaults. Sharing rules are automatic rules that grant access to groups of users based on certain criteria, such as role, public group, or territory. Manual sharing is a manual way of granting access to individual users or groups by the record owner or someone above them in the role hierarchy. Option B and C are not features that extend record access.
NEW QUESTION # 166
DreamHouse Realty (DR) has many properties for sale and wants to identify the highest value of all Offer__c records on each Property__c record.
What solution should the app builder use to meet DreamHouse Realty's needs?
- A. Text Area (Long)
- B. Lookup Object
- C. Multi-select Picklist
- D. Master-Detail Child Object
Answer: D
Explanation:
The solution that the app builder should use to meet DreamHouse Realty's needs is Master-Detail Child Object. A master-detail relationship can be used to create a parent-child relationship between two objects, where the child records inherit the sharing and security settings of their parent record. The app builder can create a roll-up summary field on the parent object to calculate the highest value of all child records. Option B is incorrect because Text Area (Long) is a field type that allows users to enter up to 131,072 characters on one line, which is not suitable for this requirement. Option C is incorrect because Multi-select Picklist is a field type that allows users to select multiple values from a predefined list, which is not suitable for this requirement. Option D is incorrect because Lookup Object is not a valid term, but rather Lookup Relationship, which is a type of relationship that links two objects together, but does not support roll-up summary fields.
NEW QUESTION # 167
What are two capabilities of Schema Builder? Choose 2 answers
- A. Editing custom settings
- B. Showing selected objects on a page
- C. Creating a new record type
- D. Viewing page layouts in a new window
Answer: A,B
Explanation:
Schema Builder is a tool that allows app builders to view and modify the data model of their Salesforce org. Some of the capabilities of Schema Builder are:
Creating and editing custom objects and fields
Creating and editing relationships between objects
Showing selected objects on a page
Editing custom settings
Schema Builder cannot be used to create a new record type or view page layouts in a new window.
NEW QUESTION # 168
Cloud Kicks has created accustom object called Interests which is joined to Accounts by way of a junction object called Account Interest.
What is the impact to users attempting to view an Account and the associated Account Interest records if they are without read access to the Interest object?
- A. Users will be unable to view the Account Interest records or the Interest records.
- B. Users will be able to view the Account Interest records and will have read-only access to the Interest records.
- C. Users will be unable to view Account records that have a related Account Interest record.
- D. Users will be able to view the Account Interest record, but unable to view the field or any information relating back to the Interest record.
Answer: A
Explanation:
Users will be unable to view the Account Interest records or the Interest records because they do not have read access to the Interest object. This is a standard behavior of Salesforce when a user does not have access to a related object.
NEW QUESTION # 169
Sales reps at Cloud Kicks (CK) forget to submit for approval when CK needs orders reviewed before close won. CK wants to automatically submit opportunities into the Secure Commitment Stage to eliminate manual submission.
Which feature meets the business requirements?
- A. Platform Event-Triggered flow
- B. Record-Triggered flow optimized for Fast Field Updates
- C. Custom button and screen flow
- D. Record-Triggered flow optimized for Actions and Related Records
Answer: D
Explanation:
To automate the submission of opportunities into the "Secure Commitment" stage and eliminate manual submission for approval, the best feature to use is:
Record-Triggered flow optimized for Actions and Related Records (D). This type of flow allows for complex automation that can include submitting records for approval based on specific criteria being met, such as reaching a particular stage in the opportunity lifecycle. It's particularly suitable for handling related record updates and other actions like submissions for approval, which are integral when an opportunity reaches a certain stage.
Record-Triggered Flow optimized for Fast Field Updates (A) is focused primarily on quick updates to fields and may not handle the complexity of submission for approval processes adequately. Custom button and screen flow (B) could be used to manually trigger processes but does not automate the submission. Platform Event-Triggered flow (C) is typically used for integrations and reacting to system-wide events, not for standard record lifecycle management.
Reference for using Flows in Salesforce, particularly for automating business processes like approval submissions:
Record-Triggered Flows: https://help.salesforce.com/articleView?id=sf.flow_considerations_trigger_record.htm&type=5
NEW QUESTION # 170
Cloud Kicks works on an annual subscription model. When a sales rep marks an opportunity as closed won, a new opportunity should automatically be created for the renewal. The contracts team works outside of Salesforce but also needs to be notified about closed deals in order to initiate the contract process with the customer.
Which automation solution would meet these requirements?
- A. Workflow Rule
- B. Approval Process
- C. Validation Rule
- D. Process Builder
Answer: D
Explanation:
The automation solution that would meet these requirements is Process Builder. Process Builder is a tool that can create and update records, send email alerts, submit records for approval, invoke flows, call Apex classes, and post to Chatter based on certain criteria and actions. The app builder can use Process Builder to create a process that starts when an opportunity is marked as closed won, creates a new opportunity record for the renewal with pre-populated fields, and sends an email alert to the contracts team. Option A is incorrect because an approval process is not suitable for this requirement, as approval processes are used to define the steps and criteria for approving records. Option B is incorrect because a validation rule is not suitable for this requirement, as validation rules are used to enforce data quality and prevent users from saving invalid records. Option D is incorrect because a workflow rule is not suitable for this requirement, as workflow rules are considered legacy tools and have limitations compared to Process Builder.
NEW QUESTION # 171
Universal Containers uses a custom picklist field Account Region on the account record. They want this region to be reflected on all related contact records and stay in sync if the value of this field changes on the Account.
How should an app builder meet this requirement?
- A. Create a picklist field called 'Account Region' on Contact object > Create a workflow rule to update this picklist field if the Account Region field on the Account is changed.
- B. Create a formula field on the Contact object > Set the value of the formula to ISPICKVAL(Account.Account_Region__c).
- C. Create a text field called 'Account Region' on Contact object > Create a workflow ruleto update this picklist field if the Account Region field on the Account is changed.
- D. Create a formula field on the Contact object > Set the value of the formula to TEXT(Account.Account_Region__c).
Answer: D
Explanation:
Creating a formula field on the Contact object and setting the value of the formula to TEXT(Account.Account_Region__c) would reflect the region of the related account on the contact record and stay in sync if the value changes on the account. This is the most efficient and maintainable way to meet the requirement. Creating a workflow rule or a picklist field would require additional configuration and complexity
NEW QUESTION # 172
An app builder wants to update a field on the parent record when a child record connected via lookup is deleted.
What automation should the app builder use?
- A. Process Builder
- B. Workflow rule
- C. Apex code
- D. Screen flow
Answer: C
Explanation:
The app builder should use Apex code to update a field on the parent record when a child record connected via lookup is deleted. Apex code is a programming language that allows developers to execute complex logic on the Salesforce platform. Apex code can be triggered by certain events, such as insert, update, delete, or undelete of records. In this case, the app builder can write an Apex trigger that runs after a child record is deleted and updates a field on the parent record accordingly. Option A, B, and D are not automation tools that can perform this task.
NEW QUESTION # 173
Sales Managers want to be automatically notified any time there is a change to an Opportunity Close Date and want these changes to be tracked on the Opportunity.
Which two configurations should an app builder recommend?
- A. Activate Historical Trending for Opportunities.
- B. Use a record-triggered flow on Opportunity and a Chatter post action.
- C. Create an Opportunity outbound message.
- D. Enable Feed Tracking on Opportunities.
Answer: B,D
Explanation:
A (Feed Tracking) allows Salesforce to automatically post updates to the Opportunity feed when certain fields (like Close Date) change.Exact Extract:"Feed tracking lets users see updates to records they follow. When feed tracking is enabled on an object, field changes appear in the feed." - Salesforce Help | Feed Tracking Overview C (Record-Triggered Flow + Chatter Post) allows real-time automated notifications to specific users (e.g., Sales Managers) when the Close Date changes.Exact Extract:"You can automate notifications by creating a record-triggered flow that posts to Chatter or sends notifications when specified conditions are met." - Salesforce Help | Flow Builder Notifications Why not B:Outbound messages are used for system-to-system communication, not internal notifications.
Why not D:Historical Trending is for reporting over time, not notifications or tracking.
Reference:
Salesforce Help | Feed Tracking Overview
Salesforce Help | Flow Builder Notifications
Salesforce Platform App Builder Exam Guide | Business Logic and Process Automation
NEW QUESTION # 174
Universal Because of the small screen, they currently have to scroll down the page to view the information for an account based on criteria about the related contact.
Which solution should an app builder use to fulfill this requirement?
- A. Add a related record component to the page layout
- B. Hide the component behind a tab on the page layout.
- C. Set the filter type on the component visibility to display based on user permissions. using custom permission to define the dynamic criteria.
- D. Set the component visibility to display based or an advanced filter type, using the contact field's) to define the dynamic criteria.
Answer: D
Explanation:
Reference:
Salesforce Help - Dynamic Forms
NEW QUESTION # 175
Cloud Kicks (CK) Is finding sales reps are Inconsistent in data entry when deals are won. CK requires that custom shoes are shipped within two weeks after the close date. A custom field called Scheduled Ship Date on the opportunity records the ship date.How should the app butler ensure this field is properly filed out before setting the opportunity to closed won?
- A. ISPICKVAL( StageName ,"Closed Won") && ( Scheduled _Ship_Date_c-CloseDate ) > 14
- B. ISPICKVAL( StageName= CloseDate ) > 14,losed Won") && ( CloseDateScheduled_Ship_Date_c) >14
- C. OR(ISPICKVAL( StageName ,"Closed Won") && ( Scheduled_Ship_Date_cCloseDate)>14,ISBLANK(Scheduled_Ship_Date_c))
- D. OR(ISPICKVAL( StageName ="Closed Won") && ( Scheduled_Ship_Date__c- CloseDate ) > 14,ISBLANK(Scheduled_Ship_Date__c))
Answer: C
Explanation:
The correct validation rule formula to ensure that the Scheduled Ship Date field is properly filled out before setting the Opportunity to Closed Won is:
OR(ISPICKVAL( StageName ,"Closed Won") && ( Scheduled_Ship_Date_cCloseDate)>14,ISBLANK(Scheduled_Ship_Date_c)) This formula checks two conditions: if the StageName is Closed Won and the Scheduled Ship Date is more than 14 days after the Close Date, or if the Scheduled Ship Date is blank. If either condition is true, the validation rule will fire and prevent saving the record. The other formulas are incorrect because they either use incorrect syntax (such as "=" instead of "," or missing parentheses) or incorrect logic (such as checking if the Scheduled Ship Date is less than 14 days after the Close Date)
NEW QUESTION # 176
Universal Containers uses Contracts for agreements with customers. A sales manager is required to provide approval for contracts and director approval for any contract over $10,000.
Which two options should an app builder use to ensure all contracts route for the correct approval and also prevent the sales rep from making changes to the record while it is being approved?
Choose 2 answers
- A. Create an approval process on the Contract object with one step for each sales manager that sets the approver as the director.
- B. Create an approval process on the Contract object with criteria set on a second approval step set as 'Amount__c > 10,000' and set the approver as director.
- C. Create an approval process on the Contract object and set the field for 'Next Automated Approver Determined By' as Manager'.
- D. Create a validation rule on the Contract object that prevents updates to the contract record while it is being reviewed.
Answer: B,D
Explanation:
The app builder should use two options to ensure all contracts route for the correct approval and also prevent the sales rep from making changes to the record while it is being approved:
Create an approval process on the Contract object with criteria set on a second approval step set as 'Amount__c > 10,000' and set the approver as director. An approval process is a type of process that automates how Salesforce records are approved in an organization. An approval process can have multiple steps with different criteria and approvers. In this case, the app builder can create an approval process on the Contract object with two steps: one for the sales manager approval and one for the director approval if the contract amount is over $10,0001.
Create a validation rule on the Contract object that prevents updates to the contract record while it is being reviewed. A validation rule is a type of rule that checks data quality by verifying that the data in a record meets certain standards before it can be saved. A validation rule can prevent users from making changes to a record that is in a certain status or stage. In this case, the app builder can create a validation rule on the Contract object that prevents updates to the contract record if its Approval Status field is not equal to Not Submitted2. Option B and D are not options that can ensure all contracts route for the correct approval and also prevent the sales rep from making changes to the record while it is being approved.
NEW QUESTION # 177
When an opportunity is closed date is pushed more than 30days, manager approval is required. An approval process is in place but reps frequently forget to submit for approval to run the process.
How can an app builder ensure that these opportunities are submitted into the approval process?
- A. Change the entry criteria on the approval process to criteria are met and lock the record on initial submission.
- B. Use a validation rule and an email alert to the manager requesting approval.
- C. Submit the record for approval from an automated process.
- D. Give the manager the "API Enabled" permission to permit approval responses by email.
Answer: C
Explanation:
To ensure that opportunities are submitted into the approval process when their close date is pushed more than 30 days, an app builder should use an automated process to submit the record for approval. An automated process can be created using tools such as Process Builder or Flow Builder, and it can define the criteria and actions for submitting a record for approval. [Source]
NEW QUESTION # 178
......
Get ready to pass the Plat-Admn-202 Exam right now using our Salesforce Developer Exam Package: https://www.realvalidexam.com/Plat-Admn-202-real-exam-dumps.html
