Given the following code snippet, that is part of a custom controller for a Visualforce page:

In which two ways can the try/catch be enclosed to enforce object and field-level permissions and prevent the DML statement from being executed if the current logged-in user does not have the appropriate level of access? Choose 2 answers

Question

Given the following code snippet, that is part of a custom controller for a Visualforce page:

In which two ways can the try/catch be enclosed to enforce object and field-level permissions and prevent the DML statement from being executed if the current logged-in user does not have the appropriate level of access? Choose 2 answers

Accepted Answer

A. Use if (Schema, sobjectType, Contact, isUpdatable ( ) ) `Schema.sObjectType.Contact.isUpdateable()` checks if the current user has object-level permissions to update records of the Contact object, preventing unauthorized DML. B. Use if (Schema , sobjectType. Contact. Field, Is_Active_c. is Updateable ( ) ) `Schema.sObjectType.Contact.fields.Is_Active_c.isUpdateable()` checks if the current user has field-level permissions to update the specific 'Is_Active_c' field on the Contact object.

Answer

C. Use if (Schema.sObjectType.Contact.isAccessible ( ) ) `Schema.sObjectType.Contact.isAccessible()` checks for read access, which is not sufficient for enforcing update permissions required for DML operations.

Answer

D. Use if (thisContact.Owner = = UserInfo.getuserId ( ) ) `thisContact.Owner == UserInfo.getUserId()` checks record ownership, which is a business logic condition, but it does not enforce object or field-level security permissions.

Given the following code snippet, that is part of a custom controller for a Visualforce page: In which two ways can the try/catch be enclosed to enforce object and field-level permissions and…

Question

Exhibit

Options

How the community answered

Why each option

Topics

Community Discussion