Free Salesforce ADM-201 Practice Exam with Questions & Answers | Set: 6

To help agents fill in event details and request dates for open house events without double-booking them, the administrator should create an approval process on the Campaign object, which is used to manage marketing events in Salesforce. The approval process can define entry criteria based on campaign fields such as type or status, specify initial submission actions such as sending email alerts or updating fields, assign approvers who can review and approve event requests, and specify final approval actions such as creating tasks or updating fields. Creating a workflow rule, a sharing rule, or a campaign will not help agents request event dates or prevent double-booking. References: https://help.salesforce.com/s/articleView?id=sf.campaigns_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.approvals_considerations.htm &type=5

Security Health Check is a tool that can be used to identify and fix potential session vulnerabilities. Security Health Check scans the security settings in an org and compares them to a baseline set of standards, such as the Salesforce Baseline Standard or the Salesforce Optimized Standard. Security Health Check provides a health check score and a list of issues and recommendations for improving the security settings. References: https://help.salesforce.com/s/articleView?id=sf.security_health_check.htm &type=5

The contact hierarchy is a feature that allows users to view contacts related to an account in a hierarchical tree structure based on their role or position within the account. The contact hierarchy respects record-level access by user, meaning that users can see only those contacts that they have access to based on their profile permissions and sharing settings. The other options are incorrect because contact hierarchy is not limited to 3,000 contacts at one time (it can display up to 5,000 contacts), customizing hierarchy columns does not change the recently viewed contacts list view (it only affects how contacts are displayed in the hierarchy), and sharing settings are not ignored by contacts displayed in the contact hierarchy (they determine which contacts are visible to users). References: https://help.salesforce.com/s/articleView?id=sf.contacts_hierarchy.htm &type=5

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

Assignment rules are tools that allow administrators to automatically route records to users or queues based on certain criteria. For example, an assignment rule can assign cases to different queues based on case priority, origin, type, or other fields. Assignment rules can be triggered when records are created manually, via email, web, or API. Assignment rules consist of multiple rule entries that define the criteria and actions for each assignment scenario. References: https://help.salesforce.com/s/articleView?id=sf.customize_leadrules.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_casesupport_assign.htm &type=5

Two considerations for preventing users from accessing Salesforce from outside of their network are:

IP address restrictions are set on the profile or globally for the org, which limit login access based on IP ranges specified by an administrator

Restrict U2F Security Keys on the user’s profile to enforce login hours, which require users to use security keys during certain hours of day Assigning single sign-on to a permission set or enforcing Login IP Ranges on Every Request will not prevent users from accessing Salesforce from outside of their network. References: https://help.salesforce.com/s/articleView?id=sf.security_networkaccess.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.security_keys_restrict.htm &type=5

Formula fields are types of fields that calculate a value based on an expression or formula that references other fields or constants. Formula fields prevent administrators from changing their field type once they are created because they may be referenced by other functionalities such as reports, validation rules, workflow rules, etc., that depend on their data type and value. If a formula field is referenced by other functionalities, then changing its field type may cause errors or unexpected results. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_formulas.htm &type=5

Description: The Account object in Salesforce is used to store information about individual customers or businesses that your organization interacts with. It holds essential data such as company name, contact information, industry, and related activities.

Use Case: Accounts are used to represent the organizations (or individuals) your support team is assisting. They serve as a central repository for tracking customer information and interactions.

Out of the Box Features: Includes fields like Account Name, Account Owner, Industry, Phone, and Address. It also supports relationships with Contacts, Opportunities, Cases, and other objects.

Description: The Case object is used to track and manage customer issues, complaints, requests, or inquiries. Each case represents a single customer interaction and can be used to manage the resolution process.

Use Case: Cases are fundamental to customer support operations. They help support agents keep track of customer problems, assign cases to appropriate team members, and ensure timely resolution.

Out of the Box Features: Includes fields like Case Number, Subject, Status, Priority, and Origin. It supports workflows, escalation rules, and case assignment rules.

Description: The Contract object stores information about the agreements between your company and your customers. These contracts define the terms of service, support levels, and other legal agreements.

Use Case: Contracts are useful for managing service level agreements (SLAs) and ensuring that support teams adhere to the agreed-upon terms. They can be linked to Accounts and Cases to provide context and track compliance.

Out of the Box Features: Includes fields like Contract Start Date, End Date, Contract Term, Status, and Account. It supports related lists to associate contracts with cases, assets, and other records.

Accounts:

Salesforce Account Object Documentation

Trailhead: Manage Your Customer Data

Cases:

Salesforce Case Object Documentation

Trailhead: Set Up Case Management

Contracts:

Salesforce Contract Object Documentation

Trailhead: Administer Salesforce Contracts

Account Object2. Case Object3. Contract ObjectReferences

A criteria-based sharing rule is a tool that allows administrators to share records with certain users based on field values rather than ownership. For example, a criteria-based sharing rule can share all opportunities with a cross-sell opportunity type with a specific group of users. A public group is a collection of individual users, roles, roles and subordinates, or other groups that can be used to simplify sharing settings and other processes. In this case, the administrator can add the subject matter experts to a public group and give them access to records with a criteria-based sharing rule that matches the cross-sell opportunity type. References: https://help.salesforce.com/s/articleView?id=sf.sharing_criteria_rules.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.public_groups.htm &type=5

Flow Builder supports creating a wizard that can collect user input and perform actions.