Cloud Kicks has been tracking how many participants wear the company's shoes in each marathon. The administrator creates two custom objects: Races and Runners. There is a master-detail relationship between them as well as a Roll-up Summary field on the Races object to show the count of runners in each race. Requirements have changed, and the administrator wants to delete the Master-detail Relationship field without deleting the Runners records.
What action should an administrator take before the Relationship field can be deleted?
Answer : A
Changing the field type to a Lookup Relationship will allow deleting the Relationship field without deleting the Runners records. A lookup relationship creates a loose association between two objects, where the child records do not depend on the parent records for their existence. A lookup relationship can be deleted without affecting the child records, unlike a master-detail relationship that enforces cascading deletes. Reference: https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm&type=5
AW Computing it running a special bundle deal on monitors and keyboards. Normally, discounts need VP approval, but this special bundle is pre-approved.
What should the administrator recommend for these requirements?
Answer : B
A price book is a list of products and their prices for a specific segment of customers or market. By creating a separate price book for the special bundle deal on monitors and keyboards, AW Computing can offer different prices for these products without affecting their standard prices or requiring VP approval. The price book can also specify which products are included in the bundle and which are not. Reference: https://help.salesforce.com/s/articleView?id=sf.products_pricebooks_def.htm&type=5
Cloud Kicks (CK) has a backup team of employees that helps short-staffed departments. These users could be working with sales one day and service the next. CK is implementing new Lightning record pages for each department so that they view records In a way that makes sense for each department.
How should the administrator ensure this Is configured correctly?
Answer : A
Configuring one app per department and activating record pages for each app will ensure that users view records in a way that makes sense for each department. An app is a collection of items that work together to serve a particular function. An app can have different record pages for different objects and profiles. By activating record pages for each app, the administrator can customize what users see based on their app context. Reference: https://help.salesforce.com/s/articleView?id=sf.app_manager_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.app_builder_customize_lex_pages_assign.htm&type=5
An administrator need a business process automated, but only for certain user and profiles. The administrator will need to frequently update which users and profiles will use the process. After evaluating the declarative options, it was determined that this functionality must be done via an Apex trigger.
What software requirement should the administrator request so that process execution can be declaratively controlled?
Answer : D
Use a custom permission set that is assigned to the user because custom permissions are a way to grant access to custom processes or functionality based on user profiles or permission sets. Custom permissions can be referenced by Apex code, validation rules, flows, or other logic to control whether a process should run for a user or not. Custom permissions can be used to declaratively control process execution by assigning them to users or profiles.
The Service team at Cloud Kicks needs a way to show the current status from the Account on the Case. This value should be on the page and is used in validation rules.
What should the administrator recommend to solve this?
Answer : A
A cross-object formula is a formula that references fields from related objects. The administrator can create a cross-object formula field on the Case object that displays the current status from the Account. This field can be used in validation rules and other processes. Reference: https://help.salesforce.com/s/articleView?id=sf.tips_on_building_formulas_cross_object_formulas.htm&type=5
Cloud Kicks (CK) has a backup team of employees that helps short-staffed departments. These users could be working with sales one day and service the next. CK is implementing new Lightning record pages for each department so that they view records In a way that makes sense for each department.
How should the administrator ensure this Is configured correctly?
Answer : A
Configure one app per department and activate record pages for each app is how the administrator should ensure this is configured correctly. An app is a collection of items that work together to serve a particular function for a group of users. An app can include items such as tabs, objects, reports, dashboards, and record pages. A record page is a type of Lightning page that displays details about a specific record. A record page can be customized using Lightning App Builder and activated for different apps, profiles, or record types. By configuring one app per department and activating record pages for each app, the administrator can ensure that the backup team users can view records in a way that makes sense for each department depending on which app they are using.
The administrator at Cloud Kicks created a flow in a sandbox that walks service agents through the Return Merchandise Authorization creation process. The administrator deployed the flow to production with a Change Set. Users are unable to use the flow in production.
Which step should the administrator take?
Activate the flow administrator take?
Answer : A
A flow is an automation tool that allows you to create processes that perform actions based on user input or record changes. A flow can be triggered by a user who launches it from a button, link, or Lightning page, or by the system when a record is created or updated. A flow has different versions that can be active or inactive. An active version is the one that runs when the flow is triggered, while an inactive version is the one that is saved but not running. When you deploy a flow to production with a change set, the flow version is deployed as inactive by default. This means that you need to activate the flow manually after deployment if you want it to run in production. Reference: https://help.salesforce.com/s/articleView?id=sf.flow_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.flow_distribute_changesets.htm&type=5