Free ADVANCED-ADMINISTRATOR Practice Test Questions and Answers (2026) | Cert Empire Practice Questions

Sharing rules are automatic exceptions to organization-wide sharing settings that grant additional

access to records based on record ownership or criteria. By creating a sharing rule on the Account

object for all members of the account services role to have Read/Write access, the administrator can

allow users in that role to edit and change ownership of Accounts owned by any of their team

members, regardless of the organization-wide sharing setting for Account. Reference:

https://help.salesforce.com/s/articleView?id=sf.security_sharing_rules.htm&type=5

Two options that the administrator should use to meet these criteria are:

Share with roles and subordinates of the finance director role. This option allows you to grant access

to records based on the role hierarchy of your org. You can share records with users who are in a

specific role or in roles below that role in the hierarchy. In this case, you can share records with roles

and subordinates of the finance director role, which includes all the members of the finance team.

Create a criteria-based sharing rule where the won field = true. This option allows you to grant access

to records based on certain field values or formulas. You can create a criteria-based sharing rule on

opportunities that grants access to records where the won field is true, which means that the

opportunity stage is closed won.

The other two options are incorrect because:

Make an owner-based sharing rule where the won field = true is not an option because owner-based

sharing rules do not allow you to specify field values or formulas as criteria. Owner-based sharing

rules only allow you to share records based on who owns them or what role or group they belong to.

Select all opportunities owned by the sales manager role is not an option because it does not meet

the criteria of sharing all closed won opportunities. It only shares opportunities that are owned by

users who are in the sales manager role, regardless of their stage.

Reference: https://help.salesforce.com/s/articleView?id=sf.admin_sharing.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.sharing_rules.htm&type=5

The data masking tool is a tool that allows you to mask sensitive data in your full sandbox by

replacing it with fictitious data. This can help you protect your data privacy and comply with

regulations while testing in a realistic environment. You can use the data masking tool to mask data

for standard and custom objects, including person accounts, and choose from different masking

formats and options. Reference:

https://help.salesforce.com/s/articleView?id=sf.data_mask.htm&type=5

A rich text component allows administrators to add custom text or images to a Lightning page.

Conditional visibility allows administrators to control when a component is visible based on criteria

such as field values or device type. By using these features, administrators can highlight Canadian

customers as a potential challenge for fulfillment without modifying the page layout or creating a

new record type. Reference:

https://help.salesforce.com/articleView?id=sf.app_builder_components_rich_text.htm&type=5

https://help.salesforce.com/articleView?id=sf.app_builder_component_visibility.htm&type=5

The user profile permissions on the Opportunity object is the item that the administrator should

review to find out why the user is unable to delete the duplicate record. The user profile permissions

determine what users can do with records and objects in Salesforce, such as creating, editing,

deleting, viewing, or sharing. In this case, the administrator should check if the user has the Delete

permission on the Opportunity object, which allows them to delete opportunity records that they

own or have access to. If not, the administrator can either grant them this permission or delete the

record for them. Reference:

https://help.salesforce.com/s/articleView?id=sf.admin_general_permissions.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.admin_object_permissions.htm&type=5

The Analyze feature in the Lightning App Builder toolbar is a tool that helps you optimize the

performance of your record pages by providing recommendations and insights on how to improve

page load time and user experience. It can help you identify which fields and components are taking

the most time to load and suggest ways to reduce their impact. You can also compare your page

performance with other pages in your org or with Salesforce best practices. Reference:

https://help.salesforce.com/s/articleView?id=sf.lightning_page_optimize.htm&type=5

The Show Unique Count option on the account name column will create a report showing all open

opportunities and the total number of accounts represented. This option will count each account

only once, even if it has multiple opportunities. The report can be grouped by account name or any

other field to show more details. Reference:

https://help.salesforce.com/s/articleView?id=sf.reports_builder_unique_count.htm&type=5

Two options that the administrator can use to solve this scenario are:

Create a custom object. A custom object is an object that you define to store information that is

specific to your organization or industry. In this case, you can create a custom object for the form that

has more than 30 fields and relates to the account or opportunity object. This way, you can store

multiple submissions of the form for each account or opportunity and track their changes over time.

Turn on Field Tracking. Field tracking is a feature that allows you to monitor changes to certain fields

on an object and display them in a history related list. In this case, you can turn on field tracking for

the fields on the form custom object and see what values were changed from one submission to

another.

A price book is a list of products and their prices that can be added to an opportunity. A product can

have different prices for different markets or segments, and these prices are stored in different price

books. In this case, the administrator should create a new price book for the new retail pricing and

add the products that are sold to retail locations for resale. This way, the users can select the

appropriate price book and products for their opportunities based on the type of customer they are

selling to. Reference:

https://help.salesforce.com/s/articleView?id=sf.products_pricebooks.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.products_define.htm&type=5

To restore the deleted Review records, you need to restore both the Account and Product master

records from the Recycle Bin. A master-detail relationship is a type of relationship that links two

objects together and enforces a parent-child relationship between them. A master-detail relationship

affects the security and deletion of the child records. If you delete a master record, all of its detail

and subdetail records are deleted as well and moved to the Recycle Bin. To restore a detail or

subdetail record, you must first restore its parent record. Reference:

https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.recyclebin_overview.htm&type=5

One possible reason why the before trigger fails is that the code could be trying to create duplicates

