Free ADX-211 Practice Test Questions and Answers (2026) | Cert Empire Practice Questions

Delegated administrators in Salesforce are designated users who are given limited administrative

privileges to assist system administrators without having full access to all administrative functions.

The two functions they can typically perform, which align with the permissions available to

delegated admins, are:

Set up users and password management:

Delegated administrators can create and manage user accounts, which includes setting up new users,

resetting passwords, and updating user details.

This is particularly useful for helping with user management tasks without providing full system

administrator access.

Configure updates to sharing rules:

Delegated administrators can manage sharing rules within their specific groups or roles, which helps

control access to records based on criteria set within the organization.

This level of access allows them to modify sharing rules to ensure appropriate data access without

requiring full administrative control over all settings.

The other options listed are not within the scope of delegated administrator capabilities:

Manage custom objects and customize nearly every aspect: Delegated administrators do not have

the ability to manage custom objects or perform extensive customization. These functions are

reserved for system administrators with broader privileges.

Make updates to permission set configurations: Delegated administrators cannot create or modify

permission sets. This is also restricted to full administrators, as it involves controlling access at a

granular level across the org.

By utilizing delegated administrators for user and sharing rule management, organizations can

maintain security and control while also sharing some administrative workload.

Reference: According to Salesforce documentation, delegated administrators have specific

permissions, such as managing users and sharing rules, which support system administrators while

limiting access to high-level customizations and configurations​​.

Formula field and Dynamic Forms should be created to meet the requirements because a formula

field can be used to count the number of open opportunities over US$10,000 related to an account

using a roll-up summary filter condition, and Dynamic Forms can be used to display or hide a

component on an account page based on a visibility filter using the formula field value. Reference:

https://help.salesforce.com/s/articleView?id=sf.customize_functions_i_z.htm

To help the finance team use Opportunity data to keep an eye on their pipeline without manually

calculating anticipated income for the quarter, the administrator should set up collaborative

forecasting. Collaborative forecasting allows users to view quota against open pipeline and make

adjustments based on changing business conditions. Reference:

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

To make inventory data from a legacy application available in Salesforce, the administrator can create

an external object that maps to the inventory application. An external object is similar to a custom

object, except that it maps to data that’s stored outside your Salesforce organization. External objects

enable users to view and report on external data in Salesforce. Reference:

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

Two combined automation tools that the administrator can use to create the task record and assign

based on date criteria are:

Create a formula field to capture the MAX date. A formula field is a custom field that calculates a

value based on other fields or expressions. In this case, a formula field can be used to capture the

maximum value between Estimated Shipping Date and Client Need By Date fields and store it as a

date value.

Make a Process Builder to create the task. A Process Builder is an automation tool that allows you to

create processes that perform actions based on certain criteria. In this case, a Process Builder can be

used to create a task record when a certain condition is met and assign its due date based on the

formula field value.

The other two options are incorrect because:

An approval process is an automation tool that allows you to route records for approval based on

certain criteria and approval steps. It does not create or assign tasks based on date criteria.

A workflow rule is an automation tool that allows you to perform actions based on certain criteria

and evaluation time. It does not create or assign tasks based on date criteria.

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

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

Configuring one app per department and activating record pages for each app will ensure that users

view records in a way that makes sense for each department. An app is a collection of items that

work together to serve a particular function. An app can have different record pages for different

objects and profiles. By activating record pages for each app, the administrator can customize what

users see based on their app context. Reference:

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

https://help.salesforce.com/s/articleView?id=sf.app_builder_customize_lex_pages_assign.htm&typ

e=5

The View Setup Audit Trail page lets you view the 20 most recent setup changes made to your org.

You can also download a file of the last six months of setup changes. Reference:

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

Manual sharing is a way of granting access to individual records by manually sharing them with other

users, roles, or groups. Manual sharing can override the organization-wide default and role hierarchy

settings and give additional access to specific records. In this case, manual sharing could be the

reason why only one user can see the account record, even though they have the same profile and

role as another user who cannot see it. Reference:

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

A validation rule and a stage guidance in Path are two features that can help ensure that users input

a use case before moving the opportunity stage to qualified.

A validation rule is a formula that validates the data entered by users and prevents records from

being saved if they do not meet certain criteria. In this case, a validation rule can be used to check if

the Use Case field is blank when the Stage field is changed to Qualified, and display an error message

