[Salesforce] CPAB - Certified Platform App Builder ​ Exam Dumps & Study Guide

Free [Salesforce] CPAB - Certified Platform App Builder ​ Practice Questions Preview

• Question 1

  Universal Containers manages internal projects by department using a custom object called Projects. Only employees in the project's respective department should have view access to all of the department's project records. If an employee changes job roles and moves to another department, the employee should no longer have access to the projects within their former department.
  Which two options will meet these requirements assuming the organization-wide default for Projects is set to Private? (Choose two.)
  

  • A. Create a criteria-based sharing rule using the Project's department that grants access to users by profiles.
  • B. Create a criteria-based sharing rule using the Project's department that grants access to users by permission sets.
  • C. Create a criteria-based sharing rule using the Project's department that grants access to users by roles.
  • D. Create a criteria-based sharing rule using the Project's department that grants access to users by public groups.

  Correct Answer: CD

  Explanation:

  The AI agrees with the suggested answer CD.
  
  Reasoning:
  Given the requirements, the organization-wide default for Projects is set to Private, and the need is to grant access to project records based on the project's department, two options are most suitable:

  • Option C: Create a criteria-based sharing rule using the Project's department that grants access to users by roles.
  • Option D: Create a criteria-based sharing rule using the Project's department that grants access to users by public groups.

  Criteria-based sharing rules allow admins to define specific criteria that, when met, grant access to records to users in roles or public groups. Roles are suitable because they often align with departmental structures. Public groups can also be used to group users by department. If an employee changes departments (and thus roles), their access is automatically updated.
  Reasons for not choosing other answers:

  • Option A: Create a criteria-based sharing rule using the Project's department that grants access to users by profiles. - Sharing rules cannot be based on Profiles.
  • Option B: Create a criteria-based sharing rule using the Project's department that grants access to users by permission sets. - Sharing rules cannot be based on Permission Sets.

  Sharing rules can extend access to users in roles, public groups, or territories. Profiles and permission sets are for granting object-level and field-level access and other permissions, not for record-level access based on dynamic criteria.

  
  

  In summary, roles and public groups are suitable for managing record access based on departmental affiliation because they can be dynamically updated as employees change roles or departments.

  • Salesforce Sharing Rules: https://help.salesforce.com/s/articleView?id=sf.security_about_sharing_rules.htm&type=5
  • Salesforce Roles: https://help.salesforce.com/s/articleView?id=sf.security_roles.htm&type=5
  • Salesforce Public Groups: https://help.salesforce.com/s/articleView?id=sf.networks_public_groups.htm&type=5

• Question 2

  Universal Containers has a customer base where many customers have the same or similar company names.
  Which functionality should be configured to improve an end user's search experience? (Choose two.)
  

  • A. Update the account search layouts search filter fields.
  • B. Update the account search layouts accounts tab columns displayed.
  • C. Update the account search layouts search results columns displayed.
  • D. Update the account search layouts list view filter settings.

  Correct Answer: AC

  Explanation:

  The AI suggests that the correct answer is AC.
  The reasoning is as follows:
  A. Update the account search layouts search filter fields: This allows users to narrow down their search by specifying additional criteria, which is crucial when company names are similar. By adding relevant fields to the search filter, users can distinguish between different accounts with similar names.
  C. Update the account search layouts search results columns displayed: This enables users to see more information about each account directly in the search results, making it easier to differentiate between accounts with similar names. Displaying key fields like Account Owner, Industry, or Location in the search results can provide the context needed to quickly identify the correct account.
  B is incorrect because updating the 'Accounts' tab columns doesn't directly impact the search experience in terms of filtering or differentiating search results.
  D is incorrect because list view filters are applied after the initial search and do not directly enhance the initial search experience when users are trying to find the correct account among many with similar names.

  • Citation 1: Configure Search Results, https://help.salesforce.com/s/articleView?id=sf.search_customize_lex.htm&type=5
  • Citation 2: Customize Search in Salesforce Classic, https://help.salesforce.com/s/articleView?id=sf.search_customize.htm&type=5

