Salesforce Plat-Admn-301 - Salesforce Certified Platform Administrator II

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

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

Go into the user record and freeze the user is the action that should be taken to ensure the user’s access is immediately revoked. Freezing a user is a way to temporarily prevent a user from logging in to Salesforce without deactivating their user record or changing their profile. Freezing a user can be useful when an employee has resigned or left the company and their access needs to be removed immediately. Freezing a user does not affect the ownership of records or email alerts that are assigned to them

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.

 Record-triggered flow is a feature that allows administrators to automate actions that occur when a record is created or updated. Record-triggered flow can perform actions such as updating fields, creating records, sending emails, or invoking Apex code. Record-triggered flow can be used to update the account checkbox field ‘Opportunity Created’ when at least one related opportunity has been created

Territory management is a feature that allows you to grant access to accounts and opportunities based on criteria such as geography, industry, product line, or customer size. A territory is a grouping of accounts and users that represents a market segment or business unit. In this case, the administrator should utilize territory management to add the operations team to the East territory, which contains all the accounts and opportunities in the East region. This way, the operations team members can access all the records in their territory regardless of who owns them or what the organization-wide default is. References: https://help.salesforce.com/s/articleView?id=sf.territories_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.territories_define.htm &type=5

To make inventory data from a legacy application available in Salesforce, the administrator can create an external object that maps to the inventory application. An external object is similar to a custom object, except that it maps to data that’s stored outside your Salesforce organization. External objects enable users to view and report on external data in Salesforce. References: https://help.salesforce.com/s/articleView?id=sf.external_object_overview.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

Escalation rules are rules that automatically escalate cases if they have not been resolved within a certain time frame or meet certain criteria such as priority or status. Escalation rules can perform actions such as changing ownership of cases, sending email notifications, or creating tasks for users or queues. By using escalation rules, AW Computing can ensure that cases are properly prioritized and handled within their SLA time limit.

Assignment rules are rules that automatically assign cases to users or queues based on criteria such as case origin, type, or product. Assignment rules can also send email notifications to users or customers when a case is assigned. By using assignment rules, AW Computing can ensure that cases are routed to the right agents or teams based on their skills and availability. References: https://help.salesforce.com/s/articleView?id=sf.case_escalation_rules_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_caseassign.htm &type=5

Building a process that updates the record type field to B2C Customer after conversion will correct this issue. The conversion layout for person accounts does not allow selecting different record types for accounts and contacts. The default record type for person accounts is determined by the organization-wide default settings. However, a process can be triggered after conversion to update the record type field based on the lead record type or other criteria. References: https://help.salesforce.com/s/articleView?id=sf.convert_leads_considerations.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.convert_leads_mapping.htm &type=5