Practice Free Plat-Admn-301 Exam Online Questions
Question #21
As part of their yearly audit, the compliance team at Cloud Kicks would like to track when a user’s profile has been changed and who changed the data.
What should the administrator review to meet this requirement?
- A . Field History Tracking
- B . Setup Audit Trail
- C . Historical Trending
- D . Analytic Snapshot
Correct Answer: B
B
Explanation:
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. One of the changes that the Setup Audit Trail tracks is when a user’s profile is changed and who changed it. This means that you can use the Setup Audit Trail to see when a user’s profile has been changed and who changed the data.
Reference: https://help.salesforce.com/s/articleView?id=sf.monitorsetup.htm&type=5
B
Explanation:
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. One of the changes that the Setup Audit Trail tracks is when a user’s profile is changed and who changed it. This means that you can use the Setup Audit Trail to see when a user’s profile has been changed and who changed the data.
Reference: https://help.salesforce.com/s/articleView?id=sf.monitorsetup.htm&type=5
Question #22
Universal Containers has found duplicate contacts in Salesforce. The sales team administrator prevent duplicate records from being created.
Which two ways should the administrator customize duplicate management? Choose 2 answers
- A . Modify the Global Picklist Value Sets.
- B . Configure custom duplicate rules.
- C . Create custom matching rules.
- D . Set up mobile duplicate alerts.
Correct Answer: B,C
B,C
Explanation:
Duplicate management is a feature that allows administrators to prevent or allow duplicate records for standard or custom objects. Duplicate management consists of two components: duplicate rules and matching rules.
B) Configure custom duplicate rules.
Duplicate rules are rules that determine what actions to take when users try to save duplicate records. Duplicate rules can block users from saving duplicates, alert users of duplicates and let them save anyway, or report on duplicates without affecting the save operation. Duplicate rules can also specify which fields to use for matching and which security settings to enforce. By configuring custom duplicate rules, the sales team administrator can prevent duplicate records from being created for contacts or other objects.
Reference: https://help.salesforce.com/s/articleView?id=sf.data_prevent_duplicates.htm&type=5
C) Create custom matching rules.
Matching rules are rules that determine how duplicate records are identified by comparing fields and applying fuzzy matching algorithms. Matching rules can be standard or custom. Standard matching rules are predefined by Salesforce and apply to common objects such as contacts, accounts, or leads.
Custom matching rules are created by administrators and apply to any standard or custom object. By creating custom matching rules, the sales team administrator can define how duplicate records are detected for contacts or other objects.
Reference: https://help.salesforce.com/s/articleView?id=sf.data_matching_rules.htm&type=5
B,C
Explanation:
Duplicate management is a feature that allows administrators to prevent or allow duplicate records for standard or custom objects. Duplicate management consists of two components: duplicate rules and matching rules.
B) Configure custom duplicate rules.
Duplicate rules are rules that determine what actions to take when users try to save duplicate records. Duplicate rules can block users from saving duplicates, alert users of duplicates and let them save anyway, or report on duplicates without affecting the save operation. Duplicate rules can also specify which fields to use for matching and which security settings to enforce. By configuring custom duplicate rules, the sales team administrator can prevent duplicate records from being created for contacts or other objects.
Reference: https://help.salesforce.com/s/articleView?id=sf.data_prevent_duplicates.htm&type=5
C) Create custom matching rules.
Matching rules are rules that determine how duplicate records are identified by comparing fields and applying fuzzy matching algorithms. Matching rules can be standard or custom. Standard matching rules are predefined by Salesforce and apply to common objects such as contacts, accounts, or leads.
Custom matching rules are created by administrators and apply to any standard or custom object. By creating custom matching rules, the sales team administrator can define how duplicate records are detected for contacts or other objects.
Reference: https://help.salesforce.com/s/articleView?id=sf.data_matching_rules.htm&type=5
Question #23
How should an administrator accomplish this?
- A . Make record-triggered flows whenever Equipment records are created, modified or deleted.
- B . Write record-triggered ftews whenever Room records are related, modified, or deleted.
- C . Configure a ral-up summary field on Equipment.
- D . Create a roll-up summary field on Room.
Correct Answer: A
A
Explanation:
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 that counts the number of Equipment records related to it.
Reference:
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
A
Explanation:
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 that counts the number of Equipment records related to it.
Reference:
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
Question #24
DreamHouse Realty wants better insights into potential revenue in the next quarter and is considering using Collaborative Forecasts.
What should the administrator consider when setting up Collaborative Forecasts?
- A . Opportunity Split data cannot be viewed in a forecast.
- B . A forecast can be either revenue-based or quantity-based.
- C . A single org can have up to six different types of forecasts.
- D . The default forecast categories cannot be customized.
Correct Answer: B
B
Explanation:
A forecast is a projection of how much revenue or quantity you can generate from your sales pipeline for a given period of time. A forecast can be either revenue-based or quantity-based, depending on what you want to measure and track. A revenue-based forecast shows the amount of money expected from closed sales, while a quantity-based forecast shows the number of units expected from closed sales. You can choose the forecast type that best suits your business needs and goals when you set up Collaborative Forecasts in Salesforce.
Reference:
https://help.salesforce.com/s/articleView?id=sf.forecasts3_overview.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.forecasts3_forecast_types.htm&type=5
B
Explanation:
A forecast is a projection of how much revenue or quantity you can generate from your sales pipeline for a given period of time. A forecast can be either revenue-based or quantity-based, depending on what you want to measure and track. A revenue-based forecast shows the amount of money expected from closed sales, while a quantity-based forecast shows the number of units expected from closed sales. You can choose the forecast type that best suits your business needs and goals when you set up Collaborative Forecasts in Salesforce.
Reference:
https://help.salesforce.com/s/articleView?id=sf.forecasts3_overview.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.forecasts3_forecast_types.htm&type=5
Question #25
Cloud Kicks uses a Review junction object to track product reviews by account. the Review object has a Master-Detail relationship to Account and a Master-Detail relationship to a customer Product object. A user accidentally deleted the Account, Product, and related Review records.
How should the deleted Review records be restored?
- A . Restore both the Account and Product master records from the Recycle Bin.
- B . Restore the Review junction object record from the Recycle Bin.
- C . Restore either the Account or Product master records from the Recycle Bin.
- D . The Review object records are permanently deleted without the ability to restore.
Correct Answer: A
A
Explanation:
To restore the deleted Review records, you need to restore both the Account and Product master records from the Recycle Bin. A master-detail relationship is a type of relationship that links two objects together and enforces a parent-child relationship between them. A master-detail relationship affects the security and deletion of the child records. If you delete a master record, all of its detail and subdetail records are deleted as well and moved to the Recycle Bin. To restore a detail or subdetail record, you must first restore its parent record.
Reference:
https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.recyclebin_overview.htm&type=5
A
Explanation:
To restore the deleted Review records, you need to restore both the Account and Product master records from the Recycle Bin. A master-detail relationship is a type of relationship that links two objects together and enforces a parent-child relationship between them. A master-detail relationship affects the security and deletion of the child records. If you delete a master record, all of its detail and subdetail records are deleted as well and moved to the Recycle Bin. To restore a detail or subdetail record, you must first restore its parent record.
Reference:
https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.recyclebin_overview.htm&type=5
Question #26
The accounting team at Universal Containers is looking to roll out two new custom objects: a parent Invoice object and a child Payment object. Whenever a Payment record is created, the Invoice object should be updated to reflect the current outstanding value of the Invoice.
What should the administrator do to build this functionality?
- A . Create a lookup-relationship on the Payment with a Roll-up Summary field on the Invoice.
- B . Create a lookup-relationship on the Payment and a workflow cross object field update.
- C . Create a master-detail relationship on the Payment and a workflow cross object field update.
- D . Create a master-detail relationship on the Payment with a Roll-up Summary field on the Invoice.
Correct Answer: D
D
Explanation:
Creating a master-detail relationship on the Payment with a Roll-up Summary field on the Invoice will build this functionality. A master-detail relationship creates a parent-child relationship between two objects, where the child records inherit the sharing and security settings of their parent. A Roll-up Summary field calculates values from related child records, such as count, sum, min, or max. In this case, the Roll-up Summary field on the Invoice can calculate the sum of all Payments related to it and subtract it from the Invoice amount to get the current outstanding value.
Reference:
https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up_summary_fields.htm&type=5
D
Explanation:
Creating a master-detail relationship on the Payment with a Roll-up Summary field on the Invoice will build this functionality. A master-detail relationship creates a parent-child relationship between two objects, where the child records inherit the sharing and security settings of their parent. A Roll-up Summary field calculates values from related child records, such as count, sum, min, or max. In this case, the Roll-up Summary field on the Invoice can calculate the sum of all Payments related to it and subtract it from the Invoice amount to get the current outstanding value.
Reference:
https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up_summary_fields.htm&type=5
Question #27
An administrator needs to Import a large amount of historical data (more than 100,000 records) from another system.
how should the administrator import the data?
- A . SOAP based API with Developer console
- B . Data Loader with Bulk API Enabled
- C . An AppExchange package
- D . Import Wizard with Add Only
Correct Answer: B
B
Explanation:
Data Loader is a tool that allows administrators to import or export large amounts of data (more than 50,000 records) from or to Salesforce using CSV files. Data Loader can be used for inserting, updating, deleting, upserting, exporting, or extracting data. Bulk API is an API that allows administrators to process large batches of records asynchronously in the background. Bulk API can handle millions of records with high performance and minimal system resources. By using Data Loader with Bulk API enabled, an administrator can import a large amount of historical data (more than 100,000 records) from another system efficiently and securely.
Reference:
https://help.salesforce.com/s/articleView?id=sf.data_loader.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.loader_api.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.bulk_api_intro.htm&type=5
B
Explanation:
Data Loader is a tool that allows administrators to import or export large amounts of data (more than 50,000 records) from or to Salesforce using CSV files. Data Loader can be used for inserting, updating, deleting, upserting, exporting, or extracting data. Bulk API is an API that allows administrators to process large batches of records asynchronously in the background. Bulk API can handle millions of records with high performance and minimal system resources. By using Data Loader with Bulk API enabled, an administrator can import a large amount of historical data (more than 100,000 records) from another system efficiently and securely.
Reference:
https://help.salesforce.com/s/articleView?id=sf.data_loader.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.loader_api.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.bulk_api_intro.htm&type=5
Question #28
Cloud Kicks has organization-wide snaring defaults on the opportunity set to prvete. However, members of the finance team need to see closed won opportunities. The Drama team members all have roles under the finance director, while the sales team members have roles under the sales marager.
Which two options should the administrator use to meet these criteria? Choose 2 answers
- A . Share with roles and subordinates of the finance director role.
- B . Make an owner-based sharing rule where the won field – true.
- C . Create a criteria-based sharing rule where the won field = true.
- D . Select all opportunities owned by the sales manager role.
Correct Answer: A,C
A,C
Explanation:
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.
Reference:
https://help.salesforce.com/s/articleView?id=sf.admin_sharing.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.sharing_rules.htm&type=5
A,C
Explanation:
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.
Reference:
https://help.salesforce.com/s/articleView?id=sf.admin_sharing.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.sharing_rules.htm&type=5
Question #29
The administrator at Cloud Kicks is troubleshooting an issue one user is having with a flow. They have decided to add a debug log to that user.
What debug log category should be used?
- A . Workflow
- B . Callout
- C . System
- D . Database
Correct Answer: A
A
Explanation:
Workflow is the debug log category that should be used to troubleshoot an issue with a flow. Workflow is a debug log category that captures information about workflow rules, flows, processes, approval processes, and entitlement processes. Workflow can help identify errors or issues related to these automation tools by showing details such as evaluation criteria, actions executed, variables assigned, and outcomes reached.
A
Explanation:
Workflow is the debug log category that should be used to troubleshoot an issue with a flow. Workflow is a debug log category that captures information about workflow rules, flows, processes, approval processes, and entitlement processes. Workflow can help identify errors or issues related to these automation tools by showing details such as evaluation criteria, actions executed, variables assigned, and outcomes reached.
Question #30
The administrator at Cloud Kicks noticed that a before trigger, which handles saving the original version of a record to an external database, fails. However, a flow configured for fast field updates runs successfully.
How should the administrator advise the developer?
- A . Record-triggered flows that are configured to run before save execute prior to all before triggers.
- B . A validation rule could be preventing records from ever meeting the conitions in the trigger.
- C . The trigger is writing the data to the wrong place in the external data archive.
- D . The code could be trying to create duplicates in the archieve when it is unable to.
Correct Answer: D
D
Explanation:
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.
Reference:
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.htm
D
Explanation:
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.
Reference:
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.htm