Salesforce-Platform-Administrator Practice Test Questions

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.

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.

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.

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.

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.

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).

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.

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.

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.

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.