The administrator at Ursa Major Solar need to make sure the unassigned cases from VP customers get transferred to the appropriate service representative within 5 hours. VIP Customers have access to support 24 hours a day. How should this be configured?
A. Assignment Rules
B. Business Hours
C. Case Queues
D. Escalation Rules
Explanation:
Escalation rules let you automatically escalate cases when they haven’t been acted on within a specified timeframe. In this scenario, you’d first define a 24-hour “VIP Customers” business hours schedule so that Salesforce counts time around the clock. Then you create an escalation rule entry that applies only to unassigned cases from VIP accounts and sets the escalation threshold to 5 hours (using your VIP business hours). When a case remains unassigned after 5 hours, the rule will fire and transfer—or reassign—the case to the correct support rep or queue. Assignment rules alone only determine initial case assignments, and queues simply hold cases—they don’t trigger time-based actions. Escalation rules are the only declarative feature designed for time-based case transfers.
An administrator has been asked to change the data type of an auto number to text field. What should the administrator be aware of before changing the field?
A. Existing field values will remain unchanged.
B. Existing field values will be Converted.
C. Existing field values will be deleted.
D. Existing auto number field to Text is prevented.
Explanation:
When you change an Auto Number field to a Text field, Salesforce preserves all existing generated values exactly as they are. The system simply converts the field’s data type, allowing you to edit those values directly like any other text. There is no data loss or automatic reformatting—your original sequence (for example, “ABC-0001”, “ABC-0002”, and so on) remains intact. Neither deletion nor conversion of values occurs, and the platform does not block the change. This flexibility is useful when you need to modify number formats or incorporate letters, prefixes, or variable segments, while still keeping all previously generated records consistent.
Northern Trail Outfitters wants to encourage employees to choose secure and appropriate passwords for their Salesforce accounts. Which three password policies should an administrator configure?
(Choose 3 answers)
A. Maximum invalid login attempts
B. Prohibited password values
C. Require use of Password Manager App
D. Password complexity requirements
E. Number of days until expiration
Explanation:
To encourage strong, appropriate passwords, configure:
1. Prohibited Password Values: Block users from using easily guessed or organization-specific words (such as “salesforce” or “password123”) in their passwords.
2. Password Complexity Requirements: Enforce a mix of uppercase, lowercase, numbers, and special characters to meet your organization’s security standards.
3. Number of Days Until Expiration: Require periodic password changes (for example, every 90 days) so that if a password is compromised, it has a limited window of usefulness.
Maximum invalid login attempts is a lockout policy (not a password-strength policy), and “Require use of Password Manager App” isn’t a native Salesforce setting. Focusing on prohibited values, complexity, and expiration covers both the strength and lifecycle dimensions of a secure password policy.
Which two capabilities are considerations when marking a field as required in Object Manager?
Choose 2 answers
A. The field is not required to save records via the API on that object.
B. The field is universally required to save a record on that object.
C. The field is added to every page layout on that object.
D. The field is optional when saving records via web-to-lead and web-to-case
Explanation:
When you mark a field Required in Object Manager, Salesforce enforces that the field must contain a value before any record can be saved—across all page layouts and via API. However, web-to-lead and web-to-case submissions bypass field-level required enforcement to avoid blocking external form submissions; those systems only respect page-layout required settings. Field-level required always applies in the UI and API, but web-to-lead/web-to-case are explicitly exempted from those field-level requirements.
An administrator has reviewed an upcoming critical update. How should the administrator proceed with activation of the critical update?
A. Activate the critical update in a sandbox.
B. Allow the critical update to auto-activate.
C. Activate the critical update in production.
D. Allow the critical update to auto-activate in a sandbox
Explanation:
Best practice dictates that any upcoming critical update should first be enabled and tested in a sandbox environment. This allows you to identify and remediate any potential impacts on custom code, integrations, or business processes under controlled conditions. After thorough testing, you can then schedule activation in your production org during a maintenance window. Letting Salesforce auto-activate without testing risks unforeseen downtime or broken functionality.
A sales rep has a list of 300 accounts with contacts that they want to load at one time. Which tool should the administrator utilize to import the records to salesforce?
A.
Dataloader.io
B.
Data Loader
C.
Manual Import
D.
Data Import Wizard
Data Loader
Explanation:
Data Loader is the ideal tool when you need to import multiple related objects (Accounts and their Contacts) in one operation. You can insert parent records (Accounts), export their Salesforce IDs, and then insert child records (Contacts) referencing those IDs—all in CSV files. Data Import Wizard is simpler but only supports one object at a time and doesn’t handle parent-child references as cleanly. Dataloader.io and Manual Import aren’t standard Salesforce‐provided import tools (the former is third-party, and manual import wouldn’t scale for 300 records).
What will happen to the Chatter post in this situation?
A. The pending Chatter post will be canceled.
B. The pending Chatter post will be sent on the 10th of the month
C. The pending Chatter post will be will be paused.
D. The pending Chatter post will be sent in 30 days.
Explanation:
Salesforce’s native Chatter functionality does not include a built-in scheduling or queuing mechanism for future posts. When a user composes a Chatter post and specifies a future date or time, Salesforce has no background process to hold and later publish that content. As a result, any “pending” post awaiting a send date is immediately discarded the moment the user attempts to schedule it. No error message appears in the interface beyond perhaps a brief notification, and the draft simply vanishes from the feed. This design choice keeps Chatter lightweight and real-time—posts are intended to be shared instantly. Organizations that require scheduled announcements must instead leverage custom solutions (such as Apex jobs publishing to the Connect API) or third-party AppExchange packages. But out of the box, native Chatter does not support postponed publishing. Therefore, any attempt to queue a Chatter post results in its cancellation rather than pausing or delaying delivery.
Administrator at Northern Trail Outfitters is unable to add a new user in Salesforce. What could cause this issue?
A. The username is already in use another organization.
B. The username is restricted to a domain specific to my domain
C. The email address used for the username has a contact record.
D. The email used for the username is not a corporate email address.
Explanation:
Salesforce usernames must be unique across all Salesforce orgs and follow email format, but they don’t need to be valid email addresses. If you attempt to create a new user with a username that matches any existing user in any org, Salesforce will block creation and display an error. Domain restrictions (My Domain) and contact record email addresses don’t affect username uniqueness.
An administrator at Northern Trail Outfitters is creating a validation rule. Which two functions should the administrator use when creating a validation rule?
(Choose 2 answers)
A. Formula return type
B. Error condition formula
C. Error message location
D. Rule active date
Explanation:
When building a validation rule, you must specify both the logical formula that determines when the rule fires (Error Condition Formula) and where the message appears (Error Message Location: either at the top of the page or next to a specific field). There is no “Formula return type” setting on validation rules, and you can’t schedule a rule by date.
Cloud Kicks executives have noticed the opportunity Expected revenue Field displays incorrect values. How Should the administrator correct this?
A. Update the expected revenue associated with the stage.
B. Adjust the forecast category associated with the stage.
C. Modify the closed won value associated with the stage.
D. Change the probability associated with the stage.
Explanation:
Expected Revenue is calculated as Amount × Probability. If the “Expected Revenue” field is showing incorrect values, it almost always means the probability percentage that Salesforce uses for that Opportunity Stage is wrong. By editing the Sales Path (or customizing the Stage picklist) to assign the correct probability to each stage, you’ll ensure that Salesforce recalculates Expected Revenue properly across all open opportunities.
An administrator at Cloud Kicks is building a flow that needs to search for records that meet certain conditions and store values from those records in variable for use later in the flow. What flow element should the administrator add?
A. Assignment
B. Get Records
C. Create Records
D. Update Records
Explanation:
When your flow needs to search Salesforce for records that meet specified criteria and then hold values from those records for later use, the Get Records element is the correct choice. The Get Records element lets you point to any object, define filter conditions (for example, “Status = ‘Open’ AND Priority = ‘High’”), and store either a single record or a collection of records into flow variables. Once the records are retrieved, you can reference any of their fields throughout your flow—for example, to make decisions, assign new values, or update related records. Assignment, Create, and Update elements serve other purposes: Assignment simply sets variable values; Create Records writes new data; and Update Records changes existing data. None of those elements query Salesforce for existing records. Only Get Records provides the powerful, declarative ability to fetch data from the database for logic and processing downstream in your automation.
The administrator at cloud kicks has been ask to change the company’s Shoe style field to prevent users from selecting more than one style on a record. Which two steps should an administrator do to accomplish this?
(Choose 2 answers)
A. Reactivate the appropriate Shoe Style values after the field type changes
B. Select the “Choose only one value“ checkbox on the pick list field.
C. Back-up the Shoe Style values in existing records
D. Change the field type from a multi-select picklist field to a picklist field.
Explanation:
Salesforce does not allow users to select more than one value on a standard picklist—but multi-select picklists do. To enforce single-value selection going forward, you must convert the existing multi-select picklist to a standard (single-select) picklist. However, changing the field type can alter or clear existing data, so best practice is to back up current selections first (for example, via a report or data export) before making the change. After you switch the field’s data type in Setup, your Shoe Style field becomes a single-select picklist, ensuring users can choose only one style per record. If any historical values become inactive during conversion, you can also reactivate them afterward under the picklist’s value settings, but the two critical steps are data backup and field-type change.
| Page 1 out of 21 Pages |