Universal Containers has a custom picklist called Support Level on the Account object. They would like to show the real-time value of Support Level on all case records.
How should an app builder implement this requirement?
Answer : A
The best way to implement this requirement is to create a formula field on the Case object using the TEXT function. A formula field can display the value of another field from a related object, such as the Account object. The TEXT function can convert a picklist value into text, which can be displayed on the Case record. Creating a formula field on the Account object using the ISPICKVAL function is not a valid solution, as it does not show the value of Support Level on the Case record. The ISPICKVAL function is used to check if a picklist field has a certain value, not to display it. Creating a Process Builder and using a field update on the Case object is not an optimal solution, as it requires more configuration and maintenance than a formula field. A Process Builder may also introduce delays or errors in updating the field value. Creating a roll-up summary field using Support Level on the Account object is not a valid solution, as it does not show the value of Support Level on the Case record. A roll-up summary field is used to aggregate numeric values from child records, not to display picklist values.
Universal Containers has a Lightning record page that supports both the mobile app and desktop. An app builder has downloaded a custom Lightning component from AppExchange, but users are unable to view the component on mobile devices.
What can be the issue?
Answer : B
The most likely reason why users are unable to view the custom Lightning component on mobile devices is that the component has been developed for Desktop Pages only. Some components are not supported on mobile devices or have different behavior on mobile devices. An app builder should check the component documentation or metadata to see if it is compatible with mobile devices.
Universal Container wants customers to be able to open cases from a public-facing website.
What should the app builder use to enable visitors to the website?
Answer : B
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.
Cloud Kicks wants to know the total value of all won Opportunities for Accounts and display it on the record.
What type of summary should the app builder use in the roll-up summary field?
Answer : C
The app builder should use Sum as the type of summary in the roll-up summary field. A Sum type of summary allows the app builder to calculate the total value of a numeric field from the child records related to a parent record by a master-detail relationship. The app builder can create a roll-up summary field on the Account object that sums the Amount field from the won Opportunities related to each Account. Count is not a valid type of summary, as it does not calculate the total value of a numeric field. A Count type of summary allows the app builder to count the number of child records related to a parent record by a master-detail relationship. Max is not a valid type of summary, as it does not calculate the total value of a numeric field. A Max type of summary allows the app builder to display the largest value of a numeric or date field from the child records related to a parent record by a master-detail relationship. Min is not a valid type of summary, as it does not calculate the total value of a numeric field. A Min type of summary allows the app builder to display the smallest value of a numeric or date field from the child records related to a parent record by a master-detail relationship.
Universal Containers (UC) has created 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.
Which feature would an app builder use?
Answer : B
The app builder should use a global picklist value set to share the list of values for the Status field across each object. A global picklist value set is a set of values that can be used by multiple picklist fields on different objects. This can ensure data consistency and reduce maintenance efforts. Option A, C, and D are not features that can share picklist values across objects.
How should an app builder configure access to a contact's Twitter profile for Salesforce mobile app users?
Universal Containers uses a private sharing model on Accounts. User A and user B both own Accounts of their own and have both been sent a new account record in an email owned by user C to take a look at. User A is able to open and view the record but user B receives an insufficient privileges error. User A and user B have the same role in the role hierarchy as user.
What are the three reasons user A has access but user B is unable to access the record? Choose 3 answers
Answer : A, C, E
The three reasons user A has access but user B is unable to access the record are:
User A is on the same account team as user C. Account teams are groups of users who work together on an account. Users who are on an account team can have access to the account and related records owned by other team members.
User C has manually shared the record with user A. Manual sharing is a way of granting access to individual users or groups by the record owner or someone above them in the role hierarchy.
User A is in a public group that has access via a sharing rule. Public groups are groups of users who can be used to share data or assign permissions. Sharing rules are automatic rules that grant access to groups of users based on certain criteria. Option B and D are not reasons for user A's access.