Salesforce Advanced-Administrator Salesforce Certified Advanced Administrator (SP25) Exam Practice Test

The Setup Audit Trail is a tool that allows you to view and download a log of changes made in your org’s Setup area. The log shows up to 20 fields of information for each change, such as who made it, when it was made, what type of change it was, and what values were changed. You can use the Setup Audit Trail to track configuration changes directly in production and identify any unauthorized or problematic changes. References: https://help.salesforce.com/s/articleView?id=sf.monitorsetup.htm &type=5

To ensure that secure fields remain protected in email templates, administrators should remove the fields from the email. Email templates can expose sensitive information if they contain fields with secure data. By excluding these fields, administrators can prevent unauthorized access to sensitive information through email communication.

Removing Secure Fields from Email Templates:

When creating or updating email templates, administrators should carefully assess the fields included and remove any that contain sensitive information, such as encrypted fields or fields that contain Personal Identifiable Information (PII).

This approach ensures that secure information is not unintentionally shared via email, aligning with best practices for data security and minimizing exposure risks.

Implications of Including Secure Data in Emails:

Secure fields, particularly those that contain sensitive or confidential information, should be restricted from emails to avoid potential data breaches.

Email communication often lacks the same security controls as the Salesforce platform, making it essential to limit the sharing of sensitive data.

Incorrect options:

Implement GDPR: While GDPR compliance ensures proper data handling practices, it does not directly prevent secure fields from being included in emails.

Set up an approval process for email alerts: An approval process can control the sending of email alerts but does not inherently protect secure fields within the email content.

Use classic encrypted fields: Encrypted fields add a layer of security for data at rest within Salesforce but do not provide specific protections for data included in email templates. Moreover, encrypted fields cannot be referenced in email templates.

In conclusion, the most effective way to ensure that secure fields are not exposed through email templates is to remove these fields from the template altogether, avoiding the inclusion of sensitive data in email communications.

Two options that the administrator can use to solve this scenario are:

Create a custom object. A custom object is an object that you define to store information that is specific to your organization or industry. In this case, you can create a custom object for the form that has more than 30 fields and relates to the account or opportunity object. This way, you can store multiple submissions of the form for each account or opportunity and track their changes over time.

Turn on Field Tracking. Field tracking is a feature that allows you to monitor changes to certain fields on an object and display them in a history related list. In this case, you can turn on field tracking for the fields on the form custom object and see what values were changed from one submission to another.

A validation rule is a formula that validates the data entered by a user and prevents the record from being saved if the data does not meet certain criteria. In this case, the administrator can create a validation rule to ensure that the custom encrypted field for credit card numbers has exactly 16 digits. The other options are not applicable for encrypted fields. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_encrypted_fields.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.v alidation_rules.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.

Changing the record type of a record does not affect the record access of a user. Record access is determined by the organization-wide default, role hierarchy, sharing rules, manual sharing, teams, and ownership. Record type only affects the page layout and picklist values that are available for the record. Therefore, if a user has access to a record before changing its record type, they will still have the same access after changing its record type. References: https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.security_sharing_overview.htm &type=5

Salesforce Authenticator is an app that adds an extra layer of security for logging into Salesforce by requiring users to verify their identity using their mobile device after entering their username and password on Salesforce login page. To see how many users have successfully used Salesforce Authenticator since it was rolled out, an administrator can use two methods:

A) Create a new view In Identity Verification History, specifying Method.

Identity Verification History is a tool that shows information about each identity verification event for users in your org, such as the date and time, the verification method used, the IP address, and the status of the verification. By creating a new view in Identity Verification History and specifying the method as Salesforce Authenticator, an administrator can see how many users have used the app to verify their identity when logging in. References: https://help.salesforce.com/s/articleView?id=sf.identity_verification_history.htm &type=5

D) Export Login History and filter based off of Authentication Method Reference.

