Salesforce Developer Certifications Questions and Answers (Dumps and Practice Questions)

Question : Sharing rules can be more restrictive than the Organization Wide Default.

1. True
2. False

Correct Answer : 2

Explanation: Sharing rules are the special sets of privileges set by the administrator to automatically grant record access to certain users or the group of users. There is a limit of 100 owner-based sharing rules. Sharing rules can allow the records for the user, which are restricted by the roles. However, if the object is not visible to the user profile, the records cannot be made visible by sharing rules. Sharing rules are one-off sharing options for complex sharing logic that cannot fit in the normal sharing structure.

Manual sharing : Finally, the last option in sharing is the manual sharing option given to the individual users with full access to a record. It is used if the organization wide defaults access for the object is set to Private. This is generally done by a record owner, for a single record. Only the record owner and users above the owner in the role hierarchy are granted full access to the record. It is not possible to grant other users full access. Users with the Modify All object-level permission for the given object or the Modify All Data permission can also manually share a record. User-managed sharing is removed when the record owner changes or when the access granted in the sharing does not grant additional access beyond the object's organization-wide sharing default access level.

Organization-Wide defaults : While roles and profiles are used to determine the user-based security, the organization wide default determines the distribution of data with the user. We use the defaults in the object to determine which people across the role hierarchy can access which objects. Objects allowed to be viewed by the organization wide defaults can be restricted using profiles and roles.

The following options determine the sharing settings of the object: Private The role hierarchy is observed and people cannot view their peer records. In the figure above, Rep1 cannot see the data for Rep2 in the object that has private settings Public Read Only This is useful if we have master data that the people refer
to for example, the books info in the library. They can be kept public read only. In this case everyone across the hierarchy can see the data Publix Read/ Write This option does not obey any role hierarchy and anyone can edit/ modify or even delete the objects depending on their profile permissions.

Organization-wide default summarized : To set up organization-wide defaults follow the simple method: o First find out which user requires least access to an object. Set the organization-wide default to all the objects based on this user. For example, the library clerk is the person in a library who mostly handles the issuing and the return of the books. He needs the least access on the customer object (assuming that only the librarian can handle membership) set the customer
object to private read only. o Most restrictive record access is defined using a organization-wide default. Access to additional records is made available through the role hierarchy,sharing rules, and manual sharing. o Changing organization-wide default settings can delete manual sharing if that sharing is no longer needed.
Permission sets A new addition to the profile-based permission is the permission sets. A user can have only one profile at a time with a static set of permission. With the new permission sets, we can create a separate set of permissions for the uses. For example, to give access to an object, instead of modifying the profile we can create a permission set and assign it to user.

Question : Which of the following are the record access levels?

1. Read only
2. Read/write
3. Full access
4. 1 and 3
5. All 1,2 and 3

Correct Answer : 5

Explanation: Read only, Read/write, Full access (this includes delete, change owner permissions)
Record Access Levels : Sharing for accounts and contacts is available in: Professional, Enterprise, Performance, Unlimited, and Developer Editions
Sharing for campaigns, cases, custom object records, leads, and opportunities is available in Enterprise, Performance, Unlimited, and Developer Editions
Sharing for custom objects is available in Database.com When you share records with other users, you can assign them different levels of access to the records.
The available access levels areAccess Level Description
Full Access User can view, edit, delete, and transfer the record. User can also extend sharing access to other users; however, the user cannot grant Full Access to other users.
Read/Write User can view and edit the record, and add associated records, notes, and attachments to it.
Read Only User can view the record, and add associated records to it. They cannot edit the record or add notes or attachments.
Private User cannot access the record in any way.
Note : If you encounter an error when selecting the Full Access option, you no longer have the permission to set full access on records. Contact your administrator to determine if this access is necessary.

Question : Which of the following values are for Organization wide defaults?

1. Public read only
2. Public read/write
3. Private
4. Only 2 and 3
5. All 1,2 and 3

Correct Answer : 5

Explanation: Organization-Wide defaults
While roles and profiles are used to determine the user-based security, the organization
wide default determines the distribution of data with the user. We use the defaults in
the object to determine which people across the role hierarchy can access which objects.
Objects allowed to be viewed by the organization wide defaults
can be restricted using profiles and roles.

The following options determine the sharing settings of the object:
Private The role hierarchy is observed and people cannot view
their peer records. In the figure above, Rep1 cannot see the
data for Rep2 in the object that has private settings
Public Read Only This is useful if we have master data that the people refer
to for example, the books info in the library. They can be
kept public read only. In this case everyone across the
hierarchy can see the data
Publix Read/ Write This option does not obey any role hierarchy and anyone
can edit/ modify or even delete the objects depending on
their profile permissions.

Salesforce Developer Certifications Questions and Answers (Dumps and Practice Questions)

Related Questions