If a field is marked as 'Visible' in 'Field-level security' and 'Read-Only' on the page layout, then how would the field be available to the end user as Visible (i.e. editable) or Read-Only?
User A belongs to profile `Custom Recruiter'. At the profile level (Path as per Enhanced Profile User Interface, Setup -> Manage Users -> Profiles -> Custom Recruiter -> Objects and Tabs -> Accounts) he does not have Read access on Account object. But yet he is able to see, edit, delete account records. What could be the reason?
'Sharing' button has been added to the page layout of the 'Account' object. OWD of account is public read/write. On any Account record, the Sharing button is still visible for sharing that record using an Apex Sharing Reason. What could be the reason?
Which of the following are true about custom objects? (Select all that apply):
A. Salesforce provides a set of custom objects that you can use to store data.
B. After you create a custom object, you need to add the user interface.
C. Custom objects come with an infrastructure including reporting, auditing and access control.
D. When you create a custom object, you get a direct access to the database.
E. Custom objects are reportable and search
Interviewers should never be able to view a candidate's social security number. Which tool would you use to meet this requirement?
A. Record types
B. Field-level security
C. Page Layouts
D. Page Layouts with Record Types
What license is needed to install or uninstall apps from AppExchange?
A. Install package license
B. Uninstall package license
C. Manage package license.