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

The requirement can be met by using a combination of process builder and approval process. The process builder can be used to trigger the approval process when the close date is delayed by more than 60 days. The approval process can be configured to require unanimous approval from the manager and VP of sales.

A master-detail relationship between two objects automatically creates a report type that includes both objects. The app builder does not need to create a custom report type for this scenario. The report type will have the format of Parent object with Child object

 The app builder should use Sum as the type of summary in the roll-up summary field. A Sum type of summary allows the app builder to calculate the total value of a numeric field from the child records related to a parent record by a master-detail relationship. The app builder can create a roll-up summary field on the Account object that sums the Amount field from the won Opportunities related to each Account. Count is not a valid type of summary, as it does not calculate the total value of a numeric field. A Count type of summary allows the app builder to count the number of child records related to a parent record by a master-detail relationship. Max is not a valid type of summary, as it does not calculate the total value of a numeric field. A Max type of summary allows the app builder to display the largest value of a numeric or date field from the child records related to a parent record by a master-detail relationship. Min is not a valid type of summary, as it does not calculate the total value of a numeric field. A Min type of summary allows the app builder to display the smallest value of a numeric or date field from the child records related to a parent record by a master-detail relationship.

The feature that the app builder should use to allow users to create the opportunity is a quick action. A quick action is a type of custom button or link that can create or update records, log calls, send emails, or launch flows from a record page or a global menu. The app builder can create a quick action on the account object that creates an opportunity record with pre-populated fields. Option B is incorrect because a default action is not a valid term, but rather a standard action that appears on every record page by default, such as Edit or Delete. Option C is incorrect because a custom button is not suitable for this requirement, as custom buttons can only display a URL or execute JavaScript when clicked. Option D is incorrect because a custom link is not suitable for this requirement, as custom links can only display a URL or execute JavaScript when clicked.

The two tools that an app builder could combine to display the number of open cases on the account page are Flow and Process Builder. Flow is a tool that allows the app builder to create a declarative automation that can query, manipulate, and display data from multiple objects. Process Builder is a tool that allows the app builder to create a trigger-based automation that can invoke a Flow when a record is created or updated. By using these two tools, the app builder can create a solution that can query the number of open cases for the account and parent account and display them on the account page using a screen element. Workflow is not a suitable tool, as it cannot query or display data from multiple objects. It can only perform actions such as field updates, email alerts, tasks, or outbound messages. Approval Process is not a suitable tool, as it is used to automate the approval of records based on certain criteria and predefined steps. It cannot query or display data from multiple objects.

To count child records (Trails) on a parent record (Park) without code, a Roll-up Summary field is required. However, Roll-up Summary fields only work when a Master-Detail relationship exists.

Why A (Roll-up Summary) is correct:Exact Extract:“A roll-up summary field calculates values from related records, such as those in a related list, on a master record. You can count the number of related records or summarize fields.” — Salesforce Help | Roll-Up Summary Fields

Why D (Master-Detail Relationship) is correct:Exact Extract:“Roll-up summary fields are available only for master-detail relationships.” — Salesforce Help | Relationships OverviewTherefore, the Trail object must be the detail and the Park object the master to enable the roll-up count.

Why D (Master-Detail Relationship) is correct:Exact Extract:“Roll-up summary fields are available only for master-detail relationships.” — Salesforce Help | Relationships OverviewTherefore, the Trail object must be the detail and the Park object the master to enable the roll-up count.

Why not B:Formula fields can’t count related records.

Why not C:Lookup relationships don’t support roll-up summaries natively.

Guided Action Flows on the record page can help service agents meet the requirement of confirming a user identity before providing support information over the phone. Guided Action Flows are a series of screens that guide agents through a predefined process, such as verifying user information, collecting case details, or resolving issues

The solution that an app builder should use to meet this requirement is creating a custom report type with converted leads as the primary object. A custom report type is a template that defines the objects and fields that are available for a report. The app builder can create a custom report type that has converted leads as the primary object and includes fields from related objects, such as accounts, contacts, and opportunities. This way, sales reps can create reports on converted leads and see their related information. Option A is incorrect because enabling preserve lead status in the lead conversion settings does not affect the reporting on converted leads, but rather allows users to retain the original lead status after conversion. Option B is incorrect because assigning the representative view and edit converted leads permission does not affect the reporting on converted leads, but rather allows users to view and edit converted lead records. Option C is incorrect because ensuring the representative has read access to the original lead records does not affect the reporting on converted leads, but rather allows users to view the original lead records.

The app builder should use Data Loader to quickly insert a list of over 60,000 net new Accounts. Data Loader is a tool that allows users to insert, update, delete, or export large amounts of data from Salesforce using CSV files or database connections. Data Loader can handle up to 5 million records at a time and supports features such as bulk API, batch operations, mapping files, etc. Data Loader is ideal for loading large data sets into Salesforce quickly and efficiently. Lightning Object Creator is not a valid tool, as it cannot insert data into existing objects. Lightning Object Creator is a tool that allows users to create custom objects from spreadsheet data by uploading a file and mapping columns to fields. It cannot load data into existing objects or handle more than 500 records at a time. Import Wizard is not a valid tool, as it cannot handle more than 50,000 records at a time. Import Wizard is a tool that allows users to insert, update, or delete data from Salesforce using CSV files or Excel files. Import Wizard supports standard objects and some custom objects and provides features such as field mapping, duplicate detection, data validation, etc. Import Wizard is ideal for loading small data sets into Salesforce with more control and accuracy.

It lacks setting up field-level security and adding fields to the page layout, so you have to choose the manual way of field creation. Adds another layer of risk with changes in Schema Builder since it is deployed in real-time.

Salesforce Schema Builder is a powerful tool for visualizing and creating objects, fields, and relationships in Salesforce, but it has certain limitations when building custom objects.

Option B (Fields and relationships can be created, but they will be unable to add the fields to the page layout from the canvas): In Schema Builder, while you can create new custom objects, fields, and relationships, you cannot directly add fields to the page layout from within the Schema Builder interface. After creating a field, you need to navigate to the Page Layout Editor to manually place the new field on the layout.

Schema Builder Overview

Option A: This is incorrect because you can perform multiple actions within Schema Builder without needing to click Save each time. Salesforce will save these changes when you click Save once at the end.

Option C: While relationships can be created in Schema Builder for both standard and custom objects, there is no requirement to use Lightning Object Manager to create relationships with standard objects.

Option D: Schema Builder supports the creation of formula fields along with other types of fields. There is no exclusion for formula fields.

In summary, Option B is the correct limitation of Schema Builder: you cannot add fields to page layouts directly from the Schema Builder interface.