Free Practice Questions for Salesforce Salesforce-Certified-Administrator Exam

To protect data with backups by using Data Export Service, two considerations that the administrator should remember when scheduling export are:

Data Backups are limited to weekly or monthly intervals depending on edition and license type

Metadata backups must be run via a separate process such as Metadata API or change sets because Data Export Service only exports data (records) Metadata backups are not limited by sandboxrefresh intervals. Data Export Service should be run from production orgs unless testing purposes require otherwise. References: https://help.salesforce.com/s/articleView?id=sf.data_export.htm &type=5

To assign agent capacity and skill set, the administrator should enable Omni-Channel, which is afeature that allows agents to work on multiple cases or chats at once based on their availability and expertise. Omni-Channel can route work items to agents based on their predefined capacity and skills, ensuring that they are working on the right tasks atthe right time. Knowledge Management, Escalation Rules, and Territory Management are not related to agent capacity and skill set. References:https://help.sal esforce.com/s/articleView?id=sf.omnichannel_overview.htm&type=5

Flow Solutions are pre-built flows or templates that can be installed from AppExchange and customized to meet specificbusiness needs. For example, Flow Solutions can provide common use cases such as lead generation, document generation, payment processing, and more. In this case, the administrator can use a Flow Solution that provides a mortgage calculator and generates leads for loans. Flow Solutions are easy to install and configure, and can help save time and budget for projects. References:https://help.salesforce.com/s/articleVi ew?id=sf.flow_solutions.htm&type=5

Standard objects are objects that are included with Salesforce by default, such as Account, Contact, Lead, Opportunity, etc. They have predefined fields and functionality that support common business processes. Custom objects are objects that you create to store information that is specific to your organization or industry. You can create new standard objects using the Object Manager in Setup. References:https://trailhead .salesforce.com/en/content/learn/modules/data_modeling/standard_and_custom_objects

Probability is a standard percentage field on the Opportunity object that indicates how likely an opportunity willclose successfully. It is automatically calculated based on the opportunity stage unless you make it editable on page layouts. To allow sales reps to change the probability field value of their opportunities, you need to make the field editable on page layouts. References: https://help.salesforce.com/s/articleView?id=sf.opportunity_fields.htm &type=5https://help.salesforce.com/s/articleView?id=sf.customize_layou tedit.htm&type=5

A junction object is a type of custom object that allows administrators to create many-to-many relationships between two other objects. A many-to-many relationship means that each record of one object can be related to multiple records of another object, and vice versa. For example, a junction object can represent thata contact can be interested in multiple pieces of merchandise, and a piece of merchandise can be of interest to multiple contacts. A junction object has two master-detail relationships with the two objects it connects. References:https://help.salesforce.com/s/articleView?id=sf.relationships_manytomany.htm &type=5

Grant access using Hierarchies is a setting that can be used to configure the custom object to meet this requirement. Grant access using Hierarchies determines whether access to records of the custom object is granted through the role hierarchy. If this setting is unchecked, managers are unable to see the feedback records from their staff, unless they are given access by other means, such as sharing rules or manual sharing. References:https://help.salesforce.com/s/articleView?id=sf.security_sharing_owd_custom_objec ts.htm&type=5

A formula field is a type of field that calculates avalue based on an expression or formula that references other fields or constants. For example, a formula field can display today’s date by using the TODAY() function. In this case, the administrator can create a formula field on the account object that updates the audited date field with today’s date when the status of the account is changed to ‘Audited’. References:https://help.salesforce.com/s/articleView? id=sf.fields_about_formulas.htm&type=5

Role hierarchy and sharing rules are two features that should be used toopen up access to Opportunity records for sales users working on collaborative deals. Role hierarchy can be used to grant access to records owned by or shared with users who are below them in the hierarchy. Sharing rules can be used to extend sharing access to users in public groups, roles, or territories based on certain criteria, such as record owner or field value. References: https://help.salesforce.com/s/articleView?id=sf.admin_sharing.htm &type=5https://help.salesforce.com/s/articleView?id=sf.security_sharing_rules.htm &type=5