Advanced-Administrator Exam Questions

Explanation: A lookup relationship with Read/Write sharing setting is the recommended option to use when adding a field to Case Outcome custom object. A lookup relationship is a type of relationship that links two objects together and allows users to associate one record with another. A lookup relationship does not affect the security or deletion of either record and can be optional or required. In this case, you can create a lookup relationship field on Case Outcome object that references Case object and allows users to link multiple Case records to multiple Case Outcome records. You can also set the sharing setting for the lookup field to Read/Write, which means that users who have access to the parent record can also access and edit the child record.

Explanation: When you have multiple record-triggered flows that are configured to run before the record is saved on the same object, the order of flow execution is unpredictable. This means that you cannot guarantee which flow will run first or last, or how they will affect each other’s field updates. Therefore, you should avoid creating multiple before-save flows on the same object and instead consolidate them into one flow if possible.

Explanation: Giving the account owner Read access to both the Account and the Quota objects will give access to all Item records. Since Item is a junction object between Account and Quota, users need to have at least Read access to both parent objects to see Item records. If users have access to only one parent object, they will not be able to see Item records related to the other parent object.

Explanation: A joined report is a type of report that allows you to create multiple report blocks that provide different views of your data. Each report block can have its own fields, columns, sorting, and filtering. A joined report can only be created from summary or matrix reports. You can use a joined report to show data from different report types or data sources on a single report. In this case, you can use a joined report to show Accounts with Open Cases by creating two report blocks: one for accounts and one for cases with a filter for open status. You can then join the two blocks by a common field such as Account ID or Account Name.

Explanation: The fields that display in the details of the record page are controlled by the page layout assigned to the user’s profile and record type. The administrator can edit the page layout to add, remove, or reorder fields on the record page.

Explanation: Two options that the administrator should check to ensure the product is available are: Confirm the correct price book is selected on the opportunity. A price book is a list of products and their prices that can be added to an opportunity. An opportunity can have only one price book at a time, and the products that are available for selection depend on the price book that is chosen. Therefore, the administrator should check if the opportunity has the right price book that contains the new keyboard product.
Ensure the product is associated with the correct price book. A product is a good or service that can be sold in Salesforce. A product can be associated with one or more price books, depending on how it is priced for different markets or segments. Therefore, the administrator should check if the new keyboard product is added to the appropriate price book that is used by the opportunity.
The other two options are incorrect because:
Making custom fields does not affect the availability of products on an opportunity. Custom fields are used to store additional information or calculations on an object, but they do not determine which products can be selected from a price book. Turning on field tracking does not affect the availability of products on an opportunity. Field tracking is used to monitor changes to certain fields on an object and display them in a history related list, but it does not determine which products can be selected from a price book.

Explanation: Debug Log is a tool that captures information about database operations, system processes, and errors that occur when executing a transaction or running a unit test. Debug Log can help troubleshoot issues related to triggers, workflows, validation rules, or other custom logic by showing the order of execution and the values of variables and expressions

Explanation: The Analyze feature in the Lightning App Builder toolbar is a tool that helps you optimize the performance of your record pages by providing recommendations and insights on how to improve page load time and user experience. It can help you identify which fields and components are taking the most time to load and suggest ways to reduce their impact. You can also compare your page performance with other pages in your org or with Salesforce best practices.

Explanation: Account teams are groups of users who work together on an account. Administrators can enable account teams and grant team members different levels of access to accounts and related records such as contacts, opportunities, and cases. By using account teams, Cloud Kicks can grant engineers access to the necessary accounts when they need assistance from them, while maintaining data security for other accounts that they do not need to access.

Explanation: A high assurance session is a type of session security level that requires users to verify their identity using a second factor of authentication, such as Salesforce Authenticator, a verification code, or a security key. Administrators can configure certain actions or permissions to require a high assurance session, such as exporting reports, viewing encrypted data, or accessing connected apps.
If users are able to run reports but are taken to a login screen and prompted for additional verification when they try to export a report, it could be because exporting is configured to require a high assurance session. This means that users need to use a second factor of authentication to export reports, even if they have already logged in with their username and password.