Login History is a tool that shows information about each login attempt for users in your org, such as the date and time, the username, the source IP address, the login type, and the status of the login. By exporting Login History as a CSV file and filtering based on the Authentication Method Reference column, an administrator can see how many users have used Salesforce Authenticator as their authentication method when logging in. References: https://help.salesforce.com/s/articleView?id=sf.monitoring_login_history.htm &type=5

Delegated administrators in Salesforce are designated users who are given limited administrative privileges to assist system administrators without having full access to all administrative functions. The two functions they can typically perform, which align with the permissions available to delegated admins, are:

Set up users and password management:

Delegated administrators can create and manage user accounts, which includes setting up new users, resetting passwords, and updating user details.

This is particularly useful for helping with user management tasks without providing full system administrator access.

Configure updates to sharing rules:

Delegated administrators can manage sharing rules within their specific groups or roles, which helps control access to records based on criteria set within the organization.

This level of access allows them to modify sharing rules to ensure appropriate data access without requiring full administrative control over all settings.

The other options listed are not within the scope of delegated administrator capabilities:

Manage custom objects and customize nearly every aspect: Delegated administrators do not have the ability to manage custom objects or perform extensive customization. These functions are reserved for system administrators with broader privileges.

Make updates to permission set configurations: Delegated administrators cannot create or modify permission sets. This is also restricted to full administrators, as it involves controlling access at a granular level across the org.

By utilizing delegated administrators for user and sharing rule management, organizations can maintain security and control while also sharing some administrative workload.

The sales manager and system administrator will be able to edit this new contact record because they are either the owner or have Modify All Data permission respectively. Users above or below the sales manager in the role hierarchy will not be able to edit this contact record because contacts are controlled by parent and accounts are set to Public Read Only. All users in the organization will be able to view but not edit this contact record because accounts are set to Public Read Only. References: https://help.salesforce.com/s/articleView?id=sf.admin_sharing.htm &type=5

Salesforce’s Data Export Service is a tool that allows you to export your organization’s data to a set of comma-separated values (CSV) files and store them in a backup location of your choice. You can schedule this service to run weekly or monthly and receive an email notification when your files are ready to download. This is one way to back up your data daily without using any external tools or services. References: https://help.salesforce.co m/s/articleView?id=sf.data_export.htm&type=5

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

change sets are tools that allow administrators to move customizations from one Salesforce org to another. However, change sets do not track dependencies or conflicts between components in different orgs, so administrators need to manually verify that all required components are included in the change set and that they do not overwrite existing customizations in the target org. To avoid losing changes in production due to deploying an incomplete or incorrect change set, administrators should push the change set to another sandbox first and test it there before deploying it to production. References: https://help.salesforce.com/s/articleView?id=sf.changesets_considerations.htm &type=5 https://help.salesforce.com /s/articleView?id=sf.changesets_best_practices.htm&type=5

A validation rule can enforce data quality by preventing users from saving records that do not meet certain criteria. In this case, the validation rule can check if both the Sales Engineer and the Account Executive lookup fields are blank, and display an error message if so. This way, the director of sales can ensure that every opportunity has either a sales engineer or an account executive assigned to the deal. References: https://help.salesforce.com/s/articleView?id=sf.validation_rules_overview.htm &type=5

The order of execution for flows that are configured to run before the record is saved on the same object is unpredictable and may vary depending on factors such as flow version, flow name, or flow creation date. Therefore, it is recommended to avoid creating multiple flows with the same trigger conditions and instead consolidate them into a single flow.

REGEX is a function that allows administrators to check whether a text value matches a regular expression pattern. Regular expressions are a way to define complex patterns of characters using symbols and operators. REGEX can be used to enforce consistent formatting for a field value by specifying the required length, characters, and separators.

