An administrator has found a free app on the AppExchanged and would like to install it.
Which three items should the administrator take to consideration before installed he
managed package?
Choose 3 answers
A. Custom objects and custom fields used by the app count against the org’s limits.
B. Managed apps do not undergo a formal security review by Salesforce.
C. Apps may require certain Salesforce editions or features to be enabled.
D. Apps may require external, third-party web services to function properly.
E. Apps must be installed in production before the app can be installed in a sandbox.
Explanation:
Before installing a managed package from the AppExchange, the administrator should take
into consideration several factors, such as:
Custom objects and custom fields used by the app count against the org’s limits.
The administrator should check how many custom objects and fields are available
in their org and how many are used by the app.
Apps may require certain Salesforce editions or features to be enabled. The
administrator should check the app’s requirements and compatibility with their
org’s edition and features.
Apps may require external, third-party web services to function properly. The
administrator should check if the app integrates with any external services and if
they need to set up any authentication or configuration for them.
The other two options are incorrect because:
Managed apps do undergo a formal security review by Salesforce before they are
listed on the AppExchange.
Apps can be installed in a sandbox before they are installed in production.
Ursa Major Solar's administrator has configured multiple record-triggered flows to run
before or after the record is saved on the Account object.
What should the administrator consider when a record-triggered flow executes first?
A. Assign the highest priority to the record-triggered flow which should execute first.
B. The flow with the longest execution time will execute first.
C. The flow with the shortest execution time will execute first.
D. The order in which those flows are executed is not guaranteed.
Explanation: The order in which record-triggered flows are executed is not guaranteed. If there are multiple record-triggered flows on the same object and trigger type, Salesforce does not guarantee which one runs first. Therefore, the administrator should consider this when designing record-triggered flows that depend on each other’s outcomes.
The administrator at Cloud Kicks is evaluating the capabilities of Schema Builder to create
custom objects and custom fields. The administrator likes the user interface of the Schema
Builder, as opposed to the new object and field wizards, but also notices some limitations.
What needs to be configured from the object manager instead of Schema Builder?
A. Add custom fields to the page layout.
B. Make available for Customer Postal.
C. Enable field history tracking
D. Allow Reports and Activities
Explanation: Field history tracking is a feature that allows you to monitor changes to certain fields on an object and display them in a history related list. Field history tracking can help you audit data quality, compliance, or business processes. Field history tracking cannot be configured from Schema Builder, but it can be configured from Object Manager. In Object Manager, you can select an object and enable field history tracking from its settings page. Then, you can choose up to 20 fields per object to track and add the history related list to the page layout.
Northern Trail Outfitters (NTO) has a private sharing model for records containing a
customer's credit Information. These records should be visible to a sales rep's manager but
hidden from their colleagues.
How should an administrator adjust NTO's sharing model to ensure the correct amount of
confidentiality?
A. Use validation rules targeting the logged-in user.
B. Add View All access for the object via the managers profile.
C. Create sharing rules for each manager based on the record owner.
D. Grant access using hierarchies via the sharing settings.
Explanation: To ensure that sales reps’ managers can view records containing customer’s credit information but their colleagues cannot, NTO should grant access using hierarchies via the sharing settings. This option allows users above another user in the role hierarchy to have access to records owned by or shared with users below them in the hierarchy.
An administrator created two record types on the Account object: Internal Customers and
External Customers. A custom profile called Sales has the External Customers record type
assigned. The sharing rules for Accounts arm set to Public Read Only. On occasion. Sales
users notice that an Account record has the wrong record type assigned. The administrator
has created a screen flow that will change the record type on the user's behalf.
What will happen to the Sales user's record access after running this flow?
A. Read access will be lost to the record.
B. Edit access will be lost to the record.
C. Record Access remains the same.
D. A new record owner will be assigned.
Explanation: Record access remains the same after running the flow because changing the record type does not affect the sharing rules or the record owner. The Sales user will still have read and edit access to the account record based on their profile and the organization-wide default for accounts. The record type assignment only affects the page layout and picklist values that are available for the account record
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 5 out of 22 Pages |
| Previous |
Copyright © - All Rights Reserved