Salesforce Certified Administrator — All Questions

In Salesforce, what determines the baseline object-level permissions (create, read, edit, delete) a user has, along with the apps and tabs they can access?

• a.The user's role in the role hierarchy
• b.The user's profile✓
• c.The organization-wide default sharing settings
• d.The user's public group membership

A profile defines baseline object and field permissions, tab and app visibility, and system permissions for a user. The role hierarchy influences record-level access for reporting and sharing, org-wide defaults set the baseline record sharing, and public groups are used in sharing rules. Object-level CRUD comes from the profile (and any assigned permission sets).

An administrator needs to grant a small group of users an extra permission without changing their profile, which is shared by many others. What is the recommended tool?

• a.Change the organization-wide defaults
• b.Modify the role hierarchy
• c.Assign a permission set to those users✓
• d.Create a new profile and migrate everyone

Permission sets grant additional permissions to specific users on top of their profile, without altering the profile that others share. This keeps profiles lean and follows the modern least-privilege approach. Editing org-wide defaults or the role hierarchy changes record sharing broadly, and creating new profiles for a few users is unnecessary overhead.

Which feature lets an administrator temporarily assume a user's view of the application to troubleshoot an access issue, when it has been enabled?

• a.Login As the user via the user's detail page✓
• b.Resetting the user's password
• c.Changing the org-wide default to Public
• d.Deleting and recreating the user

When granted login access, an administrator can use Login As to see Salesforce exactly as that user does, which is the standard way to reproduce and diagnose access or visibility problems. Resetting a password, changing sharing defaults, or recreating the user does not let you see the user's specific experience.

Where would an administrator go to control the company's default locale, currency, and business hours settings that apply org-wide?

• a.The individual user's profile
• b.A validation rule
• c.A sharing rule
• d.Company Information and related Setup pages✓

Org-wide defaults for locale, default currency, and related company settings are configured in Company Information and related organization Setup pages. Profiles and individual settings can override locale per user, but the company baseline lives in these organization-level Setup areas. Validation and sharing rules serve entirely different purposes.

An administrator needs a field on the Account object whose value is calculated automatically from other fields and cannot be edited by users. Which field type should be used?

• a.A picklist field
• b.A formula field✓
• c.A text field with a default value
• d.A lookup field

A formula field automatically calculates a read-only value from other fields and functions, recalculating whenever the record is viewed or saved. Picklists, text with defaults, and lookups all store user- or reference-supplied values rather than a derived calculation. Formula fields are ideal for computed, non-editable values.

Which relationship type creates a tight parent-child link where the child record inherits the parent's sharing and ownership and is deleted when the parent is deleted?

• a.Lookup relationship
• b.Hierarchical relationship
• c.External lookup relationship
• d.Master-detail relationship✓

A master-detail relationship tightly couples child (detail) records to a parent (master): the child inherits the parent's sharing and ownership, and deleting the master deletes its details. A lookup relationship is looser and does not cascade delete or inherit sharing. Hierarchical relationships apply only to the User object.

An administrator wants to ensure that a Close Date is never earlier than the Created Date when a record is saved. Which tool enforces this at save time?

• a.A validation rule✓
• b.A report filter
• c.A list view
• d.A page layout assignment

A validation rule evaluates a formula when a record is saved and blocks the save with an error message if the condition indicates invalid data, making it the right tool to enforce that Close Date is not before Created Date. Reports, list views, and page layouts control display or filtering, not data integrity at save time.

Using the Lightning App Builder, what can an administrator create or customize?

• a.Apex triggers and classes
• b.The underlying database schema of standard objects
• c.Lightning record pages, home pages, and app pages with drag-and-drop components✓
• d.The network firewall rules for the org

The Lightning App Builder is a point-and-click tool for building and customizing Lightning pages, including record pages, home pages, and app pages, by dragging standard and custom components onto the canvas. Writing Apex is a developer task, and schema changes are done in Object Manager, not the App Builder.

An administrator wants different groups of users to see different sets of fields and layouts on the same object. Which combination achieves this?

• a.A single page layout shared by everyone
• b.Multiple page layouts assigned to different profiles (optionally with record types)✓
• c.Changing the org-wide default sharing setting
• d.A workflow rule that hides fields

Page layouts control which fields, related lists, and buttons appear on a record, and layouts can be assigned per profile, often in combination with record types, so different user groups see tailored views. Org-wide defaults govern record access, not field arrangement, and workflow rules automate updates rather than control layouts.

In the standard sales process, which object represents a potential revenue deal that moves through stages toward closing?

• a.Opportunity✓
• b.Case
• c.Campaign
• d.Solution

An Opportunity represents a potential sale or deal that progresses through defined sales stages toward a close. Cases belong to service and support, Campaigns are marketing initiatives, and Solutions are legacy knowledge records. Opportunities are the core of pipeline and forecasting in Sales Cloud.

A company wants incoming customer support requests to be automatically assigned to the correct support queue based on the case's subject or origin. Which feature should the administrator configure?

• a.Opportunity stages
• b.Web-to-Lead
• c.Case assignment rules✓
• d.Campaign hierarchy

Case assignment rules automatically route new cases to the right user or queue based on criteria such as origin, type, or subject, which is central to Service Cloud operations. Opportunity stages and campaign hierarchy relate to sales and marketing, and Web-to-Lead captures leads rather than routing cases.