• Question 3

  An app builder creates an Account validation rule on the Industry field that will throw an error if the length of the field is longer than 6 characters. Another app builder creates a workflow with a field update that sets the Industry field to Technology whenever the Billing City field is set to San Francisco.
  What will happen the next time a sales person saves an Account with a Billing City of San Francisco?
  

  • A. The record will save and the Industry field will change to Technology.
  • B. The record will not save and no error message will be displayed.
  • C. The record will not save the validation rule's error message will be displayed.
  • D. The record will save but the Industry field will not change to Territory.

  Correct Answer: A

  Explanation:

  The AI assistant agrees with the suggested answer A.
  Here's the detailed reasoning:

  • The Salesforce Order of Execution is crucial here. Validation rules are triggered first. However, workflow rules, which execute later, can modify field values. Once a workflow rule updates a field, the validation rules are generally not re-evaluated in the same transaction.
  • In this scenario, the validation rule checks if the Industry field is longer than 6 characters. The workflow rule updates the Industry field to "Technology" when Billing City is "San Francisco".
  • Since the workflow rule executes after the validation rule and changes the Industry field to "Technology" (which is 10 characters long), the validation rule should, in theory, trigger an error. However, because of the order of execution and Salesforce's behavior of not re-evaluating validation rules after workflow updates in the same transaction, the record will save, and the Industry field will be updated to "Technology".

  Reasons for not choosing the other answers:

  • B: "The record will not save and no error message will be displayed." - This is incorrect because the record *will* save due to the order of execution.
  • C: "The record will not save the validation rule's error message will be displayed." - This is incorrect because the validation rule is not re-triggered after the workflow updates the field.
  • D: "The record will save but the Industry field will not change to Territory." - "Territory" is a typo here, should be "Technology". The record saves, and the Industry *does* change to "Technology".

  Therefore, the correct answer is A.

  Citations:

  • Salesforce Order of Operations, https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_trigger_order_of_execution.htm

• Question 4

  What is a true statement when deleting a dashboard?
  

  • A. Deleting a dashboard also deletes the components within it. It does not delete the custom reports used by the components.
  • B. Deleting a dashboard does not move the dashboard to the Recycle Bin and therefore the dashboard cannot be recovered.
  • C. Deleting a dashboard also deletes the components within it as well as the custom reports used by the components.
  • D. Deleting a dashboard requires a user to first edit the components to remove the underlying reports.

  Correct Answer: A

  Explanation:

  The AI assistant agrees with the suggested answer A.
  Reasoning: Deleting a dashboard removes its components, but the underlying reports are not deleted. They remain available for use in other dashboards or reports.
  

  • Correctness of Option A: This statement accurately reflects the behavior of deleting a dashboard in Salesforce. The dashboard components are removed as they are part of the dashboard layout. However, the source reports that feed data into these components are independent entities and are not deleted.
  • Incorrectness of Option B: Deleting a dashboard *does* move it to the Recycle Bin, where it can be recovered within a certain timeframe. Therefore, this option is incorrect. See Salesforce Help documentation on dashboard deletion and recovery.
  • Incorrectness of Option C: As stated before, deleting a dashboard does not delete the custom reports. So this option is not correct.
  • Incorrectness of Option D: Salesforce does not require a user to edit the components to remove the underlying reports before deleting a dashboard. So this option is not correct.

  In summary, option A is the only true statement.

  • Deleting a dashboard also deletes the components within it. It does not delete the custom reports used by the components.

  
  Citations:

  • Salesforce Help: Delete a Dashboard, https://help.salesforce.com/s/articleView?id=sf.dash_delete.htm&type=5

• Question 5

  A junction object has two Master-Detail relationships, a primary and a secondary master object.
  What happens to a junction object record when both associated master records are deleted?
  

  • A. The junction object record is permanently deleted and can't be restored.
  • B. The delete operation cannot be performed on both master records.
  • C. The delete operation is not allowed with Roll-up summary fields defined.
  • D. The junction object records is deleted and placed in the recycle bin.

  Correct Answer: A

  Explanation:

  The AI agrees with the suggested answer.
  When a junction object has two Master-Detail relationships, and both associated master records are deleted, the junction object record is permanently deleted and can't be restored. This is because Master-Detail relationships enforce a strong link between the records, and deleting the master record effectively orphans the detail record, leading to its permanent deletion.
  
  Here's a breakdown of why the other options are incorrect:

  • B. The delete operation cannot be performed on both master records. This is incorrect. Salesforce allows the deletion of master records in Master-Detail relationships, provided certain conditions are met (e.g., cascade delete is enabled or the related detail records are handled).
  • C. The delete operation is not allowed with Roll-up summary fields defined. This is incorrect. Roll-up summary fields can impose restrictions on deleting detail records, but they don't inherently prevent the deletion of master records. The behavior depends on the specific configuration of the Roll-up summary field.
  • D. The junction object records is deleted and placed in the recycle bin. This is incorrect. Due to the nature of Master-Detail relationships and the cascading delete behavior, the junction object record is permanently deleted and bypasses the Recycle Bin.

  
  

  Therefore, the answer is A: The junction object record is permanently deleted and can't be restored.

  
  

  Citations:

  • Master-Detail Relationship Considerations, https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm&type=5

