What components are required to be included in the change set when deploying profile and permission settings?

What components are required to be included in the change set when deploying profile and permission settings?

• A. Apex Class, Visualforce page, Assigned Apps, Custom Object, Custom Field
• B. Apex Class, Visualforce page, Assigned Apps
• C. Visualforce Page, Custom Field
• D. Custom Object, Custom Field, Apex Class

Answer: (A)

When deploying profile and permission settings, you must include every component that the profile might reference or control. Profiles specify access to Apex classes and Visualforce pages, so any classes or pages listed in the profile must be present in the target org for the profile to apply correctly. They also define which apps the user can access, so the Assigned Apps metadata needs to travel with the change set to preserve navigation and visibility. Finally, profiles set object and field permissions, which relies on the existence of the custom objects and fields themselves; without deploying those objects and fields, the profile would reference non-existent metadata and fail to deploy or operate as intended. Including Apex Class, Visualforce Page, Assigned Apps, Custom Object, and Custom Field covers these dependency areas—code access, UI access, app visibility, and data-model permissions—making the deployment of profile and permission settings reliable.

When deploying profile and permission settings, you must include every component that the profile might reference or control. Profiles specify access to Apex classes and Visualforce pages, so any classes or pages listed in the profile must be present in the target org for the profile to apply correctly. They also define which apps the user can access, so the Assigned Apps metadata needs to travel with the change set to preserve navigation and visibility. Finally, profiles set object and field permissions, which relies on the existence of the custom objects and fields themselves; without deploying those objects and fields, the profile would reference non-existent metadata and fail to deploy or operate as intended.

Including Apex Class, Visualforce Page, Assigned Apps, Custom Object, and Custom Field covers these dependency areas—code access, UI access, app visibility, and data-model permissions—making the deployment of profile and permission settings reliable.