Cloud Kicks is a large company with many divisions. Some divisions have a higher
turnover, so each division wants to be able to create and manage users only within their
division.
What should the administrator do to set this up?
A. Set up delegated administrators for the division leaders.
B. Assign a flat territory role hierarchy for the divisions.
C. Create a permission set group for the division leaders.
D. Customize and assign profiles for the division teams.
Explanation: Delegated administration allows administrators to delegate certain user management tasks to other users without granting them full administrative privileges. Delegated administrators can create and manage users only within specified roles or public groups. This option will meet the requirement of allowing each division to create and manage users only within their division.
DreamHouse Realty has a rental team and a real estate team. The two teams have
different safes processes and capture different client information on their opportunities.
How should an administrator extend the Opportunity object to meet the teams' different
needs?
A. Leverage Opportunities for the Real Estate Team and create a new custom object for the Rental Team Opportunities.
B. Use separate record types, page layouts, and sales processes for the Rental and Real Estate Teams.
C. Create Opportunity Teams for the Rental and Real Estate Teams and make appropriate fields visible to only the necessary team.
D. Add a section for Rental and a section for Real Estate on the Opportunity Master Record Type to keep the information separate.
Explanation: As explained in question 4, record types allow administrators to offer different business processes, picklist values, and page layouts to different users based on their profiles. By using separate record types for rental and real estate opportunities, DreamHouse Realty can capture different client information on their opportunities using custom page layouts for each record type. The record types can also determine which sales processes and paths are available for each opportunity type.
A user is getting an error when attempting to merge two accounts. The administrator
checks the
profile to see the user has Read/Write permission on Accounts and is the owner of both
records.
What is preventing the user from completing the merge?
A. Only administrators have permission to merge records.
B. The user is assigned to the wrong territory.
C. The Account matching rules are not set.
D. The Delete permission is missing on the user for Accounts.
Explanation: The Delete permission is missing on the user for Accounts is what is preventing the user from completing the merge. Merging accounts is a way to combine up to three duplicate accounts into one master record and update the related records accordingly. Merging accounts requires the Delete permission on accounts because merging accounts involves deleting the duplicate records and keeping only the master record.
A sales manager at AW Computing has created a contact record but is missing some of the information to complete the record. The organization-wide default for Accounts is set to Public Read Only, and Contacts are controlled by parent.
A. Who will be able to edit this new contact record?
B. Users above the sales manager in the role hierarchy
C. All users in the organization
D. The owner and users below the owner in the role hierarchy
E. Sales manager and system administrator
Explanation: The sales manager and system administrator will be able to edit this new contact record because they are either the owner or have Modify All Data permission respectively. Users above or below the sales manager in the role hierarchy will not be able to edit this contact record because contacts are controlled by parent and accounts are set to Public Read Only. All users in the organization will be able to view but not edit this contact record because accounts are set to Public Read Only.
Cloud Kicks has two record-triggered flows on the same object. One flow creates a child
record when criteria are met. The second record-triggered flow is based on criteria to check
if the child record exists and updates a field. The field on the child record that needs to be
updated Is still null after the second record trigger.
What should the administrator do to resolve this issue?
A. Make a new record-triggered flow on the child object to update the field on the parent record.
B. Have the record-triggered flows fire on create or edit to update the field.
C. Combine the two flows into one with checks to see which part of the flow needs to be run.
D. flows into schedule flows and have them update the field.
Explanation: Flows are tools that automate business processes by collecting data and performing actions in your org or an external system. Flows can be triggered by various events such as record creation, updates, or invocations from other processes or flows. Flows can also have decision elements that evaluate conditions and determine which path to follow in the flow. By combining the two flows into one with decision elements, the administrator can ensure that the flow runs in the correct order and updates the field on the child record after it is created by the first flow.
Page 10 out of 44 Pages |
Previous |