Question

John has updated field level security of the account object for the marketing user profile and wants to deploy only the FLS to higher environments. What does he need to commit in order to do so? (Select 2)

A. Record Types
B. Object Permissions
C. Field Accessibility
D. Profiles

Answer 1

John needs to commit the Profiles and Field Accessibility settings to deploy the updated Field Level Security for the Marketing user profile. Profiles contain FLS settings, and Field Accessibility settings are part of the Profile metadata which needs to be included in the deployment.

Step-by-step explanation:

When John wants to deploy only the Field Level Security (FLS) for the Account object to higher environments for the Marketing user profile, he needs to commit specific metadata components related to FLS. In the Salesforce deployment process, FLS is associated with the Profile or Permission Sets. Hence, to deploy FLS, he would need to commit the Profiles where those field permissions have been altered. Additionally, the Field Accessibility settings, which are part of the Profile metadata, must be included in the deployment package.

It's important to note that committing only the Profile might not be enough if the field permissions are managed via Permission Sets. In this case, John would have to also commit those Permission Sets. However, since the question specifically mentions only selecting two options, we focus on committing Profiles and Field Accessibility which has the FLS settings for the targeted fields within the Profile metadata.

Answer 2

To deploy updated field level security to higher environments, John needs to commit changes to Field Accessibility and Profiles, which control access and include field permissions. The correct option is c.

Step-by-step explanation:

When John has updated field level security (FLS) of the account object for the marketing user profile and wants to deploy only the FLS to higher environments, he needs to commit specific components to achieve this. The correct answers are C. Field Accessibility and D. Profiles.

Field Accessibility is a specific setting within the Field Level Security that controls which profiles have access to view and edit a field. By committing changes to Field Accessibility, John can ensure that only the desired profiles have the appropriate level of access to each field.

Moreover, changes to Profiles would be necessary because field permissions are also stored in the profile metadata. When deploying Field Level Security changes, the associated profile that contains these permission settings must be included.

In order to deploy only the Field Level Security (FLS) to higher environments, John needs to commit both Object Permissions and Field Accessibility settings.

Object Permissions are used to grant or restrict access to the entire object, while Field Accessibility settings control the visibility and editability of specific fields within the object.

By updating the FLS of the account object for the marketing user profile, John can ensure that only the necessary fields are accessible and editable by the marketing users in higher environments.