SALESFORCE ADMIN correct exams QUESTIONS
AND ANSWERS SET A+
✔✔Page layout - ✔✔Controls the position and organization of the fields and related lists
that are visible to users when viewing a record.
Control visibility and edit ability of the fields on a record. In page layouts, can set fields
as read-only or hidden, can control which fields require users to enter a value and which
don't.
Should never be used to restrict access to sensitive data that a user shouldn't view or
edit as users can still access that field through other parts of the app, such as reports or
through API.
✔✔Compact layout - ✔✔Used to display a record's key fields at a glance. Using this,
you can indicate which fields should appear in a record's highlights area.
✔✔Relationship Custom Fields - ✔✔Lookup Relationship: Creates a simple relationship
between two objects (many to one). The object with the lookup relationship field is the
many record and the reference object is the one record. Many lookup relationship fields
can be on a single object.
Master-detail relationship: creates special parent-child relationship between objects: the
object on which the master-detail relationship field is created is the child or "detail", and
the object referenced in the field is the parent or "master". Ownership and sharing are
determined by the master record. This is a required field on the detailed record.
✔✔Search Layouts - ✔✔Ordered groups of fields that are displayed when a record is
presented in a particular context, such as in search results, a lookup dialog, or a related
list.
You can choose up to 10 fields to include in the lookup dialog, and order them in any
way you choose.
, ✔✔Review the different type of searches available in Salesforce - ✔✔
✔✔Review Salesforce mobile and offline capability - ✔✔
✔✔Hyperlink function - ✔✔lets you create a hyperlink to any URL or record in
Salesforce.
✔✔Junction object - ✔✔Is a custom object with two master-detail relationships, and is
the key to making a many-to-many relationship.
The first master-detail relationship will be the primary relationship. The detail and edit
pages of the junction object will use the color and any associated icon of the primary
master object. The junction object will inherit the value of the Owner field and share
settings from their associated primary master record.
✔✔Object-level security - ✔✔Object-level access allows us to hide whole tabs and
objects from particular users, so they don't even know that type of data exists.
Object-level access is set with object permissions in user profiles and permission sets.
✔✔Field-level security - ✔✔Prevents a user from seeing, editing, or deleting the value
for a particular field on an object. Allow us to hide sensitive information like salary or
SSN w/o having to hide the whole object. Controls the visibility of fields in any part of
the app, including related lists, list views, reports, and search results. To be absolutely
sure that a user can't access a particular field, it's important to use the field-level
security page for a given object to restrict access to the field.
Field level access is set with field permissions in profiles and permission sets.
✔✔Record Level Security - ✔✔Allows particular users to view an object but then restrict
the individual object records that they're allowed to see.
This can be done through:
.Org wide defaults (OWD) - allows you to specify the baseline level of access that a
user has in your organization
.role hierarchies - allows us to make sure that a manager will always have access to teh
same records as his or her subordinates
.Sharing rules - allows us to make automatic exceptions to organization-wide defaults
for particular groups of users.
✔✔What are the standard profiles? - ✔✔Read Only
Standard User
Marketing User
Contract Manager
Solution Manager
AND ANSWERS SET A+
✔✔Page layout - ✔✔Controls the position and organization of the fields and related lists
that are visible to users when viewing a record.
Control visibility and edit ability of the fields on a record. In page layouts, can set fields
as read-only or hidden, can control which fields require users to enter a value and which
don't.
Should never be used to restrict access to sensitive data that a user shouldn't view or
edit as users can still access that field through other parts of the app, such as reports or
through API.
✔✔Compact layout - ✔✔Used to display a record's key fields at a glance. Using this,
you can indicate which fields should appear in a record's highlights area.
✔✔Relationship Custom Fields - ✔✔Lookup Relationship: Creates a simple relationship
between two objects (many to one). The object with the lookup relationship field is the
many record and the reference object is the one record. Many lookup relationship fields
can be on a single object.
Master-detail relationship: creates special parent-child relationship between objects: the
object on which the master-detail relationship field is created is the child or "detail", and
the object referenced in the field is the parent or "master". Ownership and sharing are
determined by the master record. This is a required field on the detailed record.
✔✔Search Layouts - ✔✔Ordered groups of fields that are displayed when a record is
presented in a particular context, such as in search results, a lookup dialog, or a related
list.
You can choose up to 10 fields to include in the lookup dialog, and order them in any
way you choose.
, ✔✔Review the different type of searches available in Salesforce - ✔✔
✔✔Review Salesforce mobile and offline capability - ✔✔
✔✔Hyperlink function - ✔✔lets you create a hyperlink to any URL or record in
Salesforce.
✔✔Junction object - ✔✔Is a custom object with two master-detail relationships, and is
the key to making a many-to-many relationship.
The first master-detail relationship will be the primary relationship. The detail and edit
pages of the junction object will use the color and any associated icon of the primary
master object. The junction object will inherit the value of the Owner field and share
settings from their associated primary master record.
✔✔Object-level security - ✔✔Object-level access allows us to hide whole tabs and
objects from particular users, so they don't even know that type of data exists.
Object-level access is set with object permissions in user profiles and permission sets.
✔✔Field-level security - ✔✔Prevents a user from seeing, editing, or deleting the value
for a particular field on an object. Allow us to hide sensitive information like salary or
SSN w/o having to hide the whole object. Controls the visibility of fields in any part of
the app, including related lists, list views, reports, and search results. To be absolutely
sure that a user can't access a particular field, it's important to use the field-level
security page for a given object to restrict access to the field.
Field level access is set with field permissions in profiles and permission sets.
✔✔Record Level Security - ✔✔Allows particular users to view an object but then restrict
the individual object records that they're allowed to see.
This can be done through:
.Org wide defaults (OWD) - allows you to specify the baseline level of access that a
user has in your organization
.role hierarchies - allows us to make sure that a manager will always have access to teh
same records as his or her subordinates
.Sharing rules - allows us to make automatic exceptions to organization-wide defaults
for particular groups of users.
✔✔What are the standard profiles? - ✔✔Read Only
Standard User
Marketing User
Contract Manager
Solution Manager
