Salesforce Prepare for your Platform App Builder Certification CRT-403 Exam Practice Test

Answer : C

Cloud Kicks needs to insert 25,000 records with deduplication for the Race_Track__c custom object. Here's the reasoning for choosing Data Loader:

Data Loader: This is the appropriate tool for importing large volumes of data (up to 5 million records) into Salesforce. It also provides deduplication options through Salesforce's native matching rules or by implementing external checks. Data Loader is highly scalable, and for 25,000 records, it is well-suited because it can handle more than the Import Wizard's record limits.

Option A (Import Wizard): The Import Wizard is not a good choice here because it supports up to 50,000 records, which may seem acceptable. However, it is generally recommended for smaller data imports, and deduplication options are limited compared to what Data Loader offers. Additionally, for bulk operations like 25,000 records, Data Loader is more efficient and robust.

Option B (Lightning Object Creator): This tool is used to create custom objects from spreadsheets and is not designed for bulk data loading or deduplication. It's not appropriate for large data imports.

Option D (Schema Builder): Schema Builder is a tool used to view and modify the structure of objects and fields in Salesforce, not for data import or deduplication purposes.

In summary, Data Loader is the most appropriate tool for importing a large number of records with deduplication needs.

Reference: Data Loader Overview Import Wizard vs Data Loader

Answer : D

The app builder should use a custom button and Flow to achieve the desired result. A custom button is a button that can invoke custom logic or actions when clicked by a user. A Flow is a type of automation tool that can guide users through a series of screens and perform actions based on user input. In this case, the app builder can create a custom button on the Account object that launches a Flow when clicked by a user.The Flow can display a popup window with questions for the user to answer and populate additional fields on the Account record based on the user input4. Option A, B, and C are not tools that can achieve this result.

Answer : D

The solution that an app builder should use to meet this requirement is master-detail relationship. A master-detail relationship is a type of relationship that creates a parent-child relationship between two objects, where the child records inherit the sharing and security settings of their parent record. The app builder can create a master-detail relationship between Supplier__c and SupplierItem__c objects, where Supplier__c is the parent object and SupplierItem__c is the child object. This way, when a Supplier__c record is deleted, all related SupplierItem__c records are also deleted automatically. Option A is incorrect because many-to-many relationship is not suitable for this requirement, as many-to-many relationship allows two objects to be linked in both directions through a junction object, but does not support cascading delete. Option B is incorrect because indirect lookup relationship is not suitable for this requirement, as indirect lookup relationship allows an external object to link with another object using an external ID field, but does not support cascading delete. Option C is incorrect because hierarchical relationship is not suitable for this requirement, as hierarchical relationship allows users to use a lookup field that links an object with itself, but does not support cascading delete.

Answer : C

Set the Organization-Wide Default to Private for accounts and create criteria-based sharing rules for each marketing team are the actions that can accomplish the requirement of restricting access to accounts based on region and role. Setting the Organization-Wide Default to Private will limit access to accounts to only owners and administrators. Creating criteria-based sharing rules will grant additional access to accounts based on region for each marketing team. Creating an Inside Sales Team profile with the ''View All'' setting for accounts will grant access to all accounts for the inside sales team. Update the Sales profile, update the organization-wide defaults to Public for accounts, create profiles for each marketing team, create permission sets for each marketing team, and create an Inside Sales Team role are not necessary or sufficient actions for this requirement.

Answer : B, C

The app builder should consider two things before overriding standard buttons:

Standard buttons can be overridden with a Visualforce page. A Visualforce page is a web page that displays custom user interface elements using Visualforce markup and Apex code.A Visualforce page can be used to override a standard button and provide custom functionality or logic3.

Standard buttons that are not available for overrides can still be hidden on page layouts. A page layout is a layout that determines how fields, related lists, and buttons are arranged on a record detail or edit page.A page layout can be used to hide a standard button that cannot be overridden by removing it from the layout4. Option A and D are not things that the app builder should consider before overriding standard buttons.

Answer : C

A master-detail relationship between two objects automatically creates a report type that includes both objects. The app builder does not need to create a custom report type for this scenario.The report type will have the format of Parent object with Child object

Answer : A, C, D

Email alert, task, and invocable flow are three action types that can be used in an approval process. Email alert can send an email message to one or more recipients. Task can assign a task to a user or queue.Invocable flow can launch a flow that performs complex logic and actions