 I think there is some issue with my video. I think your video is stuck. Yeah. And we are live. Just a second. Okay, okay. No problem. We'll check it. Okay. So, hi everyone. I am Sanjay Gupta. I welcome you on Sanjay Gupta Tech School. So, today I have Pulva with me. So, as you all are aware, like we are doing mock interviews. So, in continuation with that. So, today we'll be doing some admin related Q&As. Right? So, welcome once again Pulva on the channel. Thank you for having me again. Yeah. So, I can see with the number of views, like people are liking these kind of sessions very much. And I am sure like these sessions are helping them in preparing the interview question and answers. Right? And sorry guys. There is some glitch in the video. So, meanwhile I am figuring out what happened. So, let me ask one question from Pulva. So, like today also Pulva will be answering all the admin related questions. And wherever like she needs my help. So, I will pitch in and so we'll try to share my experiences as well. Okay. So, my first question would be, can you tell us about different clouds available in Salesforce? Absolutely. I think this question not in terms of interview perspective, but this question is going to be helpful for people anyway, because they are not aware about the clouds. So, what I am going to do is I am going to answer this question from an interview's point of view, as well as I am going to explain some basic stuff. I am going to explain the definitions about each and every cloud also, so that it will be helpful for people to understand that what all Salesforce offers. So, in Salesforce, basically we have six types of primary clouds. We have Salesforce, Sales Cloud, Service Cloud, which is absolutely free, which comes by default by Salesforce, which is used for sales. And I will explain each one of them separately. Then we have Marketing Cloud, which is also known as Salesforce, Marketing Cloud, SFMC. We have Commerce Cloud, which is also known as SFCC, Salesforce Commerce Cloud. Then we also have Health Cloud. We have Finance Cloud. And that's how we have all these clouds in Salesforce. If we talk about Sales Cloud, which captures your sales process in Salesforce. Basically, it helps you to capture your opportunities, contacts, lead management. All of this is managed under one roof, which is considered in sales. And it is captured as Salesforce, Sales Cloud. Then we have Service Cloud means Service Cloud, just customer service. Anything related to cases, ticketing, all of these, which is helping you, maybe live agent, omnisudio, all of these are considered, not omnisudio, that is considered as separate velocity. But Service Cloud means anything related to customer service. If you're providing any specific service to your customers, you can manage in Service Cloud. Marketing Cloud means anything you deal with marketing. If you want to send some email campaigns, run some email campaigns, or send some mask, bulk emails, do any kind of marketing, then you have Marketing Cloud in place. Then if we talk about Commerce Cloud, it means it is also known as IoT Internet of Things. That means it was earlier known as Experience Cloud. Now it is known as Commerce Cloud. So basically it is used for e-commerce websites, like Mintra, Amazon, or eBay, any e-commerce websites, these platforms are using e-commerce cloud so that they can manage their business, that kind of e-commerce business into Commerce Cloud. Then we have Experience Cloud, that is different. So Experience Cloud was earlier known as Communities. And with the help of that, you are able to create portals. Like you have Idea Exchange portal, or you have Partner Portals. Partner Portals can be managed using Experience Cloud. Then you have Health Cloud and Finance Cloud. That is specifically for those industries if a healthcare industry wants to use Salesforce. They can specifically use the healthcare cloud for their businesses. And similarly, it goes with Finance Cloud, where finance industries, banking, and all of that, they can, or mutual fund advisors, all of these people have started using Finance Cloud of Salesforce. So this is how these many clouds are there in Salesforce, which you can explain with the help of example of each one of the clouds. Yeah, brilliantly explained. And I think you covered lots of clouds. One quick check here, like if you want to know the list of available clouds, so just visit salesforce.com. And at top left corner, you will find products. So there you will find some basic products like Sales Cloud, Service Cloud, Marketing Cloud, Commerce Cloud. Now, two more clouds are added, Data Cloud, AI Cloud. And if you click on Industries, so all the industry related clouds list will be available there. And one more thing, we can add like all these clouds are having pre-built configuration. So on top of that, like if any customer wants some customization, so like as a consultant or consultancy form, we just need to modify that particular cloud configuration as per the customer's need, right? And rest, I think Purva already covered individual clouds. So whenever interviewer is asking, tell me different, different clouds. So don't just tell the names, like explain it a little bit more clearly so that interviewer understand like you have lots of cloud knowledge and sales and service are common. So just go till like Purva explained Finance Cloud as well. So you also need to touch those, Experience Cloud. These are like, these are the clouds which like all the consultants and developers or freshers doesn't really talk, okay? So I think we can move on to the next question. So like in today's session, lots of questions which we are targeting are basically for fresher interview, right? So you will see some basic questions if you are experienced for. So if you are fresher, then these questions and answers will be really helpful for you. So next question Purva for you is tell me what are objects and fields in Salesforce? Right. So I always love to explain either the interviewer or my candidates with the help of some real life examples, which makes it easy for people to, you know, learn it and remember it. So when we talk about objects and field, the best example which I always give is how you organize your cupboards at home. When you're organizing your cupboards at home, you keep your trousers at different sections, you keep your footwear at different sections and you just organize your cupboard in that way so that it will look clean. Same way in Salesforce, you have different objects where you keep your data, not in one place, but in different sections or in different, different objects. So that we call as objects. So in objects, we have two types of objects in Salesforce. We have standard object and custom object. Standard object are those which are given to you by default by Salesforce. And custom objects are those which you create as an admin or as a developer. So that's the difference between standard object and custom object. And custom object is just like the spreadsheet which you put in Salesforce in more graphical representative manner. That's the only difference. So it provides you fields. Now when we talk about fields, that means we are just understanding that where exactly to put the data. So for example, if you are belonging to education industry, if you have a school, then you will be entering your student's name, address, class, marks and all of that. So all this type of information you will store in Salesforce in the form of fields. So if you go or refer the Excel file, the columns are known as the objects and the rows are known as the records. So this is how you identify between object, fields and records. These three things go in parallel where we just discuss and talk and explain more about what is object just to store the information or the data in Salesforce and fields means what exactly and where exactly you are going to put the data and records means what exactly you are going to enter as entity in Salesforce. So that is the definition of object, field and record. Okay, nicely explained and I'm really very sorry about the video. I'm trying to start but don't know what is happening. Okay, so moving on to the next question. Like we have lots of applications in Salesforce which we say as app. So can you tell me like can we create more than one application in Salesforce? If yes like what is the advantage or uses of app in Salesforce? Right, absolutely. So I will continue the same example. For example, you are organizing your cupboards at home and you are falling short of place. You have already organized your clothes and accessories and footwear in a proper way but you are falling short of place. So in that case, we use hangers and we use extra sections or things like that in order to keep our stuff in proper way. Similarly, if you compare the same example in Salesforce, how you do it if you already have some inbuilt apps provided by Salesforce like marketing, sales, service, these are the apps which are provided by Salesforce. But on the top of that if you belong to a different industry like education, healthcare, you will have to create some custom apps where you can put the data into these applications. So yes, we can answer the apps, sorry, we can create more than one application in Salesforce and there are two types of apps which you can create there is one console navigation and there is one standard navigation app which you can create in Salesforce. So console navigation apps are primarily used to create a console view where you can have some sub tabs into one tab rather than having separate objects looking at besides each other and in standard navigation whatever you see if you go to marketing app or if you go to sales app, the similar type of structure you create in standard app. So this is I think good explanation that if you try to explain the answer of the questions by explaining the practical knowledge which you have gained if you have created application you will know the answer that what kind of apps you can create in Salesforce and what is the use of creating these applications. So I think that's how we can answer it as my opinion. Yeah, I think very well answered and I'm back on video. So nothing is there that I can add. So these were simple questions. Now I'm going to throw a difficult question to you. So and it is very much interesting as well which is related to relationships. So we have two major relationships in Salesforce. One is lookup and one is master detail. So what what are the differences and in which scenario we need to go for lookup and in which we need to go for master detail. Absolutely. So as you rightly mentioned this question itself is complicated and the relationships are itself complicated whether in personal life or in professional life. It's always complicated but that is important. It's very important for each and every individual any relationship right. So similarly in Salesforce also relationship is the base of any objects. So if I have to define relationship in a simple words, it's simply connecting objects. You can connect one object with many objects which will have one too many relationship. You can connect with many objects also like you can connect multiple objects with each other using junction objects which will be considered as many to many. So when talking about master detail or lookup relationship we have to understand the combinations also which you can make using these relationships. So let's first try to understand that what are these types of relationships. So I will take example of standard relationship first because we have accounts, contacts and opportunity. This is the best way to understand relationship in Salesforce. For example if you have one account in Salesforce which you have created. Now you will create multiple opportunities associated with one particular account. That means you are creating one too many relationship here which is standard given by Salesforce. Same with account and contact. You have one too many because you are creating many contacts associated with one particular account. But can you imagine the situation vice versa. Can a person work in multiple companies at the same time? No. Can a person have multiple parents at the same time? No. But a parent can have multiple children. So that is also a parent child relationship which is defined in Salesforce where one parent will have multiple children as simple as that. One account will have multiple contacts but one can contact or one opportunity cannot have multiple accounts. So that's the best way to understand simplify it if you want to understand relationship and I always give this example as the best example to explain because you will not get confused. Otherwise if you try to explain relationship with any other example you will get stuck because it is complicated to explain. So this account, contact and opportunity example is the best example. So we have understood two types of relationship now. One too many and many too many. Now when you are creating many to many relationship you need someone. Let's try to understand with a very creamy example I can say. For example if you like someone, if you want to approach them, you need some messenger right? You need some mediator to connect with the person. Similarly in Salesforce if you want to connect many objects or more than one object you need one mediator which is known as junction object. So junction object is nothing but it helps you to combine multiple objects. I'll take another reasonable example if you want to understand more about it. For example you have school, teachers and students which is the common project we all practice in Salesforce as a beginner also. So you need school as junction object if you want to combine student and teachers together. So school is one common object which is combining the students as well as the teachers. So you cannot combine school students and teachers directly. That's why if you want to explain junction object also it is nothing but one object which is combining more than two objects. Now we have talked about many to many we have talked about one to many. Now there is one more which is self-relationship which an object can create with himself or herself or themselves. So an account can have a self-relationship with account itself, a user can have a self-relationship with user itself. For example if you want on user record to capture the managers of the users. So you can create a manager field on the user record and that will be considered as self-relationship. Then we have hierarchical relationship that means you want to define a hierarchy in Salesforce like we have account hierarchies and we also have users and roles that also defines the hierarchical relationship that kind of relationship is also used in approval processes where if you want to send approvals to the hierarchy some managers or managers manager then you can have a hierarchical relationship. Then you also have indirect lookup relationship and external lookup relationship. This is used when a third party system is involved when you are integrating Salesforce with SAP or any other CRM then you will have to create a field or a relationship between these two objects of these two CRMs in order to show your data from one CRM to another CRM. Then you will use either indirect lookup relationship or you will use external lookup relationship. So these are the some types of relationship in one example only you can explain all these relationships. Now we will come to master retail relationship and lookup relationship. Master retail you are going to use when you want to control one object. So master itself explains you that it is controlling person. So in our daily lives also we have in partners also we have one partner who is more dominating it is always the case. Similarly in Salesforce also if you are talking about master retail relationship the master object will control the children. The best example if you are deleting if you are created master relationship and if you are deleting one of the object the master one the child records will automatically be deleted that's the major difference between a master detail and a lookup relationship. Whereas in lookup relationship the child records remains the same there is no effect on the child records. So it behaves separately they don't they have their separate entities in Salesforce. So that's the difference between master retail and lookup relationship also and when you have to create it if you want to analyze it more you have to figure out that if you want the master record to be controlling in Salesforce then you have to choose master retail and if you want two objects to behave separately as separate entities then you have to choose lookup relationship. Yeah nicely explained one thing someone is asking about can we have any real-time example for self-relationship Yes for example if you want to capture your manager's manager on a user page so there is no field standard field in Salesforce which will help you to capture the manager's manager you only have manager field so you will create a self-relationship between user and user so that you can capture the information of another user on to the same object so that's the example Yeah and I think if I remember correctly so on account record there is a lookup to account already created which is labeled as parent account parent account if in a case like you have one parent company and that company is having lots of child companies under an umbrella so in that case you can use that self-lookup okay and so you compared lookup and master detail but like you didn't cover security thing so can you elaborate those things as well like how security applies in master detail and how in lookup Right see so security when we talk about security there are lots of things and people get confused between when to apply OWD when it's applied and when to use role hierarchy when to use sharing settings opportunity, territory, lot of sharing things are there so let us sum up this whole security model of Salesforce is there are only two types of sharing which provides which is provided by Salesforce record level sharing and object level sharing so if you remember things like that then it will be easy for you to remember it even after 10 years in Salesforce so if you want to talk about object level security that means we have profile and permission set which is covered into object level security if you want to talk about record level security then comes everything under record level security because you're controlling the records if you want your users not the object itself on the top of any app then you will use profiles and permission set you cannot hide the object itself from any other feature in Salesforce so object level security straight away go to permission set and profiles but if you want to segregate into and bifurcate into or narrow down your search then you will use record level security with the help of rule hierarchies with the help of OWD's with the help of manual sharing or team sharing and territory sharing at the end so rule hierarchy means you are just sharing the data on the basis of rules for example if a manager they should be able to see the data of the team members however the team members should not be able to see the data of the rule so the person who is above in the rule hierarchy will have access to the person's data who is below in the rule hierarchy that's simple this is with the help of rule hierarchy then you have OWD's or white defaults so I will start from basic because this is specifically for freshers who were just to interrupt can you just related with lookup and master detail as well yes sure so when you are using master detail relationship and lookup relationship the security will work as it is for example if you have created master detail relationship on account with any other object or lookup with any other object the security will work on the top of it and the person will have the same level of access what he has on the profile level so the access or the security will be driven from the top level yeah so just to add on there like in master detail the master object security will apply on child like if you have access to master record then only you will be able to access child but in case of lookup it is not the case right so this is the minor difference if we talk about security in these two so there I remember simple word which we can remember so master detail is tightly coupled and lookup is loosely coupled yeah just continue with the record level security sure so then comes the order beauty that means or quite default so that settings we have three or four types of settings right private public read only public read write and public read write transfer so private means it's private the data is private nobody will be able to see each other's data and public read only means the data will be read only but nobody will be able to edit it and read write means everybody will have access full access on each other's records so order beauty is set on object level because it is or quite default and it is set for the whole organization you cannot bifurcate it on the basis of rules profiles or users once it is set for the whole organization the whole organization will follow the same settings and then you can bifurcate with sharing rules if you want to expand the access if the order beauty is set as private for any object you can just expand it with the help of sharing rules or you can share the records with the help of manual sharing or territory sharing these type of models can be used if you want to understand or apply the security in Salesforce okay so moving on to the next question so there is one question from chat so it is related to conversion like look up to master detail so how to convert look up to master detail right so you can any time convert look up to master detail but a few considerations like you don't have to there should not be any active records on that particular object otherwise it will not allow you to convert the look up to a master detail and master detail cannot be converted to a look up vice versa is not possible only look up can be converted to master detail and only two master details are allowed on any object so that's the simple answer if you have anything to add yeah so like if you're converting look up to master detail so initially like if you are not having any records so we can directly convert there will not be any issues but if records are available so what you need to do you just need to convert that look up field and then you can simply convert that look up to master detail and as an architect I I would suggest like if you are creating any object so you just need to decide in initial phase whether to have master detail or not because if you have created look up and in the middle of the like implementation when you have created lots of records if you try to convert look up to master detail so it would be less of the things yeah right okay so we have one more question can we have more than one master objects so answer will be yes and we can have two master objects sort of and siraj is asking if we have parent like parent object is having record access child don't have any access so I'm thinking he's asking about access like if child is not having object access so can he be able to see yeah so access should be there and if object and field access are there then only record access will be there right because profile is the head of sales force if a person not have access through profile then this will not work and one more thing like whenever we are creating we are going on to the sharing rules and we are changing OWD so there is one option controlled by parent so if you have that option then basis on the parent you will be having the security on your child but provided you should have object access yes so I up is asking about with sharing and without sharing in apex so we are not discussing about this thing right now so we are skipping it so one more question related to OWD so whenever we apply OWD so there are three options public read public right and public transfer so if you can add something so what they are asking exactly type OWD no whenever we try to make any object OWD to private so other than private there are other options are available public read only public read right and public transfer so private is straight forward like you won't be able to access the records but if we do public read only so record will be shared but you won't be able to modify the records and if you have public read right then like you can view and edit the records but again on object level if you have access edit access then only and transfer is for lead like if you want to transfer lead into account contact and opportunity so transfer is basically for that purpose okay so I think we can pick next one roll up summary if you can talk about that sure so we have already talked about master detail now before starting about roll up summary you should know that only roll up summary can be created when you have a master relationship between two objects otherwise you cannot create roll up summary field so roll up summary field gives you the access to perform four types of operations on the object you can find the sum minimum maximum and average means for example if you want to find the opportunities then how many opportunities are associated or added on one particular account then you can use the count operation using the roll up summary you can count the number of opportunities or number of records associated with that particular object then you can also summarize it for example you have a closed amount on the opportunity and if you want the sum of all those opportunities which are added on the account level the sum of all those opportunities so you can use the roll up summary field in order to find out the sum of all total opportunities similarly if you want to find out the minimum amount out of all those records added on to the object and maximum also you can do that there is more to it you can also filter down the data using the criteria option in roll up summary field if you want to find out the amount of only closed one opportunities then you have the filter option also available which we rarely use so it is good to explore that feature also that's it about roll up summary field if you want to add something so I want to take one more question like Saurabh is asking OWD's private then can manager access the records of the user who is under the manager if the OWD is private and if the access is expanded through roll up through roll hierarchy then yes they will be able to access it I think Saurabh you got the answer okay so Kunal is asking what if you need roll up on a lookup so through configuration can we do no yeah no we cannot it has to be master it's a standard limitation of functionality still if you want to create roll ups on lookup relationship so you need to implement a trigger for that Sai Mahesh okay so one group records shouldn't access to view by another group in the hierarchy but both the groups have the same profile then how we can achieve so if you are talking about roll hierarchy so roll hierarchy means like the subordinate record will be shared who is above in the hierarchy and if we have two groups so in that case like sharing rules will be good fit Sai Mahesh in my opinion your question is little bit confusing you are just saying hierarchy so I just want to confirm like is it roll hierarchy or something else Sneha is asking is there any standard junction object available in Salesforce by default I think yes there are a lot more available yes you can take the example of opportunity products and opportunity product opportunity product is junction object which is combining opportunity and the product object there are lots of junction objects available so someone is asking how roll up summary field behave in junction object so like if you are creating a junction object so it will be having two master detail so basically roll up we create on master so I think both the master both the parents will be having separate roll up fields created right yes because it doesn't affect the master object you have to create it separately because it is created on the parent object so we are creating roll up on master record so we have two master records so on both we can create it separately yes relating to other child record object okay so I am asking look up to master but in the object there is large amount of data how to do that so I already told you in all the records you need to populate that lookup field so how you can do it mass level so you need to export the data then import the data having that lookup field populated and then only you will be able to convert so or maybe you can create some automation through that you can fill that lookup field okay one more interesting question if two managers have same profile so is it possible to see each other profile I think this question is incomplete he is asking if two managers have same profile so is it so it is possible to see each other profile I think he must be asking if they are able to see each other's data so yes if we have lookup file they have same access they will be able to see it not each other's data that depends on record level security actually but other than that they will be having same things yes so siraj is asking how to provide org level security through OWD's right org level security I am assuming not record level security he is asking about org level like org level we can have like user access or password policies those kind of things okay that is managed under profile you have password policies and login IP ranges all of these can be managed through profiles and you have under session settings also you have all these settings where you can manage the login IP address and browser cookie settings and all of that under sessions so that can be controlled through on the organization level yeah so Kunali is asking junction object how to identify and explain it in interview so please go ahead the junction object is used in many to many object to join the multiple or many objects and if you want to explain with the help of example you can take the example of students teachers and school where school is acting as a junction object combining teachers and students together so that is how you can explain the junction object it is nothing but one object which is combining other objects yeah and just to add one thing here if any object is having two master detail so that will be actually junction object so in normal case like for look up this rule doesn't apply because junction is having a nature like if you delete any master records so junction records should also be deleted so that's where you can answer there is one question I am not aware about it I am just asking to you if you know otherwise we can skip so he is asking what is entitlement and milestone tracker is it similar to escalation rule okay so this is related to service cloud actually entitlements and milestones this is created usually to track SLAs and all of that so this is used on cases this is related to escalation rule and similar we cannot say because escalation rules are created to escalate the cases and manage the tier 1, tier 2 stuff on cases but entitlements and milestones are used to capture the SLAs it primarily works on the SLAs followed on cases on time or not so that's how you create entitlements and milestones and sales force okay Srikanth is asking how we can set IP address so I think you already answered session settings yes under the setup in session settings you will find the IP address for organization and it is also there on profile also login IP ranges okay next question difference between page layout and record page record layout record types right no page layout record page lightning record okay okay so page layout is where you manage the fields sections and how to rearrange the fields how to make the page look better record page includes the buttons and everything also that is lightning page or lightning record page which you can customize which includes your related list section which includes your report sections your chapter tabs all of this is managed under the record pages which you can customize and page layout is only to control the fields the read only if the field is read only if you want to make the field required then you can control these settings with the help of page layouts and both the record pages and the page layouts can be assigned to different profiles through the assignments right just to add one thing like on page layout we can have related list as well yeah yeah rest I think you covered okay next is lightning pages so one you already covered record page other than record page what all lightning pages we have right so we have our home page components also under the lightning pages which you can create and you can add some dashboards, accordions and a lot of stuff on the home page components also and you can create more lightning pages on the custom lightning pages like you can change the whole standard view of the pages by assigning those pages to org level or to profile level or to app level also okay next is what is the uses of validation rule right so validation rule when we are talking about making a field required right so I'll add something to it whenever somebody is asking you to make a field required there are various ways to do it first thing you can do it at the field level which will be required for everyone by default for all the profiles and then you can make the field required on the page layout which will be applicable to the profiles whom the page layout is assigned then the what comes the validation rule where you can make the field required or you can throw some errors on the basis of some criteria if you want to make the same field required like opportunity stage if you want to make required when the closed region is filled as something then you want to make that field required you can do that lots of permutations and combinations are there which you can use through validation rule of you can do validation rule it is just a way of throwing an error in sales force using some criteria if you want that amount should not exceed more than 10,000 then you can have the validation rules anything you want to control or restrict you use validation rules yeah so now let's pick some questions from chat so somebody is asking what if an object has one master detail and one lookup so does it it is considered as junction object so in my opinion no to master detail it should be it is a junction object there only it will be considered as junction yeah and related to this question there is one more question how we can identify the primary and secondary object so I think the first one which we create will be considered as primary yes next is if also also in order to identify what is primary object you will see the related list as only for the child object yeah on parent so if we have two parents so both the parents will be having the related list yeah and one more question is in junction objects which master object sharing security applicable so I think the first one master right yeah then one is related to security if two users have under different profiles how can they see each other's data so I think so they you need to understand data security properly through profiles like records are not shared or not controlled so it is controlled through record level security OWD roles which Poova already explained so in my opinion like we are doing mock interview session so we are assuming like you have gone through the concepts properly so just understand that concept well because the question you are asking it is not correct okay and if we see it from profile perspective so if we have two users and two profiles so in that case they will be able to access the objects and fields as per their profile right so each other comes for records not for like object and fields okay next is so another interesting question if I have two master detail object and one junction object there and I want to delete one filed on junction object what effect on one of the master object no effect I think from junction if we delete anything nothing happens on master but if we delete any record from master so that related entry in junction will be deleted yeah okay so next is how to give access to lightning component select users what is custom he is asking three questions together so yeah this is also like not related to admin it is related to development and one more question I want to delete some customer records but don't want anyone else to recover what can I do so I think admin can recover yeah recycle bin can be controlled by admins only none of the users have access to no I think there if see if the customer record is owned by you then you will be able to recover it from recycle bin but apart from that only admins can recover it if the record owner is different right another one is what is business hours so do you have any idea okay yes so business hours is something where so in my company first company cognizant what they used to do is they used to set up business hours for us like if the shift timing is from 12 p.m. to 9 p.m. we were allowed to log in only during that time so we were logged out and thrown out of sales force automatically as soon as the business hours are over so this setting can be controlled under setup business hours is the name where you can control the login of your users during those business hours similarly you have holidays also where you can set up holidays in sales force if 25th of December is a holiday then none of your users will be able to log in during that time so just to control the login during those hours okay yeah I think we are good on time so we already did this session for 50 minutes so I think we can wrap it here because we will be having couple of more sessions on admin stuff and I think today's session was more interesting because lots of folks involved and they asked good questions and I appreciate your efforts as well like you really very well answered those questions so people are liking your like you are relating answers with real life scenarios so like Kunal is appreciating your efforts so it is great and maybe tomorrow we will deep dive on security more right yeah so okay anything you want to add or you want to say to viewers so that they can be prepared for next session yeah I would say that they can do some homework before because these are mock interviews right so we are covering the concepts also because it helps people to use the example and another advice is use example in order to explain any of the concept to your interviewers that will really help you to crack the stuff that's the advice from my end and I'm also enjoying these sessions because because of these sessions as Salesforce is vast right so we are not able to cover each and everything but because of these sessions we are able to talk about important stuff which people will be able to relate and understand and remember it so it's good that we are able to use these and we have come up with this idea so I'm sure people will be able to make the best use of it yeah I'm sure too and I think now people will follow all the sessions because now we are talking technical so people like technical stuff more if we talk about Salesforce so yeah let's see how much sessions we will be able to conduct so guys we have planned 3 for admin and I think 3-4 for development but we'll see like how it goes okay so with this note I take your leave and thanks to Purva for spending some time for the community and I'm sure it is helping a lot of people thank you Purva thank you for inviting me yeah guys see you tomorrow with the new lot of questions thank you everyone thank you everyone bye bye