A summary report with a cross-filter is a type of report that allows you to summarize data by grouping rows and columns and applying filters based on related objects and fields. A cross-filter is a filter that lets you include or exclude records in your report based on related objects and their fields. In this case, you can create a summary report that includes a cross-filter to the Account object with a sub-filter for credit card number equal to null. This will show you all B2C accounts that are missing the credit card number, regardless of whether it is encrypted or not. References: https://help.salesforce.com/s/articleView?id=sf.reports_summary_charts.htm &type=5 https://help.salesforce.com/s/articleView? id=sf.reports_cross_filters.htm&type=5

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 have decision elements that evaluate conditions and determine which path to follow in the flow. By combining the two flows into one with decision elements, the administrator can ensure that the flow runs in the correct order and updates the field on the child record after it is created by the first flow. References: https://help.salesforce.com/s/articleView?id=sf.flow_concepts.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_decision.htm &type=5

To ensure that multiple field updates occur in a specific order on a custom object, the administrator should create a process with one criteria node and three field updates arranged in the correct order. This approach allows the updates to execute sequentially within a single automation framework, ensuring that they happen in the intended order.

Using Process Builder with a Single Criteria Node:

In Process Builder, the administrator can define a single criteria node that triggers the field updates. By adding multiple field updates within this single node and arranging them in the desired sequence, Salesforce will execute them in that specific order.

This setup provides better control over the sequence of updates compared to multiple workflow rules, as Process Builder will execute each field update step by step as configured within the node.

Advantages Over Workflow Rules:

Unlike workflow rules, where the order of execution can be less predictable due to separate triggers, Process Builder enables precise control over the execution sequence within the same process.

Using multiple workflow rules or multiple criteria nodes with stop actions would complicate the setup without guaranteeing the specific order. Process Builder’s structure ensures that updates proceed in the exact order defined.

Incorrect options:

Option A (Three workflow rules): Creating separate workflow rules for each update does not ensure a specific order of execution, as workflow rules are not guaranteed to run sequentially.

Option C (Three criteria nodes with stop actions): This approach would execute each node separately, and the stop action after each node adds unnecessary complexity, without ensuring the sequential order required.

Option D (One workflow rule with three field updates): Workflow rules do not guarantee the order of field updates within a single rule. Using Process Builder with a single node is more reliable for sequential execution.

In conclusion, Process Builder with one criteria node and ordered field updates is the most effective approach to ensure a specific execution sequence for multiple field updates on the Shipment object.

Case Source updates to ‘email’ before the record is saved because the Process Builder runs before the auto-response rule. Then, an email is sent out using Template2 because the auto-response rule evaluates the Case Source value after it is updated by the Process Builder and matches the criteria for Template2

Delegated administration allows administrators to delegate certain user management tasks to other users without granting them full administrative privileges. Delegated administrators can create and manage users only within specified roles or public groups. This option will meet the requirement of allowing each division to create and manage users only within their division. References: https://help.salesforce.com/articleView?id=delegated_administration_overview.htm &type=5

Data Loader is a tool that allows administrators to import, export, insert, update, delete, or upsert records in Salesforce using CSV files. Data Loader can handle large data sets and complex data transformations. Data Loader can be used to import records for a custom object from a spreadsheet. Lightning Object Creator is a tool that allows administrators to create custom objects in Salesforce from spreadsheets. Lightning Object Creator can automatically map spreadsheet columns to fields and create relationships between objects. Lightning Object Creator can be used to create a custom object from a spreadsheet and import records at the same time.

Deselecting disable session timeout warning popup enables a warning message to appear before a user’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

 A cross-object formula is a formula that references fields from related objects. The administrator can create a cross-object formula field on the Case object that displays the current status from the Account. This field can be used in validation rules and other processes. References: https://help.salesforce.com/s/articleView?id=sf.tips_on_building_formulas_cross_object_formulas.htm &type=5

To use outbound change sets, a user needs to have the Create and Upload Change Sets permission on their profile or permission set. This permission allows users to create change sets in a sandbox or Developer Edition organization and upload them to another organization. References: https://help.salesforce.com/s/articleView?id=sf.changesets_create_upload_perm.htm &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/docs/atlas.en-us.api_asynch.meta/api_asynch/asynch_api_intro.htm https://dataloader.io/