• Question 6

  Universal Containers wants its Field Sales team to only see the accounts that they own. Separate North American and European marketing teams should only see accounts in their respective regions. The Inside Sales Team needs to see all accounts in Salesforce.
  How should an app builder accomplish this?
  

  • A. Set the Organization-Wide Default to Public for accounts. Create profiles for each Marketing Team, and create an Inside Sales Team role that is at the top of the Role Hierarchy.
  • B. Set the Organization-Wide Default to Public for accounts. Create criteria-based sharing rules for each Marketing Team, and create an Inside Sales Team permission set with the "View All" setting for accounts.
  • C. Set the Organization-Wide Default to Private for accounts. Create permission sets for each Marketing Team, and create an Inside Sales Team profile with the "View All" setting for accounts.
  • D. Set the Organization-Wide Default to Private for accounts. Create criteria-based sharing rules for each Marketing Team, and create an Inside Sales Team profile with the "View All" setting for accounts.

  Correct Answer: D

  Explanation:

  The AI suggests that the answer is D.
  
  Reasoning:
  The scenario requires restricting access to accounts for specific teams while granting full access to the Inside Sales Team. This can be achieved by setting the Organization-Wide Default (OWD) to Private and using sharing rules to grant access to the Marketing teams. The Inside Sales Team can be granted "View All" access through their profile.
  
  Here's why option D is the most suitable:

  • OWD set to Private: This ensures that users can only see the accounts they own unless explicitly granted access through other mechanisms.
  • Criteria-based Sharing Rules for Marketing Teams: This allows granting access to accounts based on specific criteria, such as region, to the North American and European marketing teams.
  • "View All" Profile setting for Inside Sales Team: This provides the Inside Sales Team with the necessary access to view all accounts in Salesforce.

  
  Why other options are not suitable:

  • Option A: Setting the OWD to Public would allow everyone to see all accounts, which contradicts the requirement that the Field Sales team only see the accounts they own and the marketing teams only see accounts in their respective regions.
  • Option B: Similar to option A, setting the OWD to Public negates the need for sharing rules and permission sets for restricting access.
  • Option C: While setting the OWD to Private is correct, using permission sets for Marketing Teams to grant access is not the ideal approach. Sharing rules are better suited for this purpose as they can be based on specific criteria (e.g., region). Furthermore, using a profile for "View All" access for the Inside Sales Team is appropriate.

  Citations:

  • Salesforce Sharing and Visibility Designer; https://trailhead.salesforce.com/en/content/learn/modules/data_security/sharing_visibility_designer
  • Record-Level Security; https://help.salesforce.com/s/articleView?id=sf.security_data_access.htm&type=5

• Question 7

  The app builder has just created a Visual Workflow for the VP of Service.
  Which two Flow be accessed by users? (Choose two.)
  

  • A. Custom Button
  • B. Quick Action
  • C. Visual Workflow Launcher
  • D. From a Process

  Correct Answer: AB

  Explanation:

  The AI recommends answers A and B as the correct choices.
  Here's the reasoning:

  • A: Custom Button: Flows can be launched from custom buttons, allowing users to initiate them directly from a record or other context.
  • B: Quick Action: Flows can also be launched from Quick Actions, providing another way for users to easily access and run them.

  
  Reasoning for excluding other options:

  • C: Visual Workflow Launcher: There's no standard Salesforce feature called "Visual Workflow Launcher". While flows are launched, this isn't a typical launch method exposed to end users.
  • D: From a Process: Processes can trigger flows, but this is an automated backend process, not a direct user interaction method for *accessing* a flow. Processes typically launch autolaunched flows (flows without screens), not screen flows that require user interaction.

  The key here is the question is asking how the flow can be *accessed by users*.

