Ursa Major Solar provides a 1-year warranty on all of the panels it installs. Installation details, along with the warranty information, a captured on a custom object called Installation. The installation record is created by the installer from the mobile app. Customers son receive a longer warranty as a way of increasing customer satisfaction when an installation gets delayed or has issues.
How should the administrator configure Salesforce to capture the expiration date of the warranty?
Correct Answer:
A
To capture the expiration date of warranty based on installation date and warranty length (1 year by default), the administrator should use a formula as the default value of Warranty Expiration Date field on Installation object. The formula can calculate one year from installation date using DATE function or DATEVALUE function. For example, DATE(YEAR(Installation_Date c) + 1 , MONTH(Installation_Date c) , DAY(Installation_Date c)) will return one year from installation date. Creating a formula field, adding a validation rule, or including Warranty Expiration Date field on mobile page layout will not capture expiration date based on installation date and warranty length.
References:https://help.salesforce.com/s/articleView?id=sf.formula_using_date_dat etime.htm&type=5
The administrator at Ursa Major Solar has been asked to change the work Item and Project Custom
Object Relationship from a master detail to a Lookup.
Which Scenario Could prevent the administrator from fulfilling this requirement?
Correct Answer:
D
One scenario that could prevent an administrator from changing the relationship between work item and project custom objects from master-detail to lookup is
that roll-up summary fields exist on the master object (project). Roll-up summary fields are fields that calculate values from related records in a master-detail relationship; they cannot be used in a lookup relationship. If roll-up summary fields exist on the project object, they would prevent the administrator from changing the relationship type unless they are deleted first. A junction object is not required to support a lookup relationship; it is only used when creating many-to-many relationships between two objects using two master-detail relationships. The lookup field in all the records containing a value or the lookup field being required for saving records are not scenarios that would prevent changing the relationship type; they are scenarios that would allow changing the relationship type without losing data or functionality. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up_summary_fields.htm&t ype=5https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm&typ e=5
Support agent at Cloud Kicks are spending too much time finding resources to solve cases.
The agents need a more efficient way to find documentation and similar cases from the Case page
layout.
How should an administrator meet this requirement?
Correct Answer:
D
Knowledge is a feature that can be used to meet this requirement. Knowledge allows users to create, manage, and share articles that provide information and solutions for common issues or questions. Data categories can be used to organize articles into different topics and make them easier to find and access. Users can view related articles from the Case page layout based on the data category of the case. References: https://help.salesforce.com/s/articleView?id=sf.knowledge_overview.htm&type=5https://hel p.salesforce.com/s/articleView?id=sf.knowledge_categories.htm&type=5
The administrator at AW Consulting has created a custom picklist field. Business users have requested that it be a text field. The administrator attempts to change the field type but, is unable to because it is referenced by other functionalities.
Which functionality is preventing the field type from being changed?
Correct Answer:
A
Formula fields are types of fields that calculate a value based on an expression or formula that references other fields or constants. Formula fields prevent administrators from changing their field type once they are created because they may be referenced by other functionalities such as reports, validation rules, workflow rules, etc., that depend on their data type and value. If a formula field is referenced by other functionalities, then changing its field type may cause errors or unexpected results.References:https://help.salesforce.com/s/articleView?id=sf.fields_about_formulas.ht m&type=5
What data loss considerations should an administrator keep in mind when changing a custom field type from Text to Picklist?
Choose 2 answers
Correct Answer:
BD
Two data loss considerations when changing a custom field type from Text to Picklist are:
✑ Assignment and escalation rules may beaffected, because the values in the
picklist may not match the values that were previously entered in the text field, and the rules may not trigger as expected.
✑ Any list view based on the custom field is deleted, because the filter criteria for the list view may not be valid for the new field type, and the list view cannot be displayed. There will be no data loss with use of a global value set or auto updates to Visualforce references, because these are not related to changing a custom field type from Text to Picklist. References: https://help.salesforce.com/s/articleView?id=sf.fields_changing_type_consideration s.htm&type=5