A custom summary formula is a formula that calculates values from summary fields in reports such as sum, average, min, max, etc. Custom summary formulas can use functions such as PREVGROUPVAL to compare values from different groups in reports. For example, to calculate the year-over-year change in dollar amount of opportunities, an administrator can create a custom summary formula that uses PREVGROUPVAL to compare the sum of amount from this year’s group with the sum of amount from last year’s group, and divide it by last year’s sum of amount. References: https://help.salesforce.com/s/articleView?id=sf.reports_builder_fields_summary_formulas.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.reports_formulas_prevgroupval.htm &type=5

Assignment rules and validation rules are two features that can satisfy these requirements:

Assignment rules are used to automatically assign leads or cases to users or queues based on certain criteria. In this case, an assignment rule can be used to assign leads to different planetary teams depending on which planet the lead is coming from.

Validation rules are used to validate the data entered by users and prevent records from being saved if they do not meet certain criteria. In this case, a validation rule can be used to ensure that every team has all of the information they need by making certain fields required or dependent on other fields.

The other two options are incorrect because:

Matching rules are used to identify duplicate records based on certain fields or fuzzy logic. They do not assign records or validate data.

Workflow rules are used to automate tasks or actions based on certain criteria. They do not assign records or validate data.

One possible reason why the before trigger fails is that the code could be trying to create duplicates in the archive when it is unable to. A before trigger is a type of trigger that executes before a record is saved and can be used to validate or modify record data. In this case, the before trigger is supposed to save the original version of a record to an external database before it is updated or deleted in Salesforce. However, if the code does not handle errors or exceptions properly, it could try to create duplicate records in the external database when it is not allowed or possible. This could cause the trigger to fail and prevent the record from being saved in Salesforce. References: https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers.htm https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers_context_variables.h tm

Permission sets are collections of settings and permissions that give users access to various tools and functions without changing their profile or requiring multiple profiles for users who perform different tasks across apps in your org. By assigning a permission set that has View All on Leads to the contractor, Cloud Kicks can grant them view access to all lead records without modifying their profile or creating a new one. References: https://help.salesforce.com/s/articleView?id=sf.perm_sets_overview.htm&type=5

Move some page components behind a tab, remove some of the fields displayed, and reduce the number of related lists displayed are three options available to the administrator to help with this issue. Moving some page components behind a tab can help reduce the loading time of a record page by hiding some components until they are needed by the user.

A custom summary formula is a formula that calculates values from summary fields in reports such as sums, averages, counts, etc. Custom summary formulas can use functions such as PREVGROUPVAL which returns the value of a field from the previous row at the same grouping level. By using a custom summary formula with the PREVGROUPVAL function, an administrator can create a report to calculate the year-over-year change in the dollar amount of a company’s opportunities by subtracting the amount from the previous year from the amount from the current year and dividing by the amount from the previous year. References: https://help.salesforce.com/s/articleView?id=sf.reports_builder_summary_formulas.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.reports_builder_functions.htm &type=5

Changing the field type to a Lookup Relationship will allow deleting the Relationship field without deleting the Runners records. A lookup relationship creates a loose association between two objects, where the child records do not depend on the parent records for their existence. A lookup relationship can be deleted without affecting the child records, unlike a master-detail relationship that enforces cascading deletes. References: https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm &type=5

A sandbox is a copy of a production org that can be used for development, testing, or training purposes. Sandboxes allow administrators to make changes and test them without affecting the live production org. A shared sandbox is a type of sandbox that can be used by multiple users or teams to collaborate on development or testing projects. By testing changes in a shared sandbox, the AW Computing administrator team can avoid conflicts and errors when deploying changes to production. References: https://help.salesforce.com/s/articleView?id=sf.data_sandbox.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.data_sandbox_environments.htm &type=5

