Platform-App-Builder Exam Dumps - Salesforce App Builder Questions and Answers

Two reasons that can prevent an app builder from adding a custom component to the Lightning home page are if My Domain is not deployed, or if the component is tagged for record pages instead of home pages. My Domain must be deployed to add custom components to the page with the App Builder, as it enables Lightning components and other features. The component must be tagged for home pages in its configuration file, otherwise it will not show up in the App Builder for home pages

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.

AppExchange is a marketplace where app builders can find prebuilt resources to help with migration and adoption projects. AppExchange offers apps, components, solutions, and consulting services that can assist with moving from Classic to Lightning Experience. Import Wizard, Lightning Object Creator, and Flow Builder are not sources of prebuilt resources, but tools for data import, object creation, and automation respectively.

The solution that should meet this requirement is updating the support team profile to remove the Bronze record type. This way, the support team users will not be able to create new cases with the Bronze record type, as it will not appear in their record type selection list. Option A is incorrect because updating the organization-wide defaults to private for Case does not affect the record type availability, but rather the record access level. Option C is incorrect because creating permission set group for Case that includes Platinum and Diamond record types does not prevent the support team users from creating new cases with the Bronze record type, as they may still have access to it through their profile. Option D is incorrect because making the record type hidden to support users and updating sharing roles to private does not prevent the support team users from creating new cases with the Bronze record type, as they may still have access to it through their profile.

The common items that can be moved using a change set are custom object, Apex class, and custom field. These are metadata components that can be deployed from one environment to another using change sets. Web-to-lead and standard fields are not metadata components that can be moved using change sets.

 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. 

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.

 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.

The app builder should use the CASESAFEID(Id) formula to create this new field. The CASESAFEID function returns the 18-digit case-insensitive version of the record ID, which is unique for each record in Salesforce. The 18-digit record ID is useful for exporting data to external systems that require case-sensitive IDs1. Option A, C, and D are not formulas that can return the 18-digit record ID.

This formula concatenates the four custom fields for the Galactic Vendor’s location into a single text value, separated by commas and spaces. The formula also uses the BR function to insert a line break after the second field, creating two lines of text. Option A, B, and D are not formulas that fulfill the requirement.