Salesforce Platform-App-Builder - Salesforce Certified Platform App Builder (Plat-Admn-202)

When a record is submitted for approval, Salesforce automatically locks it, preventing further edits until it is approved, rejected, or recalled.

Why A (Record Lock) is correct:Exact Extract:“When a record is submitted for approval, Salesforce automatically locks the record to prevent users from editing it unless they have ‘Modify All Data’ permission or are designated as an approver.” — Salesforce Help | Approval Processes OverviewThus, the user will receive a message indicating that the record is locked and cannot be edited.

Why A (Record Lock) is correct:Exact Extract:“When a record is submitted for approval, Salesforce automatically locks the record to prevent users from editing it unless they have ‘Modify All Data’ permission or are designated as an approver.” — Salesforce Help | Approval Processes OverviewThus, the user will receive a message indicating that the record is locked and cannot be edited.

Why not B or C:Once locked, no field (including Description) is editable by the submitter.

Why not D:Ownership does not change upon approval submission.

Historical data will be updated to 12:00 timestamp when changing a Date field to Date/Time field. According to the Salesforce documentation, “When you convert a Date field to Date/Time, Salesforce appends “12:00” to existing data in your records.” The change will not be instant, but will require some time for processing. The field name will not change unless specified by the app builder. Data loss will not be experienced, but data accuracy might be affected.

The best actions to take to avoid creating duplicate leads when uploading a list of 400 leads are to utilize a Lead Matching Rule and corresponding Duplicate Rule to block newly created duplicate leads, and to upload the lead list using the import wizard and select a Matching type to prevent duplicate lead creation. The Lead Matching Rule defines the criteria for identifying duplicate leads, and the Duplicate Rule defines the actions to take when a duplicate is detected. The import wizard allows users to choose a Matching type based on the Lead Matching Rule and block or allow duplicates. Using Data Loader’s update function or enabling Duplicate Matching in the Data Management section will not prevent duplicate lead creation.

 NOT(ISBLANK(Job_Accepted__c)) && ISCHANGED(Hire_Date__c) is the validation formula that the app builder should use to meet the requirement of preventing changes to Hire Date after Job Accepted is entered. This formula will return TRUE if Job Accepted is not blank and Hire Date is changed, which will display an error message and prevent saving the record. The other formulas are not correct or valid.

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.

 Global actions can be accessed anywhere actions are pages, feed and Chatter groups. This is correct because global actions are not tied to a specific object, and they can be added to any page that supports actions, such as record pages, home pages, feed pages, and Chatter groups.

Research and evaluate products available on AppExchange to send mass emails is the action that the app builder should take to meet the requirement of broadcasting an email to 7,000 contacts in Salesforce on a regular basis. AppExchange is a marketplace where app builders can find products or solutions that can extend Salesforce functionality. There are many products on AppExchange that can send mass emails without hitting the Salesforce limit. Request Salesforce increase the number of maximum daily emails, develop Apex code and Lightning web component to send daily emails, and export Contacts to a CSV file and use an email client to send the emails are not valid or recommended actions.

 Marking stage dependent fields as required on the Opportunity page layout is a good solution to improve efficiency and data quality, as it ensures that users enter the necessary information for each stage of the sales process. Adding a Path component with fields and instructions aligning to stages on the Opportunity is another good solution to improve efficiency and collaboration, as it provides guidance and best practices for users to move the Opportunity along the sales cycle. Using two Tabs components to separate record information from activities may not be an optimal solution, as it may reduce the visibility and accessibility of important data. Setting up an approval process requiring manager consent at each stage of the Opportunity may not be a feasible solution, as it may introduce unnecessary delays and complexity in the sales process

The common items that can be moved using a change set are custom object, Apex class, and custom field. These are metadata components that can be deployed from one environment to another using change sets. Web-to-lead and standard fields are not metadata components that can be moved using change sets.