Platform-App-Builder Salesforce Certified Platform App Builder (Plat-Admn-202) Questions and Answers

Changing the data type of custom fields in Salesforce has specific limitations that need to be considered to ensure system integrity and prevent errors:

A. It is not possible to change the data type of a formula field to any data type. Formula fields are calculated based on other field values and cannot be converted into a storage data type because they do not store data themselves.

D. It is not possible to change the data type of a Text Area (Long) field to Text. Text Area (Long) fields support up to 131,072 characters, which far exceeds the 255 character limit of standard Text fields. Converting such a field to a smaller capacity field would potentially lead to data truncation or loss.

For official guidance on data type changes, refer to Salesforce's Custom Field Considerations.

Standard buttons can be overridden with a Visualforce page to provide custom functionality or user interface. For example, you can override the New button on an object to display a custom Visualforce page instead of the standard page layout3. Standard buttons that are not available for overrides can still be hidden on page layouts to prevent users from accessing them. For example, you can hide the Delete button on an object to prevent users from deleting records

The validation rule should be AND(ISNEW(), ISBLANK(Lead.Owner:User.Id)). This rule will prevent saving a new lead record if the owner is not a user. This will ensure that campaign members have a sales owner. Option A is incorrect because it will prevent saving any lead record if the owner is blank, which is not the requirement. Option B is incorrect because it will prevent saving an existing lead record if the owner is a queue, which is not the requirement. Option D is incorrect because it will prevent saving any lead record if the owner is a queue, which is not the requirement.

 The app builder would enable this ability in Chatter Settings. Chatter Settings is a setup menu that allows an app builder to configure various aspects of Chatter functionality, such as feeds, groups, email notifications, and more. One of the options in Chatter Settings is Enable Approvals via Chatter, which allows users to approve or reject requests from their team via Chatter posts or comments. Option A, B, and D are not places where an app builder would enable this ability.

 The two considerations that an app builder should keep in mind during the deployment process using change sets are: Change sets do not include all components and may have to perform some changes manually. Change sets are a way to deploy metadata changes from one Salesforce org to another, but they do not support all types of components, such as reports, dashboards, email templates, etc. The app builder may have to use other methods, such as unmanaged packages or manual configuration, to deploy these components. Users should be logged out of production when receiving inbound change sets. This is a best practice to avoid any errors or conflicts that may occur when deploying changes to production. Users may be working on records or components that are being updated by the change set, which may cause data loss or inconsistency. Salesforce Connect does not automatically establish a link between environments. Salesforce Connect is a feature that allows users to access data from external sources without storing it in Salesforce. It does not have anything to do with deploying changes between Salesforce orgs. Transactions will not revert if the deployment errors. Transactions are units of work that are either completed entirely or not at all. If a deployment error occurs during a transaction, the transaction will be rolled back and no changes will be made to the target org. However, this does not mean that the source org will revert to its previous state before the deployment.

A flow or a process can be used to assign a permission set to new users. A flow can be triggered by a record change or an invocable action, while a process can launch a flow as an immediate or scheduled action

The requirement is to automatically grant record visibility to all users in a specific role (Service Manager) based on record criteria (“Opportunity Type = Service Agreement”).

This is a textbook case for a criteria-based sharing rule.

Why C (Criteria-Based Sharing Rule) is correct:Exact Extract:“A criteria-based sharing rule determines which records to share based on field values, rather than who owns the record.” — Salesforce Help | Sharing Rules OverviewYou can define the rule to share all Opportunities where Type = 'Service Agreement' with all users in the Service Manager role.Exact Extract:“Use criteria-based sharing rules to share records based on record field values with roles, roles and subordinates, or public groups.” — Salesforce Help | Criteria-Based Sharing Rules

Why C (Criteria-Based Sharing Rule) is correct:Exact Extract:“A criteria-based sharing rule determines which records to share based on field values, rather than who owns the record.” — Salesforce Help | Sharing Rules OverviewYou can define the rule to share all Opportunities where Type = 'Service Agreement' with all users in the Service Manager role.Exact Extract:“Use criteria-based sharing rules to share records based on record field values with roles, roles and subordinates, or public groups.” — Salesforce Help | Criteria-Based Sharing Rules

Why not A (Manual Sharing):Manual sharing requires a user to share each record individually — it is not automated.

Why not B (Owner-Based Sharing Rule):Owner-based rules share records based on who owns them, not on a record field value.

Why not D (Apex Sharing Rule):Apex sharing is used only when declarative sharing rules cannot meet the requirement. In this case, a standard criteria-based rule is sufficient.

References (Salesforce Platform App Builder documentation / Study Guide topics):

Salesforce Help | Sharing Rules Overview

Salesforce Help | Criteria-Based Sharing Rules

Salesforce Platform App Builder Exam Guide | Security

 Apex. This is correct because Apex is a programming language that can perform complex logic and manipulate data in Salesforce. Apex can be used to create a trigger on the opportunity object that copies the value of the billing state from the related account record when the opportunity is created, and prevents it from being changed afterwards. The other options are not suitable for this requirement because they either cannot copy data from a related object (formula field, roll-up summary field) or cannot prevent data from being changed (workflow).

All profiles will get access to the new field by default when it is created using Schema Builder. The app builder can modify the field-level security settings later to restrict access for certain profiles. Standard profiles, no profiles, and internal profiles are not correct options.

The app builder should use the Path feature to provide the functionality that the VP of Sales wants. The Path feature allows an app builder to create a visual representation of the stages in a business process, such as the Opportunity sales process. The app builder can also add key fields, guidance, and resources for each stage to help sales reps gather information and complete tasks4. Option A, C, and D are not features that can provide this functionality.

