2026 Actual Salesforce ADX-211 Dumps, Updated Exam Questions for Guaranteed Pass

ADX-211 free sample questions and answers

Salesforce ADX-211 practice quiz with correct answers for search indexing.

1. Question 1

   The administrator at AW Computing has been asked to review whether any users are making configuration changes directly in production.

   Which item should the administrator review to find these details?

   ASetup Audit Trail
   

   BField History Tracking
   

   CLogin History
   

   DOrganization-Wide Defaults
   

   Correct answer: A

   The Setup Audit Trail is a tool that allows you to view and download a log of changes made in your org's Setup area. The log shows up to 20 fields of information for each change, such as who made it, when it was made, what type of change it was, and what values were changed. You can use the Setup Audit Trail to track configuration changes directly in production and identify any unauthorized or problematic changes. Reference: https://help.salesforce.com/s/articleView?id=sf.monitorsetup.htm&type=5

   
   

2. Question 2

   The administrator at Cloud Kicks is evaluating the capabilities of Schema Builder to create custom objects and custom fields. The administrator likes the user interface of the Schema Builder, as opposed to the new object and field wizards, but also notices some limitations.

   What needs to be configured from the object manager instead of Schema Builder?

   AAdd custom fields to the page layout.
   

   BMake available for Customer Postal.
   

   CEnable field history tracking
   

   DAllow Reports and Activities
   

   Correct answer: A

   While the Schema Builder is a powerful tool in Salesforce for visually creating and managing custom objects and fields, there are certain configurations that must be done in Object Manager rather than Schema Builder. One of these configurations is enabling field history tracking.

   Field History Tracking:

   Field history tracking cannot be configured directly within Schema Builder. This setting must be enabled from within the Object Manager, where administrators can specify which fields on an object should have their changes tracked.

   Enabling field history tracking involves navigating to the object in Object Manager, accessing the field history tracking settings, and selecting specific fields to track.

   Limitations of Schema Builder:

   Schema Builder is useful for quickly creating custom objects, relationships, and fields, but it does not support all configurations, such as enabling field history tracking, defining object-level permissions, or setting advanced object configurations.

   For these types of configurations, administrators need to return to Object Manager where these settings are available.

   Incorrect options:

   Add custom fields to the page layout: This task is typically done within Object Manager, but Schema Builder does allow customization of page layouts to a certain extent through drag-and-drop.

   Make available for Customer Portal: Schema Builder does not control portal availability; however, this is managed through Object Manager settings related to record visibility for portal users.

   Allow Reports and Activities: This setting can be configured in Schema Builder when initially creating an object, but further refinements and permission settings must often be done in Object Manager.

   In conclusion, enabling field history tracking requires access to the Object Manager, as it cannot be configured through Schema Builder.

   
   

3. Question 3

   The administrator at Universal Containers does a soft launch of the Salesforce Authenticator app and allows users to optionally use it to log in. The administrator would now like to look at how many users have successfully used it since it was rolled out.

   What are two ways the administrator can get this information?

   Choose 2 answers

   ARun a session setting report, specifying login methods by user.
   

   BOpen the Login Access Policies in Setup which shows how many users are using MFA.
   

   CCreate a new view in Identity Verification History, specifying Method.
   

   DThe order of flow execution is unpredictabl
   

   Correct answer: A, C

   Salesforce Authenticator is an app that allows users to verify their identity when logging in to Salesforce using two-factor authentication (2FA). 2FA adds an extra layer of security by requiring users to enter a verification code or approve a notification on their mobile device after entering their username and password.

   To look at how many users have successfully used Salesforce Authenticator since it was rolled out, an administrator can use two ways:

   A) Run a session setting report, specifying login methods by user.

   A session setting report is a report that shows information about users' login sessions, such as login time, location, IP address, browser, platform, etc. A session setting report can also show the login methods used by users, such as password, verification code, or notification. By running a session setting report, specifying login methods by user, an administrator can see how many users have used Salesforce Authenticator to log in to Salesforce. Reference: https://help.salesforce.com/s/articleView?id=sf.reports_session.htm&type=5

   C) Create a new view in Identity Verification History, specifying Method.

   Identity Verification History is a page that shows the history of identity verification attempts for each user in the org. Identity verification history includes information such as date, time, status, method, and IP address of each attempt. By creating a new view in Identity Verification History, specifying Method as a filter criterion, an administrator can see how many users have used Salesforce Authenticator to verify their identity when logging in to Salesforce. Reference: https://help.salesforce.com/s/articleView?id=sf.identity_verification_history.htm&type=5

   
   

4. Question 4

   The Cloud Kicks administrator wants to open up opportunity sharing to directors who oversee regional managers so they can access records to assist regional managers.

   What sharing mechanism should be used?

   Aorganization wide Defaults
   

   BRole Hierarchy
   

   CManual Sharing
   

   DSharing Settings
   

   Correct answer: B

   Role hierarchy is a sharing mechanism that should be used to open up opportunity sharing to directors who oversee regional managers so they can access records to assist regional managers. Role hierarchy is a way to grant access to records based on the user's position in an organization's hierarchy of roles. Role hierarchy can grant users access to records owned by or shared with users below them in the hierarchy for objects that have organization-wide defaults set to Private or Public Read Only. By using role hierarchy, the administrator can ensure that directors can access opportunities owned by or shared with regional managers who report to them

   
   

5. Question 5

   The administrator at Cloud Kicks noticed that a before trigger, which handles saving the original version of a record to an external database, fails. However, a flow configured for fast field updates runs successfully.

   How should the administrator advise the developer?

   ARecord-triggered flows that are configured to run before save execute prior to all before triggers.
   

   BA validation rule could be preventing records from ever meeting the conitions in the trigger.
   

   CThe trigger is writing the data to the wrong place in the external data archive.
   

   DThe code could be trying to create duplicates in the archieve when it is unable to.
   

   Correct answer: D

   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.en-us.apexcode.meta/apexcode/apex_triggers_context_variables.htm