welcome to the start of our brand new series on Salesforce mock interviews in this playlist we are bringing you realistic in-depth interview simulations that may make this actual Salesforce job interview experience our goal is to help you prepare thoroughly and confidently for your Salesforce job interviews we'll cover a wide range of questions and scenarios providing you with valuable insights and tips to a your interviews whether you are a freser all an experienced professional this series is designed to boost your confidence and Readiness so if you're serious about that Salesforce job make sure to like this
video And subscribe to Salesforce Hulk Channel and hit the Bell icon to stay updated with the latest videos in the series let's get you interview ready hey tar how are you hello like uh I'm good okay so are you prepared for the interview yes I am great so let's start it and I want you to provide me a brief introduction okay so yeah like uh I had uh done multiple internship in Salesforce domain as a Salesforce admin uh majorly I had worked in admin part like I had worked on flows and like process automation approval
process I had also created data models reviewed like seen various data models of different different projects done Trail ad as well so I had into three months of inter internship experience as well as I am having like uh I had done lots of things over traed as well and also I have learned from various uh other sources okay so since you have done internship do you have any certifications yes I had like uh I am having Salesforce admin certification okay nice uh so it's great that you have a certification so if you don't mind let's
switch let's jump to the questions okay the first question I would ask is what do you understand about data model a data model is simply a data structure like which defines the tables and the fields yeah that's that's our data structure is like a data model is which also includes validations look up filters relationship between various tables that's all okay since you added relationships how many type of relationships do we have in Salesforce like if I classify relationships there are three types of relationships one too many uh one to one and many to many so
which all we can create in Salesforce like we can create uh one to many as well as many to many as well as oneon-one by using some customizations okay great so that's great that we can do all these but how do we achieve one too many like simply uh we need to create if you want to relate two tables or two objects uh then we need to create a relationship in one of them which is a many side basically which relationship would you create uh like it depends on the requirement if there is a dependency
like security related dependency between these two objects or there is a roll of summary required then definitely I'll go for master detail otherwise I'll go for lookup so is it required to create a master DET relationship always when we want to create a ro of somebody uh come again what do you say okay the question is that is it required to create master de relationship always when you want to create a ro of some yes like it's not necessary but like let's say there are two objects on which there are already two Master detail created
then definitely I cannot create a third Master detail relationship field on it so in that case I'll be achieving the role of summary kind of functionality by using flows or triggers uh and like I'll be creating lookup relationship I have to create that so you will create a look relationship then use flows right yeah yeah okay great so since you added uh flows which type of flow would you create like I'll be creating record triggered flow okay so you'll be creating a record triggered flow and what all type of flows do we have like we
have five there are many other templates which exist in flows but the core if I'll talk about there are five uh yeah okay so can you name them yes of course like uh there is a screen flow record ticket flow like record flow record ticket flow comes under Auto launch one so Auto launch is further classified into record Tri flow scheduled event flow platform event flow and also there is a newly added flow it's not that newly added but it's it's something which is which came latest uh which is orchestration flow okay nice so since
I think that you have knowledge about uh triggers and all as well right do you a little bit I haven't done much on like practical part on that but yeah I no problem so do you know what differen is between a flow and a trigger when to use which uh yeah I had to observe one thing uh like in flows if you'll see record triggered flows are there right which is which comes as an alternative to triggers which are code related thing so in record flow you'll be observing that there is a create event there
is a create or update event there is a delete event but there is no undelete event which is there in the trigger okay so that would be one anything else anything else like uh yeah obviously like in triggers when it comes to complex functionalities we can use map to optim the code to reduce the time complexity of that but when it comes to the admin part the flows part there is no map kind of functionality in flows so that that optimization related things cannot be achieved there you have to use for Loop in inside a
loop so that is something which I find like in coding and flows like the difference okay great so let's move to the next thing uh I would ask you questions regarding data security okay can you tell me what's the difference between a profile and a role so a profile is having set of permissions like app permission page layout object level security field level security login access time login RS basically so these are the things which are there in profile but uh like if I talk about roles it's simply added in Salesforce for the purpose to
give additional access to the managers of the subordinates okay uh anything else you want to add yeah that's that's I think uh that is the major difference that's a major difference okay so when do we create which when do we need to create a role or when do we need to create a profile we always need a profile and like a role is also necessary in some situations like uh when we need some additional access like profile is something which is which gives the minimum access to a user in the organization and and as I
specified already that role is something which give additional access to the managers to the people who are in higher role provider higher access does it in terms of object level access or in terms of feed level or in the terms of record level I'm talking about when I'm talking about rules I'm talking about record level security okay so it provides more access to the records yes okay great so if we want to provide provide access higher access with the help of rules can we do that of the object uh like let's say uh if I'll
think of an example for this to explain you so like there is a user right and uh there is a manager of that particular person so at like a profile level they have create and added access right both of them have create an added access now uh like in the owd it is set to private so both of them can see their own records only right both the users the user which is a normal employer and the the person who there is a person who is above the hierarchy like he is the manager of that
user so if the role AR key is enabled then in that case the above the manager will be able to access his own records as well as the subordinates records and the subordinate will only able to access his own records okay that's great uh since you know the difference or whatever we will be creating for as in considering a a role okay now let's move to the next question to whom okay uh I have a better question what what is um mutable permission set what is a mutable permission set H actually I don't know about
that but uh I know permission set if you want I can explain that yeah let's let's go with that so in permission set we can give additional access more than a profile and there there in that the the like uh we can give more access to the profile and also we can set the expiration like we can set a duration a particular duration till which the access will be there the addition access will be there to set up users okay so the scenario states that we have a organization which is having a sales using Salesforce
and it already have around 500 users which are using it there is a certain requirement that is there is a user which can see a record of account object or you can say any object whichever you want to consider it now what we want is that we shouldn't we we cannot as there is multiple users already present we don't we don't want to provide any profile level security or any we don't want to create any profile as well we can't do any owd because as we already have multiple users but still we want that the
particular particular user should not see the records of that particular object or you can say the subset of those records he he should see certain records but not all the records what do you think we should do like for uh uh like o owd we can make private and then we can create sharing rules yeah but that that's the thing which we don't want to do because once we do that we need to change the set all the complete sharing settings and all the things again for our or organization why why can because we already
have it public read right so if we change it to private all the user will not able to see anything right so we need to establish every single thing from the base that's the problem that's why we just have have only one user should not see a particular set of Records in a particular object in that case uh like I am get I'm able to think of one solution which I haven't like not tried much which is restricted rules or scoping rules which we can use there in data security okay which one you would use
scoping rules or restriction rules no restriction rules I think maybe I'm not very sure about okay so do you know about restriction rules no not much but I had heard about it okay okay great uh since you don't know about restri let that's not a problem uh let's move to the next question okay what's the difference between public group and a q they are totally different things like a public group can consist of users roles roles and subordinates it's a group of multiple things like this cu's is simply a functionality which allows someone to take
the responsibility of a particular case or a lead something like this okay where do we see the cues like we have to go into the setup in the quick find box we need to write down the cue and there we can create a queue and if we want to like uh see the cues like the create already created cues then obviously you have to go to the record page you can change the owner and there you will be finding one more option Q if you have created the queue for that particular object anywhere else you
think no I am not getting like uh right now any other okay uh have you heard about list views list views yes yes so don't you think we will see the cues there as well yeah I think yeah the list view also get created when we create a queue for a particular object okay can we have a single CU for multiple objects uh no I I actually I'm not sure about it but I feel no okay uh just check about it uh I think it we can create a single CU for multiple objects maybe yeah
okay so let's move to the next question so let's uh since you know about sales Cloud right so I'll ask you questions regarding that the first question I want to ask uh do you know about opportunity line item yes what's it what's an object what's the use of that object uh as you can see like its name is opportunity line item it represents a junction object between o opportunity and product are you sure it's a junction object it's a yeah like uh it's a common object between opportunity and product uh what do you meant by
common object like uh there is a relationship of opportun relationship field of opportunity on this object as well as the product relationship field is also there okay okay so you meant right reference object right something like reference object uh I didn't get you can you repeat you meant the common object like a reference object right yeah okay so okay uh do you know what is campaign member oh yes I know okay so what's the relationship between campaign members and all the objects like campaign member is a tri Junction object which is uh related to lead
contact and campaign but maybe it is also related to if I am able to remember recall that it is also related to opportunity we need to enable something in the quick find books okay uh I think you meant account object right no I'm actually not sure I'm sure about lead contact and uh campaign itself that's that that is something I am sure about okay what is a standard price book standard price book is a price book which is already present in the arc anything else what is the use of it why it's already present uh
okay so because let's let's let's understand that if we want to add a product to opportunity then in that case there is there is a need of a price book without a price without adding a price book we cannot add a prodct to a opportunity the reason being that there is price book defines the price of the product if price book will not be there then obviously from where we'll be taking the price of the product okay can there be multiple price of a single product yes there can be but of uh like of course
while adding it to a opportunity we have to choose one of the price one of the price how do we do that exactly like uh if you like uh like I am trying to recall that like if I'll go to the record page of opportunity from there we add the product and while adding the product the we get two options first option is add a product second option is choose a price book so so that's that's where from like uh we can add a product or we can choose a price book to select a particular
price okay great uh that's right and let's take this interview to an end do you have any questions for me yes uh of course like I I want to ask for the feedback like it's good or no tar I think that it was great but you have a basic knowledge of the foundation of Salesforce you need to have more knowledge since you already told that you don't have uh development knowledge much so that's was the feedback you should focus on that as well thank you