The two considerations that should be made are: The Star records are all required to have an existing value in their Galaxy field. This is a prerequisite for converting a lookup relationship to a master-detail relationship. A lookup relationship is an optional relationship that links two objects together, but does not enforce referential integrity or cascade delete. A master-detail relationship is a required relationship that links two objects together and enforces referential integrity and cascade delete. To convert a lookup relationship to a master-detail relationship, all child records must have a value in their lookup field that references an existing parent record. The Galaxy object has fewer than two existing master-detail relationships. This is another prerequisite for converting a lookup relationship to a master-detail relationship. An object can have up to two master-detail relationships with other objects and can act as both the parent and child in different relationships. To convert a lookup relationship to a master-detail relationship, the parent object must have fewer than two existing master-detail relationships with other objects. The Galaxy object is required to contain existing roll-up summary fields is not a valid consideration, as it is not related to converting a lookup relationship to a master-detail relationship. 

 The recommended solution to grant the customer service agent access to the field is creating a permission set that allows read-only access to the field via Field Level Security and assigning it to the agent. A permission set is a collection of settings and permissions that give users access to various tools and functions. Field Level Security (FLS) is a setting that controls the access level of fields for different profiles or permission sets. The app builder can create a permission set that grants read-only access to the custom field on the account object via FLS and assign it to the agent. Option B is incorrect because creating a new profile to allow for read-only access to the field via FLS and assigning it to the agent is not recommended, as profiles are used to define the baseline permissions and settings for a group of users, and creating multiple profiles for individual users can be hard to maintain. Option C is incorrect because updating the Customer Service Profile already assigned to the agent to allow for read-only access to the field via FLS is not recommended, as this will affect all users who have the same profile, which may violate the security policy. Option D is incorrect because updating the custom field’s FLS in setup to allow the agent read-only access to the field is not possible, as FLS can only be set at the profile or permission set level, not at the user level.

When creating a new field, if an app builder does not want the field to be automatically added to pre-existing custom report types, the step to take is:

Deselect 'Add Field to Custom Report Types' (D). This option is available when creating or editing a custom field and ensures that the field is not automatically included in report types where 'Automatically add new custom fields to report type layouts' is enabled.

Removing the field from page layouts (A) affects the visibility on record pages but not reports. Adjusting visibility (B) or setting read-only access (C) for report profiles affects user permissions to see the field in reports, but does not remove the field from report types if it was previously added.

Reference for managing fields in custom report types:

Custom Report Types and Fields: https://help.salesforce.com/articleView?id=reports_report_type_layouts.htm &type=5

 Global actions can be accessed anywhere actions are pages, feed and Chatter groups. This is correct because global actions are not tied to a specific object, and they can be added to any page that supports actions, such as record pages, home pages, feed pages, and Chatter groups.

For a formula to evaluate to true when the stage is set to "Negotiation/Review" and the close date is less than one week away, the correct formula is:

Option B. This formula uses the ISPICKVAL function to check the text value of a picklist and compares the CloseDate to a week from today:

AND( I AND(

ISPICKVAL(StageName, "Negotiation/Review"),

CloseDate - 7 < TODAY()

)SPICKVAL(StageName, "Negotiation/Review"), CloseDate - 7 < TODAY() )

This formula checks that both conditions are met: it confirms the stage name is "Negotiation/Review" and that the CloseDate is within the next 7 days from the current date.

Option A lacks the ISPICKVAL function necessary for evaluating picklist fields. Option C uses DAY(7) which is not a valid Salesforce formula expression. Option D also uses DAY(7) incorrectly and fails to use the ISPICKVAL function.

Reference for creating formula fields in Salesforce:

Formula Field Reference: https://help.salesforce.com/articleView?id=sf.customize_functions.htm &type=5

To communicate to the CK web service when a shoe’s inventory has changed, an app builder should use an after-save record-triggered flow. An after-save record-triggered flow is a type of flow that runs after a record is saved and can perform actions such as updating related records, sending emails, calling external services, etc. An after-save record-triggered flow can use an Apex action to invoke a SOAP web service using a WSDL file. [Source]

The "Accordion" Lightning component is designed to break up content into collapsible sections. This component would be suitable for managing the visibility of large numbers of fields by grouping them into separate tabs or sections that can expand and collapse. This makes navigation easier and declutters the interface.

A: Highlights panel is used for displaying key record information at the top of the page and is not designed for managing multiple fields.

B: Record detail displays all fields on a single layout, which does not suit the requirement to break up the fields.

C: Field section does not exist as a standard Lightning component. Reference: Accordion Component in the Lightning Component Library

The setting for the visibility of custom tabs is default off for all users when they are deployed via change sets without including the profile settings or permission sets. This means that the custom tabs are not visible in any apps or navigation menus for any users unless they are manually added by each user or by an administrator3. Option B, C, and D are not correct settings for the visibility of custom tabs.

Dynamic actions are a new feature that allow app builders to create custom buttons or actions that can call Lightning Web Components and display them conditionally based on field values or other criteria. Formula fields, AppExchange products, and custom links are not able to call Lightning Web Components.

The best Lightning component to add to the layout to display the ‘New Task’ custom action is Highlights panel. This component shows key information and actions for a record, such as its name, owner, and custom actions. Related record, related lists, and activities are not Lightning components that display custom actions. See [this article] for more information on Highlights panel.

 The app builder wants to create a formula field on an Account to include data from related Contacts but cannot find the relationship in the formula editor. This limitation occurs because formula fields in Salesforce cannot reference child records directly.

