Free Salesforce Advanced-Administrator Practice Exam with Questions & Answers

The equivalent field is the field that matches the dashboard filter field on the source report object. For example, if the dashboard filter is on Account Owner, then the equivalent field on the Opportunity object is Opportunity Owner. Changing the equivalent field ensures that the dashboard filter applies correctly to the Opportunity components. References: https://help.salesforce.com/s/articleView?id=sf.dashboard_filters.htm &type=5

Data categories and visibility are features that allow you to organize and control access to your Salesforce Knowledge articles based on different topics or criteria. Data categories are logical groupings of articles that reflect your business needs and processes. You can create a data category group and assign it to one or more article types, and then create data categories and subcategories within that group. Data category visibility is a setting that determines which data categories users can access based on their profiles or permission sets. You can use data categories and visibility to provide relevant and appropriate product documentation to your customers and support team. References: https://help.salesforce.com/s/articleView?id=sf.knowledge_categories.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.knowledge_category_visibility.htm &type=5

Use separate record types, page layouts, and sales processes for the Rental and Real Estate Teams is how the administrator should extend the Opportunity object to meet the teams’ different needs. Record types are a way to offer different business processes, picklist values, and page layouts to different users based on their profiles or permission sets. Page layouts are a way to control the layout and organization of fields, buttons, related lists, and other components on a record page. Sales processes are a way to define the stages that an opportunity goes through from creation to close. By using separate record types, page layouts, and sales processes for each team, the administrator can customize the opportunity object according to their different requirements and preferences.

A permission set is a collection of settings and permissions that can extend users’ functional access without changing their profiles. By creating a permission set with view All on Accounts and assigning it to the service and sales managers, an administrator can grant them access to all account records in their org without modifying their existing profiles. References: https://help.salesforce.com/s/articleView?id=sf.users_permissionsets.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. References: 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

A delegated administrator is a user who has been granted limited administrative privileges by an administrator through delegated administration groups. Delegated administrators can perform some administrative tasks without having full access to Setup.

Some functions that delegated administrators can perform are:

B) Build automation and validation rules using screen flows

Screen flows are types of flows that guide users through screens with elements such as text boxes, picklists, radio buttons, etc. Screen flows can also perform actions such as creating records, updating fields, sending emails, etc. Delegated administrators can build automation and validation rules using screen flows if they have been granted access to create and edit flows by an administrator. References: https://help.salesforce.com/s/articleView?id=sf.flow_concepts_design_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_distribute_delegated_admins.htm &type=5

D) Make updates to permission set configurations

Permission sets are collections of settings and permissions that can extend users’ functional access without changing their profiles. Delegated administrators can make updates to permission set configurations if they have been granted access to manage users by an administrator. References: https://help.salesforce.com/s/articleView?id=sf.users_permissionsets.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.admin_useradmin_delegated.htm &type=5

A cross-filter lets you filter records based on related objects and their fields. For example, you can filter accounts that have at least one opportunity from this year and at least one completed activity in the last 30 days. References: https://help.salesforce.com/s/articleView?id=sf.reports_cross_filters.htm &type=5

The Fields component is a Lightning component that allows administrators to display fields from a record on a Lightning page based on certain conditions or criteria. For example, administrators can use filter logic to show or hide fields based on field values or user profiles. In this case, the administrator can use the Fields component to display fields that only apply to condos based on the value of a field that indicates the type of property. References: https://help.salesforce.com/s/articleView?id=sf.lightning_app_builder_fields.htm &type=5

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. References: 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

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. References: 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. References: https://help.salesforce.com/s/articleView?id=sf.identity_verification_history.htm &type=5