Universal Containers generates leads from three different sources: web, trade shows, and partners. Some of the information collected is applicable to all sources, there is also information that is unique to each type of lead. What should an app builder configure to meet these requirements?
A. Create three lead record types each with its own page layout containing the relevant fields
B. Create a partner community and a record type for web and trade show leads
C. Create three sections on the lead layout and instruct users to collapse the non-relevant fields
D. Create custom page payouts for each type of lead only containing the relevant fields
Explanation: 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.
Ann app builder has been to display an overdue date that is two months after a tasks due date. Which approach should the app builder take?
A. Use process builder and set overdue date equal to Due Date + ((365/12)*2)
B. Create a formula field using Due Date + 60
C. Use process builder and set overdue Date equal to Due Date + 60
D. Create a formula field using the ADDMONTHS () function
Explanation: The best way to calculate an overdue date that is two months after a task due date is to use a formula field with the ADDMONTHS() function. This function adds a specified number of months to a date value, and returns a new date value. See [this article] for more information on formula fields.
Containers have the Account object's Organization-Wide Default set to Private. The marketing team owns Accounts; however, they also need to be able to see the sales team's Accounts. Both the sales and marketing teams are in completely different branches of the rote hierarchy. What feature should be used to enable marketing to see sales-owned accounts?
A. Public Group
B. Flow
C. Workflow
D. Sharing Rules
Explanation: 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.
What are two reason to create an unmanaged package? (Choose 2 answers)
A. Distributing open-source projects on the AppExchange.
B. Publishing an application for sale on the AppExchange
C. Deploying from a Developer Edition environment
D. Distributing upgradeable components to another Salesforce org
Explanation: The two reasons to create an unmanaged package are to distribute open-source projects on the AppExchange and to deploy from a Developer Edition environment. An unmanaged package is a collection of components that can be installed in any Salesforce org but cannot be upgraded or controlled by the developer. An unmanaged package can be used to share open-source projects or to deploy components from a Developer Edition environment to another org.
A business user wants a quick way to edit a record's status and enter a custom due date field from the record's feed in Salesforce Mobile App. What should be used to accomplish this?
A. Custom action
B. Custom button
C. Custom quick access link
D. Custom URL formula Field
Universal Containers is setting up salesforce for the first time. Management wants the sales and marketing teams to have different navigation names in the salesforce1 mobile app. Which option is available to an app builder to satisfy the requirement?
A. Create sales and marketing profiles to ensure read access to different objects
B. Create roles for sales and marketing and assign a custom homepage layout for each role.
C. Create mobile navigation menus for both the sales and marketing profiles.
D. Create public groups for sales and marketing and create mobile navigation menus for each group.
Explanation: Create mobile navigation menus for both the sales and marketing profiles. This is correct because mobile navigation menus allow users to customize the items that appear in the navigation bar of the Salesforce mobile app, and they can be assigned to different profiles.
Universal Containers (UC) has several large customers that sell their products through dealers. UC identifies and works with a single individual at each customer and at each dealer. Separate bills are sent to each customer and each dealer. These details need to be stored in a format that clearly displays the business entities and their appropriate representatives. How should an app builder Implement these regalements?
A. Create a single parent record, add each rep as a contact to the parent account and add each dealer as a child record.
B. Create both customer and dealer as accounts, create account teams on each account and associate the dealer records with the parent account.
C. Create a single account record, add each rep as a contact and create a custom dealer object.
D. Create both customer and dealer as accounts, add each rep as a contact on the corresponding account and create an account hierarchy.
Explanation: Creating both customer and dealer as accounts, adding each rep as a contact on the corresponding account, and creating an account hierarchy provides a clear organizational structure and relationship between the entities.
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?
A. Establish upper bound on existing picklists in Picklist Settings.
B. Set up Global Values in Picklist Value Sets.
C. Remove upper bound on inactive picklist values in Picklist Settings.
D. Convert the picklist fields to a different field type that will still meet the business requirements.
Explanation: 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.
Ursa Major Solar wants to convert the relationship between Galaxy and Star from a lookup
relationship to a master-detail relationship so each Galaxy record can be equipped with a
roll-up summary count of Star records.
Which two considerations should be made?
(Choose 2 answers)
A. The Star records are all required to have an existing value in their Galaxy field.
B. The Galaxy object has fewer than two existing master-detail relationships.
C. The Galaxy object is required to contain existing roll-up summary fields.
D. The Star object has fewer than two existing master-detail relationships.
Explanation: 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.
Universal Containers has several new fields they've requested for the Opportunity Product object. What should an app builder be able to configure using a formula field?
A. A hyperlink to the parent Account of the parent Opportunity.
B. A Rich Text area field that uses HTML to bold certain characters.
C. A combination of the Opportunity's Text and a Description fields.
D. A mix of functions and concatenation of 10 Account fields and 10 Opportunity fields.
Explanation: Formula fields in Salesforce can use various functions including text,
mathematical, and logical functions to create simple or complex expressions. They can
handle data from fields of the same record. Option C, "A combination of the Opportunity's
Text and a Description fields," is a valid configuration for a formula field as it involves
simple concatenation of text fields, which is supported. Options A, B, and D exceed the
capabilities of formula fields:
A: Hyperlinks to other objects using formula fields do not directly support
navigation to parent records of a different object.
B: Rich Text and HTML formatting are not supported in formula fields.
| Page 4 out of 29 Pages |
| Previous |
Copyright © - All Rights Reserved