SF-Admin Sales and Marketing Applications Practice Question
Exhibit
JSON Payload: {"opportunity_id": "006xx000001yZzA", "status": "Closed Won", "stage_history": [...] } | The user gets an 'Insufficient Privileges' error.What is the most likely cause if the user has access to the opportunity but still receives this error during a status update?
⚠ Common exam trap
Students mistakenly think permission errors during record edits always stem from sharing rules, ignoring that Field-Level Security can restrict editing specific fields despite full record access.
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
✓
Field Level Security
The error is likely due to the user lacking Field Level Security (FLS) on the 'Stage' field. Even if a user has record-level access, FLS acts as a final gatekeeper for data modification. Identifying this is essential for administrators to troubleshoot permission issues quickly, ensuring that sales users have the necessary access to update their pipeline without encountering blocking errors that hinder productivity.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Field Level Security
Why this is correct
Field-level security settings control whether a user can see or edit a field, regardless of their object-level permissions. If the 'Stage' field is set to 'Read-Only' or 'Hidden' for the user's profile, they will be unable to modify it, resulting in an 'Insufficient Privileges' error.
- ✗
Organization-Wide Defaults
Why it's wrong here
Organization-wide defaults define the baseline access level for records. If the user already has access to the opportunity record, OWDs have already granted that permission. Changing OWDs would not resolve a field-level error, as OWDs do not control access to individual fields within a record.
- ✗
Role Hierarchy
Why it's wrong here
The role hierarchy is used to extend access to records horizontally and vertically across the organization. It does not govern whether a specific user can edit a particular field. If the user already has access to the record itself, the hierarchy is functioning as expected.
- ✗
Sharing Rules
Why it's wrong here
Sharing rules are used to open up access to records for users who wouldn't otherwise have it. They do not control access to the individual fields of a record. If the user can view the record, sharing rules are not the source of the field-level editing error.
About these practice questions
Courseiva writes every SF-Admin question from scratch — 202 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
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.