• Home
• Salesforce Exams
• Certified Platform App Builder

Certified Platform App Builder Salesforce Practice Test Questions and Exam Dumps

Question No 1:

Universal Containers manages internal projects by department using a custom object called Projects. Only employees in the 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. The organization-wide default for Projects is set to Private. 

Which two options will meet these requirements? (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.

Answer:

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.

Explanation:

In Salesforce, when you want to control the visibility of records based on specific criteria, sharing rules are used to grant users access to records that meet certain conditions. In this scenario, the objective is to ensure that only employees in a specific department have access to the projects belonging to that department. Additionally, if an employee changes departments, their access to the projects of the previous department should be revoked. Since the organization-wide default for the Projects object is set to Private, users can only see records they own or are explicitly shared with them. To meet these requirements, we need to implement sharing rules based on the department attribute of the project.

Option C: Create a criteria-based sharing rule using the Project's department that grants access to users by roles.
Roles are typically used in Salesforce to define access hierarchies. When creating a sharing rule based on roles, you can specify that users in specific roles (like managers or employees of a particular department) should have access to the records. Since departments can be aligned with roles, this option ensures that employees in the right role (department) have access to the project records. Moreover, when an employee changes roles, their access to records from their previous department is automatically revoked, as their role no longer grants them access to the former department's projects.

Option D: Create a criteria-based sharing rule using the Project's department that grants access to users by public groups.
Public groups are collections of users, roles, or territories that can be used to grant access to records. By creating a public group for each department and then setting up sharing rules based on the department, you can ensure that only the members of the appropriate department's group have access to the project records. If an employee moves to another department, their access to the previous department's projects can be automatically revoked by changing their group membership.

Why other options don’t work:

• Option A: Profiles are used to define user access at the object and field level but do not directly govern record visibility. They cannot be used in sharing rules to grant access based on record criteria like department.

• Option B: Permission sets are used to grant additional permissions to users, but they do not control record-level visibility for sharing purposes.

Question No 2:

Universal Containers has a diverse customer base, and many of their customers have similar or identical company names. To enhance the search experience for end users and make it easier to find the right accounts, 

Which two functionalities should be configured? (Choose two.)

Options:

 A. Modify the account search layout's search filter fields.
B. Modify the account search layout's account tab columns displayed.
C. Modify the account search layout's search results columns displayed.
D. Modify the account search layout's list view filter settings.

Answer: The correct answers are:
A. Modify the account search layout's search filter fields.
C. Modify the account search layout's search results columns displayed.

Explanation:

Universal Containers has a customer base where many customers share similar or identical company names. In this scenario, it is important to improve the search experience for end users to make it easier to differentiate between accounts. There are several functionalities within Salesforce that can be configured to optimize searchability.

A. Modify the account search layout’s search filter fields:
One way to enhance search functionality is by adding more filter options to the account search layout. Filters help narrow down results based on specific criteria, making it easier for users to locate the correct account, even when many have similar names. For example, adding fields like Account Type, Industry, or Location as searchable filters allows users to refine their search results more effectively, improving their ability to distinguish between similar company names.

C. Modify the account search layout’s search results columns displayed:
Another useful configuration is customizing the columns that appear in the search results. By including additional relevant columns such as Account Number, Phone Number, or Email, users can quickly distinguish between accounts that might otherwise appear identical. The search results should show key information that can help users identify the correct account at a glance, which reduces confusion and increases efficiency when working with a large customer base.

Why the other options are less effective:

• B. Modify the account search layout’s account tab columns displayed: This option affects the tab view but does not directly impact the search process.

• D. Modify the account search layout’s list view filter settings: While this may improve list views, it does not address the core issue of improving search results for users dealing with similar account names.

By configuring the search filter fields and search result columns, end users will have a much more streamlined experience when trying to locate the correct account.

Question No 3:

An app builder creates an Account validation rule on the Industry field that triggers an error if the length of the field exceeds 6 characters. Another app builder creates a workflow rule that updates the Industry field to "Technology" whenever the Billing City field is set to "San Francisco."

What will happen the next time a salesperson saves an Account record 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, and the validation rule’s error message will be displayed.
D. The record will save, but the Industry field will not change to "Technology."

Answer: C. The record will not save, and the validation rule’s error message will be displayed.

Explanation:

This scenario involves two key components: a validation rule on the Industry field and a workflow rule that updates the Industry field based on the Billing City field.

1. Validation Rule:
   The validation rule is set to trigger an error if the Industry field’s length exceeds 6 characters. This means that any value in the Industry field longer than 6 characters will prevent the record from being saved.

2. Workflow Rule:
   The workflow rule updates the Industry field to "Technology" whenever the Billing City is "San Francisco." If this condition is met, the Industry field will be automatically set to "Technology."

Now, consider what happens when the salesperson saves an Account with a Billing City of "San Francisco."

• When the record is saved, the workflow rule will automatically update the Industry field to "Technology."

• The value "Technology" is 10 characters long, which exceeds the 6-character limit set by the validation rule.

• Since the Industry field’s value now violates the validation rule, the save operation will fail.

• No other error message will be displayed apart from the validation rule’s error message, indicating that the Industry field's value is too long.

Thus, the correct answer is C: The record will not save, and the validation rule’s error message will be displayed.

Question No 4:

What happens when a dashboard is deleted in a system? Choose the most accurate statement regarding the deletion process of a dashboard.

A. Deleting a dashboard also deletes the components within it, but the custom reports used by the components are not deleted.
B. Deleting a dashboard does not send the dashboard to the Recycle Bin, so the dashboard cannot be recovered.
C. Deleting a dashboard results in the deletion of both the components within the dashboard and the custom reports associated with those components.
D. Deleting a dashboard requires the user to first edit the components and remove the underlying reports before the dashboard can be deleted.

Answer: A. Deleting a dashboard also deletes the components within it, but the custom reports used by the components are not deleted.

Explanation:

When a user deletes a dashboard in a system, it's important to understand the implications for both the dashboard's components and the underlying data or reports. Option A is the correct answer because it accurately reflects how dashboards and their associated components work in many systems, particularly those used in data analytics and reporting tools.

When a dashboard is deleted, all of the components (e.g., charts, widgets, or graphs) within the dashboard are removed. However, the custom reports or data sources used by those components are generally not deleted. This distinction is crucial because the reports, which may be shared across multiple dashboards or used independently, are typically stored separately. As a result, even if the dashboard is deleted, the reports remain intact and can still be used elsewhere in the system.

Option B is incorrect because in most systems, deleting a dashboard does not permanently remove it; instead, it is moved to the Recycle Bin (or equivalent), where it can be restored if necessary. Therefore, a deleted dashboard can usually be recovered.

Option C is inaccurate because it implies that deleting a dashboard also deletes the custom reports used within it. However, reports are often separate entities in the system and are not tied to a specific dashboard. Therefore, deleting a dashboard does not automatically delete those reports.

Option D is also incorrect because there is no typical requirement to edit the components or remove underlying reports before deleting a dashboard. Deleting a dashboard can usually be done directly without needing to adjust the components or the reports associated with it.

In summary, when you delete a dashboard, you remove the visual components but leave the underlying reports intact, allowing them to be used in other contexts or dashboards. This helps ensure that data remains available and is not unnecessarily deleted.

Question No 5:

In Salesforce, when a junction object has two Master-Detail relationships—one as the primary master and one as the secondary master—what happens to the junction object record when both associated master records are deleted?

A. The junction object record is permanently deleted and cannot be restored.
B. The delete operation cannot be performed on both master records.
C. The delete operation is not allowed when Roll-up Summary fields are defined.
D. The junction object record is deleted and placed in the Recycle Bin.

Answer: The correct answer is D. The junction object record is deleted and placed in the Recycle Bin.

Explanation:

In Salesforce, a junction object is used to model many-to-many relationships between two objects. It achieves this by utilizing two Master-Detail relationships, one as the primary master and the other as the secondary master.

When both associated master records of a junction object are deleted, the following occurs:

1. Master-Detail Relationship Behavior: In a Master-Detail relationship, the child (junction object in this case) is tightly coupled to the parent (master records). If either of the master records is deleted, the related child (junction object) record is typically deleted as well. This ensures referential integrity between the parent and child objects.

2. Impact of Deleting Both Master Records: If both associated master records are deleted, Salesforce will delete the junction object record as well. However, instead of being permanently deleted, the junction object record is placed in the Recycle Bin. This is because Salesforce allows for some flexibility and recovery of data within a certain period, thus providing a way to restore deleted records from the Recycle Bin.
   
   

3. Reasoning Behind Other Options:
   
   

• Option A ("The junction object record is permanently deleted and cannot be restored") is incorrect because Salesforce places deleted records in the Recycle Bin, where they can be restored.

• Option B ("The delete operation cannot be performed on both master records") is incorrect because Salesforce does allow the deletion of both master records, which will result in the deletion of the junction object record.

• Option C ("The delete operation is not allowed when Roll-up Summary fields are defined") is also incorrect because Roll-up Summary fields don't prevent the deletion of master records. They are just used to aggregate values from related child records.

Thus, the junction object record is deleted and moved to the Recycle Bin, making Option D the correct answer.

Question No 6:

Universal Containers wants to ensure that its Field Sales team can only see the accounts they own, while the North American and European marketing teams should only see accounts within their respective regions. Additionally, the Inside Sales team needs to be able to see all accounts in Salesforce. 

How should an app builder configure Salesforce to meet these requirements?

A. Set the Organization-Wide Default to Public for accounts. Create profiles for each marketing team and establish an Inside Sales Team role 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:

To meet the requirements of Universal Containers in controlling account visibility, the app builder needs to configure a few key features in Salesforce: Organization-Wide Defaults (OWD), sharing rules, profiles, and permission sets.

1. Organization-Wide Default (OWD) for Accounts:

• By setting the OWD for accounts to Private, the app builder ensures that only users who have explicit access to an account can view it. This means, by default, Field Sales users will only see accounts that they own, which aligns with the requirement for them to only see their own accounts.

2. Marketing Teams' Regional Access:

• To restrict each marketing team to only see accounts in their respective regions (North American and European), the app builder will create criteria-based sharing rules. These rules will share accounts with the respective marketing teams based on criteria such as region or territory. For example, the North American marketing team will only see accounts where the region is North America, and similarly for the European marketing team.

3. Inside Sales Team Access:

• The Inside Sales Team needs to see all accounts in Salesforce. To achieve this, the app builder can assign a profile to the Inside Sales Team with the "View All" setting for accounts. This permission allows the Inside Sales team to see all accounts, irrespective of ownership or sharing rules.

4. Security and Flexibility:

• Using Private OWD for accounts provides the flexibility to grant specific users access through sharing rules and profiles. It ensures that sensitive account data is not publicly visible, while still allowing controlled sharing and access for different teams.

In summary, Option D is the best solution because it implements a private OWD for accounts, defines criteria-based sharing rules for regional access, and provides the Inside Sales team with the necessary "View All" access via their profile. This solution ensures proper access control while meeting the visibility requirements for each team.

Question No 7:

The app builder has just created a Visual Workflow for the Vice President (VP) of Service. Which two of the following options can be used by users to access the Visual Workflow? (Select two.)

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

Answer:

B. Quick Action
C. Visual Workflow Launcher

Explanation:

In Salesforce, Visual Workflows allow users to automate business processes and guide them through complex tasks using a visual interface. When a Flow is created, the app builder needs to decide how to make it accessible to users. Two common ways to do this are through Quick Actions and Visual Workflow Launchers.

1. Quick Action (B): Quick Actions are buttons or links that users can access from record pages, mobile apps, or the Salesforce Lightning Experience. These actions can launch Visual Workflows, providing a way for users to start the flow directly from a record page. By adding a Flow to a Quick Action, users can initiate the workflow by simply clicking on a button, making the process faster and more streamlined.

2. Visual Workflow Launcher (C): The Visual Workflow Launcher is a feature in Salesforce that allows app builders to specify when and how to launch a flow. This can be based on certain user actions, like clicking a button, or triggered through automation. By setting up the Visual Workflow Launcher, users can directly launch flows in the Salesforce environment without additional steps.

Why Not the Other Options?

• Custom Button (A): While custom buttons are often used to initiate actions, they are typically linked to a specific action such as opening a URL, creating a record, or calling a JavaScript function. Custom buttons are not ideal for launching Visual Workflows unless they are explicitly set up to do so, which makes them less common for user-facing workflows in comparison to Quick Actions or Launchers.

• From a Process (D): A Process, like a Process Builder, automates behind-the-scenes tasks, but it does not directly provide a way for users to interact with a Visual Workflow. A process can trigger a Flow in the background, but it does not offer users direct access to launch the workflow manually.

In conclusion, the most user-friendly and efficient ways for users to access a Visual Workflow are through Quick Actions or Visual Workflow Launchers, allowing for quick initiation of automated tasks directly within the Salesforce interface.

Question No 8:

Which two types of metadata changes can be made directly in a production environment without the need to deploy from a sandbox? (Choose two.)

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

Answer:
A. Validation rules
D. Visualforce pages

Explanation:

In Salesforce, metadata changes refer to modifications to the configuration and customization of the platform, including objects, fields, triggers, classes, and user interfaces. Normally, most metadata changes are deployed from a sandbox environment to production using change sets or other deployment tools. However, some metadata changes can be made directly in the production environment, without requiring a deployment from a sandbox. These changes are typically lower-risk changes that do not require heavy coding or complex testing.

A. Validation Rules:

Validation rules are business logic formulas that ensure data entered into Salesforce meets certain criteria. They are used to validate user input during record creation or updates. Validation rules can be created or modified directly in the production environment because they are typically lightweight and don’t have significant dependencies on other components. These rules are often used to enforce data quality, and making them directly in production is a common practice since they can be easily tested and modified without impacting other parts of the system.

D. Visualforce Pages:

Visualforce is a framework for building custom user interfaces in Salesforce. Visualforce pages can be created or modified directly in production as long as the changes are not too complex and do not involve the introduction of new components that require detailed testing. Visualforce pages are often part of custom applications or user interface customizations, and minor changes can be deployed directly in the production environment.

Why Not the Others?

• B. Apex Triggers: Apex triggers are pieces of code that run when certain events occur on Salesforce records (e.g., insert, update, delete). While triggers can technically be edited in the production environment using tools like the Developer Console, Apex triggers are typically deployed from a sandbox because they involve logic that may affect the stability and integrity of data. This ensures that the code has been properly tested in a non-production environment before being applied to production.

• C. Apex Classes: Like Apex triggers, Apex classes contain logic that can impact business processes and data integrity. Apex classes should also be deployed from a sandbox to production to ensure thorough testing and reduce the risk of introducing errors. Changes to Apex classes are more complex and can have unintended consequences if not thoroughly tested.

In conclusion, validation rules and Visualforce pages are examples of metadata changes that are typically safe to modify directly in a production environment, while changes to Apex triggers and classes generally require deployment through a sandbox for proper testing and validation.

Question No 9:

The Training team at Universal Containers tracks customer training sessions using a custom Training object. An app builder needs to create a relationship between the Training object and related Student records.

Which two of the following statements are true when creating a Student Lookup field on the Training object? (Choose two.)

A. The Student Lookup field on the Training record can be made optional.
B. Users can create a Roll-up Summary field on the Student record to aggregate data from related Training records.
C. On the Training record, users can only delete Student records if they have access to them.
D. Cross-object field updates between the Training and Student records are not supported.

Answer:

A. The Student Lookup field on the Training record can be made optional.
C. On the Training record, users can only delete Student records if they have access to them.

Explanation:

When setting up a relationship between two objects in Salesforce, such as a custom Training object and the related Student records, it's important to understand how the different features and permissions work with Lookup Relationships.

1. Statement A (Correct):
   A Lookup field on the Training record can be made optional. A lookup relationship allows you to relate a record from one object (in this case, the Student) to a record in another object (the Training object). By default, Salesforce requires that a lookup field be filled out, but you can configure it to be optional, allowing users to leave it empty if no student is associated with a particular training record. This flexibility is beneficial when certain training sessions may not have a student tied to them.

2. Statement B (Incorrect):
   Roll-up Summary fields are used in master-detail relationships to summarize data from related child records to the parent record. However, Roll-up Summary fields cannot be created for Lookup relationships, as they are specific to master-detail relationships. Therefore, the ability to create a Roll-up Summary field on the Student record to aggregate data from the Training records does not apply in this case, making this statement incorrect.

3. Statement C (Correct):
   Users can only delete the Student records if they have appropriate access to the Student record. This is a key aspect of Salesforce’s data security and permissions model. A Lookup relationship does not enforce data ownership in the same way a master-detail relationship does. However, users can delete related records, such as a Student, from a Training record only if they have the necessary permissions on the Student record. This is part of Salesforce's user access and sharing model.

4. Statement D (Incorrect):
   Cross-object field updates between Training and Student records are supported in Salesforce. This means that you can create field updates based on values from the related records using automation tools like Process Builder or Flows. This is possible even for Lookup relationships, so the statement that cross-object field updates are not supported is incorrect.

In summary, when creating a Student Lookup field on the Training object, you can make the field optional and users can only delete the related Student record if they have proper access permissions to it. However, you cannot use Roll-up Summary fields in a Lookup relationship, and cross-object field updates are indeed supported.

Question No 10:

An app builder is working on enhancing the user experience by summarizing specific field values across different objects. The goal is to display aggregate calculations based on certain fields within a record. To achieve this, the builder is considering using roll-up summary fields. 

Which three of the following field types can be used in roll-up summary fields to perform these summarized calculations? (Select three.)

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

Answer: 

A. Checkbox
C. Percent
E. Currency

Explanation:

Roll-up summary fields in Salesforce are powerful tools that allow users to aggregate data from related child records (typically in a master-detail relationship). The roll-up summary field automatically calculates and displays the summarized value of specific fields from related child records on the parent record. However, not all field types are supported for use in roll-up summary fields. Let’s break down the field types mentioned:

1. Checkbox (A): Checkbox fields can be used in roll-up summary fields. When performing roll-up calculations like COUNT, Salesforce counts the number of records where the checkbox is selected (True). It can be helpful for counting records based on a binary true/false condition, like counting the number of completed tasks or approved records.

2. Percent (C): Percent fields can also be used in roll-up summary fields. If the child record contains a percentage field (such as a discount rate or progress percentage), a roll-up summary can be used to calculate the average, minimum, or maximum percentage across the child records and reflect that value in the parent record.

3. Currency (E): Currency fields are commonly used in roll-up summary fields. These are particularly useful in financial contexts, such as summing up the total amount of sales, expenses, or other monetary values from related child records. Roll-up summary fields can calculate totals, averages, or other aggregate metrics from currency fields.

On the other hand:

• Date (B): Date fields cannot be used in roll-up summary fields for calculations. While you can filter records based on dates, you cannot perform aggregations like SUM or AVERAGE on date fields.

• Time (D): Similar to Date fields, Time fields are not supported in roll-up summary fields. You cannot aggregate time values across records using roll-up summary.

In summary, the field types that are suitable for use in roll-up summary fields are Checkbox, Percent, and Currency. These field types allow for meaningful aggregation and calculation, such as counting, averaging, or summing values, to streamline the user experience by reflecting summarized data on parent records.