SalesForce Scenario-Based Interview Questions

At every job interview, scenario-based salesforce interview questions are quite normal to be asked by the hiring managers. You can not think about just answering them right on the bat in your interview, which is why preparations are necessary.

Questions like these are a way to portray yourself as more capable in the recruiter’s eye. Here we have prepared some questions beforehand, to help you think the salesforce interview questions through and respond in a better way. Let’s get started.

Scenario 1: Even if the approval process is activated, I am willing to add another step. can this step be added?

Approval steps are there to explain the chain of different approval to define a specific procedure. Every step tries to define, which of the records can move forward to the next step, to whom the approval requests can be given, and if the approver’s representative can answer the particular requests.

There is no possibility of adding another step because it will deactivate the whole approval procedure and create clones of the deactivated process to start new steps. So, the steps can be added only when the approval process is deactivated.

Scenario 2: Imagine two workflows wf1 and wf2, ruling over the very same thing. If the field gets updated because of fired wf1, then will wf2 fire or not, if the wf2’s criteria meet that of the updated field?

This question is a must to read among every salesforce interview question.Wf2 will not fire because to fire the workflow we need to go through the field and re-evaluate the rules of the workflow which is only possible in wf1.

If the updates of the field always use the automatic change feature on any particular record it ends by triggering “Re-evaluate Workflow Rules”. It is authorized for the update and then Salesforce goes on and re-evaluates, every action of the object. Those workflow rules which were not fired before will get an automatic retrigger. 

Scenario 3: You have both a controller extension along with a regular controller. Instead of writing it in the custom controller, you wrote the logic in the other. Though both Custom controller and Controller Extension can be processed in a system mode, then why would you ask for a Custom Controller?

A custom controller can execute logic that the need to impose on a standard controller. If you wish that the VF page be running in the system mode, it is way better to use custom controllers. This way there is no field-level security or permissions enforced on the present user.

The controller extension proposes the qualities of a custom or standard controller. If you wish for results to impose the built-in functionality but overrule one or any other action like save the view, or edit, try on adding new actions.


Even if in system mode, a controller extension class is worked on, if a controller extension enlarges a standard controller, as a result, the logic of the standard controller executes in the user mode instead of system mode.

So, if you implement developing everything from the beginning without any standard functions, the custom controllers are the key. This is one of the most common salesforce scenario-based interview questions asked in the interview.

Scenario 4: What if a user did not allow permissions to the nursing personnel within a profile for example called ‘P1’ for an object called O1. But still, the user can produce records for the mentioned object. How is this possible?

Deletion/viewing/creation/Updating these kinds of relevance are attainable through profile permission.  It proves that we always have a small tendency of getting the results in associate with the nursing object. This produced permission needs to get enabled from the Permission Set or Profile. It is sure to be permitted within the Permission Set if not in the Profile.

If the object level Permission and the record level Permission go against each other, The Permission on a  record should result in a combining object level, record level, and field-level Permissions. The winner is the more restrictive one. 

Scenario 5: If there are two objects Obj1 and Obj2 not related to one another of a state of affair. Try to make an MDR between these two objects.

First, we need to separate the two objects into master and detail. Let’s think of Obj1 as the parent and Obj 2 as the kid object. Now, what should be the relation between these two? Every child must have one parent, meaning that every record should have a linked parent record in Obj1 which is also present in Obj2. But there is also the possibility that there might be multiple kids of that parent.

 Scenario 6:  If there are pre-existing records within Obj2 then?

In this case, there surely will be connected records in the master object of the detail object, but they are not associated. To find the relation between these two we need to go through a basic search.

  • A search field is produced in the Obj2
  • Obj1 is a  related field, from which all records are taken. The search field in Obj1 is updated.
  • Then the search might be turned into a  master-detail relation.

Remember to prepare it in an easy to understanding way for salesforce scenario-based interview questions. 

Scenario 7: There is a profile called ‘ProvideReadAccess’ and there are two present users U1, and U2. Then there is an object named X. How can we go with it if I want read-only access for the user U2 and read-write access for U1?

The settings which declare ‘Read’ access, make it common for both users. The condition affected, both U1 and U2 can read the records. In the next step, we need to generate ‘GrantWriteAccess’. This Permission set would be given to the object to access the permission set to U1.

Final Thought

The above salesforce scenario-based interview questions will surely help you ace the upcoming interviews with the highest possible success rate. Prepare these questions before the interview. Even though all the questions asked might not be similar, knowing that you have worked hard preparing the types of questions will boost your confidence. We wish you the Best of luck with the interview.