Option A (Unable to reference the child records): In Salesforce, formula fields can reference parent objects but not child objects. In this case, Contacts are child records of Accounts in a lookup relationship, and Account is the parent. This is why the formula editor does not provide access to the child records (Contacts) from the Account.

Formula Field Considerations

Option B (A master-detail relationship should be created): While master-detail relationships allow for roll-up summaries, creating a master-detail relationship is not applicable here since the standard Account-Contact relationship is a lookup, and changing it to master-detail is not possible.

Option C (Formula field limit reached on the Account object): This would limit the number of formulas but is not the root cause of the issue described.

Option D (More than 5,000 characters in the formula): This limit refers to formula field complexity, but it does not explain the inability to reference child records.

In summary, the limitation is due to Salesforce not allowing formula fields to reference child records.

The issue described occurs due to the settings in the master-detail relationship. Specifically:

The Allow reparenting checkbox, Child records can be reparented to other parent records after they are created, is unchecked (B). This setting prevents changing the parent record (contact) of a child record (service plan) once it has been set. If 'Allow reparenting' is unchecked, it restricts the ability to change the associated contact, leading to the issue observed.

The other options do not directly address the inability to change the associated contact on a service plan record. The 'Read Only' and 'Read/Write' settings (A and C) pertain to access rights to the detail records based on the master record's access but do not affect the ability to reparent a record.

For a detailed understanding of master-detail relationships and their settings, including reparenting, see the Salesforce documentation on relationships:

Master-Detail Relationships: https://help.salesforce.com/articleView?id=relationships_considerations.htm &type=5

The app builder needs to do two steps to make the custom Lightning App available to the internal users at Universal Containers:

Create a subdomain using My Domain: My Domain is a feature that allows an organization to set up a custom domain name for their Salesforce instance. This is required to use custom Lightning components and apps in Salesforce1.

Build a Custom Tab for the app: A custom tab is a tab that displays any custom object or web page in Salesforce. This is required to make the custom Lightning App accessible from the navigation menu or app launcher2. Option A and B are not necessary steps to make the custom Lightning App available to the internal users.

Data is unable to be deployed with change sets. Change sets are used to deploy metadata components such as custom objects, fields, workflows, reports, etc. from one Salesforce org to another. However, change sets do not include any data or records from the source org. Users will need to use other tools such as Data Loader or Data Import Wizard to migrate data between orgs. [Source]

Apex unit test failures can cause a package installation to fail. According to the Salesforce documentation, “If your package contains Apex code, all tests must complete successfully for your package to install.” Incorrect license types, package features not compatible, and object limits exceeded are not valid reasons for a package installation failure.

Sales reps are forgetting to manually submit the record for approval. The correct declarative solution is to automate the submission when conditions are met — in this case, when the Opportunity Close Date is pushed more than 30 days.

This can be achieved using Flow Builder or Process Builder (deprecated) to automatically submit the record into the existing approval process.

Why C (Submit the record for approval from an automated process) is correct:Exact Extract:“You can automatically submit a record for approval from a process or flow when specified criteria are met.” — Salesforce Help | Automate Record Approval with FlowThis ensures the approval process runs automatically whenever the rule is triggered, eliminating user dependency.

Why C (Submit the record for approval from an automated process) is correct:Exact Extract:“You can automatically submit a record for approval from a process or flow when specified criteria are met.” — Salesforce Help | Automate Record Approval with FlowThis ensures the approval process runs automatically whenever the rule is triggered, eliminating user dependency.

Why not A:The “API Enabled” permission allows programmatic access; it has no impact on triggering approvals.

Why not B:A validation rule and email alert only notify; they do not submit the record into the approval process.

Why not D:Changing entry criteria doesn’t auto-submit; it only defines which records can enter if submitted.

To ensure that opportunities are submitted into the approval process when their close date is pushed more than 30 days, an app builder should use an automated process to submit the record for approval. An automated process can be created using tools such as Process Builder or Flow Builder, and it can define the criteria and actions for submitting a record for approval. [Source]

 To manually share individual records with specific people or group of people on a case by case basis, users can use public groups, roles, or users. Public groups are collections of users, roles, or other groups that can be used to share access to records. Roles define the level of access that users have to their organization’s data based on their position in the hierarchy. Users are individual people who log in to Salesforce and have access to records based on their profile, role, and sharing settings. 

The app builder should create a master-detail relationship field on the gift card object to support the requirement. A master-detail relationship field creates a parent-child relationship between two objects, where the master record controls certain behaviors of the detail record. In this case, the Account object would be the master and the gift card object would be the detail. By creating a master-detail relationship field, the app builder can meet these requirements:

Track the total number of gift cards opened and gift cards issued on an Account: This can be done by creating roll-up summary fields on the Account object that count or sum up the values from the gift card records related to each account.

Permanently ensure the gift cards are unable to be moved across any other Account once it is created: This can be done by making the master-detail relationship field required on the gift card object, which means that every gift card record must be associated with an account record and cannot be changed once set. Option B, C, and D are not types of fields that can support this requirement.

 The best way to configure Account sharing so that community users only see their own Account is to set the account external OWD to private. This will restrict the access to Account records for external users based on the sharing rules and criteria. Creating an account record type, defining an owner-based sharing rule, or defining a permission set will not prevent community users from seeing other accounts.

The two components that could be included on the layout to display the actions are the Highlights panel and the Path. The Highlights panel is a component that shows key information and actions for a record. It can display up to 10 actions from the Mobile & Lightning Actions section of the page layout. The Path is a component that shows the stages of a process, such as a sales process or a service process. It can display up to 5 actions from the Mobile & Lightning Actions section of the page layout. The Chatter and Activities components do not display actions from the Mobile & Lightning Actions section of the page layout. They display other types of actions, such as posting, commenting, liking, logging a call, creating a task, or sending an email.