if so.

A stage guidance in Path is a feature that displays helpful information or tips for each stage of a sales

process on an opportunity record page. In this case, adding the Use Case field to the stage guidance

in Path can remind users to fill out this field before moving to the next stage.

A validation rule can enforce data quality by preventing users from saving records that do not meet

certain criteria. In this case, the validation rule can check if both the Sales Engineer and the Account

Executive lookup fields are blank, and display an error message if so. This way, the director of sales

can ensure that every opportunity has either a sales engineer or an account executive assigned to

the deal. Reference:

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

A validation rule on the Opportunity Product object to require custom date fields based on the

product family will ensure that the data is captured properly. A validation rule can check if the

product family matches the service plan and if so, require the start and end date fields to be filled

out. This way, AW Computing can capture the term length for each service plan sold. Reference:

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

A price book is a list of products and their prices for a specific segment of customers or market. By

creating a separate price book for the special bundle deal on monitors and keyboards, AW

Computing can offer different prices for these products without affecting their standard prices or

requiring VP approval. The price book can also specify which products are included in the bundle and

which are not. Reference:

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

Data Import Wizard is a tool that allows administrators to import data for standard and custom

objects in Salesforce using CSV files. Data Import Wizard can handle up to 50,000 records at a time

and supports simple data transformations and validations. Data Import Wizard can be used to upload

records for a custom object when the number of records is small and the import frequency is low.

Case Source updates to ‘email’ before the record is saved because the Process Builder runs before

the auto-response rule. Then, an email is sent out using Template2 because the auto-response rule

evaluates the Case Source value after it is updated by the Process Builder and matches the criteria

for Template2

A junction object is a custom object with two master-detail relationships that allows you to create

many-to-many relationships between two objects. In this case, the Job Application object can be

used as a junction object to link the Application object and the Job Posting object, so that each

application can be related to one or more job postings, and each job posting can have one or more

applications. Reference:

https://help.salesforce.com/s/articleView?id=sf.relationships_manytomany.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

To ensure that multiple field updates occur in a specific order on a custom object, the administrator

should create a process with one criteria node and three field updates arranged in the correct order.

This approach allows the updates to execute sequentially within a single automation framework,

ensuring that they happen in the intended order.

Using Process Builder with a Single Criteria Node:

In Process Builder, the administrator can define a single criteria node that triggers the field updates.

By adding multiple field updates within this single node and arranging them in the desired sequence,

Salesforce will execute them in that specific order.

This setup provides better control over the sequence of updates compared to multiple workflow

rules, as Process Builder will execute each field update step by step as configured within the node.

Advantages Over Workflow Rules:

Unlike workflow rules, where the order of execution can be less predictable due to separate triggers,

Process Builder enables precise control over the execution sequence within the same process.

Using multiple workflow rules or multiple criteria nodes with stop actions would complicate the

setup without guaranteeing the specific order. Process Builder’s structure ensures that updates

proceed in the exact order defined.

Incorrect options:

Option A (Three workflow rules): Creating separate workflow rules for each update does not ensure a

specific order of execution, as workflow rules are not guaranteed to run sequentially.

Option C (Three criteria nodes with stop actions): This approach would execute each node separately,

and the stop action after each node adds unnecessary complexity, without ensuring the sequential

order required.

Option D (One workflow rule with three field updates): Workflow rules do not guarantee the order of

field updates within a single rule. Using Process Builder with a single node is more reliable for

sequential execution.

In conclusion, Process Builder with one criteria node and ordered field updates is the most effective

approach to ensure a specific execution sequence for multiple field updates on the Shipment object.

Reference: According to Salesforce best practices, Process Builder is recommended over multiple

workflow rules when specific ordering and complex logic are required for field updates

As explained in

Setup Audit Trail is a tool that tracks the recent setup changes made by anyone in an org. It can help

identify who made what changes and when, as well as any errors or failures that occurred during the

changes. Setup Audit Trail can help troubleshoot deployment issues by comparing the changes made

in production with those made in sandbox

Check the Reevaluate Workflow Rules After Field Change box on the Approval Process Field Update

Action is what the administrator should do to troubleshoot the issue. This option allows the approval

process field update to trigger any workflow rules or processes that are based on the updated field

value. If this option is not checked, the approval process field update will not trigger any workflow

rules or processes, and the Process Builder will not fire