ADX-201E Practice Questions

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.

Reference:

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

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

Creating a new quote record for each of the different product configurations and syncing the most

likely to be purchased back to the opportunity will ensure that their quotes and opportunities reflect

their sales. This way, sales reps can show customers different options and prices, and keep track of

which one is most likely to close. Syncing a quote with an opportunity will update the opportunity

amount, stage, and expected revenue fields based on the quote information. Reference:

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

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

Bucket field is a feature that allows administrators to group report values into categories without

changing the data in Salesforce. Bucket field can help simplify reports and charts by reducing the

number of values displayed and summarizing data based on criteria such as ranges or groups. Bucket

field can be used to group specific picklist values together into one of two lists

Permission set groups are a combination of permission sets that grant users access to various tools

and functions. Muting permission sets are used to remove access that is granted by other permission

sets in the group. However, muting permission sets cannot remove object-level access that is

granted by Modify All or View All permissions. Therefore, if a user is assigned to a permission set

group that gives them Modify All access to Accounts, a muting permission set that mutes Delete

access on Account will not have any effect. The user will still have Modify All access on the Account

object,

which

includes

Delete

access.

Reference:

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

As explained in

An after-save autolaunched flow is a type of flow that runs in the background when a record is saved

and performs actions based on the record data or changes. An after-save autolaunched flow does not

require user input or interaction and can be triggered by a record-triggered flow element or by an

Apex trigger. In this case, you can create an after-save autolaunched flow that runs when a Project

record is created and creates a standard set of related Project Milestone records based on predefined

values

or

variables.

Reference:

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

Building a process that updates the record type field to B2C Customer after conversion will correct

this issue. The conversion layout for person accounts does not allow selecting different record types

for accounts and contacts. The default record type for person accounts is determined by the

organization-wide default settings. However, a process can be triggered after conversion to update

the

record

type

field

based

on

the

lead

record

type

or

other

criteria.

Reference:

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

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

Contacts to Multiple Accounts is a feature that allows administrators to relate a contact to multiple

accounts without creating duplicate contacts for each account. This feature is useful for scenarios

where a contact has business relationships with more than one account, such as consultants, brokers,

or loan advisors. By setting up Contacts to Multiple Accounts for loan advisors at DreamHouse Realty,

administrators can track which loan advisors work with which customers and which accounts without

creating

duplicate

contacts

for

each

account.

Reference:

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

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