To manage both B2C and B2B customers, CK should use Person Accounts and Contacts to Multiple Accounts features. Person Accounts allow CK to store information about individual consumers without requiring a separate account record. Contacts to Multiple Accounts allow CK to associate a contact with multiple accounts, such as their employer and their personal account. References: https://help.salesforce.com/s/articleView?id=sf.account_person_behavior.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.account_contact_rel_overview.htm &type=5

A junction object is a custom object that has two master-detail relationships with two other objects. A junction object allows administrators to create many-to-many relationships between objects, such as relating multiple accounts to multiple regions.

To create a junction object called Account Region to link the standard Account object with a custom object called Region, an administrator needs to do the following steps:

A) Make a master-detail relationship field on the junction object to the Region object.

A master-detail relationship field is a field that links a child record to a parent record. The child record inherits the sharing and security settings of the parent record. By making a master-detail relationship field on the junction object to the Region object, an administrator can link each Account Region record to one Region record and make Region the first master of the junction object. References: https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm &type=5

D) Configure a master-detail relationship field on the junction object to the Account object.

By configuring a master-detail relationship field on the junction object to the Account object, an administrator can link each Account Region record to one Account record and make Account the second master of the junction object. This allows administrators to relate multiple accounts to multiple regions through the junction object. References: https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm &type=5

To resolve the issue with the Process Builder, the administrator should do the following steps:

Review the Error Email for the Process Builder and rectify the issues. The error email contains information about what caused the error and how to fix it.

Deactivate the Process Builder in production. This will prevent further errors from occurring while the administrator fixes the Process Builder.

Fix the Process Builder in a sandbox and migrate the change to production. This will ensure that the Process Builder is tested and validated before deploying it to production. References: https://help.salesforce.com/s/articleView?id=sf.flow_troubleshoot_error_email.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_deploy.htm &type=5

The Security Health Check tool in Salesforce provides a detailed overview of an organization’s security posture, which includes information on how objects are shared externally. This tool is particularly useful for administrators who need to review and assess various security configurations, including the visibility of objects to external users.

Security Health Check:

This tool helps administrators quickly identify and manage risks related to security settings, including those pertaining to data sharing externally.

By using Health Check, administrators can access a report that shows the sharing settings of objects, allowing them to confirm if any objects have been shared as "Public" externally, which is crucial during an audit.

It provides insights into high-risk settings and areas where the configuration does not align with Salesforce security best practices, such as public access levels.

Use Case:

For an audit focused on understanding external access to objects, Security Health Check is the most appropriate choice because it gives a quick snapshot of how data sharing settings compare against Salesforce's recommended security baseline.

This can help AW Computing immediately identify which objects have broader public access than desired, addressing potential security vulnerabilities.

Incorrect options:

Setup Audit Trail: This tool tracks configuration changes within Salesforce over time, but it does not provide specific details about data sharing settings or external visibility of objects.

Session Security Settings: These settings control session policies and timeouts but are not related to object sharing or external visibility.

Object Manager: While Object Manager allows administrators to configure object-specific settings, it does not provide an overall view or quick audit of external sharing configurations.

Identity Verification History stores up to 20,000 records of users’ identity verification attempts for various features that require MFA, such as logging in from an unknown browser or device, resetting a password, or changing personal information. The data is stored for up to 6 months and then deleted automatically. Therefore, if a user has been inactive for more than 6 months or if there are more than 20,000 records in total, their data may be missing from Identity Verification History. References: https://help.salesforce.com/articleView?id=sf.identity_verification_history.htm &type=5

While the Schema Builder is a powerful tool in Salesforce for visually creating and managing custom objects and fields, there are certain configurations that must be done in Object Manager rather than Schema Builder. One of these configurations is enabling field history tracking.

Field History Tracking:

Field history tracking cannot be configured directly within Schema Builder. This setting must be enabled from within the Object Manager, where administrators can specify which fields on an object should have their changes tracked.

