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

Three recommendations that the administrator can make to reduce the file size of full data exports are:

• Reduce the amount of objects per export. By selecting only the objects that are necessary for the backup and excluding the ones that are not, you can reduce thenumber of files and records that are exported and decrease the file size.
• Deselect ‘Include images, documents, and attachments’ in the export. By unchecking this option, you can exclude the files that are stored in Salesforce as images, documents, or attachments from the export. These files can take up a lot of space and increase the file size significantly.
• Keep deleted record counts to a minimum. By emptying the recycle bin regularly or using hard delete options, you can reduce the number of deleted records that are included in the export. Deleted records are still counted as part of the export limit and can increase the file size.

The other two options are incorrect because:

• Requesting a backup file every 5 days does not reduce the file size of each export. It only increases the frequency of exports and may cause more storage issues.
• Unselecting the recycle bin in the object export option does not reduce the file size of full data exports. It only applies to individual object exports and not to weekly ormonthly exports.

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

An authentication app is a mobile app that generates verification codes for logging in to Salesforce or other services that require multi-factor authentication (MFA). A username and password are also required for logging in to Salesforce, but they are not sufficient for MFA. References:https://help.salesforce.com/s/articleView?id=sf.identity_auth_apps.htm &type=5

Dynamic actions are actions that appear on Lightning record pages based on criteria such as field values or user profiles. Dynamic actions allow administrators to customize which actions are available for users on different record types or page layouts without creating multiple page layouts for each scenario. By using dynamic actions and conditional visibility for accounts at AW Computing, administrators can show only relevant actions for customer service and sales users based on their situation. References:https://help.salesforce.com/s/articleView?id=sf.dynamic_actions_overview.htm &type=5

Flows are tools that automate business processes by collecting data and performing actions in yourorg 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 andupdates 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=5https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_decision.htm &type=5

Password Policies on the System Administrator profile is a feature that allows administrators to set different password requirements for users with different profiles. Password Policies can specify the minimum length, complexity, expiration period, history enforcement, lockout interval, and warning message for passwords. Password Policies can be used to enforce stricter password requirements for system administrators than for other users

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

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

Another quote is already synced with the opportunity will prevent a user from syncing a quote with an opportunity. Only one quote can be synced with an opportunity at a time. If a user tries to sync another quote, they will get an error message saying that the opportunity already has a synced quote. References:https://help.salesforce.com/s/articleView?id=sf.quotes_syncing.htm &type=5

A roll-up summary field is a type of field that calculates values from related records and displays them on the parent record. A roll-up summary field can be used to count, sum, min, or max values from child records. You can create a roll-up summary field on an object that has a master-detail relationship with another object. In this case, you can create a roll-up summary field on Room thatcounts the number of Equipment records related to it. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up_summary_fields.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fields_defining_field_types.htm &type=5

Three reasons CK should utilize Data Categories when creating articles in Knowledge are:

• Data Categories help organize the Knowledgebase content displayed. Data categories are logical groupings of articles that reflect your business needs and processes. You can create a data category group and assign it to one or more article types, and then create data categories and subcategories within that group. Data categories help you organize your articles by topic or criteria and make them easier to find and browse by your users or customers.
• Data Categories provide a way to secure access to the Knowledge base content. Data category visibilityis a setting that determines which data categories users can access based on their profiles or permission sets. You can use data category visibility to control access to your articles based on their data categories and ensure that only relevant and appropriate content is displayed to different users or customers.
• A Knowledge article can be tagged to more than one Data Category. A Knowledge article is a document that provides information or answers to common questions or issues. A Knowledge article can be tagged to one or more data categories within each data category group that is assigned to its article type. This allows you to classify your articles by multiple criteria and make them searchable and accessible by different users or customers.