The feature that the app builder should use to solve this issue is component visibility filter. A component visibility filter is a setting that can be applied to a Lightning component on a record page to control when the component is hidden or displayed based on certain conditions. The app builder can use a component visibility filter to hide the component from users with a Marketing profile. Option A is incorrect because detail page layouts are not related to Lightning components, but rather the fields and related lists that appear on record detail pages. Option C is incorrect because field-level security is not related to Lightning components, but rather the access level of fields for different profiles or permission sets. Option D is incorrect because AppExchange is not related to Lightning components, but rather an online marketplace where users can find and install apps and components.

The app builder should recommend a workflow rule to automate this process. A workflow rule is a type of automation tool that can execute actions based on certain criteria. In this case, the workflow rule can have a criterion that evaluates if the DoNotCall checkbox is checked on a Contact record, and then execute a field update action that sets the Phone field to null. Option A, B, and C are not automation tools that can perform this task.

 Marking stage dependent fields as required on the Opportunity page layout is a good solution to improve efficiency and data quality, as it ensures that users enter the necessary information for each stage of the sales process. Adding a Path component with fields and instructions aligning to stages on the Opportunity is another good solution to improve efficiency and collaboration, as it provides guidance and best practices for users to move the Opportunity along the sales cycle. Using two Tabs components to separate record information from activities may not be an optimal solution, as it may reduce the visibility and accessibility of important data. Setting up an approval process requiring manager consent at each stage of the Opportunity may not be a feasible solution, as it may introduce unnecessary delays and complexity in the sales process

The app builder should create a new roll-up summary field called First Order Date, using Type MIN on the Opportunity Close Date with a filter where IsWon = TRUE. A roll-up summary field is a type of field that calculates values from related records and displays them on the parent record. In this case, the app builder can create a roll-up summary field on the Account object that calculates the minimum (earliest) value of the Opportunity Close Date field from the related opportunities where IsWon = TRUE. This will show when customers made their first purchase. Option B, C, and D are not correct ways to use a roll-up summary field to meet the requirement.

 A formula field cannot be referenced by a roll-up summary field if it contains a cross-object field reference or a time-based function. A cross-object field reference is a reference to a field from a different object, such as Account. Name on a Contact object. A time-based function is a function that returns the current date or time, such as NOW() or TODAY(). Option A and C do not prevent a formula field from being referenced by a roll-up summary field.

The Twitter component is a standard Lightning component that can be added to mobile view Lightning pages using the Lightning App Builder. It displays a contact’s Twitter profile and recent tweets

For an app builder who needs to ensure all fields from the page layout are visible on a Lightning Record Page after using the Lightning Object Creator, the correct component to use is:

Record Detail (C). The Record Detail component automatically displays all fields that are included on the assigned page layout for the object. It is designed to reflect the layout configuration and is the simplest way to ensure all fields are presented as configured in the layout editor.

Highlights Panel (A) is used primarily to display key fields at the top of the record page, providing a summary view rather than full field visibility. Recommendations (B) is used for displaying prompts or suggestions and does not display record fields. Path (D) is useful for displaying stages in a process (like sales stages or service processes) and does not show field data directly.

Reference for setting up Lightning Record Pages and using components effectively:

Lightning Record Pages: https://help.salesforce.com/articleView?id=sf.lightning_page_components.htm &type=5

Updating the account search layouts search results columns displayed and updating the account search filter fields can improve an end user’s search experience by showing more relevant information and allowing more refined filtering. The view filter settings and the accounts tab columns displayed are not related to the search functionality

The inability to create a Roll-Up Summary field in this context can be attributed to:

B. The organization has Advanced Currency Management enabled. When Advanced Currency Management (ACM) is enabled, it affects how currency data is managed and aggregated, impacting the functionality of roll-up summary fields that involve currency amounts across different records.

To address this limitation, consider using custom reporting or a custom solution like a trigger or a scheduled batch class to manually calculate and update the total.

For more information on limitations with ACM, consult Salesforce's help article on Advanced Currency Management.

To manage frequently changing picklist values effectively:

B. Set up Global Values in Picklist Value Sets. This approach allows for centralized management of picklist values that can be reused across multiple fields and objects. By using global value sets, inactive values can be efficiently managed and deactivated without impacting fields that use these sets.

For further information on managing picklists, check Salesforce's Picklist Management guide.

The best practice that the app builder should follow when building out automation is one record change process per object. A record change process is a type of process in Process Builder that starts when a record is created or updated. Having one record change process per object can avoid conflicts or errors when multiple processes try to update the same record at the same time. Option A is incorrect because one workflow rule per object is not a best practice, as workflow rules are considered legacy tools and have limitations compared to Process Builder. Option B is incorrect because one flow per object is not a best practice, as flows are more complex and require more resources than processes. Option C is incorrect because one invocable process per object is not a best practice, as invocable processes are used to invoke other processes from within a process or a flow.

To allow users access to Flows, Salesforce offers multiple integration points:

A. Quick Action: Flows can be initiated from record pages, the app utility bar, or global actions using Quick Actions. This allows users to execute flows relevant to specific records or global processes.

C. Flow Launcher: A component available in Lightning App Builder that enables users to start flows directly from a Lightning page.

Steps to set up these features:

For Quick Actions, navigate to Setup → Object Manager → select object → Buttons, Links, and Actions → New Action → Action Type (Flow).