Which feature lets a business capture information from a form on its public website and automatically create Lead records in Salesforce?

• a.Case escalation rules
• b.Opportunity contact roles
• c.Case queues
• d.Web-to-Lead✓

Web-to-Lead generates a form and endpoint so that submissions from a company's website create Lead records automatically, feeding the sales funnel. Escalation rules and case queues are support features, and opportunity contact roles document who is involved in a deal, none of which capture web form submissions as leads.

What is the purpose of the Lead Conversion process in Sales Cloud?

• a.To merge two duplicate Accounts into one
• b.To turn a qualified Lead into an Account, Contact, and optionally an Opportunity✓
• c.To escalate an overdue support Case
• d.To archive old Campaign members

Converting a qualified Lead creates (or matches to) an Account and Contact and optionally an Opportunity, moving the prospect into the standard sales objects. Merging duplicates, escalating cases, and archiving campaign members are separate operations unrelated to lead conversion.

An administrator needs to import several thousand Account records from a spreadsheet into Salesforce. Which tool is well suited for this bulk load?

• a.The Data Import Wizard or Data Loader✓
• b.A validation rule
• c.The role hierarchy
• d.A Lightning record page

The Data Import Wizard handles common bulk imports for standard and custom objects up to its limits, and Data Loader handles larger volumes and more objects. Validation rules enforce data quality, the role hierarchy manages access, and record pages control display, none of which perform data import.

Which report format displays records grouped into rows and columns to summarize data across two dimensions, such as opportunities by stage and by owner?

• a.Tabular report
• b.Summary report
• c.Matrix report✓
• d.Joined report

A matrix report groups data by both rows and columns, making it ideal for comparing a measure across two dimensions. Tabular reports are simple lists, summary reports group by rows only, and joined reports combine multiple report blocks. Matrix is the correct choice for a two-dimensional grouping.

A manager wants a single screen that shows several charts and metrics from different reports at a glance, refreshed on demand. Which Salesforce feature provides this?

• a.A list view
• b.A dashboard✓
• c.A validation rule
• d.A permission set

A dashboard displays components such as charts, gauges, and metrics that are each powered by an underlying report, giving a consolidated visual summary that can be refreshed. List views show records of one object, validation rules enforce data integrity, and permission sets grant access, none of which aggregate multiple reports visually.

To help keep the database clean, which native feature can alert users or block them from creating records that match existing ones?

• a.Sharing rules
• b.The role hierarchy
• c.Escalation rules
• d.Duplicate rules and matching rules✓

Duplicate management uses matching rules to identify potential duplicates and duplicate rules to alert or block users when they try to save a matching record, improving data quality. Sharing rules and the role hierarchy govern access, and escalation rules route overdue cases, so none of them address duplicate prevention.

Which tool is Salesforce's recommended, point-and-click automation platform for building complex record-triggered and screen-based automation?

• a.Flow (Flow Builder)✓
• b.Apex triggers only
• c.The role hierarchy
• d.Report subscriptions

Flow, built in Flow Builder, is Salesforce's primary declarative automation tool, supporting record-triggered flows, scheduled flows, and interactive screen flows. It is the recommended replacement for the retired Workflow Rules and Process Builder for most new automation. Apex is a code option, and reports and roles are unrelated to automation.

An administrator wants a flow to run automatically whenever an Opportunity is created or updated to meet certain criteria, without any user interaction. Which flow type fits?

• a.A screen flow launched from a button
• b.An autolaunched flow with no trigger
• c.A record-triggered flow✓
• d.A scheduled flow that runs nightly

A record-triggered flow runs automatically when a record is created, updated, or deleted and meets the entry conditions, with no user interaction. Screen flows require user input, a scheduled flow runs on a time schedule rather than on record changes, and a no-trigger autolaunched flow must be invoked by something else.

An administrator needs an approval process for discounts above a threshold, routing the request to a manager for sign-off. Which capability best matches this requirement?

• a.A validation rule
• b.An approval process✓
• c.A list view filter
• d.A sharing rule

An approval process defines the steps, approvers, and actions for records that require formal sign-off, such as routing a large discount to a manager and recording the decision. Validation rules only block bad saves, list views filter records, and sharing rules control access, none of which orchestrate multi-step approvals.

Where should an administrator build and test automation before deploying it to the production org that users rely on?

• a.Directly in production during business hours
• b.In a personal spreadsheet
• c.In a deactivated user account
• d.In a sandbox environment✓

A sandbox is a copy of the production org used to build and test configuration and automation safely before deploying changes to production. Building directly in production risks disrupting users, and spreadsheets or deactivated accounts are not development environments. Sandboxes are the standard practice for safe change management.

Organization-Wide Defaults (OWD) for an object are set to Private. What does this mean for record access before any sharing rules are applied?

• a.Every user can view and edit every record of that object
• b.Users can access only records they own, plus records shared with them through other means✓
• c.The object becomes read-only for all users
• d.Records are automatically deleted after 30 days

A Private org-wide default means users can only see and edit records they own by default; access to others' records must be granted through the role hierarchy, sharing rules, manual sharing, or teams. Private does not make records read-only or cause deletion, and it is the most restrictive baseline you can then open up selectively.