Salesforce Certified Administrator — All Questions
4 questions
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.