For Flow Launcher, navigate to Lightning App Builder → select the page → drag the Flow component to the desired section of the page → configure it to launch the specific flow.

For more information on integrating Flows, check the Salesforce documentation on Flow Distribution.

The solution that the app builder should use to meet DreamHouse Realty’s needs is Master-Detail Child Object. A master-detail relationship can be used to create 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 roll-up summary field on the parent object to calculate the highest value of all child records. Option B is incorrect because Text Area (Long) is a field type that allows users to enter up to 131,072 characters on one line, which is not suitable for this requirement. Option C is incorrect because Multi-select Picklist is a field type that allows users to select multiple values from a predefined list, which is not suitable for this requirement. Option D is incorrect because Lookup Object is not a valid term, but rather Lookup Relationship, which is a type of relationship that links two objects together, but does not support roll-up summary fields.

To automate the submission of opportunities into the "Secure Commitment" stage and eliminate manual submission for approval, the best feature to use is:

Record-Triggered flow optimized for Actions and Related Records (D). This type of flow allows for complex automation that can include submitting records for approval based on specific criteria being met, such as reaching a particular stage in the opportunity lifecycle. It's particularly suitable for handling related record updates and other actions like submissions for approval, which are integral when an opportunity reaches a certain stage.

Record-Triggered Flow optimized for Fast Field Updates (A) is focused primarily on quick updates to fields and may not handle the complexity of submission for approval processes adequately. Custom button and screen flow (B) could be used to manually trigger processes but does not automate the submission. Platform Event-Triggered flow (C) is typically used for integrations and reacting to system-wide events, not for standard record lifecycle management.

Reference for using Flows in Salesforce, particularly for automating business processes like approval submissions:

Record-Triggered Flows: https://help.salesforce.com/articleView?id=sf.flow_considerations_trigger_record.htm &type=5

The solution that an app builder should use for this request is a lookup field. A lookup field is a type of relationship field that links two objects together and allows users to select a record from another object. The app builder can create a lookup field on the account object that references the user object and allows users to assign a customer service manager (CSM) to the account. Option A is incorrect because a multi-select picklist field is not suitable for this request, as multi-select picklist fields allow users to select multiple values from a predefined list, not from another object. Option B is incorrect because a picklist field is not suitable for this request, as picklist fields allow users to select one value from a predefined list, not from another object. Option D is incorrect because a text field is not suitable for this request, as text fields allow users to enter any alphanumeric characters, not from another object.

 One of the easiest ways to display real-time stock price for each account is to install a solution from the AppExchange, such as Stock Price Lightning Component3. This component can be added to any record page using the Lightning App Builder.

To import leads while preventing duplicates:

B. Data Import Wizard is the appropriate tool. The Data Import Wizard in Salesforce includes functionality to check for duplicates based on matching records by certain criteria (like email or lead ID) during the import process, thus preventing duplicate lead records from being created.

More details on using the Data Import Wizard can be found in the Salesforce Data Import Wizard guide.

Sharing rules can be used to extend access to records owned by certain users or roles to other users or roles. In this case, a sharing rule can grant read-only or read/write access to sales-owned accounts to the marketing team

Create a master-detail relationship field on Applicant__c to Application__c is what the app builder should recommend to meet the requirements of allowing the same applicant to apply for multiple open positions using a single application. This will create a many-to-many relationship between Applicant__c and Open_Position__c using Application__c as a junction object. Create a master-detail relationship on Open_Position__c to Application__c, create a master-detail relationship field on Application__c to Open_Position__c, and create a lookup relationship field on Applicant__c to Application__c are not valid or correct ways to create a many-to-many relationship.

 A custom button, a validation rule, and record types can be used to meet the requirement of hiding the convert button on leads until the lead status picklist is set to qualified. The custom button can replace the standard convert button and invoke a validation rule that checks the lead status. The record types can be used to assign different page layouts with different buttons for different lead statuses

To start tracking how many shoe subscriptions have been sold for each shoe catalog, a roll-up summary field should be created. A roll-up summary field calculates values from related records on a master-detail relationship. It can count, sum, min, or max numeric values from child records on a parent record. 

The best choice for capturing geographic location data, such as crossroads or location markers provided by customers, is the Geolocation field type. This field type stores latitude and longitude data, allowing accurate pinpointing of locations on a map. Geolocation fields are suitable for any application that needs to handle coordinates for mapping and proximity calculations.

A: Number field is not specific enough for geographical coordinates.

C: Reference fields link to other records, not geographical data.

Workflow rule and an outbound message or Process Builder and Apex Code are two ways to integrate Salesforce with an external web service. Workflow rule can define criteria and actions for triggering an outbound message, which is an XML message sent to a designated endpoint URL. Process Builder can invoke Apex Code, which is a programming language that can make callouts to external web services using HTTP requests. Flow Builder and an outbound message or Process Builder and an outbound message are not possible combinations.

The best solution to create a report to compare the number of support cases in each status and by priority is to use grouping. Grouping allows the app builder to summarize data by one or more fields, such as status and priority, and display them in rows and columns. Grouping also enables the app builder to use different chart types, such as stacked bar charts or matrix charts, to visualize the data. Bucket columns are not a suitable solution, as they are used to categorize data into predefined groups, such as high, medium, or low. Custom report types are not a suitable solution, as they are used to define the objects and fields available for a report, not how to display them. Filters are not a suitable solution, as they are used to limit the data shown in a report based on certain criteria, not how to compare them

