Courseiva

SF-Admin Sales and Marketing Applications Practice Question

Exhibit

Object: Opportunity | Field: Stage | Values: Prospecting, Qualification, Needs Analysis, Negotiation, Closed Won, Closed Lost. Requirement: When an Opportunity reaches 'Closed Won', the 'Close Date' must not be in the future.

Which automation tool is best for enforcing this validation constraint?

⚠ Common exam trap

Students often mistake Record-Triggered Flows for Validation Rules, overlooking that validation rules are specifically designed to block invalid saves and display immediate user interface errors.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Validation Rule

A validation rule is the most efficient and standard way to enforce data integrity when a record is being saved. By writing a formula that checks if the stage is 'Closed Won' and if the close date is greater than today, the system provides immediate feedback to the user, preventing incorrect data entry before the record is ever committed to the database, ensuring clean reporting and accurate forecasting.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✓

    Validation Rule

    Why this is correct

    Validation rules are the native mechanism for enforcing business logic on fields during the save process. They allow for complex formulas that compare current field values against system variables like 'TODAY()', providing an immediate, user-friendly error message if the data entered violates the established business requirements.

  • ✗

    Record-Triggered Flow

    Why it's wrong here

    Flows execute after or before the save, but they are generally used for automation tasks like updating related records or sending emails. Using a flow to force an error on record entry is less efficient than a validation rule and can result in confusing user experiences during saving.

  • ✗

    Workflow Rule

    Why it's wrong here

    Workflow rules are legacy automation tools that perform field updates or email alerts. They are not capable of preventing a record from being saved or displaying error messages to the user, meaning they cannot fulfill the requirement of enforcing a specific data constraint during the user experience.

  • ✗

    Approval Process

    Why it's wrong here

    Approval processes manage the lifecycle of a record's submission for managerial review. While they can lock records, they are not designed to validate field values on entry; they would only trigger after the record is already saved, which is too late to prevent the entry of invalid data.

About these practice questions

This SF-Admin question is part of Courseiva's 202-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written and reviewed by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

Last reviewed September 2026 · checked against the official Salesforce exam blueprint

This SF-Admin practice question is part of Courseiva's free Salesforce certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SF-Admin exam.