How should the Architect ensure that OBJECT-LEVEL SECURITY is enforce within a custom Visualforce application that was a standard Apex controller on the Lead object?

• A.Use the Schema.DescribeSObjectResultisAccessible() method in the Apex controller.
• B.Use the {!$ObjectType.lead.accessible} expression within the Visualforce page.
• C.Use the "With Sharing" keyword when defining the Visualforce page.
• D.Use the runAs() method to enforce user permissions in the Apex controller.

Comment: *

Name: *

Email: *

Verification: *

Universal Containers is designing a new community using the Customer Community license type. They would like to have the users complete survey questions through the community interface and store the responses in a Custom Object that has a lookup to the account object. Any internal user who has access to the account should be able to see all survey responses. All Customer Community users should be able to see surveys filled in by other users for their company, but not surveys for other companies. What are the correct security settings to achieve this?

• A.Set all Organization-Wide Default security to be "Public Read/Write" for internal users and "Private" for external users.
• B.Set all Organization-Wide Default security to be "Private" for both internal and external users and use Sharing Rules to grant the desired access
• C.Set the custom object to be master-detail to the Account and leave the Organization-Wide Default settings as their default values.
• D.Set all Organization-Wide Default settings to be "Public Read/Write" for both internal and external users.

Comment: *

Name: *

Email: *

Verification: *

UniversalContainers(UC)servicerepsareassignedtoaprofilewhichhas"ViewAll"inCase object(Private OWD).To make sure service repshaveaccess toallrelevant information to attendtocustomerrequests, whichtwodetailsshouldasalesforceArchitectsconsider? Choose 2answers:

• A.Service reps willnotbeable toaccessallthe UCAccountsrecordsbecause Account OWD is private.
• B.Service repswill be able to access all UC contactrecords if theyare controlled by parent.
• C.Servicerepswillbeable toaccessall the UC Accountrecordsdue to Implicit Sharing.
• D.Service reps will notbe able to access all UC contactrecords if theyare controlled by parent.

Comment: *

Name: *

Email: *

Verification: *

Universal Containers wants to store Payment Term Details on the Account object, but the fields should only be visible on certain record types and for certain user profiles.
How can a System Administrator quickly determine which user profiles, page layouts, and record types include certain fields?

• A.Use the Field Accessibility Viewer for the fields in question
• B.Universally require the field at the field level.
• C.Log in as each user profile and view the Account Page Layouts.
• D.Click the Field-Level Security for the field on each Profile.

Comment: *

Name: *

Email: *

Verification: *

Universal Containers (UC) is in legal dispute regarding several orders. UC has found out these records were removed from system. The VP of Sales has asked to ensure this cannot happen in the future. What approach would meet this requirement?

• A.Remove the delete button from the Order page layout.
• B.Implement a sharing rule that changes access for the records to read.
• C.Change the record type/page layout assignment for orders to be read-only.
• D.Remove order delete permission from profiles and permission sets.

Comment: *

Name: *

Email: *

Verification: *