The app builder should use Web-to-Case to enable visitors to the website to open cases. Web-to-Case is a feature that allows users to create an HTML form that can be embedded into a public-facing website. When visitors fill out and submit the form, a new case is automatically created in Salesforce with the information from the form fields. Web-to-Case can also assign cases to queues or users based on predefined rules and criteria. Outbound message is not a valid tool, as it does not enable visitors to open cases. An outbound message is a type of workflow action that sends a secure XML message to a designated endpoint URL when a record meets certain criteria. An outbound message can be used to integrate Salesforce with external systems or applications. Screen flow is not a valid tool, as it does not enable visitors to open cases from a public-facing website. A screen flow is a type of flow that allows users to create an interactive guided process that can collect, display, and update data from multiple objects within Salesforce. A screen flow can be embedded into Lightning pages or Visualforce pages, but it cannot be exposed to unauthenticated users on a public website. Email-to-Case is not a valid tool, as it does not enable visitors to open cases from a website. Email-to-Case is a feature that allows users to create cases from email messages sent to a specific email address. Email-to-Case can also capture email attachments and thread information and associate them with the case.

It lacks setting up field-level security and adding fields to the page layout, so you have to choose the manual way of field creation. Adds another layer of risk with changes in Schema Builder since it is deployed in real-time.

Salesforce Schema Builder is a powerful tool for visualizing and creating objects, fields, and relationships in Salesforce, but it has certain limitations when building custom objects.

Option B (Fields and relationships can be created, but they will be unable to add the fields to the page layout from the canvas): In Schema Builder, while you can create new custom objects, fields, and relationships, you cannot directly add fields to the page layout from within the Schema Builder interface. After creating a field, you need to navigate to the Page Layout Editor to manually place the new field on the layout.

Schema Builder Overview

Option A: This is incorrect because you can perform multiple actions within Schema Builder without needing to click Save each time. Salesforce will save these changes when you click Save once at the end.

Option C: While relationships can be created in Schema Builder for both standard and custom objects, there is no requirement to use Lightning Object Manager to create relationships with standard objects.

Option D: Schema Builder supports the creation of formula fields along with other types of fields. There is no exclusion for formula fields.

In summary, Option B is the correct limitation of Schema Builder: you cannot add fields to page layouts directly from the Schema Builder interface.

For Universal Containers to understand the return on investment (ROI) for their latest advertising buy while using a private security model, the best recommendation is to use Campaign Hierarchies and Campaign statistics.

Campaign Hierarchies and Campaign Statistics: Campaign hierarchies allow Universal Containers to track the effectiveness and ROI of marketing efforts by grouping related campaigns (e.g., advertising buys) under a parent campaign and rolling up key metrics like responses, converted leads, and won opportunities. Campaign statistics provide detailed insights into individual and aggregate campaign performance, helping calculate ROI.

This method works well within a private security model since it respects existing sharing rules and access controls, ensuring that only authorized users can see the campaign data.

Campaign Management Overview

Option A (Account Hierarchies and Roll-Up Summary fields): Account hierarchies and roll-up summary fields focus on aggregating account-level data, which doesn’t directly support measuring the ROI of advertising campaigns.

Option B (Opportunities Pipeline Report): While an opportunities pipeline report can provide insights into sales, it doesn’t track campaign-related data or advertising ROI directly.

Option C (Change to a Public Security Model): Changing to a public security model isn’t necessary and could expose sensitive data. Campaign hierarchies and statistics work well with a private security model.

In summary, Campaign Hierarchies and Campaign Statistics are the recommended approach to track the ROI of advertising buys.

When multiple objects require the same picklist values, the correct approach is to create a Global Picklist Value Set (also called a Global Value Set). This allows an organization to maintain one centralized list of picklist values that can be reused across multiple picklist fields on different objects.

Why C is correct:Exact Extract:“Global value sets let you share the same picklist values with more than one picklist field. A global value set is a set of shared values that you define once and use in multiple custom picklist fields.” — Salesforce Help | Global Value SetsThis ensures consistent data values, simplifies maintenance, and makes changes automatically available wherever the global picklist is used.

Why C is correct:Exact Extract:“Global value sets let you share the same picklist values with more than one picklist field. A global value set is a set of shared values that you define once and use in multiple custom picklist fields.” — Salesforce Help | Global Value SetsThis ensures consistent data values, simplifies maintenance, and makes changes automatically available wherever the global picklist is used.

Why not A (Related Picklist):“Related Picklist” is not a valid Salesforce feature.

Why not B (Shared Custom Field):Salesforce does not provide a “Shared Custom Field” functionality. Each field belongs to a specific object.

Why not D (Dependent Picklist):Dependent picklists control available values based on another field’s value. They do not allow reuse of a single value list across multiple objects.

References (Salesforce Platform App Builder documentation / Study Guide topics):

Salesforce Help | Global Value Sets

Salesforce Help | Picklist Fields

Salesforce Platform App Builder Exam Guide | Data Modeling and Management

To restrict visibility of the Jupiter field on the Solar System object specifically to users with the Outer Planets profile:

C. Field-level security (FLS). This allows the app builder to control access to fields based on user profiles.

Steps to set up field-level security:

Navigate to Setup → Object Manager → Solar System.

Select Fields & Relationships → Jupiter field.

Click Field-Level Security.

For all profiles except Outer Planets, set the Visible option to unchecked, ensuring these users cannot see the field.

For the Outer Planets profile, check Visible to grant access.

This configuration ensures that only users with the Outer Planets profile can view the Jupiter field.

For more information on field-level security, check Salesforce's guide on Field-Level Security.