Enabling field history tracking involves navigating to the object in Object Manager, accessing the field history tracking settings, and selecting specific fields to track.

Limitations of Schema Builder:

Schema Builder is useful for quickly creating custom objects, relationships, and fields, but it does not support all configurations, such as enabling field history tracking, defining object-level permissions, or setting advanced object configurations.

For these types of configurations, administrators need to return to Object Manager where these settings are available.

Incorrect options:

Add custom fields to the page layout: This task is typically done within Object Manager, but Schema Builder does allow customization of page layouts to a certain extent through drag-and-drop.

Make available for Customer Portal: Schema Builder does not control portal availability; however, this is managed through Object Manager settings related to record visibility for portal users.

Allow Reports and Activities: This setting can be configured in Schema Builder when initially creating an object, but further refinements and permission settings must often be done in Object Manager.

In conclusion, enabling field history tracking requires access to the Object Manager, as it cannot be configured through Schema Builder.

Product schedules are features that allow 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 created automatically 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 administrators cannot 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 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.

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

Query and export the Account History object using Data Loader is how the administrator can acquire the field history data for analysis. Data Loader is a tool that allows administrators to import, export, insert, update, delete, or upsert records in Salesforce using CSV files. Data Loader can handle large data sets and complex data transformations. Data Loader can be used to query and export the Account History object, which stores the field history data for accounts, using SOQL statements. 

Move some page components behind a tab, remove some of the fields displayed, and reduce the number of related lists displayed are three options available to the administrator to help with this issue. Moving some page components behind a tab can help reduce the loading time of a record page by hiding some components until they are needed by the user. Removing some of the fields displayed can help reduce the loading time of a record page by minimizing the number of queries and calculations that need to be performed when rendering the page. Reducing the number of related lists displayed can help reduce the loading time of a record page by limiting the amount of data that needs to be retrieved and displayed on the page

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.

Creating a new quote record for each of the different product configurations and syncing the most likely to be purchased back to the opportunity will ensure that their quotes and opportunities reflect their sales. This way, sales reps can show customers different options and prices, and keep track of which one is most likely to close. Syncing a quote with an opportunity will update the opportunity amount, stage, and expected revenue fields based on the quote information. References: https://help.salesforce.com/s/articleView?id=sf.quotes_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.quotes_sync ing.htm&type=5

Lightning Object Creator is a tool that allows you to create custom objects and fields from a spreadsheet in a few clicks. Lightning Object Creator analyzes the spreadsheet data and suggests the best way to map it to Salesforce fields and relationships. You can also import the data from the spreadsheet into the new custom object and view it in a list view or a related list. In this case, you can use Lightning Object Creator to create a custom Project object from the spreadsheet that tracks installations and also import the data into the new object. References: https://help.salesforce.com/s/articleView?id=sf.object_creator_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.object_creator_create_obje ct.htm&type=5

An administrator should consider using Person Accounts when they have a B2C business model and the consumer is the intended recipient of sales and marketing attention. Person Accounts allow administrators to store information about individual consumers without requiring a separate account record for each contact. References: https://help.salesforce.com/s/articleView?id=sf.account_person_behavior.htm &type=5

Two options that the administrator should use to meet these criteria are:

Share with roles and subordinates of the finance director role. This option allows you to grant access to records based on the role hierarchy of your org. You can share records with users who are in a specific role or in roles below that role in the hierarchy. In this case, you can share records with roles and subordinates of the finance director role, which includes all the members of the finance team.

Create a criteria-based sharing rule where the won field = true. This option allows you to grant access to records based on certain field values or formulas. You can create a criteria-based sharing rule on opportunities that grants access to records where the won field is true, which means that the opportunity stage is closed won.

The other two options are incorrect because:

Make an owner-based sharing rule where the won field = true is not an option because owner-based sharing rules do not allow you to specify field values or formulas as criteria. Owner-based sharing rules only allow you to share records based on who owns them or what role or group they belong to.

