Salesforce Certified Platform App Builder Practice Test - Questions Answers, Page 11

The two components that could be included on the layout to display the actions are the Highlights panel and the Path. The Highlights panel is a component that shows key information and actions for a record. It can display up to 10 actions from the Mobile & Lightning Actions section of the page layout. The Path is a component that shows the stages of a process, such as a sales process or a service process. It can display up to 5 actions from the Mobile & Lightning Actions section of the page layout. The Chatter and Activities components do not display actions from the Mobile & Lightning Actions section of the page layout. They display other types of actions, such as posting, commenting, liking, logging a call, creating a task, or sending an email.

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 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)

The app builder should recommend configuring Campaign Hierarchies and Campaign statistics to understand return on investment for the latest advertising buy. Campaign Hierarchies allow users to organize campaigns into parent-child relationships based on common goals or themes, such as product lines or marketing channels. Campaign statistics allow users to track and measure key metrics for campaigns and campaign hierarchies, such as budgeted cost, actual cost, expected revenue, number of leads, number of contacts, etc. By using these features, users can calculate return on investment for each campaign and campaign hierarchy by comparing actual cost and expected revenue. Utilizing Account Hierarchies and Roll-Up Summary fields is not a valid recommendation, as it does not relate to campaigns or advertising buys. Account Hierarchies allow users to organize accounts into parent-child relationships based on business structure or affiliation, such as subsidiaries or partners. Roll-Up Summary fields allow users to aggregate numeric values from child records related to a parent record by a master-detail relationship. Running an opportunities pipeline report is not a valid recommendation, as it does not provide information about campaigns or advertising buys. An opportunities pipeline report shows the stages and amounts of opportunities in the sales process, such as prospecting, qualification, negotiation, etc. Changing to a public security model is not a valid recommendation, as it does not affect the ability to track and measure campaigns or advertising buys. A public security model is a type of organization-wide default that determines the baseline level of access that users have to records they do not own. A public security model grants all users read or read/write access to all records, regardless of ownership.

The two actions that an app builder should take to meet the requirements are: Implement a sharing rule. A sharing rule is a way to grant additional access to records based on certain criteria, such as record owner, role, profile, or field value. The app builder can create a sharing rule that grants read access to all accounts with the VIP Account field value to all users. This way, all users can view these accounts, but only the owners can edit them. Change organization-wide defaults. Organization-wide defaults are the baseline level of access that users have to records they do not own. The app builder can change the organization-wide default for accounts from Public Read Only to Private. This way, only the owners can view and edit their own accounts, unless additional access is granted by other means, such as sharing rules. Configuring a permission set is not a valid action, as it does not affect record-level access. A permission set is a way to grant additional permissions and access settings to users on top of their profile settings, such as object permissions, field permissions, app permissions, etc. Setting up an Account Team is not a valid action, as it does not restrict record-level access. An Account Team is a way to share an account and its related records with a group of users who work together on the account, such as sales reps, managers, or support agents. An Account Team grants additional access to team members based on predefined roles and access levels.

The app builder should use Web-to-Case to enable visitors to the website to open cases. Web-to-Case is a feature that allows users to create an HTML form that can be embedded into a public-facing website. When visitors fill out and submit the form, a new case is automatically created in Salesforce with the information from the form fields. Web-to-Case can also assign cases to queues or users based on predefined rules and criteria. Outbound message is not a valid tool, as it does not enable visitors to open cases. An outbound message is a type of workflow action that sends a secure XML message to a designated endpoint URL when a record meets certain criteria. An outbound message can be used to integrate Salesforce with external systems or applications. Screen flow is not a valid tool, as it does not enable visitors to open cases from a public-facing website. A screen flow is a type of flow that allows users to create an interactive guided process that can collect, display, and update data from multiple objects within Salesforce. A screen flow can be embedded into Lightning pages or Visualforce pages, but it cannot be exposed to unauthenticated users on a public website. Email-to-Case is not a valid tool, as it does not enable visitors to open cases from a website. Email-to-Case is a feature that allows users to create cases from email messages sent to a specific email address. Email-to-Case can also capture email attachments and thread information and associate them with the case.

To import opportunities with the proper country currency, the app builder needs to include the currency ISO code in all currency fields in the import file, and use Data Loader to import the records. Data Loader supports importing multiple currencies, while Import Wizard does not.The currency ISO code column in the import file specifies the currency for each record

Formulas cannot reference child records, only parent records. This is a limitation of formulas that could be causing the issue.To include data from related child records, the app builder could use roll-up summary fields or Apex triggers instead

Before replacing workflow rules and Apex triggers with Process Builders, the app builder should consider avoiding generating infinite loops and combining actions when possible. Infinite loops can occur when a process updates a record that causes another process to run on the same record, and so on.Combining actions can reduce the number of processes and improve performance and maintainability