Universal Containers has a single Contact Lightning record page. A component takes up a lot of room on the page and is NOT needed by users with a Marketing profile.
What should the app builder use to solve this Issue?
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.
Northern Trail Outfitters wants to initiate a daily backup of its Salesforce org.
Which tool should an app builder recommend for this task?
Data Export Service is the appropriate tool for initiating scheduled or immediate backups of Salesforce data. References:
Salesforce Help - Data Export Service
Universal Containers (UC) has several picklist fields on the Account object whose values are routinely modified to meet changing business requirements. Due to
these revolving changes, UC has a high number of inactive picklist values that are impacting system performance and user experience.
What can the app builder do to alleviate this issue?
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.
At Universal containers, all US Sales reps should be able to view the US Team dashboard, however, only the US sales directors should be able to see the data in the component and view its source report. How can an app builder ensure the proper access is granted?
Sharing the dashboard folder with roles and subordinates of the US Sales Director and sharing the report folder with the role of US Sales Director will ensure that only the US sales directors can see the data in the component and view its source report, while all US sales reps can view the US Team dashboard. Making the US Sales Director the running user will show only his or her data in the component, not the whole team's data. Making the dashboard dynamic will show different data depending on who is viewing it, not based on their role. Sharing the dashboard with the public group US Sales Reps and sharing the dashboard source reports folder with the US Sales Director profile will not prevent other profiles from accessing the reports if they have access to the report folder.
Ursa Major Solar wants to create a relationship between the standard Contact object and a custom Solar Project object Contacts potentially be related to multiple Solar Project objects, and a Solar Project can have multiple Contacts associated with it.
How should an app builder configure the data model?
Two Master-detail relationships on a new custom object is how an app builder should configure the data model to create a relationship between Contact and Solar Project objects where each Contact can be related to multiple Solar Project objects, and each Solar Project can have multiple Contacts associated with it. This is an example of a many-to-many relationship that requires a junction object with two master-detail relationships. One Master-detail relationship on Contact and one Master-detail relationship on Solar Project, two Lookup relationships on a new custom object, and one Lookup relationship on Contact and one Lookup relationship on Solar Project are not valid or correct ways to create a many-to-many relationship.