The app builder should verify that there is an Apex test that provides test coverage for the Flow. An Apex test is a unit test that verifies the functionality and quality of Apex code. Apex tests are required to deploy any change that contains Apex code or references Apex code, such as an auto launched flow3. The app builder should ensure that there is an Apex test that covers at least 75% of the Flow logic before deploying it to production in an active state4. Option B, C, and D are not things that the app builder should take into consideration when planning the deployment.

Set up a delegated approver for the manager is the recommended solution to ensure all of the appropriate deals are reviewed and the leaderboard is up to date. According to the Salesforce documentation, “A delegated approver can approve records that are submitted for approval by users below them in the role hierarchy.” Forwarding the approval request to the manager’s assistant, having the manager log on and reassign the approval request, and using Process Builder to assign a delegated approver are not valid or feasible options.

To troubleshoot the issue of a contact being unavailable for other users to see, an app builder should check the following things:

Confirm whether Default Organization-Wide Sharing Settings provide access to the Account. This setting determines the baseline level of access that users have to each other’s records.

Review the Contact record and ensure it is linked to an Account. Contacts that are not linked to an account are private and only visible to the owner and administrators.

Verify the users with the issue have access to the Contact object. Users need to have at least read permission on the Contact object to view contact records. Option A and E are not relevant for troubleshooting this issue.

Opportunities are in a master-detail-like relationship with Accounts (standard lookup behaves with special roll-up capabilities). Salesforce provides a standard roll-up summary feature on the Account object to count related Opportunities.

Why B (Roll-up Summary) is correct:Exact Extract:“Use a roll-up summary field to automatically display a value from related detail records on a master record. You can count related records, or calculate the sum, min, or max of a field on those records.” — Salesforce Help | Roll-Up Summary FieldsOn Account, you can create a roll-up summary field to COUNT related Opportunities.

Why B (Roll-up Summary) is correct:Exact Extract:“Use a roll-up summary field to automatically display a value from related detail records on a master record. You can count related records, or calculate the sum, min, or max of a field on those records.” — Salesforce Help | Roll-Up Summary FieldsOn Account, you can create a roll-up summary field to COUNT related Opportunities.

Why not A:Formula fields cannot count related records.

Why not C:AppExchange is not required; Salesforce provides native functionality.

Why not D:A lookup only links records—it does not perform aggregation.

 NOT(ISBLANK(Job_Accepted__c)) && ISCHANGED(Hire_Date__c) is the validation formula that the app builder should use to meet the requirement of preventing changes to Hire Date after Job Accepted is entered. This formula will return TRUE if Job Accepted is not blank and Hire Date is changed, which will display an error message and prevent saving the record. The other formulas are not correct or valid.

Guided Action Flows on the record page can help service agents meet the requirement of confirming a user identity before providing support information over the phone. Guided Action Flows are a series of screens that guide agents through a predefined process, such as verifying user information, collecting case details, or resolving issues

The best way to show Asset Inventory as a related list on Asset is to create a lookup relationship on Asset Inventory to Asset. This will allow one-to-many relationship between Asset and Asset Inventory, and display the related records on the Asset page layout.

To connect Testimonial__c records with both the submitter’s Contact record and Account record, an app builder should create a master-detail relationship from Testimonial__c to Account and a lookup relationship from Testimonial__c to Contact. A master-detail relationship creates a parent-child relationship between two objects and allows for roll-up summary fields, sharing settings, and cascading actions. A lookup relationship creates a loose association between two objects and allows users to relate records from one object to another. Source

 The app builder should use three features to meet the business requirements:

Process Builder: This is a type of automation tool that can execute actions based on certain criteria. In this case, the process builder can have a criteria that evaluates if an opportunity is in the Secure Commitment Stage, and then execute an action that submits it for approval.

Apex: This is a programming language that allows developers to execute complex logic on the Salesforce platform. Apex can be used to create triggers that run before or after certain events, such as insert, update, delete, or undelete of records. In this case, Apex can be used to create a trigger that runs before an opportunity is updated and submits it for approval if it is in the Secure Commitment Stage.

Flow: This is another type of automation tool that can guide users through a series of screens and perform actions based on user input. Flow can also be triggered by certain events, such as when a record is created or updated. In this case, Flow can be used to create a record-triggered flow that runs after an opportunity is updated and submits it for approval if it is in the Secure Commitment Stage. Option A and D are not features that can meet the business requirements.

TEXT() is a formula function that converts a picklist value to text. This can be used to display the Type field from the parent object Galaxy on the child record Star. ISPICKVAL() is used to check if a picklist value is equal to a specified value. VALUE() is used to convert text that represents a number to a number. FIND() is used to locate one text string within another text string.

The feature that can be used to meet these requirements is two-step approval process. An approval process defines the steps and criteria for approving records. A two-step approval process requires two levels of approval before a record can be deleted. The app builder can configure an approval process for opportunities that requires sales reps to submit their delete requests for approval from their managers. Option A is incorrect because Process Builder with Submit for Approval action is not a valid feature, as Process Builder cannot submit records for approval. Option B is incorrect because Approval Process with a triggered Flow process is not a valid feature, as Approval Process cannot trigger Flow processes. Option C is incorrect because Approval Process with Time-Dependent Workflow action is not a valid feature, as Approval Process cannot use Time-Dependent Workflow actions.

 Groups is available in the Chatter section of the navigation menu, not in the selected list for the navigation menu. According to the Salesforce documentation, “Groups appear in Chatter, not in Navigation Menu.” Groups is not available in the recent section of the navigation menu, nor is it included in the Smart Search items but unavailable on the navigation menu. Groups is unavailable in the selected list for the navigation menu.