Select all opportunities owned by the sales manager role is not an option because it does not meet the criteria of sharing all closed won opportunities. It only shares opportunities that are owned by users who are in the sales manager role, regardless of their stage.

A record type allows administrators to offer different business processes, picklist values, and page layouts to different users based on their profiles. By creating a record type for the type of property (single-family home or condo), DreamHouse Realty can assign different page layouts to each record type that display only relevant fields for each property type. The record type can also determine which sales process and path are available for each opportunity. References: https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.htm &type=5

Read permission is required on at least one master record to be able to see the solar panel records. Since Item is a junction object between Doc and Solar Panel, users need to have access to either Doc or Solar Panel to see Item records. If users have access to both Doc and Solar Panel, they can see all Item records related to either object. References: https://help.salesforce.com/s/articleView?id=sf.relationships_manyto many.htm&type=5

Check the Reevaluate Workflow Rules After Field Change box on the Approval Process Field Update Action is what the administrator should do to troubleshoot the issue. This option allows the approval process field update to trigger any workflow rules or processes that are based on the updated field value. If this option is not checked, the approval process field update will not trigger any workflow rules or processes, and the Process Builder will not fire

Person Account cannot be disabled is something that the administrator should consider before enabling Person Accounts. Person Accounts are a special type of accounts that allow storing information about individual people who are not associated with an organization or business account. Once Person Accounts are enabled, they cannot be disabled or removed from the org without contacting Salesforce support

A change set is a tool that allows you to 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=5 https://help.salesforce.com/s/articleView?id=sf.changesets_components_field.htm &type=5

Login Forensics is a Salesforce feature that allows you to monitor and analyze login behavior and trends in your org. It can help you identify and prevent brute-force password attacks by showing you the number of login attempts, successes, and failures per user, location, and device. You can also set up alerts to notify you when a user exceeds a certain number of login failures or when a login originates from an unusual location or device. References: https://help.salesforce.com/s/articleView?id=sf.security_loginforensics.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.security_loginforensics_alerts.htm &type=5

A price book is a list of products and their prices for a specific segment of customers or market. By creating a separate price book for the special bundle deal on monitors and keyboards, AW Computing can offer different prices for these products without affecting their standard prices or requiring VP approval. The price book can also specify which products are included in the bundle and which are not. References: https://help.salesforce.com/s/articleView?id=sf.products_pricebooks_def.htm &type=5

Email logs provide information about email delivery, such as the sender, recipient, date and time, delivery status, and any error messages. The administrator can use email logs to troubleshoot why users are missing expected email alerts and identify which emails are hitting the daily limit. References: https://help.salesforce.com/articleView?id=email_logs.htm &type=5

A dashboard is a visual display of key metrics and trends for records in your org. Dashboards allow users to quickly monitor performance and identify trends or issues at a glance. To make it easier for users to see a dashboard they use frequently, administrators can add it to their home page using Lightning App Builder. This way, users can see their dashboard every time they log in or go to their home tab without having to navigate elsewhere. References: https://help.salesforce.com/s/articleView?id=sf.dashboards_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.dashboards_add_to_home_page.htm&type=5

Modify All is the level of access that the sales user will have on the Account object after being assigned to a muting permission set that mutes Delete access on Account. Muting permissions are a way to reduce or remove access to objects or fields for users who are assigned to permission set groups. Muting permissions can only mute object-level permissions, such as Create, Read, Edit, Delete, View All, or Modify All, but not field-level permissions or other permissions. Muting permissions can only reduce or remove access that is granted by other permission sets or permission set groups within the same permission set group, but not by profiles or other sources of access. Therefore, in this case, the muting permission set will only mute the Delete access on Account that is granted by the permission set group, but not the Modify All access that is also granted by the permission set group.

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

Implement Service Console is what the administrator should recommend to support staff at Cloud Kicks for a better agent experience. Service Console is a Salesforce app that provides a unified interface for agents to manage multiple customer interactions and records at once. Service Console can help agents work more efficiently and productively by providing features such as tabs, subtabs, list views, related lists, highlights panel, interaction log, macros, keyboard shortcuts, and more

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

