Master the Salesforce Certified Advanced Administrator (WI24) Advanced-Administrator Exam with Confidence!

Flows are tools that automate business processes by collecting data and performing actions in your org or an external system. Flows can be triggered by various events such as record creation, updates, or invocations from other processes or flows. Flows can also send email alerts aspart of their actions. To send a notification when a record is deleted and by whom, and to maintain their own discovery information, an administrator can use a flow that runs when a record is deleted, queries the record owner’s email address and discoveryinformation from another object or variable, and sends an email alert with those details. References:https://help.salesforce.com/s/articleView?id=sf.flow_concepts.ht m&type=5

Bulk API and Dataloader.io are both tools that can be used to update large numbers of records in Salesforce. Bulk API is a RESTful API that allows you to create, update, delete, or query millions of records asynchronously by submitting batches of data. Dataloader.io is a web-based data loader tool that allows you to import, export, or delete data using a simple user interface. References: https://developer.salesforce.com/doc s/atlas.en-us.api_asynch.meta/api_asynch/asynch_api_intro.htmhttps://dataloader.io/

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

Contacts to Multiple Accounts is a feature that allows administrators to relate a contact to multiple accounts without creating duplicate contacts for each account. This feature is useful for scenarios where a contact has business relationships with more than one account, such as consultants, brokers, or loan advisors. By setting up Contacts to Multiple Accounts for loan advisors at DreamHouse Realty, administrators can track which loan advisors work with which customers and which accounts without creating duplicate contacts for each account. References:https://help.salesforce.com/s/articleView?id=sf.contacts_multiple_accounts_overview.htm &type=5

Product schedules are features thatallow administrators to track revenue or quantity over time for products in opportunities or orders. Product schedules can be either revenue schedules or quantity schedules, depending on whether the product is sold by amount or by quantity. Product schedules can be either standard or customizable, depending on whether they use predefined settings or custom settings.

Line item schedules are records that represent each installment of revenue or quantity for a product over time. Line item schedules are createdautomatically when a product with a product schedule is added to an opportunity line item or an order product.

One limitation of product schedules is that line item schedules are unavailable in Process Builder and Workflow. This means that administratorscannot use these tools to automate actions based on line item schedules, such as sending email alerts, creating tasks, updating fields, or invoking flows. References: https://help.salesforce.com/s/articleView?id=sf.forecasts3_product_schedules.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.orders_line_item_schedules.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.product_schedule_considerations.htm &type=5

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 theopportunity.

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 determinewhich 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.

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

Product schedules allow users to track revenue or quantity over time for products in opportunities or orders by creating schedules manually or automatically based on predefined criteria such as start date, end date, frequency etc. However, product schedules have some limitations that administrators should consider before enabling this feature. One of these limitations is that line item schedules are unavailable in Process Builder and Workflow rules; only revenue schedules are available. References: https://help.salesforce.com/s/articleView?id=sf.products_schedules_def.htm &type=5https://help.salesforce.com/s/articleView?id=sf.products_schedules_considerations.htm &type=5

A change set is a tool that allows youto send customizations from one Salesforce org to another. A change set can contain components such as objects, fields, profiles, permission sets, workflows, and more. You can use change sets to migrate changes from a sandbox org to a production org or between two sandbox orgs that are affiliated with the same production org. In this case, you can deploy a change set from the sandbox to production that includes the Amount field and all the custom profiles that need access to it. This way, you can update the field-level security settings for the field on each profile in one deployment. References: https://help.salesforce.com/s/articleView?id=sf.changesets.htm &type=5https://help.salesforce.com/s/articleView?id=sf.changesets_components_field.htm &type=5

Workflow debug log category captures information about workflow rules,flows,processes, and actions that are executed as a result of a DML operation.References: 

QUESTIONNO: 18

An administrator is planning he release process for the year. The team will be using change sets to process deployment to production.

Which three best practices should be considered?

A. Plan your deployments around the production and sandbox maintenance schedules.

B. Use matching names for global publisher layouts and Outlook publisher layouts.

C. Be sure to test only after business hours the data after deployment.

D. Make sure to deploy all dependent components.

E. Make sure change sets are limitedto 10,000 files.

Answer: A, D, E

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 forchange sets

Deselecting disable session timeout warning popup enables a warning message to appear before auser’s session expires due to inactivity. This gives the user a chance to extend their session or save their work before being logged out. This can help prevent users from being logged out of Salesforce without notice