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

To access the account object in Salesforce, users need to have permission to the account object on

their profile or permission set. Permission to an object determines what users can do with records of

that object, such as create, read, edit, delete, view all, or modify all. If users do not have permission

to an object, they will not be able to see or access that object in Salesforce. Reference:

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

A lookup relationship is a type of relationship that links two objects together, but does not affect

security or deletion. It can be used to create a relationship between shipments and accounts where

shipments should have a lookup to accounts; this way, shipments can show related account

information on their records, but when an account is deleted, the shipments remain. Accounts

should have a lookup to shipments is not a valid option because it does not match the requirement

of seeing all shipment items from an account page; it would show related account information on

shipment records instead. Shipments should have a master-detail to accounts or accounts should

have a master-detail to shipments are not valid options either because they do not match the

requirement of keeping shipments when an account is deleted; they would delete shipments along

with their master account records. Reference:

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

Outbound message allows you to send information to an external system as part of a workflow rule

or approval process. You can use outbound message to specify which fields to send and which

endpoint URL to send them to.

Reference:

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

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

The mass transfer tool allows you to transfer up to 250 records at a time from one user to another

user while keeping the existing team members intact. You can access this tool from Setup by entering

Mass Transfer Records in the Quick Find box. Reference:

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

Data Import Wizard allows you to import up to 50,000 records at a time.

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

To advertise on TV, radio, print, and social under one banner called New Runners and aggregate total

statistics for this marketing effort, an administrator should use Parent campaign field on Campaign

object. This field allows creating hierarchical relationships between campaigns by specifying one

campaign as parent of another campaign. Parent campaigns roll up statistics from child campaigns

such as number of leads generated, amount of revenue won etc. For example, an administrator can

create four child campaigns for TV, radio, print and social ads respectively and link them to one

parent campaign called New Runners using Parent campaign field. Junction object, lookup

relationship, and master-detail relationship are not features related to Campaign object or hierarchy.

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

To display only the proper lead sources based on the product category chosen, an administrator

should create a dependency between the Product Category field and Lead Source field on Lead

object. A dependency is a relationship between two picklist fields that restricts the values available in

one picklist based on the value selected in another picklist. For example, an administrator can create

a dependency that shows only Online Store and Social Media as lead sources if Product Category is

Shoes, but shows only Trade Show and Magazine as lead sources if Product Category is Apparel.

Creating a page layout for each category, creating business processes and record types for each

category, or creating a single business process with record types for each category will not display

only the proper lead sources based on the product category chosen. Reference:

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

Probability is a standard percentage field on the Opportunity object that indicates how likely an

opportunity will close successfully. It is automatically calculated based on the opportunity stage

unless you make it editable on page layouts. To allow sales reps to change the probability field value

of their opportunities, you need to make the field editable on page layouts. Reference:

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

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

Forecasting is a feature that allows you to predict and plan the sales cycle from pipeline to closed

sales, and manage sales expectations throughout your organization. Opportunity stages are the steps

that an opportunity goes through as it moves from creation to close, and they determine the

probability and forecast category of the opportunity. Reference:

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

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

A related record component is a type of component that allows users to view and edit fields from a

parent record on a child record page without leaving the page. For example, a related record

component can allow users to update the account status from the case layout by selecting an

account record from a drop-down list. A rich text component is a type of component that allows

users to display formatted text on a record page using rich text editor tools such as bold font, bullet

points, images, and links. For example, a rich text component can display a message in bold font

when a case is saved as acriticalrecord type by using conditional visibility rules. Reference:

https://help.salesforce.com/s/articleView?id=sf.lightning_page_components_related_record.htm&t

ype=5

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

To create a many-to-many relationship between two existing custom objects, the administrator

needs to create a junction object that has two master-detail relationships, one to each of the custom

objects. This will allow each record of one object to be linked to multiple records from another object

and vice versa. Reference:

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

Record types allow you to update the options in a picklist based on the kind of opportunity.

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

The $Record global variable allows you to reference the values of the active record the flow is

running on.

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

Roll-up summary fields allow you to calculate the sum of a field from child records related to a parent

record.

Reference:

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

To make sure that all of the Salesforce users log in using the branded login URL after deploying my

domain, and give them a grace period for updating their bookmarks, the administrator should set the

Redirect policy to Redirect with a warning to the same page within the domain. This will redirect

users who try to log in from https://login.salesforce.com or another domain to

https://nto.my.salesforce.com, and show them a warning message that they need to update their

bookmarks. Setting the Login policy or preventing login from https://login.salesforce.com will not

redirect users or give them a warning. Filtering with Form Factor will not affect login URL. Reference:

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

Lightning record page is a type of page that should be created to meet this requirement. Lightning

record page allows an administrator to customize the layout and components for a specific object

record page in Lightning Experience or the Salesforce mobile app. To create tabs for account details,

related lists, and chatter feeds, use the Tabs component in the Lightning App Builder and drag the

desired components to each tab. Reference:

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

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

A PriceBook is a feature that allows administrators to define different prices for the same products

based on different criteria such as customer segment, region, channel, etc. For example, a PriceBook

can provide reseller partners with discounted prices on the products they purchase compared to

regular customers. A PriceBook consists of one or more PriceBook entries that specify the product ID,

pricebook ID, list price, currency, and active status for each product-pricebook combination.

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

Bucket column allows you to categorize report data into groups without creating a formula or custom

field. You can create buckets for different ranges of values and assign labels to them.

Reference:

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

A custom profile is a profile that can be created and customized by administrators to define what

users can see and do in Salesforce based on their job function or role. It can be used by Cloud Kicks to

give read, create, and edit access for objects and restrict users from deleting any records by creating

and assigning a custom profile with delete access removed for each object in the object settings.

Assigning the standard system administrator profile to analytical user, giving user view all access and

assigning them to highest role in role hierarchy, or creating and assigning permission set that

includes read, create, and edit access are not solutions for giving read, create, and edit access for

objects and restricting users from deleting any records; they either give too much access or do not

remove delete access. Reference:

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

Paths allow you to display key fields and guidance for each stage of an opportunity. Kanban list views

allow you to update records by dragging them between columns.

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

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