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

The feature that the app builder should use to solve this issue is component visibility filter. A component visibility filter is a setting that can be applied to a Lightning component on a record page to control when the component is hidden or displayed based on certain conditions. The app builder can use a component visibility filter to hide the component from users with a Marketing profile. Option A is incorrect because detail page layouts are not related to Lightning components, but rather the fields and related lists that appear on record detail pages. Option C is incorrect because field-level security is not related to Lightning components, but rather the access level of fields for different profiles or permission sets. Option D is incorrect because AppExchange is not related to Lightning components, but rather an online marketplace where users can find and install apps and components.

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 steps that the app builder should take to meet these requirements are creating a Partial Copy Sandbox and using a sandbox template. A Partial Copy Sandbox can include data records, exclude confidential objects, and be refreshed weekly. A sandbox template can specify which objects and data are copied from the production org to the sandbox org. Option A is incorrect because creating a Full Sandbox and using a sandbox template is not necessary for this requirement, as Full Sandboxes copy all data and metadata from the production org and can only be refreshed every 29 days. Option B is incorrect because creating a Developer Pro Sandbox and scheduling Data Loader to download selected object data weekly is not feasible for this requirement, as Developer Pro Sandboxes do not include data records by default and Data Loader cannot be scheduled to run weekly. Option D is incorrect because creating a Developer Sandbox and scheduling Data Loader to download selected object data weekly is not feasible for this requirement, as Developer Sandboxes do not include data records by default and Data Loader cannot be scheduled to run weekly.

Create a master-detail relationship field on Applicant__c to Application__c is what the app builder should recommend to meet the requirements of allowing the same applicant to apply for multiple open positions using a single application. This will create a many-to-many relationship between Applicant__c and Open_Position__c using Application__c as a junction object. Create a master-detail relationship on Open_Position__c to Application__c, create a master-detail relationship field on Application__c to Open_Position__c, and create a lookup relationship field on Applicant__c to Application__c are not valid or correct ways to create a many-to-many relationship.

Record-triggered flow is the automation tool that the app builder should use to best address all these requests of sending an email to the finance manager and creating a task for the sales manager when a new client is won. According to theSalesforce documentation, ''Record-triggered flows automate processes for you. They start when a record is created or updated, or when a platform event occurs.'' A record-triggered flow can perform actions such as sending an email alert or creating a record based on criteria or conditions. Screen flow, Apex, and Approval process are not automation tools that can handle all these requests.

Create a validation rule on the Account object is how the app builder can keep accounts with open opportunities from being deleted. According to theSalesforce documentation, ''Validation rules verify that data entered by users in records meet the standards you specify before they can save it.'' A validation rule can check if an account has any open opportunities and display an error message if someone tries to delete it. Create an Apex trigger on the Account object, remove the delete button on the account layout, and remove the Delete permission from the Sales Rep profile are not valid or sufficient solutions for this requirement.

A: Changing the Lead Matching Rule to 'Block on create' will directly prevent duplicates at the point of lead creation based on defined criteria.

C: Changing the Lead Duplicate Rule to 'Bypass Sharing Rules' allows the system to compare leads across the entire organization regardless of the user's access level, which is crucial especially when OWD is set to 'Private'.

Reference:

Salesforce Help - Duplicate Management