The solution that the app builder should configure to meet these requirements is creating three lead record types each with its own page layout containing the relevant fields. This way, the app builder can customize the fields and sections that appear on each record type based on the source of the lead. Option B is incorrect because creating a partner community and a record type for web and trade show leads does not address the requirement of collecting information that is unique to each type of lead, as partner community users may have different fields and layouts than internal users. Option C is incorrect because creating three sections on the lead layout and instructing users to collapse the non-relevant fields does not address the requirement of collecting information that is unique to each type of lead, as users may still see or enter data in the wrong fields. Option D is incorrect because creating custom page layouts for each type of lead only containing the relevant fields does not address the requirement of collecting information that is applicable to all sources, as users may miss some common fields.

Schema Builder is a tool that presents a comprehensive view of all relationships in one place. It allows app builders to see how objects are connected and create new relationships. Lightning Object Creator, Object Manager, and Lightning Record Page are not tools for viewing relationships, but for creating objects, managing fields, and customizing record pages respectively.

A report type that is in a status of In Development is not available for users to select when creating a new report. The app builder needs to change the status to Deployed to make it visible to users

 The best feature to use to ensure consistent case priority entry is Path. Path allows users to see key fields and guidance for each stage of a process, such as a case lifecycle. Path can also enforce data quality by making certain fields required at each stage. See [this article] for more information on Path.

Roll-up summaries allow MAX, MIN, SUM, COUNT, and AVG functions on numeric fields from child records related by a master-detail relationship. Roll-up summaries are limited to master-detail relationships and cannot be used with lookup relationships. An object can have up to 40 roll-up summary fields, not 25. An object can have up to 25 relationship fields (master-detail or lookup), not 20.

All data should be backed up before converting a text field to a picklist, as some data may be lost or truncated during the conversion. Changing a field type will remove existing field history, as the history tracking values are not converted

Polls and Out of Office are two ways that CK can use Chatter to gather feedback and understand availability. Polls allow users to create surveys and collect opinions from other users. Out of Office lets users set a status message and an end date to inform others when they are away or busy. Streams and Topics are not related to the problem.

The requirement is to copy the parent Account’s Billing State onto a custom field on Opportunity at the moment the Opportunity is created, and keep that value static thereafter.

Why not Formula (B): A formula would always recalculate, so the value would change if the Account’s Billing State later changes.Exact Extract: “Formula fields are read-only fields that automatically recalculate their values when any referenced fields change.” — Salesforce Help | Formula Fields

Why not Roll-Up Summary (A): Roll-up summary fields only summarize child records onto a master (parent) record; they do not copy values from a parent (Account) down to a child (Opportunity), and they can’t summarize a text/state value.Exact Extract: “A roll-up summary field calculates values from related records, such as those in a related list, on a master record.” — Salesforce Help | Roll-Up Summary Fields

Why Flow (C) is correct: A Record-Triggered Flow on Opportunity (when a record is created) can set a field value by referencing the related Account (e.g., Opportunity.Account.BillingState) and writing it into a dedicated “snapshot” field (e.g., Billing State at Create__c). Because this is a one-time assignment on create, the value remains static unless intentionally updated by further automation.Exact Extract 1: “Use Flow Builder to automate business processes by collecting data and performing actions in your Salesforce org.” — Salesforce Help | Flow BuilderExact Extract 2: “Record-triggered flows launch when a record is created, updated, or deleted, and can update fields on the triggering record.” — Salesforce Help | Record-Triggered Flows

Why Apex (D) is not preferred: While Apex could do the same copy-on-create, Salesforce’s recommended approach is to use declarative automation (Flow) when possible.Exact Extract: “Before considering Apex, evaluate whether your solution can be implemented with declarative tools such as Flow.” — Salesforce Architect Guidance | Clicks, Not Code

Implementation note (for clarity): Create a custom text field on Opportunity, e.g., Billing State at Create (Billing_State_at_Create__c). Build a Record-Triggered Flow:

Trigger: Opportunity — “A record is created”

Get or use the related Account from the $Record.AccountId relationship

Update the new Opportunity field with Account.BillingState

Do not run the flow on updates

References (Salesforce Platform App Builder documents / Study Guide topics):

Salesforce Help — Formula Fields

Salesforce Help — Roll-Up Summary Fields

Salesforce Help — Flow Builder

Salesforce Help — Record-Triggered Flows

Salesforce Architect Guidance — Clicks, Not Code

Salesforce Platform App Builder Exam Guide — Business Logic and Process Automation

Historical data will be updated to 12:00 timestamp when changing a Date field to Date/Time field. According to the Salesforce documentation, “When you convert a Date field to Date/Time, Salesforce appends “12:00” to existing data in your records.” The change will not be instant, but will require some time for processing. The field name will not change unless specified by the app builder. Data loss will not be experienced, but data accuracy might be affected.

Send an email alert, update a related record, and create a child record are three capabilities of Process Builder that can improve productivity for the sales team. Process Builder can automate these actions based on criteria or events that occur on records or objects. Send an outbound message and delete a related record are not capabilities of Process Builder, but of other tools such as Workflow Rules or Apex.

To deploy a new account detail page layout from sandbox to production, an app builder should include three components in the change set:

Detail page layout: The page layout defines the arrangement of fields, buttons, related lists, and other components on a record detail or edit page. It also controls which fields are required or read-only for users. Source

Custom fields: Custom fields are fields that are created by users to store additional information on standard or custom objects. Custom fields can have different data types, such as text, number, date, picklist, etc. Source

Custom actions: Custom actions are actions that are created by users to extend the functionality of standard or custom objects. Custom actions can be global or object-specific, and they can invoke different tools such as Lightning components, Visualforce pages, flows, etc. [Source]