Salesforce Administer, Extend, and Automate Salesforce ADX-211 Exam Practice Test

Answer : C

Displaying the related contacts related list and adding the direct field will allow users to distinguish between contacts and related contacts. The related contacts related list shows all contacts that are related to an account, either directly or indirectly. The direct field indicates whether a contact is directly associated with an account or not. By adding this field to the related list, users can easily see which contacts are direct and which are not. Reference: https://help.salesforce.com/s/articleView?id=sf.contacts_multiple_accounts.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.contacts_multiple_accounts_direct_field.htm&type=5

Answer : A

Configuring one app per department and activating record pages for each app will ensure that users view records in a way that makes sense for each department. An app is a collection of items that work together to serve a particular function. An app can have different record pages for different objects and profiles. By activating record pages for each app, the administrator can customize what users see based on their app context. Reference: https://help.salesforce.com/s/articleView?id=sf.app_manager_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.app_builder_customize_lex_pages_assign.htm&type=5

Answer : B

A validation rule and a stage guidance in Path are two features that can help ensure that users input a use case before moving the opportunity stage to qualified.

A validation rule is a formula that validates the data entered by users and prevents records from being saved if they do not meet certain criteria. In this case, a validation rule can be used to check if the Use Case field is blank when the Stage field is changed to Qualified, and display an error message if so.

A stage guidance in Path is a feature that displays helpful information or tips for each stage of a sales process on an opportunity record page. In this case, adding the Use Case field to the stage guidance in Path can remind users to fill out this field before moving to the next stage.

Answer : B

The Automated Case User is the default user for cases created via Email-to-Case. This user needs to have permissions to the new record type in order to assign it to the incoming cases. If the Automated Case User does not have the permissions, the cases will receive a different record type based on the organization-wide default settings. Reference: https://help.salesforce.com/s/articleView?id=sf.case_email_to_case.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.case_automated_user.htm&type=5

Answer : A, B

Delegated administrators in Salesforce are designated users who are given limited administrative privileges to assist system administrators without having full access to all administrative functions. The two functions they can typically perform, which align with the permissions available to delegated admins, are:

Set up users and password management:

Delegated administrators can create and manage user accounts, which includes setting up new users, resetting passwords, and updating user details.

This is particularly useful for helping with user management tasks without providing full system administrator access.

Configure updates to sharing rules:

Delegated administrators can manage sharing rules within their specific groups or roles, which helps control access to records based on criteria set within the organization.

This level of access allows them to modify sharing rules to ensure appropriate data access without requiring full administrative control over all settings.

The other options listed are not within the scope of delegated administrator capabilities:

Manage custom objects and customize nearly every aspect: Delegated administrators do not have the ability to manage custom objects or perform extensive customization. These functions are reserved for system administrators with broader privileges.

Make updates to permission set configurations: Delegated administrators cannot create or modify permission sets. This is also restricted to full administrators, as it involves controlling access at a granular level across the org.

By utilizing delegated administrators for user and sharing rule management, organizations can maintain security and control while also sharing some administrative workload.

Answer : B

In this scenario, a Lookup relationship is the most appropriate choice for relating the Audit custom object to the Account object. This relationship allows for flexibility, especially when it comes to data retention and access control requirements, as outlined by AW Computing's security team.

Lookup Relationship:

A Lookup relationship links two objects, allowing records from the custom Audit object to be associated with the Account object. Unlike a Master-Detail relationship, it offers greater flexibility in terms of record ownership, sharing, and visibility controls, which is particularly useful for sensitive data.

The Lookup relationship will enable administrators to set specific permissions, ensuring that only the audit team has access to the records, as required.

Additionally, records in the Lookup relationship are independent. Therefore, if the Account record is deleted, the Audit record can persist, aligning with the need to retain Audit records for 10 years.

Preservation and Access Control:

Given the 10-year retention requirement, the independence of records under a Lookup relationship is ideal. It ensures that Audit records are not automatically deleted when an associated Account record is removed.

Access to Audit records can be restricted to the audit team by setting up custom sharing rules or permissions, which is achievable through the Lookup relationship's flexible sharing model.

Incorrect options:

Master-Detail: In a Master-Detail relationship, the detail (child) records are dependent on the master (parent) record. Deleting an Account would automatically delete any associated Audit records, which would conflict with the retention requirement.

Many-To-Many: This type of relationship involves a junction object to associate multiple records from both sides. It is not necessary in this case, as the requirement is a one-to-many relationship from Account to Audit records.

Self: A self-relationship would allow records within the Audit object to be related to each other. This does not apply to linking the Audit object to the Account object.

In conclusion, the Lookup relationship provides the necessary flexibility for data preservation and access control, making it the optimal choice for this requirement.

Answer : C, D

Change sets are tools that allow administrators to move customizations such as fields, page layouts, profiles, permission sets, etc. from one Salesforce org to another. To use change sets, administrators need to establish a deployment connection between a source org (such as a sandbox) and a target org (such as production). Then, administrators can create an outbound change set in the source org that contains the components they want to deploy, and upload it to the target org. In the target org, administrators can view and validate the inbound change set before deploying it to their org. Reference: https://help.salesforce.com/s/articleView?id=sf.changesets.htm&type=5