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?
Correct Answer: B
A primary account relationship is a feature that allows you to link a contact to a single account as its primary account. A primary account relationship is required on a contact regardless of the page layout settings or the contact to multiple accounts feature. This means that you cannot remove the primary account from a contact, but you can change it to another account. You can also add secondary accounts to a contact if you have enabled the contact to multiple accounts feature. References: https://help.salesforce.com/s/articleView?id=sf. contacts_multiple_accounts.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.contacts_fields. htm&type=5
Question 2
The distributors at Cloud Kicks are eligible for support based on a specific service contract-How should the administrator show this in Salesforce?
Correct Answer: A
Entitlement management lets you create and maintain service contracts that specify the support terms for each account. You can use entitlement processes to automatically apply the correct service contract to a case based on criteria you define. References: https://trailhead.salesforce.com/en/content/learn/modules/entitlements /entitlements_overview
Question 3
Cloud Kicks has updated several profiles and created a new app in the sandbox. After testing, everything is working as expected. Which two options should the administrator use to migrate these changes to production from the sandbox? Choose 2 answers
Correct 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. References: https://help.salesforce.com/s/articleView?id=sf. changesets.htm&type=5
Question 4
Cloud Kicks (CK) is working on adding a Knowledge base to its online customer community. The administrator suggests using Salesforce Knowledge to meet this requirement. What are three reasons CK should utilize Data Categories when creating articles in Knowledge? Choose 3 answers
Correct Answer: B,D,E
Three reasons CK should utilize Data Categories when creating articles in Knowledge are: * Data Categories help organize the Knowledge base content displayed. 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 categories help you organize your articles by topic or criteria and make them easier to find and browse by your users or customers. * Data Categories provide a way to secure access to the Knowledge base content. 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 category visibility to control access to your articles based on their data categories and ensure that only relevant and appropriate content is displayed to different users or customers. * A Knowledge article can be tagged to more than one Data Category. A Knowledge article is a document that provides information or answers to common questions or issues. A Knowledge article can be tagged to one or more data categories within each data category group that is assigned to its article type. This allows you to classify your articles by multiple criteria and make them searchable and accessible by different users or customers.
Question 5
AW Computing has a new requirement from its security team where audit information relating to an account must be recorded in a new custom object called Audit. Audit records need to be preserved for 10 years and only accessible by the audit team. What relationship should be used to relate the Audit object to the Account object?
Correct 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. Reference: Salesforce documentation recommends using Lookup relationships when objects need to remain independent or when additional flexibility for sharing and retention is required.
