Salesforce-Certified-Administrator Practice Test Questions

Use lead assignment rule

Explanation:

Lead Assignment Rules in Salesforce allow administrators to automate the distribution of new Lead records to the appropriate users or queues based on criteria such as geographic location, industry, or any other field. When a Lead is created—whether manually, via Web-to-Lead, or through an integration—Salesforce evaluates the active assignment rule and assigns ownership according to the rule entries. This ensures that, for example, all Leads with a billing address in California are routed to the California sales team, while those in New York go to a different rep. Assignment Rules are evaluated in order, and the first matching rule entry takes effect, providing granular control over routing logic. Other options like validation rules or formula fields cannot change record ownership, and escalation rules are designed for Cases, not Leads.

Omni-Channel

Explanation:

Omni-Channel in Salesforce Service Cloud provides intelligent routing of work items—such as Leads, Cases, or custom objects—directly to service agents based on their available capacity and skill set. By enabling Omni-Channel and defining Service Channels, Presence Configurations (to set capacities), and Skills (to tag agents with abilities like language fluency or expertise), incoming work is automatically matched to the most qualified and least-loaded agent. Status-based or tab-based capacity models ensure agents receive only as many tasks as they can handle. Escalation Rules and Territory Management do not manage agent workload or skills, and Knowledge Management is for organizing content articles. Omni-Channel centralizes capacity and skills-based routing in real time, enhancing both agent efficiency and customer satisfaction.

use a fault connector and display a screen with text explaining what went wrong and how to correct it.

Explanation:

In a Screen Flow, adding a fault connector from a data or action element to a Screen element enables custom error handling. When the Create or Update Records element fails—such as due to missing required fields or validation rule violations—the Flow continues along the fault path instead of crashing. By capturing the standard $Flow.FaultMessage and presenting it with user-friendly guidance on a Screen element, users understand exactly which fields need attention before retrying. Removing validation rules or bypassing permissions hides the real issue, and disabling error screens in Setup merely suppresses messages without guidance. Fault connectors thus provide a robust, maintainable way to improve user experience and enforce data integrity.

Reset password on the user's record detail page.

Use the unlock button on the user's record detail page.

Explanation:

When a user exceeds the maximum login attempts, Salesforce locks the account for security. As an administrator, you can unlock the account by navigating to Setup → Users, selecting the locked user, and clicking the Unlock button on the User detail page. Additionally, you can immediately send the user a new password by clicking Reset Password from the same page, which prompts Salesforce to email the user a password-reset link. Both actions restore the user’s ability to log in without altering org-wide password policies. Changing policy settings isn’t necessary for a single user, and “Log in as” is only for troubleshooting and does not automatically reset or unlock credentials.

process builder

workflow Rule

Explanation:

To automate tasks at specific times, Salesforce offers two legacy tools: Workflow Rules (with time-dependent actions) and Process Builder (with Scheduled Actions). A single Workflow Rule on the Opportunity object can have an immediate action to create a Task when Stage = Closed Won, and a time trigger set for 60 days after the Close Date to create a second Task. Workflow time-dependent actions are queued and execute automatically at the specified offset. Alternatively, Process Builder allows defining both immediate and scheduled actions in the same process, scheduling a Task 60 days after CloseDate. Combining both tools offers flexibility: Process Builder can evaluate complex criteria and invoke the Workflow Rule for time-based tasks, or vice versa, depending on org standards. Field Updates and Outbound Messages cannot directly create tasks.

Path can include guidance and key fields for each stage.

Explanation:

Salesforce Path is a Lightning component that visually represents record stages and provides admins the ability to surface Key Fields and Guidance for Success at each stage. When configuring Path for Opportunities, you select which picklist field (e.g., Stage) drives the path, then specify which fields should appear inline (Key Fields) and add rich text guidance to help users know what steps to take to advance the deal. Kanban views are separate features, celebration confetti is only available on Leads/Cases, and the Owner field cannot be edited in the Path UI—it’s not a configurable key field. Path enhances adoption by combining visual cues with inline coaching.

Account

Contact

Explanation:

During Lead Conversion, Salesforce can automatically create or link to an Account and Contact record. If a matching Account exists, you can choose to attach the Lead to that Account; otherwise, a new one is created. Similarly, a new Contact is always created from the Lead’s name and information. Opportunities are optional, but Campaigns and Cases are not created as part of standard Lead Conversion. This streamlined conversion ensures all prospect information transitions seamlessly into the account and contact lifecycle.

Explanation:

In Screen Flows, variables intended to accept input when debugging or when called by another flow must have Available for Input selected. If this checkbox is unchecked, the variable won’t appear as an input parameter on the Debug screen, preventing you from supplying values manually during testing. Inactive flow versions or unsupported field types might cause other issues, but missing debug inputs always trace back to not marking the variable for input. Ensuring both Available for Input and, if needed, Available for Output are configured correctly guarantees the variable appears in the Debug interface.

Set up Big Deal Alerts for the amount.

Explanation:

Salesforce’s Big Deal Alerts feature allows admins to send Chatter notifications to designated users or groups when an Opportunity’s Amount exceeds a specified threshold. By enabling Big Deal Alerts and configuring a threshold of $500,000, the Director of Sales (or a Chatter group) automatically receives a real-time alert whenever an Opportunity meets or surpasses that value. This configuration is quick to set up in Setup → Big Deal Alerts. Opportunity Update Reminders, Kanban warnings, and homepage components require manual monitoring or additional customization, whereas Big Deal Alerts provide out-of-the-box automated notifications.

Bucket Column

Explanation:

Bucket Fields in Salesforce Reports allow administrators to group report data on the fly without creating custom formula fields. By defining buckets such as Small (e.g., ContractValue < $100,000), Medium ($100,000–$500,000), and Large (> $500,000), you can categorize each Account record based on its ContractValue. The bucket field appears as a column in report builder and can be used for grouping, filtering, and charting. Detail columns simply display raw data, grouping rows organizes by field value, and filter logic refines which records appear, but only Bucket Columns provide custom ranges without additional metadata.