An administrator has created a new custom object in a sandbox environment and now is ready to deploy in production. How can the administrator ensure that the field-level security that was tested and approved in the sandbox environment is maintained as part of the deployment? a) Create a change set that includes the custom object and all custom fields b) Create a change set that includes the custom object and all profiles c) Create a change set that includes the custom object, check the retain field-level security option d) Create a change set for the custom object; use Data Loader to transfer field-level security

Option D

Explanation:

Option A is rejected because adding a custom object will cost both in memory and computation power. Consider that you have 1 million users, than there will be 1 million custom objects in the memory for checking the security which is not good.

Option B is not answer because again making a custom object will cost in memory and computation power.

Option C is not good because it also makes the custom object.

Option D is selected because change sets can be made which will not cost as much as the other options are costing. Also Data Loader can have come credentials defined in it which we can use to check if the user activities are according to the rules at each level. These days these data loader object technique is used because there will be static change sets for the class of users to check security.