1) in first question if there is no profile level access for the object, then user have got the extended permission using the permission set that the reason he is able to create the record for that object 2) after deleting records go to the setup and search for hard delete, if u delete from there u can't recover the deleted records from the system.
1) in first question, user might be getting additional permission through a permission set 2) in secod question, to delete bulk records permanantely, we can use Hard Delete, to enable this go to user's profile and enable "Bulk Api Hard Delete" and use tools like Data Loader to hard delete data(in data loader setting, check Enable Bulk API and Enable Hard Delete.)
Yess, Nice questions But now a days no one asking tricky questins. Interviewer directlly asking to write trigger or LWC code. I will include some of them in my question bank 😅 Thanks!
That question on Full permission on parent object but not on related object record can also be extended by saying --> if trigger creates it , will user be able to see it or not ? So we can add to it like Trigger runs in system mode ---> so record will be created but user cannot see it.
Default batch size is 200. Object A could be the detail object since the sharing settings and object permissions will be inherited from the parent. correct me if i am wrong Hard delete in data loader
Question 1 Answer Via Permission Set, additional permission might given like 'Create' if not then 'Modify all data' permission check box might be tick for that profile.
For the batch class rollback question, The error chunk of 200 records will be rolled back only if we are using Insert statement, in case we use database.insert statement the correct records will be inserted and the error one will be ignored. In that case the answer will be 399 records are inserted. Correct me if my concept is wrong. And thanks for the questions.. all of them are relevant to current interviews.😊
Yesterday in my interview, interviewer asked me, is it possible to restrict the LWC component, like if that component show account object data then this component is only exposed on the account object record detail page only??
@@TechJourneyWithAnkit another question they ask me, when we refresh fully sandbox from prod, then we want to like one object have some confidential data and we need to hide that data from developer or other user. so no one able to see that data, how can we achieve?
A User: CRUD Permissions B User: No Permissions Trigger on Child, performing by B user which is fetching (SOQL Query) Parent record. Will be able to fetch records? Please answer.
answer of second QUE: correct me if i'm wrong. we can use dataLoader, in dataLoader we have an option named "Hard Delete" using that option we can delete all the customer records. and those records totally removed from the database. and those records cannot be recovered by any user/admin.
Very very useful scenerio questions
Glad you think so!
Really nice thank you for sharing all the scenarios based question
Glad it was helpful!
1) in first question if there is no profile level access for the object, then user have got the extended permission using the permission set that the reason he is able to create the record for that object
2) after deleting records go to the setup and search for hard delete, if u delete from there u can't recover the deleted records from the system.
Correct
Thank you for this please bring more videos Like this scenario based questions are tricky to solve
Glad you found this helpful
really helpful this video tqq...Ankit
You're welcome 😊
Nice session.
I think we can also use Custom Permissions to bypass validation rules in Salesforce!
Yes Good Option.
Thanks Ankit , this series is helpful
Glad to hear that
Super..... waiting for it...❤
Nice session
Thank you
1) in first question, user might be getting additional permission through a permission set
2) in secod question, to delete bulk records permanantely, we can use Hard Delete, to enable this go to user's profile and enable "Bulk Api Hard Delete" and use tools like Data Loader to hard delete data(in data loader setting, check Enable Bulk API and Enable Hard Delete.)
Correct and very detailed
@@TechJourneyWithAnkit thank you sir
very helpful serias😍
Glad to know that
Yess, Nice questions
But now a days no one asking tricky questins.
Interviewer directlly asking to write trigger or LWC code.
I will include some of them in my question bank 😅
Thanks!
Agree. But you have to get prepared with all aspects
That question on Full permission on parent object but not on related object record can also be extended by saying --> if trigger creates it , will user be able to see it or not ? So we can add to it like Trigger runs in system mode ---> so record will be created but user cannot see it.
Yep good point
1. Permission set
2. Hard delete
Correct
Default batch size is 200.
Object A could be the detail object since the sharing settings and object permissions will be inherited from the parent. correct me if i am wrong
Hard delete in data loader
Second answer is for which one. Rest all are good
I have come across one question in an interview " Users with a Sales Profile only should have access to the opportunity object " .
I don't think this is possible. Default Implicit sharing will not allow it
Ques 1 ans: provided access through permission set or having modify all access.
Ques 2 ans: hard delete checkbox ornoption in dataloader
Correct
Question 1
Answer
Via Permission Set, additional permission might given like 'Create' if not then 'Modify all data' permission check box might be tick for that profile.
Correct Gaurav
For the batch class rollback question, The error chunk of 200 records will be rolled back only if we are using Insert statement, in case we use database.insert statement the correct records will be inserted and the error one will be ignored. In that case the answer will be 399 records are inserted. Correct me if my concept is wrong.
And thanks for the questions.. all of them are relevant to current interviews.😊
Yes you are correct. However in question i explicitly put DML statement,😀
Yesterday in my interview, interviewer asked me, is it possible to restrict the LWC component, like if that component show account object data then this component is only exposed on the account object record detail page only??
Will cover this in next video
@@TechJourneyWithAnkit another question they ask me, when we refresh fully sandbox from prod, then we want to like one object have some confidential data and we need to hide that data from developer or other user. so no one able to see that data, how can we achieve?
For last que of 30000 record
Hard delete option from dataloader
M i right??
Yes correct
Also make Bulk API Enable then we can able to Hard delete
A User: CRUD Permissions
B User: No Permissions
Trigger on Child, performing by B user which is fetching (SOQL Query) Parent record.
Will be able to fetch records?
Please answer.
Yes if query is running in system mode, else no
answer of second QUE: correct me if i'm wrong.
we can use dataLoader, in dataLoader we have an option named "Hard Delete" using that option we can delete all the customer records. and those records totally removed from the database. and those records cannot be recovered by any user/admin.
Yes correct
Answer to 1 question:
User may be assigned with permission set which providing access to create record.
Yes one option what else can be possibility?