Practice Free Plat-Admn-301 Exam Online Questions
Question #11
Which two tools should an administrator use to required data to be entered in a field and improve data quality on a record in Salesrorce? Choose 2 answers
- A . validation Rules
- B . Dashboards
- C . Workflow Rules
- D . Page Layouts
Correct Answer: A,D
A,D
Explanation:
Validation rules and page layouts are two tools that can be used to require data to be entered in a field and improve data quality on a record in Salesforce. Validation rules are a way to enforce data quality and integrity by checking the values of fields before a record is saved and displaying an error message if the values do not meet the specified criteria. Page layouts are a way to control the layout and organization of fields, buttons, related lists, and other components on a record page. Page layouts can also make fields required so that users must enter a value before saving a record.
A,D
Explanation:
Validation rules and page layouts are two tools that can be used to require data to be entered in a field and improve data quality on a record in Salesforce. Validation rules are a way to enforce data quality and integrity by checking the values of fields before a record is saved and displaying an error message if the values do not meet the specified criteria. Page layouts are a way to control the layout and organization of fields, buttons, related lists, and other components on a record page. Page layouts can also make fields required so that users must enter a value before saving a record.
Question #12
Universal Containers’ support team wants to use Salesforce Knowledge to allow customers and the support team to have access to the product documentation. There are many different types of documentation with usage across the globe.
What feature should the administrator configure?
- A . Enable the Case Feed.
- B . Create article types.
- C . Define data categories and visibility.
- D . Setup record types and page layouts.
Correct Answer: C
C
Explanation:
Data categories and visibility are features that allow you to organize and control access to your Salesforce Knowledge articles based on different topics or criteria. 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 category visibility is a setting that determines which data categories users can access based on their profiles or permission sets. You can use data categories and visibility to provide relevant and appropriate product documentation to your customers and support team.
Reference:
https://help.salesforce.com/s/articleView?id=sf.knowledge_categories.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.knowledge_category_visibility.htm&type=5
C
Explanation:
Data categories and visibility are features that allow you to organize and control access to your Salesforce Knowledge articles based on different topics or criteria. 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 category visibility is a setting that determines which data categories users can access based on their profiles or permission sets. You can use data categories and visibility to provide relevant and appropriate product documentation to your customers and support team.
Reference:
https://help.salesforce.com/s/articleView?id=sf.knowledge_categories.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.knowledge_category_visibility.htm&type=5
Question #13
After setting up field history tracking on the Account object, the administrator for AW Computing wants to retrieve the field history data for analysis.
how should the administrator acquire this data?
- A . Create a report of Accounts and export it to Excel.
- B . Query and export the Account History object using Data Loader.
- C . Use the Data export service in setup.
- D . Create a list view of Account History and print using the Printable View action.
Correct Answer: B
B
Explanation:
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.
B
Explanation:
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.
Question #14
An administrator created a new custom object. When trying to upload new records to the custom object using.
Date Loader, they are unable to see the new custom object in the list of available objects.
What should the administrator do to resolve the issue?
- A . Assign a permission set to give them access to the new object.
- B . Check the Field-Level Security of the new custom object’s Name field.
- C . Ensure Allow Sharing is checked on the custom object.
- D . Confirm the object us marked as deployed and not in development.
Correct Answer: D
D
Explanation:
Confirm the object is marked as deployed and not in development is what the administrator should do to resolve the issue. A custom object can be marked as deployed or in development depending on its readiness for use. A custom object that is marked as in development is not visible to users or available for data import or export. A custom object that is marked as deployed is visible to users and available for data import or export. Therefore, the administrator should make sure that the new custom object is marked as deployed before using Data Loader to upload records to it
D
Explanation:
Confirm the object is marked as deployed and not in development is what the administrator should do to resolve the issue. A custom object can be marked as deployed or in development depending on its readiness for use. A custom object that is marked as in development is not visible to users or available for data import or export. A custom object that is marked as deployed is visible to users and available for data import or export. Therefore, the administrator should make sure that the new custom object is marked as deployed before using Data Loader to upload records to it
Question #15
The VP of sales at AW Computing utilizes a Lead report grouped by Country and Lead Source to show where the leads are coming from. The number of leads vanes greatly for each Country.
What should the administrator configure on the report to show the Lead Source effectiveness for each country?
- A . The ‘Show Unique Count*
- B . PARENTGROUPVAL Function
- C . Bucket fitters
- D . PREVGROUPVAL function
Correct Answer: B
B
Explanation:
The PARENTGROUPVAL function is a formula function that returns the value of a parent group in a report. It can be used to compare values across different groupings and show relative performance.
In this case, the administrator can use this function to show the lead source effectiveness for each country by calculating the percentage of leads from each lead source divided by the total number of leads for each country.
Reference: https://help.salesforce.com/s/articleView?id=sf.reports_formulas_parentgroupval.htm&type=5
B
Explanation:
The PARENTGROUPVAL function is a formula function that returns the value of a parent group in a report. It can be used to compare values across different groupings and show relative performance.
In this case, the administrator can use this function to show the lead source effectiveness for each country by calculating the percentage of leads from each lead source divided by the total number of leads for each country.
Reference: https://help.salesforce.com/s/articleView?id=sf.reports_formulas_parentgroupval.htm&type=5
Question #16
The salts team at Universal Containers has asked the administrator to build functionality to automatically update the account checkbox field ‘Opportunity Created’ to checked when at least one related opportunity has been created.
What feature should the administrator use to build this functionality?
- A . Screen flow
- B . Workflow rule
- C . Record-triggered flow
- D . Assignment rule
Correct Answer: C
C
Explanation:
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
C
Explanation:
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
Question #17
AW Computing has a new requirement from its security team where audit information relating to an account must be recorded in a new custom object called Audit. Audit records need to be preserved for 10 years and only accessible by the audit team.
What relationship should be used to relate the Audit object to the Account object?
- A . Master-Detail
- B . Lookup
- C . Many-To-Many
- D . Self
Correct Answer: B
B
Explanation:
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.
Reference: Salesforce documentation recommends using Lookup relationships when objects need to remain independent or when additional flexibility for sharing and retention is required.
B
Explanation:
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.
Reference: Salesforce documentation recommends using Lookup relationships when objects need to remain independent or when additional flexibility for sharing and retention is required.
Question #18
The administrator at Cloud Kicks needs to set up automation to update three fields on the Shipment custom object. Because of the effect these updates will have on some programmatic customizations, they need to happen in a very specific order.
How should the administrator configure the field updates to ensure the proper order.
- A . Create three workflow rules in order, one workflow rule for each field update.
- B . Create a process with one criteria node and three field updates in the correct order.
- C . Create a process with three criteria nodes and stop after each action.
- D . Create a workflow rule with three field updates entered in the correct order.
Correct Answer: B
B
Explanation:
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.
Reference: According to Salesforce best practices, Process Builder is recommended over multiple workflow rules when specific ordering and complex logic are required for field updates
B
Explanation:
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.
Reference: According to Salesforce best practices, Process Builder is recommended over multiple workflow rules when specific ordering and complex logic are required for field updates
Question #19
An administrator created and activated several record-triggered flows that are configured to run before the record is saved on the same object.
What should the administrator consider about the order of execution for flows?
- A . The flow type will determine the order of execution.
- B . The last created date of the flow will determine the order.
- C . The order of flow execution is unpredictable.
- D . The flows will execute in alphabetical order based on their names.
Correct Answer: C
C
Explanation:
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.
Reference: https://help.salesforce.com/s/articleView?id=sf.flow_considerations_recordtriggered_before.htm&t ype=5
C
Explanation:
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.
Reference: https://help.salesforce.com/s/articleView?id=sf.flow_considerations_recordtriggered_before.htm&t ype=5
Question #20
An administrator is creating a custom Opportunity record page for Sales users for new logo opportunities. They need to control what fields display on the record when a sales user is viewing the opportunity.
Where should the administrator edit what fields display in the details of the record page?
- A . Record Detail Component
- B . Custom Lightning Component
- C . Record Types
- D . Page Layout
Correct Answer: D
D
Explanation:
The fields that display in the details of the record page are controlled by the page layout assigned to the user’s profile and record type. The administrator can edit the page layout to add, remove, or reorder fields on the record page.
Reference: https://help.salesforce.com/s/articleView?id=sf.customize_layouts.htm&type=5
D
Explanation:
The fields that display in the details of the record page are controlled by the page layout assigned to the user’s profile and record type. The administrator can edit the page layout to add, remove, or reorder fields on the record page.
Reference: https://help.salesforce.com/s/articleView?id=sf.customize_layouts.htm&type=5