CompTIA
Checkpoint
ISC
HP
Dell
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
Certiport
ISC2
All Vendors
  2. Home
  3. Exams
  4. Salesforce
  5. ADX-201E

Free ADX-201E Exam Braindumps (page: 26)

Page 25 of 61
PDF with 243 Questions

Sales reps at AW Computing hove been reporting that contact phone numbers sometimes revert book to on old value after being updated.
What should the administrator do to resolve this issue?

  1. Schedule Apex jobs.
  2. Delete all workflow rules.
  3. Add an invocable process.
  4. Consolidate automation tools.

Answer(s): D

Explanation:

One possible cause of unexpected changes to record values is having multiple automation tools that update the same field on the same object. This can create conflicts and overwrite each other's values. To resolve this issue, the administrator should consolidate automation tools and use only one tool per object and field combination. This can help avoid confusion and ensure consistent results.


Reference:

https://help.salesforce.com/s/articleView?id=sf.process_which_tool.htm&type=5 https://trailhead.salesforce.com/en/content/learn/modules/business_process_automation/automa tion_considerations



AW Computers has enabled the feature for Contact to multiple Accounts. A rep is trying to remove the primary Account from a Contact but Is unable to do so. The administrator has already updated the page layout to no longer require an Account.
What could be the issue?

  1. A primary Account relationship Is required on a Contact regardless of the page layout settings.
  2. The Contact has Indirect relationships to other Accounts.
  3. The Account Contact relationship record needs to be deleted first In order to disassociate Contact from the Account.
  4. Private Contacts need to be enabled in Setup.

Answer(s): A



AW Computers has enabled the feature for Contact to multiple Accounts. A rep is trying to remove the primary Account from a Contact but Is unable to do so. The administrator has already updated the page layout to no longer require an Account.
What could be the issue?

  1. A primary Account relationship Is required on a Contact regardless of the page layout settings.
  2. The Contact has Indirect relationships to other Accounts.
  3. The Account Contact relationship record needs to be deleted first In order to disassociate Contact from the Account.
  4. Private Contacts need to be enabled in Setup.

Answer(s): A

Explanation:

When the feature for Contacts to multiple Accounts is enabled, a Contact can have a direct relationship with multiple Accounts. However, one of these relationships must be designated as the primary Account relationship. This relationship is required on a Contact regardless of the page layout settings and cannot be removed unless the Contact is deleted or merged with another Contact.


Reference:

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



An administrator created two record types on the Account object: Internal Customers and External Customers. A custom profile called Sales has the External Customers record type assigned. The sharing rules for Accounts arm set to Public Read Only. On occasion. Sales users notice that an Account record has the wrong record type assigned. The administrator has created a screen flow that will change the record type on the user's behalf.
What will happen to the Sales user's record access after running this flow?

  1. Read access will be lost to the record.
  2. Edit access will be lost to the record.
  3. Record Access remains the same.
  4. A new record owner will be assigned.

Answer(s): C

Explanation:

Changing the record type of a record does not affect the record access of a user. Record access is determined by the organization-wide default, role hierarchy, sharing rules, manual sharing, teams, and ownership. Record type only affects the page layout and picklist values that are available for the record. Therefore, if a user has access to a record before changing its record type, they will still have the same access after changing its record type.


Reference:

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






Post your Comments and Discuss Salesforce ADX-201E exam with other Community members:

ADX-201E Discussions & Posts