Practice Free Certified Advanced Administrator Exam Online Questions
Question #11
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.
Correct Answer: D
D
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.
D
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.
Question #12
Ursa Major Solar has a training sandbox with 160MB of test data that needs to be refreshed every other day.
Which two sandboxes should be used in this instance? Choose 2 answers
- A . Partial
- B . Developer
- C . Developer Pro
- D . Full
Correct Answer: AC
AC
Explanation:
To create a training sandbox with 160MB of test data that needs to be refreshed every other day, NTO should use either Partial or Developer Pro sandboxes. Partial sandboxes have a storage limit of 10GB and can be refreshed every 5 days. Developer Pro sandboxes have a storage limit of 1GB and can be refreshed every day. Both sandboxes can include test data from production.
Reference: https://help.salesforce.com/s/articleView?id=sf.data_sandbox_environments.htm&type=5
AC
Explanation:
To create a training sandbox with 160MB of test data that needs to be refreshed every other day, NTO should use either Partial or Developer Pro sandboxes. Partial sandboxes have a storage limit of 10GB and can be refreshed every 5 days. Developer Pro sandboxes have a storage limit of 1GB and can be refreshed every day. Both sandboxes can include test data from production.
Reference: https://help.salesforce.com/s/articleView?id=sf.data_sandbox_environments.htm&type=5
Question #13
A sales rep at Ursa Major Solar reafized that the wrong price book was selected for an opportunity.
How can the sales rep change the price book on the opportunity?
- A . Once selected, the price book can be updated via the forecasts tab.
- B . Once selected, the price book is locked on the opportunity.
- C . They change can be made through the desktop site.
- D . The change can be made through the mobile app.
Correct Answer: C
C
Explanation:
The change can be made through the desktop site by using the Edit All button on the related list of products on the opportunity page. This button allows you to edit multiple products at once and change their price book entries. You cannot use this button on the mobile app, as it is not supported. You also cannot change the price book on the opportunity once it has products added to it, unless you remove all the products first.
Reference:
https://help.salesforce.com/s/articleView?id=sf.opportunity_products_edit.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.opportunity_products_change_pricebook.htm&type =5
C
Explanation:
The change can be made through the desktop site by using the Edit All button on the related list of products on the opportunity page. This button allows you to edit multiple products at once and change their price book entries. You cannot use this button on the mobile app, as it is not supported. You also cannot change the price book on the opportunity once it has products added to it, unless you remove all the products first.
Reference:
https://help.salesforce.com/s/articleView?id=sf.opportunity_products_edit.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.opportunity_products_change_pricebook.htm&type =5
Question #14
When should an administrator apply a permission set to a user or group of users versus configuring the user’s profile with the necessary access?
- A . When a user is part of a team with an assigned profile that covers the majority of their needs but requires just a little less access than the rest of their team.
- B . When a user is part of a team with an assigned profile that covers the majority of their needs but requires more access than the rest of their team.
- C . When an organization’s sharing model is too broad and they need to restrict access beyond what their sharing model and existing profiles provide.
- D . When an organization has opted out of using the standard profiles and created custom profiles.
Correct Answer: B
B
Explanation:
As explained in question 13, permission sets are collections of settings and permissions that give users access to various tools and functions without changing their profile or requiring multiple profiles for users who perform different tasks across apps in your org. Permission sets are useful when a user is part of a team with an assigned profile that covers the majority of their needs but requires more access than the rest of their team for some specific tasks or functions. For example, a user may need access to a custom object or field that is not available to their profile, but only for a limited time or project. In this case, assigning a permission set to the user can grant them the additional access they need without affecting their profile or other users with the same profile.
Reference: https://help.salesforce.com/s/articleView?id=sf.perm_sets_overview.htm&type=5
B
Explanation:
As explained in question 13, permission sets are collections of settings and permissions that give users access to various tools and functions without changing their profile or requiring multiple profiles for users who perform different tasks across apps in your org. Permission sets are useful when a user is part of a team with an assigned profile that covers the majority of their needs but requires more access than the rest of their team for some specific tasks or functions. For example, a user may need access to a custom object or field that is not available to their profile, but only for a limited time or project. In this case, assigning a permission set to the user can grant them the additional access they need without affecting their profile or other users with the same profile.
Reference: https://help.salesforce.com/s/articleView?id=sf.perm_sets_overview.htm&type=5
Question #15
Universal Containers has found duplicate contacts in Salesforce. The sales team administrator prevent duplicate records from being created.
Which two ways should the administrator customize duplicate management? Choose 2 answers
- A . Modify the Global Picklist Value Sets.
- B . Configure custom duplicate rules.
- C . Create custom matching rules.
- D . Set up mobile duplicate alerts.
Correct Answer: B, C
B, C
Explanation:
Duplicate management is a feature that allows administrators to prevent or allow duplicate records for standard or custom objects. Duplicate management consists of two components: duplicate rules and matching rules.
B) Configure custom duplicate rules.
Duplicate rules are rules that determine what actions to take when users try to save duplicate records. Duplicate rules can block users from saving duplicates, alert users of duplicates and let them save anyway, or report on duplicates without affecting the save operation. Duplicate rules can also specify which fields to use for matching and which security settings to enforce. By configuring custom duplicate rules, the sales team administrator can prevent duplicate records from being created for
contacts or other objects.
Reference: https://help.salesforce.com/s/articleView?id=sf.data_prevent_duplicates.htm&type=5
C) Create custom matching rules.
Matching rules are rules that determine how duplicate records are identified by comparing fields and applying fuzzy matching algorithms. Matching rules can be standard or custom. Standard matching rules are predefined by Salesforce and apply to common objects such as contacts, accounts, or leads. Custom matching rules are created by administrators and apply to any standard or custom object. By creating custom matching rules, the sales team administrator can define how duplicate records are
detected for contacts or other objects.
Reference: https://help.salesforce.com/s/articleView?id=sf.data_matching_rules.htm&type=5
B, C
Explanation:
Duplicate management is a feature that allows administrators to prevent or allow duplicate records for standard or custom objects. Duplicate management consists of two components: duplicate rules and matching rules.
B) Configure custom duplicate rules.
Duplicate rules are rules that determine what actions to take when users try to save duplicate records. Duplicate rules can block users from saving duplicates, alert users of duplicates and let them save anyway, or report on duplicates without affecting the save operation. Duplicate rules can also specify which fields to use for matching and which security settings to enforce. By configuring custom duplicate rules, the sales team administrator can prevent duplicate records from being created for
contacts or other objects.
Reference: https://help.salesforce.com/s/articleView?id=sf.data_prevent_duplicates.htm&type=5
C) Create custom matching rules.
Matching rules are rules that determine how duplicate records are identified by comparing fields and applying fuzzy matching algorithms. Matching rules can be standard or custom. Standard matching rules are predefined by Salesforce and apply to common objects such as contacts, accounts, or leads. Custom matching rules are created by administrators and apply to any standard or custom object. By creating custom matching rules, the sales team administrator can define how duplicate records are
detected for contacts or other objects.
Reference: https://help.salesforce.com/s/articleView?id=sf.data_matching_rules.htm&type=5
Question #16
An administrator created and activated several record-triggered flows that are configured to run before the record is saved on the same object.
What should the administrator consider about the order of execution for flows?
- A . The flow type will determine the order of execution.
- B . The last created date of the flow will determine the order.
- C . The order of flow execution is unpredictable.
- D . The flows will execute in alphabetical order based on their names.
Correct Answer: C
C
Explanation:
When you have multiple record-triggered flows that are configured to run before the record is saved on the same object, the order of flow execution is unpredictable. This means that you cannot guarantee which flow will run first or last, or how they will affect each other’s field updates. Therefore, you should avoid creating multiple before-save flows on the same object and instead consolidate them into one flow if possible.
Reference: https://help.salesforce.com/s/articleView?id=sf.flow_considerations_recordtriggered_before.htm&t ype=5
C
Explanation:
When you have multiple record-triggered flows that are configured to run before the record is saved on the same object, the order of flow execution is unpredictable. This means that you cannot guarantee which flow will run first or last, or how they will affect each other’s field updates. Therefore, you should avoid creating multiple before-save flows on the same object and instead consolidate them into one flow if possible.
Reference: https://help.salesforce.com/s/articleView?id=sf.flow_considerations_recordtriggered_before.htm&t ype=5
Question #17
An administrator needs to Import a large amount of historical data (more than 100,000 records) from another system.
how should the administrator import the data?
- A . SOAP based API with Developer console
- B . Data Loader with Bulk API Enabled
- C . An AppExchange package
- D . Import Wizard with Add Only
Correct Answer: B
B
Explanation:
Data Loader with Bulk API Enabled is a tool that can import a large amount of historical data (more than 100,000 records) from another system. Data Loader can insert, update, delete, or export Salesforce records. Bulk API is an API that allows fast and parallel processing of large batches of records.
Reference: https://help.salesforce.com/s/articleView?id=sf.data_loader.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.loader_api.htm&type=5
B
Explanation:
Data Loader with Bulk API Enabled is a tool that can import a large amount of historical data (more than 100,000 records) from another system. Data Loader can insert, update, delete, or export Salesforce records. Bulk API is an API that allows fast and parallel processing of large batches of records.
Reference: https://help.salesforce.com/s/articleView?id=sf.data_loader.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.loader_api.htm&type=5
Question #18
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?
- A . Activate the flow manually after deployment.
- B . Include the active and prior inactive flow version in the Change Set.
- C . Ensure there is an active flow version in the sandbox.
- D . Deployment the flow, with the Metadata API instead of Change Sets
Correct Answer: A
A
Explanation:
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
A
Explanation:
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
Question #19
What are three options available to the administrator to help with this issue? Choose 3 answers
- A . Move some page components behind a tab.
- B . Remove some of the fields displayed.
- C . Deactivate unnecessary validation rules.
- D . Convert all Process builders to flows.
- E . Reduce the number of related lists displayed.
Correct Answer: A, B, E
A, B, E
Explanation:
To help with this issue, the administrator can do the following options:
Move some page components behind a tab. This will reduce the number of components that load initially and improve performance.
Remove some of the fields displayed. This will reduce the amount of data that needs to be retrieved and rendered on the page.
Reduce the number of related lists displayed. This will also reduce the amount of data that needs to
be retrieved and rendered on the page.
Reference: https://help.salesforce.com/s/articleView?id=sf.lex_performance_considerations.htm&type=5
A, B, E
Explanation:
To help with this issue, the administrator can do the following options:
Move some page components behind a tab. This will reduce the number of components that load initially and improve performance.
Remove some of the fields displayed. This will reduce the amount of data that needs to be retrieved and rendered on the page.
Reduce the number of related lists displayed. This will also reduce the amount of data that needs to
be retrieved and rendered on the page.
Reference: https://help.salesforce.com/s/articleView?id=sf.lex_performance_considerations.htm&type=5
Question #20
The salts team at Universal Containers has asked the administrator to build functionality to automatically update the account checkbox field ‘Opportunity Created’ to checked when at least one related opportunity has been created.
What feature should the administrator use to build this functionality?
- A . Screen flow
- B . Workflow rule
- C . Record-triggered flow
- D . Assignment rule
Correct Answer: C
C
Explanation:
Record-triggered flow is a feature that allows administrators to automate actions that occur when a record is created or updated. Record-triggered flow can perform actions such as updating fields, creating records, sending emails, or invoking Apex code. Record-triggered flow can be used to update the account checkbox field ‘Opportunity Created’ when at least one related opportunity has been created
C
Explanation:
Record-triggered flow is a feature that allows administrators to automate actions that occur when a record is created or updated. Record-triggered flow can perform actions such as updating fields, creating records, sending emails, or invoking Apex code. Record-triggered flow can be used to update the account checkbox field ‘Opportunity Created’ when at least one related opportunity has been created