At Universal Containers, there is a custom field on the Lead named Product Category. Management wants this information to be part of the Opportunity upon lead conversion. What action should the administrator take to satisfy the request?
A. Map the lead custom field to the product's product category field.
B. Create a workflow to update Opportunity fields based on the lead.
C. Create a custom field on the Opportunity and map the two fields.
D. Configure the product categories picklist field on the product.
Explanation:
When converting a Lead, Salesforce only automatically maps standard Lead fields to their corresponding Opportunity fields. Custom Lead fields must be explicitly mapped to custom Opportunity fields. To pass the “Product Category” from Lead to Opportunity upon conversion, you create a custom picklist (or text) field named “Product Category” on the Opportunity object, then go into Lead Field Mappings in Setup and map the custom Lead field to the new Opportunity field. From that point on, whenever a Lead is converted, Salesforce transfers the Product Category into the newly created Opportunity field automatically. Workflow or picklist settings on the Product object won’t accomplish this mapping, as only field-to-field mappings on the Lead Conversion page take effect.
The service manager at Ursa Major Solar wants to let customers know that they have received their cases via email and their websites. Medium-priority and high priority cases should receive different email notifications than low-priority cases. The administrator has created three email templates for this purpose. How should an administrator configure this requirement?
A. Include three assignment rules that fire when cases are created. Add a filter for case priority. Select the appropriate email template for each rule.
B. Add three auto-response rules. Configure one rule entry criteria for each rule and set a filter for case priority. Select the appropriate email template for each rule entry.
C. Configure one workflow rule that fires when cases are created. Add a filter for case priority. Select the appropriate email template for the rule.
D. Create one auto-response rule. Configure three rule entry criteria and set a filter for case priority. Select the appropriate email template for each rule entry.
Explanation:
Auto-response rules are designed to send instant email acknowledgements to customers when they submit cases, and they support multiple rule entries within a single rule. By creating one auto-response rule for your Ursa Major Solar org, you can then add three entries—one each for Low, Medium, and High priorities. Each entry’s criteria filters on Priority = Low/Medium/High and selects the corresponding email template. When a case is created via the web or Email-to-Case, Salesforce evaluates the entries in order: the first matching entry fires and sends its designated template to the customer. Assignment rules are for routing cases, workflow rules don’t email the case creator automatically, and you cannot create three separate auto-response rules—each org supports exactly one.
The Human resources department at Northern Trail outfitters wants employees to provide feedback about the manager using a custom object in Salesforce. It is important that managers are unable to see the feedback records from their staff. How should an administrator configure the custom object to meet this requirement?
A. Uncheck grant access using Hierarchies.
B. Define a criteria-based sharing rules.
C. Set the default external access to private.
D. Configure an owner-based sharing rules.
Explanation:
By default, when you set an object’s Organization-Wide Default (OWD) sharing to Private, records owned by subordinates are visible to their managers through the sharing hierarchy. For the feedback custom object, you want feedback records to remain invisible to anyone except their creator (and system administrators). After setting the OWD for the custom object to Private, you must disable hierarchy-based access so that managers in the “Direct Manager” field cannot see down into their team’s feedback. This is done by unchecking the “Grant Access Using Hierarchies” option on the object’s Sharing Settings. Criteria-based or owner-based sharing rules aren’t needed because you aren’t granting extra access; you’re strictly removing hierarchical visibility.
An administrator gets a rush request from Human Resources to remove a user’s access to Salesforce Immediately. The user is part of a hierarchy field called Direct Manager. What should the administrator do to fulfil the request?
A. Freeze the user to prevent them from logging in while removing them from being referenced in the Direct Manager field.
B. Deactivate the user and delete any records where they are referenced in the Direct Manager field.
C. Change the user’s profile to read-only while removing them from being referenced in the Direct Manager Field.
D. Delete the user and leave all records where they referenced in the Direct Manager Field without changes.
Explanation:
When HR needs a user’s access removed immediately, freezing the user is best practice: it locks the account so they cannot log in but preserves all ownerships and references. Because this user is set in a “Direct Manager” lookup on other records, you cannot deactivate them until no queries or formulas reference the lookup. Freezing avoids login while you update all records that point to them (or reassign that lookup). Deactivation immediately breaks those references and can cause errors; deleting a user is never allowed in Salesforce; changing their profile to read-only still permits API access. Thus, freeze first, then correct all Direct Manager lookups, and finally deactivate the user cleanly.
Users at Cloud Kicks are reporting different options when uploading a custom picklist on the Opportunity object based on the kind of opportunity. Where Should an administrator update the option in the picklist?
A. Fields and relationships
B. Related lookup filters
C. Record Type
D. Picklist value sets
Explanation:
Picklist values in Salesforce can vary by Record Type. When users report different picklist options on Opportunity, it usually means their profile is seeing a different record type configuration. To update which values appear, you navigate to the Opportunity object, open each Record Type’s settings, and add or remove the picklist values under “Picklists Available for Editing.” Adjusting fields and relationships or the global value set affects all record types; lookup filters don’t control the master list; and picklist value sets manage the list of possible values but cannot assign them by record type. Only the Record Type interface allows you to tailor which values are visible on that type of opportunity.
An administrator Creates a custom text area field on the Account object and adds it to the service team's page layout. The services team manager loves the addition of this field and wants it to appear in the highlights panel so that the services reps can quickly find it when on the Account Page. How should the administrator accomplish this?
A. Create a new page layout and a new section titled highlights panel.
B. In the Account object manager, create a custom compact layout.
C. From the page layout editor, drag the field to the highlights panel.
D. Make the field required and move it to the top of the page.
Explanation:
The Highlights Panel on Lightning record pages displays fields defined in the Compact Layout. To surface your new custom text area in that panel, go to Setup → Object Manager → Account → Compact Layouts, either edit an existing compact layout or create a new one, and add your field to it. After saving, assign that compact layout as the primary layout for the org. There is no drag-and-drop in the page layout editor for the Highlights Panel, and making a field required or moving it in the standard page layout does not affect the compact layout. Only the compact layout controls which fields display in the header area.
Sales reps miss key fields when filling out on opportunity record through the process. Reps need to move forward Win unable to enter previous stage. Which three options should the administrator use to address this need?
(Choose Three answers)
A. Enable guided selling.
B. Use Validation Rules.
C. Configure Opportunity Path.
D. Use Flow to mark fields required.
E. Mark fields required on the page layout.
Explanation:
To ensure reps complete key fields before advancing an Opportunity stage, combine three declarative features:
1. Validation Rules enforce that certain fields meet criteria (for example, close date must be populated) before a user can save a record—blocking stage progression until requirements are met.
2. Opportunity Path gives users visual guidance on each stage, and you can mark key fields as “Required” within the Path configuration so that users see inline reminders and tooltips for fields that must be filled in before moving past that stage.
3. Page Layout Required (via the wrench icon next to picklist fields) forces data entry on the layout itself.
Guided Selling (the older feature) is deprecated, and Flows to mark fields required adds unnecessary complexity when simpler, native tools already enforce data quality.
DreamHouse Reality needs to use consistent picklist value on a category filed on accounts and cases, with value respective to record types. Which two features should the administrator use to fulfill this requirement?
(Choose 2 Answers)
A. Dependent Picklist
B. Global Picklist
C. Multi-Select Picklist
D. Custom Picklist
Explanation:
When you require the same picklist values across multiple objects (Accounts and Cases), you use a Global Picklist Value Set. Global picklists centralize your value definitions; you then create custom picklist fields on each object and point them to the global value set. Record Types can tailor which values are available per record type, but the underlying list of values comes from the global set. A standard custom picklist field without a global value set would require individually maintaining each field’s values. Dependent and multi-select picklists serve different use cases.
Universal Containers (UC) would like to count the number of open cases associated with each account and update the account with this value everyFriday evening. UC has several hundred open cases at any given time. What should the administrator use to complete this request?
A. Use a record trigger flow.
B. Use a scheduled process builder.
C. Use a Roll-Up summary.
D. Use a scheduled flow
Explanation:
Because Cases are related to Accounts via a lookup relationship, you cannot use a roll-up summary field (which only works on master-detail relationships). A record-triggered flow or Process Builder cannot execute on a defined schedule; they run only when records are created or updated. Instead, a scheduled flow (also called a schedule-triggered flow) allows you to run automation at specified intervals—every Friday evening in this scenario—to query all open Cases, group them by Account, count them, and then update each Account record with the calculated count. Scheduled flows are more scalable and efficient than repeatedly triggering on each Case change, especially when dealing with several hundred open Cases. They also supersede the older “Scheduled Paths” in Process Builder, offering greater performance and flexibility.
Sales users at Universal Containers are reporting that it is taking a long time to edit opportunity records. Normally, the only field they are editing is the Stage field. Which two options should the administrator recommend to help simplify the process?
(Choose 2 answers)
A. Add a path for stage to the opportunity record page.
B. Use a Kanban list view for Opportunity.
C. Configure an auto launched flow for Opportunity editing
D. Create a simplified Opportunity page layout.
Explanation:
When users are only updating the Stage field, reducing page complexity speeds up their edits. Adding a Path component focuses attention on the Stage field by displaying it prominently at the top of the record page, guiding reps through key stages and required fields without navigating the full layout. Meanwhile, a simplified page layout that only includes essential fields and related lists minimizes load time and scrolling, so users can quickly save their changes. Although a Kanban view (option B) provides a board-style view of opportunities, it’s a list-view feature rather than editing the record page itself; an auto-launched flow (option C) would require users to trigger a separate flow, adding overhead rather than simplifying. Together, Path and a streamlined layout improve performance and user experience for routine Stage updates.
Sales raps at Ursa Solar are having difficulty managing deals. The leadership team has asked the administrator to help sales reps prioritize and close more deals. What should the administrator and close more deals.
A. Einstein Lead Scoring
B. Einstein Search Personalization
C. Einstein Activity Capture
D. Einstein Opportunity Scoring
Explanation:
Einstein Opportunity Scoring analyzes historical opportunity data and identifies key factors that indicate a deal’s likelihood to close, assigning each opportunity a score and recommending focus areas. By highlighting high-probability deals and indicating at-risk opportunities, Sales reps can prioritize their pipeline more effectively and close more deals. Einstein Lead Scoring (option A) scores leads rather than open opportunities. Einstein Activity Capture (option C) syncs emails and events but doesn’t provide predictive insights on deal health. Einstein Search Personalization (option B) optimizes search results for individual users. Thus, Einstein Opportunity Scoring is the right tool to help Ursa Solar’s leadership and sales reps focus efforts on the most promising deals.
Which tool should an administrator use to identify and fix potential session vulnerabilities?
A.
Field History Tracking
B.
Setup Audit Trail
C.
Security Health Check
D.
Organization-Wide Defaults
Security Health Check
Explanation:
Security Health Check analyzes your org’s security settings (including session settings, password policies, network access, and more) and compares them against the Salesforce Baseline Standard or a custom baseline. It highlights any settings that are less secure than recommended—such as session timeout, session fixation protection, or clickjack protection—and provides remediation steps. Field History Tracking (A) logs data changes, Setup Audit Trail (B) tracks metadata changes, and Organization-Wide Defaults (D) define record-level access; none evaluate session or security settings holistically. Therefore, the Security Health Check is the correct tool to identify and fix potential session vulnerabilities.
| Page 2 out of 21 Pages |
| Previous |