Configuring one app per department and activating record pages for each app will ensure that users view records in a way that makes sense for each department. An app is a collection of items that work together to serve a particular function. An app can have different record pages for different objects and profiles. By activating record pages for each app, the administrator can customize what users see based on their app context. References: https://help.salesforce.com/s/articleView?id=sf.app_manager_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.app_builder_customize_lex_pages_assign.htm &type=5

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

Use an Insert operation to load data because the data is not already in Salesforce and does not need to be updated or deleted3. Map an External ID data value to the object because External IDs are used to create relationships between records that are being imported and records that already exist in Salesforce4. References: 3 https://help.salesforce.com/s/articleView?id=sf.data_loader_insert.htm &type=5 4 https://help.salesforce.com/s/articleView?id=sf.data_loader_relationships.htm &type=5

Salesforce Authenticator is an app that allows users to verify their identity when logging in to Salesforce using two-factor authentication (2FA). 2FA adds an extra layer of security by requiring users to enter a verification code or approve a notification on their mobile device after entering their username and password.

To look at how many users have successfully used Salesforce Authenticator since it was rolled out, an administrator can use two ways:

A) Run a session setting report, specifying login methods by user.

A session setting report is a report that shows information about users’ login sessions, such as login time, location, IP address, browser, platform, etc. A session setting report can also show the login methods used by users, such as password, verification code, or notification. By running a session setting report, specifying login methods by user, an administrator can see how many users have used Salesforce Authenticator to log in to Salesforce. References: https://help.salesforce.com/s/articleView?id=sf.reports_session.htm &type=5

C) Create a new view in Identity Verification History, specifying Method.

Identity Verification History is a page that shows the history of identity verification attempts for each user in the org. Identity verification history includes information such as date, time, status, method, and IP address of each attempt. By creating a new view in Identity Verification History, specifying Method as a filter criterion, an administrator can see how many users have used Salesforce Authenticator to verify their identity when logging in to Salesforce. References: https://help.salesforce.com/s/articleView?id=sf.identity_verification_history.htm &type=5

To grant access for the sales rep who broke their phone and needs multi-factor authentication using Salesforce Authenticator app, the administrator can generate a temporary identity verification code for them. This code allows users who don’t have their verification method available to log in securely without compromising their account security. References: https://help.salesforce.com/s/articleView?id=sf.identity_verification_codes.htm &type=5

Delegated Administration allows administrators to delegate certain user management tasks to non-administrators. For example, a delegated administrator can assign permissions sets to users in specified roles or public groups without having full access to modify permission sets. References: https://help.salesforce.com/s/articleView?id=sf.admin_usermgt_delegated.htm &type=5

Flows deployed with change sets are inactive by default and need to be manually activated in the destination org before they can run. Deploying or redeploying a flow with change sets creates a new version of the flow in the destination org, which preserves the previous versions and allows for rollback if needed. All flow dependencies, such as custom fields, objects, or variables, are automatically added to the change set when a flow is added

Two combined automation tools that the administrator can use to create the task record and assign based on date criteria are:

Create a formula field to capture the MAX date. A formula field is a custom field that calculates a value based on other fields or expressions. In this case, a formula field can be used to capture the maximum value between Estimated Shipping Date and Client Need By Date fields and store it as a date value.

Make a Process Builder to create the task. A Process Builder is an automation tool that allows you to create processes that perform actions based on certain criteria. In this case, a Process Builder can be used to create a task record when a certain condition is met and assign its due date based on the formula field value.

The other two options are incorrect because:

An approval process is an automation tool that allows you to route records for approval based on certain criteria and approval steps. It does not create or assign tasks based on date criteria.

A workflow rule is an automation tool that allows you to perform actions based on certain criteria and evaluation time. It does not create or assign tasks based on date criteria.