- Email support@dumps4free.com
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
| Page 9 out of 44 Pages |
| Previous |