Universal Containers (UC) delivers purchased containers to remote construction sites. Customers supply UC with crossroads or location markers.
Which field type should the app builder use to capture this information?
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.
Universal Containers (UC) needs a picklist field called Status on three separate custom objects. UC has a requirement to share the list of values for this field across each object.
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.
Reference (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
Universal Containers (UC) utilizes two custom picklist fields called sales_Organization__c and Pricing_Tier__c.
Which validation rule should an app builder use to ensure pricing_Tier__c is required for customers with a Sales_Organization__c value of Canada?
A.

B.

C.

D.

Ursa Major Solar wants to provide sales console users with an Incredible experience, with the most-used components easily accessible at all times.
What solution can enable reps to see and access these components from anywhere within the app without leaving the pages where the team is working?
The best solution to enable reps to see and access the most-used components from anywhere within the app without leaving the page they are working on is Utility bar. This is a footer that can be added to any Lightning app and can contain tools such as history, notes, or softphone. Favorites, home page, and global actions are not solutions that provide access to components from anywhere within the app. See [this article] for more information on Utility bar.
An app builder is tasked with adding key performance indicators on client pages. They want to see a summary of the number of open Opportunities and the number of won Opportunities for each Account.
Where should the app builder go to build these new rollups?
The app builder should go to the Account object to build these new rollups. A roll-up summary field is a type of field that can aggregate numeric values from child records related to a parent record by a master-detail relationship. The app builder can create two roll-up summary fields on the Account object that count the number of open Opportunities and the number of won Opportunities related to each Account. Lightning App Builder is not a place where the app builder can build these new rollups. Lightning App Builder is a tool that allows the app builder to customize the layout and components of Lightning pages, such as record pages, home pages, or app pages. It cannot create new fields or relationships on objects. Lightning Object Creator is not a place where the app builder can build these new rollups. Lightning Object Creator is a tool that allows the app builder to create custom objects from spreadsheet data by uploading a file and mapping columns to fields. It cannot create roll-up summary fields or relationships on existing objects. Opportunity object is not a place where the app builder can build these new rollups. The Opportunity object is the child object in the relationship with the Account object, and roll-up summary fields can only be created on the parent object.
Hollis
6 days agoEmeline
13 days agoEmmett
21 days agoCaren
28 days agoMarsha
1 month agoChaya
1 month agoGlendora
2 months agoTrina
2 months agoAliza
2 months agoWillard
2 months agoShannon
3 months agoPaulene
3 months agoJamal
3 months agoNa
3 months agoFloyd
4 months agoNaomi
4 months agoShizue
4 months agoMalinda
4 months ago