• Question 8

  Which two metadata changes can be made directly in a production environment without deploying from a sandbox? (Choose two.)
  

  • A. Validation rules
  • B. Apex Triggers
  • C. Apex Classes
  • D. Visualforce pages

  Correct Answer: AD

  Explanation:

  The AI agrees with the suggested answer of AD.
  Reasoning:
  Based on Salesforce documentation and best practices, certain metadata types can be modified directly in a production environment without requiring a full deployment from a sandbox. This is generally limited to low-risk changes that do not have the potential to disrupt critical functionality. Validation rules and Visualforce pages fall into this category because changes to these components typically don't require code compilation or database schema modifications. Making changes directly in production should be done with caution and proper testing in a sandbox first is always recommended.

  • Validation Rules: These can be modified directly in production to adjust data validation logic.
  • Visualforce Pages: Minor changes to Visualforce pages, such as text adjustments or layout tweaks, can be made directly in production.

  
  Reasons for not choosing other answers:

  • Apex Triggers and Apex Classes: These require a deployment from a sandbox environment to production. This is because Apex code requires compilation and testing to ensure it doesn't introduce errors or security vulnerabilities. Deploying Apex code directly to production without proper testing is a high-risk practice.

  Supporting Documentation:

  • Salesforce Help: Change Sets, https://help.salesforce.com/s/articleView?id=sf.changesets.htm&type=5
  • Salesforce Metadata API, https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_types_list.htm

• Question 9

  The Training team at Universal Containers uses a custom Training object to track their customer training sessions. An app builder needs to create a relationship between the Training object and the related Students' record.
  Which two statements are true when creating a Student Lookup field on the Training object? (Choose two.)
  

  • A. On Training record, the Student Lookup field can be made optional.
  • B. On Student record, users can set up Roll-up summary field on Training records.
  • C. On Training record, users can only delete Students, if they have access to it.
  • D. Cross-object field updates between Training and Student records are not supported.

  Correct Answer: AD

  Explanation:

  The AI agrees with the suggested answer.
  The correct answers are A and D.
  Here's a detailed explanation:

  • A: On Training record, the Student Lookup field can be made optional.
    • Reasoning: Lookup fields, by default, are optional. This means that a Training record can exist without being associated with a Student record. This aligns with real-world scenarios where a training session might be created before students are assigned to it.
  • D: Cross-object field updates between Training and Student records are not supported.
    • Reasoning: With a standard Lookup relationship, direct cross-object field updates (where changing a field on the Training record automatically updates a field on the related Student record or vice-versa via workflow rules or Process Builder) are not directly supported the same way they are with Master-Detail relationships. While you can *access* data on the related record for formulas or display purposes, you can't trigger updates to fields on the related record using the lookup relationship itself. You'd need Apex triggers or potentially Flow to achieve such updates.

  Here's why the other options are incorrect:

  • B: On Student record, users can set up Roll-up summary field on Training records.
    • Reasoning: Roll-up summary fields are only available on the master object in a Master-Detail relationship, summarizing data from the detail records. Since Student is related to Training via a Lookup relationship, and not a Master-Detail relationship (where Training would likely be the detail), you cannot create roll-up summary fields on the Student object to summarize Training records.
  • C: On Training record, users can only delete Students, if they have access to it.
    • Reasoning: This statement is misleading and not entirely accurate. Deleting a *Student* record is governed by the user's access to the Student object and record-level permissions on the Student record itself, not directly tied to access from the *Training* record. The lookup relationship allows association, but doesn't inherently control deletion rights. A user might have read-only access to Student records, preventing them from deleting students, regardless of their access to Training records.

  Therefore, options A and D are the most accurate statements regarding the creation of a Student Lookup field on the Training object.

  • Salesforce Relationships Overview
  • Relationship Considerations

• Question 10

  An app builder would like to streamline the user experience by reflecting summarized calculations of specific fields on various objects.
  Which three field types could be used in roll-up summary fields to accomplish this? (Choose three.)
  

  • A. Checkbox
  • B. Date
  • C. Percent
  • D. Time
  • E. Currency

  Correct Answer: BCE

  Explanation:

  The AI assistant agrees with the suggested answer BCE.
  Reasoning:
  The question asks which field types can be used in roll-up summary fields to accomplish summarized calculations. Roll-up summary fields support calculations like COUNT, SUM, MIN, and MAX. Currency, Percent, and Date fields are valid options for these calculations.

  • Currency: Can be used for SUM, MIN, and MAX.
  • Percent: Can be used for SUM, MIN, and MAX.
  • Date: Can be used for MIN and MAX.

  Why other options are incorrect:
  

  • A. Checkbox: Checkbox fields can only be used with the COUNT roll-up type.
  • D. Time: Time fields are not supported in roll-up summary fields.

  Citations:

  • Roll-Up Summary Fields, https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up_summary_fields.htm&type=5