Pass the Salesforce Advanced Administrator Advanced-Administrator Questions and answers with ExamsMirror

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

Opening the flow in Debug mode and running it as another user allows simulating how the flow behaves for different users with different permissions and settings. This can help identify any issues related to user

The Campaign Member option is only available for Update when using Data Import Wizard. This means that you can use Data Import Wizard to update existing campaign members with new or modified information, but you cannot use it to create new campaign members from a spreadsheet. To create new campaign members from a spreadsheet, you need to use other tools such as Data Loader, Import Wizard for Leads and Contacts, or Manage Members button on the campaign page. References: https://help.salesforce.com/s/articleView?id=sf.campaigns_members_adding_parent.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.data_importer.htm &type=5

A forecast is a projection of how much revenue or quantity you can generate from your sales pipeline for a given period of time. A forecast can be either revenue-based or quantity-based, depending on what you want to measure and track. A revenue-based forecast shows the amount of money expected from closed sales, while a quantity-based forecast shows the number of units expected from closed sales. You can choose the forecast type that best suits your business needs and goals when you set up Collaborative Forecasts in Salesforce. References: https://help.salesforce.com/s/articleView?id=sf.forecasts3_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.forecasts3_forecast_types.htm &type=5

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

Manual sharing is a way of granting access to individual records by manually sharing them with other users, roles, or groups. Manual sharing can override the organization-wide default and role hierarchy settings and give additional access to specific records. In this case, manual sharing could be the reason why only one user can see the account record, even though they have the same profile and role as another user who cannot see it. References: https://help.salesforce.com/s/articleView?id=sf.security_sharing_manual.htm &type=5

Planning deployments around maintenance schedules ensures that there are no interruptions or delays in the deployment process. Deploying all dependent components ensures that there are no missing metadata or references that could cause errors or failures in the deployment. Limiting change sets to 10,000 files ensures that the deployment does not exceed the maximum size limit for change sets

A record-triggered flow lets you automate actions when a record is created or updated. You can use scheduled paths to schedule actions relative to a date field on the record, such as close date. You should configure the trigger to flow after the record is saved so that you can access the updated field values. References: https://help.salesforce.com/s/articleView?id=sf.flow_concepts_trigger_types_record.htm &type=5

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

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