in the archive when it is unable to. A before trigger is a type of trigger that executes before a record

is saved and can be used to validate or modify record data. In this case, the before trigger is

supposed to save the original version of a record to an external database before it is updated or

deleted in Salesforce. However, if the code does not handle errors or exceptions properly, it could try

to create duplicate records in the external database when it is not allowed or possible. This could

cause the trigger to fail and prevent the record from being saved in Salesforce. Reference:

https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers.htm

https://developer.salesforce.com/docs/atlas.enus.apexcode.meta/apexcode/apex_triggers_context_variables.htm

Three recommendations that the administrator can make to reduce the file size of full data exports

are:

Reduce the amount of objects per export. By selecting only the objects that are necessary for the

backup and excluding the ones that are not, you can reduce the number of files and records that are

exported and decrease the file size.

Deselect ‘Include images, documents, and attachments’ in the export. By unchecking this option, you

can exclude the files that are stored in Salesforce as images, documents, or attachments from the

export. These files can take up a lot of space and increase the file size significantly.

Keep deleted record counts to a minimum. By emptying the recycle bin regularly or using hard delete

options, you can reduce the number of deleted records that are included in the export. Deleted

records are still counted as part of the export limit and can increase the file size.

The other two options are incorrect because:

Requesting a backup file every 5 days does not reduce the file size of each export. It only increases

the frequency of exports and may cause more storage issues.

Unselecting the recycle bin in the object export option does not reduce the file size of full data

exports. It only applies to individual object exports and not to weekly or monthly exports.

Reference: https://help.salesforce.com/s/articleView?id=sf.data_export.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.admin_exportdata.htm&type=5

​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

A phone field that provides the full phone number of the seller, a number field that designates the

square footage of the listing, and a picklist field that designates the county of the listing should be

used as filter criteria because they are fields that can be used to narrow down the report results

based on specific values or ranges. A multi-select picklist field that designates features of the listing

and a formula field that calculates a price for the listing should not be used as filter criteria because

they are fields that cannot be filtered on in reports. Reference:

https://help.salesforce.com/s/articleView?id=sf.reports_filtering.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.reports_fields_unavailable.htm&type=5

Territory management is a feature that allows you to grant access to accounts and opportunities

based on criteria such as geography, industry, product line, or customer size. A territory is a grouping

of accounts and users that represents a market segment or business unit. In this case, the

administrator should utilize territory management to add the operations team to the East territory,

which contains all the accounts and opportunities in the East region. This way, the operations team

members can access all the records in their territory regardless of who owns them or what the

organization-wide default is. Reference:

https://help.salesforce.com/s/articleView?id=sf.territories_overview.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.territories_define.htm&type=5

A primary account relationship is a feature that allows you to link a contact to a single account as its

primary account. A primary account relationship is required on a contact regardless of the page

layout settings or the contact to multiple accounts feature. This means that you cannot remove the

primary account from a contact, but you can change it to another account. You can also add

secondary accounts to a contact if you have enabled the contact to multiple accounts feature.

Reference: https://help.salesforce.com/s/articleView?id=sf.contacts_multiple_accounts.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.contacts_fields.htm&type=5

The flow debug option is a tool that allows you to test and troubleshoot your flow by running it in

debug mode and inspecting the values of variables and resources at each step. You can also set the

debug mode to run as another user and see how the flow behaves for different users with different

permissions and settings. In this case, using the flow debug option and setting the selection to run as

another user can help identify why one user is experiencing a flow error while others are not.

Reference: https://help.salesforce.com/s/articleView?id=sf.flow_debug.htm&type=5

Run the standard Data Classification report is what the administrator should recommend to the

compliance team. Data Classification is a feature that allows administrators to flag where sensitive

information is stored in Salesforce by assigning sensitivity and classification levels to fields. Data

Classification also provides a standard report that shows field level sensitivity and classification for all

fields in an org. The administrator can run this report and share it with the compliance team to meet

their requirement.​

Two practices that the administrator should adhere to in order to ensure a successful deployment to

production are:

Add permissions and access settings to outbound change sets in addition to the dependent

component list. This can help avoid deployment errors or access issues caused by missing

permissions or settings for the components in the change set. For example, if the change set includes

a new custom object, the administrator should also include the object permissions, field-level

security, page layouts, and record types for that object.

Run deployment validations on the change set in the sandbox prior to uploading to production. This

can help test the change set for any errors or conflicts before deploying it to production. Deployment

validations simulate the deployment without actually making any changes and report any issues or

warnings.

The other two options are incorrect because:

Cloning a change set does not add forgotten dependent components to an uploaded change set. It

only creates a copy of the existing change set that can be modified before uploading.

When deploying a new record type, it is not necessary to have it as the only component in the

change set. It can be deployed along with other components as long as they are compatible and have

the required dependencies.

Reference: https://help.salesforce.com/s/articleView?id=sf.change_sets_components.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.change_sets_deploy.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.change_sets_validate.htm&type=5

Salesforce’s Data Export Service is a tool that allows you to export your organization’s data to a set of

comma-separated values (CSV) files and store them in a backup location of your choice. You can

schedule this service to run weekly or monthly and receive an email notification when your files are

ready to download. This is one way to back up your data daily without using any external tools or

services. Reference: https://help.salesforce.com/s/articleView?id=sf.data_export.htm&type=5