ADVANCED-ADMINISTRATOR Practice Questions

The Dev Console Log Inspector is a tool that allows you to view and analyze debug logs in a graphical

interface. Debug logs contain information about database operations, system processes, and errors

that occur when executing a transaction or running unit tests. To troubleshoot a process builder, the

administrator should look for event types beginning with FLOW in the event column. These event

types indicate the start and end of a flow interview, as well as any flow elements, faults, or decisions

that occur during the execution. Reference:

https://help.salesforce.com/s/articleView?id=sf.code_dev_console_log_inspector.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.code_debug_log_event_types.htm&type=5

Data Import Wizard is a tool that allows administrators to import data for standard and custom

objects in Salesforce using CSV files. Data Import Wizard can handle up to 50,000 records at a time

and supports simple data transformations and validations. Data Import Wizard can be used to upload

records for a custom object when the number of records is small and the import frequency is low.

Data Loader is a tool that allows administrators to import or export large amounts of data (more than

50,000 records) from or to Salesforce using CSV files. Data Loader can be used for inserting, updating,

deleting, upserting, exporting, or extracting data. Bulk API is an API that allows administrators to

process large batches of records asynchronously in the background. Bulk API can handle millions of

records with high performance and minimal system resources. By using Data Loader with Bulk API

enabled, an administrator can import a large amount of historical data (more than 100,000 records)

from another system efficiently and securely. Reference:

https://help.salesforce.com/s/articleView?id=sf.data_loader.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.loader_api.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.bulk_api_intro.htm&type=5

:

To show forecast numbers by territory regardless of who owns the record, CK should enable Territory

Forecast. To forecast based on role hierarchy, CK should enable Role Hierarchy Forecast. To match the

Territory Forecast to the Hierarchy Forecast model, CK should modify the Territory Forecast

accordingly. Reference:

https://help.salesforce.com/s/articleView?id=sf.forecasts3_territory_forecasts.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.forecasts3_enable.htm&type=5

A flow is an automation tool that allows you to create processes that perform actions based on user

input or record changes. A flow can be triggered by a user who launches it from a button, link, or

Lightning page, or by the system when a record is created or updated. A flow has different versions

that can be active or inactive. An active version is the one that runs when the flow is triggered, while

an inactive version is the one that is saved but not running. When you deploy a flow to production

with a change set, the flow version is deployed as inactive by default. This means that you need to

activate the flow manually after deployment if you want it to run in production. Reference:

https://help.salesforce.com/s/articleView?id=sf.flow_overview.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.flow_distribute_changesets.htm&type=5

A permission set is a collection of settings and permissions that can extend users’ functional access

without changing their profiles. By creating a permission set with view All on Accounts and assigning

it to the service and sales managers, an administrator can grant them access to all account records in

their org without modifying their existing profiles. Reference:

https://help.salesforce.com/s/articleView?id=sf.users_permissionsets.htm&type=5

When the feature for Contacts to multiple Accounts is enabled, a Contact can have a direct

relationship with multiple Accounts. However, one of these relationships must be designated as the

primary Account relationship. This relationship is required on a Contact regardless of the page layout

settings and cannot be removed unless the Contact is deleted or merged with another Contact.

Reference: https://help.salesforce.com/s/articleView?id=sf.shared_contacts_set_up.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.shared_contacts_considerations.htm&type=5

The setup audit trail tracks the recent setup changes that you and other administrators have made to

your org. It can help you troubleshoot issues by showing you what changes were made, who made

them, and when. In this case, the setup audit trail can help the administrator identify if someone

changed the field-level security, page layout, or profile settings for the industry picklist field.

Reference: https://help.salesforce.com/s/articleView?id=sf.monitorsetup.htm&type=5

To debug platform events in Apex code, you need to set a debug log on the Automated Process

entity. This entity represents an automated process user that runs flows and processes in your org.

By setting a debug log on this entity, you can capture the events that are published and consumed by

your flow and Apex code, as well as any errors or exceptions that occur during the execution.

Reference: https://developer.salesforce.com/docs/atlas.enus.platform_events.meta/platform_events/platform_events_debug.htm

https://help.salesforce.com/s/articleView?id=sf.code_add_users_debug_log.htm&type=5