Admin Bootcamp 3

Question 1

Standard Objects

Answer 1

Accounts, Contacts, Opportunities, Cases, Campaigns, Leads (campaign and leads are Marketing)

Question 2

Company Profile

Answer 2

Collection of information about your org, mostly captured during signup: Company information (name, address, primary contact, default locale, default currency, storage used, license avail). Financial information (fiscal year, currencies), Support Information (business hours, holidays)

Question 3

Local Settings

Answer 3

allow you to personalize display of data for different uses based on their geographical location.

Question 4

Fiscal Year

Answer 4

default standard fiscal year follows the gregorian calendar

Question 5

Currency

Answer 5

SF orgs are single currency by default. you set the required currency locale in the company profile. all currency values on records will display in appropriate currency. However, you can activate additional currencies. if you do this, new users will inherit the corp currency but can set their own. new records will inherit a user’s personal currency.

Question 6

Advanced Currency Management

Answer 6

allows you to “lock” the converted amount on closed opportunities based on the closeed date.

Question 7

Profile

Answer 7

collection of settings and permissions that determines what users can see in the UI and what they can do. Settings are what they see (apps, tabs, record types, page layouts, fields) and permissions (app permissions, system permissions, standard object, custom object)

Question 8

Standard Profiles

Answer 8

can’t be deleted and permissions can’t be edited.
sys admin - view and modify all data, customize app.
standard user - view, edit, and delete records they can access
solution manager - standard user + manage published solutions
marketing user - standard user + import leads
contract manager - standard user + manage contracts
read only - only view records they can access

Question 9

Tab Settings

Answer 9

Users can access tabs set to Default Off through the App Launcher in All Items

Question 10

User

Answer 10

someone with login access to your SF org who has a license and a user record containing personal, security, and locale information.

Question 11

Login Issues

Answer 11

Login History related list on a user record displays when, where, and how a user attempts to login. Status column diagnoses any login issues

Question 12

Restricting Login Hours and IP Ranges

Answer 12

Setup/Admin/Users/Profiles

Question 13

Object Permissions

Answer 13

Object Permissions only determine the KINDS of records users can view, create, edit, or delete, not the individual records themselves

Question 14

Permission Sets

Answer 14

Permission sets can be assigned to users from the permission set itself or through the Permission Set Assignments related list on a user’s record. The user’s total access will be determined by the user’s profile, plus any permission sets assigned to the user’s record

Question 15

Record Access

Answer 15

Determines which individual records users can view and edit in each object they have access to on their profile

Question 16

Org Wide Defaults (OWD)

Answer 16

Use OWD to set the default level of access users have to records they do not own, in each object.

Access levels determine what a user can do with records they do not own

Question 17

Role Hierarchy

Answer 17

in a private or hybrid model, role hierarchy lets you open up record access to managers, team leaders, and operations people, who may have been denied access via the OWD

Question 18

Sharing Rules

Answer 18

Create sharing rules to grant additional record access to groups of users on an object by object basis. Sharing rules are:

1. exceptions to OWD
2. irrelevant for public data access models
3. comprising 3 components (Share which records, with which users, what level of access)

Question 19

Account Teams and Opportunity Teams

Answer 19

enable account/opportunity teams to allow users to grant additional access to their accounts and related records/opportunities.

Question 20

Standard Fields

Answer 20

All objects have a predefined set of fields to capture common business information. You can’t delete them, but you can use field-level security to hide them, or remoo

Question 21

Controlling/Dependent Picklists

Answer 21

Users select a value in a controlling picklist, which filters the values available in a second, dependent picklist

Question 22

Picklists

Answer 22

Fields that allow users to select either single or multiple values from a predefined list during data entry.

Question 23

Lookups

Answer 23

Lookups are fields that allow users to select a record from another object, including the User object, during data entry. In this way, they can link two records together to create a parent-child relationship.

Question 24

Formula fields

Answer 24

Custom formula fields allow you to define calculations that reference other fields to display new numeric, text, date, or checkbox values specifc to your business requirements.
Formula fields:
1. read-only, don’t display on record edit pages
2. can reference fields on the same object, or a parent or lookup object.
3. can’t reference encrypted, description, or customer long text area fields
4. are not searchable, or available for lead conversion or the weekly export service.

Question 25

Record Types

Answer 25

allow you to offer users different page layouts and picklist values for different business scenarios, based on their profiles. Each object has a default master record type, but you can create new ones

Question 26

What record type is used for records created through web-to-case or web-to-lead?

Answer 26

Cases use the default record type of the default case owner. Leads use the default record type of the default lead owner.

Question 27

What happens when an admin adds new values to a picklist for an object with multiple record types

Answer 27

the admin is prompted to select which record types should include the new value

Question 28

how can a user identify the record type of a record

Answer 28

admins can add the record type to field pay layouts

Question 29

do users always have to select a record type when creating new records?

Answer 29

no. users can choose to always use an object’s default record type as set on their profile

Question 30

Validation rules

Answer 30

allows you to specify your own business-specific criteria to prevent users saving invalid data in one or more fields.