Security

Question 1

Which statement is true regarding field-level secruity?(Choose Two)

1. It is enforced through the UI and the API
2. It can be used to prevent users from seeing specific records
3. It can be used to make a field required
4. It determines which fields are hidden, read-only, and read/write for a particular profile

Answer 1

Answer: 1 and 4

Question 2

Which statement best describes the purpose of the profile?

1. It controls access to records within your organization
2. It is a way for the Sys Admin to determine who can see specific opportunites in your org
3. It determines what users can do with the records hat they can access
4. It is a way for the sys Admin to determine who can use the workflow feature

Answer 2

Answer: 3

Question 3

These contain user permissions and access settings that control what users can do

Answer 3

Profiles

Profiles give users permission to each object and determine what a user can do to records within the object

Question 4

Set the baseline of what users can see

Answer 4

Org-wide defaults

Question 5

This/These control how much data users can see

Answer 5

Role hierarchies

Question 6

These allow users to see/edit data they don’t own in an otherwise private setup

Answer 6

Sharing rules

Question 7

Who can manually share a record?

Answer 7

1. Owner
2. Anyone above the owner in the hierarchy
3. Admins

Question 8

At what levels can you restrict logging in by IP address ranges?

Answer 8

1. Org wide level
2. Profile level

• Org wide level: Go to Setup > Security Controls > Network access*
• Users logging in to salesforce.com with a browser from trusted networks are allowed to access salesforce.com without having to activate their computers.*

Question 9

Is a user always able to edit records they own?

Answer 9

DEPENDS: If their profile is not given READ access to that object then NO.

Question 10

What is the maximum number of roles that can be created?

Answer 10

500

Question 11

What is the difference between settings and permissions on a profile? List some of them.

Answer 11

• Settings determine what users can see in the user interface, for example, apps, tabs, record types, page layouts, and fields.
• Permissions determine what users can do with the data they have access to, for example, customize app, run reports, mass email, create leads, edit opportunities.

Question 12

What do object permissions control?

Answer 12

The kind of records (object) users can view, create, edit, or delete

Question 13

What information is contained in a user record?

Answer 13

• Personal information, such as name and contact details
• Security and access information, such as usemame, profile, role, and login history
• Locale information, such as time zone, locale, language, and currency

Question 14

Does enabling Chatter Invitations require additional CRM licenses?

Answer 14

No, it uses no CRM licenses. However, each invitee that accepts the invitation to join

Chatter is assigned one of the 5,000 Chatter Free licenses that come with each erg.

Question 15

One of your users receives an error message when they try to log in. Where could you look to
troubleshoot the issue?

Answer 15

The Login History related list on the user record

Question 16

Which standard profile has these permissions?

Standard User Permissions+ can
import leads for the organization

Answer 16

Marketing User

Question 17

Which standard profile has these permissions?

Can view, edit and delete their own
records

Answer 17

Standard User

Question 18

How can you restrict login access to an organization?

Answer 18

You can restrict access to an organization by specifying login hours or login IP ranges
on user profiles.

Question 19

What do organization-wide defaults control?

Answer 19

The default level of access users have to records they do not own, in each object

Question 20

What does the role hierarchy control?

Answer 20

The role hierarchy lets you open up record access to users who may have been denied access by the organization-wide defaults. Users in higher roles inherit the special ownership privileges on all records owned by users in roles below them.

Additionally, the role hierarchy appears at the top of opportunity reports, allowing users to drill down to data at different levels of the hierarchy.

Question 21

How does a profile differ from a role?

Answer 21

A profile determines what users can do with records they have access to, for example,
view or edit. A role determines what individual records users have access to.

Question 22

Why are sharing rules used?

Answer 22

To grant additional record access to groups of users on an object-by-object basis,
allowing you to create exceptions to the organization-wide defaults

Question 23

When would you choose to build a public group?

Answer 23

To simplify the creation of sharing rules when more than one sharing rule is required

Question 24

Where can you configure field-level security?

Answer 24

You can configure field-level security when you create a new custom field, when you edit
an existing field in Setup, or by editing a profile.