Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
58 Cards in this Set
- Front
- Back
|
What levels of access can be granted using sharing rules ? Choose all that apply 1. Read–Only 2. Read/Write 3. Full Access 4. Create, Read, Edit, Delete |
1. Read–Only 2. Read/Write Granting ‘Full Access’ is not possible using sharing rules - this is determined by the Ownership of the record. |
|
|
Field level security and record types can be set at the Profile level. True or False? |
True |
|
|
Organisation wide default (OWD) & sharing rules are applied at the:
A. Profile level B. Object level C. Record level |
B. Object level. But manual sharing is applied at the Record level |
|
|
Checking 'Grant Access Using Hierarchies' gives what type of access to records owned by subordinates? A. Read B. Read, Edit C. Read, Edit, Delete D. Depends on what access the profile of the senior has for that object out of Read, Edit, Delete. |
D. Depends on what access the profile of the senior has for that object out of Read, Edit, Delete. |
|
|
Allison only has the "read" permission for the case object on her profile. A criteria-based sharing rule gives her Read/Write access to product support cases. Will Allison be able to edit product support cases? |
No. Allison will not be able to edit product support cases because object permissions give her only read permissions. When working with object access, the most restrictive wins. |
|
|
Allison's account page layout makes the Rating field required, but her FLS setting make the field Read-Only. Will Allison be able to edit the Rating field? |
No. Allison will not be able to edit the Rating field, because FLS make the field Read-Only. When working with field access, the most restrictive wins. |
|
|
What is order of evaluation for record viewing ? |
Profile: Read or View All or Modify All Record Ownership Organization Wide Default Role Hierarchy Sharing rules |
|
|
If OWD of Opportunity is set to private, then which opportunities can a user view ? |
1. Opportunities owned by the user. 2. Opportunities shared with the user using Opportunity Sharing Rule. 3. Opportunities owned by users below this user in the organization role hierarchy as 'Grant Access Using Hierarchies' is always checked for standard objects. It cannot be unchecked. 4. Opportunities on which this user has been added as an Opportunity Team member. (Due to this a manual sharing rule automatically gets created on that opportunity record with sharing reason as ‘Sales Team’.) 5. Opportunities present in related lists on parent record pages like Account page, where a User is an owner. 6. Opportunities present in related lists of other records shared with this user which have related opportunities in Opportunity Related List like accounts shared with this user. Here the access to the opportunities in the related list is determined by how the sharing rule has been defined. |
|
|
What values are available for Field–level security? |
Visible, Read–Only |
|
|
What properties can be given to a field on the page layout ? Select all that apply.
1. Required 2. Read-Only 3. Read/Write 4. Full Access |
Required, Read–Only
|
|
|
If a field is marked as 'Visible' in Field–Level Security and 'Read–Only' on the page layout. Would the field be available to the end user as Visible (i.e. editable) or Read–Only ? |
Read–Only |
|
|
Both a sharing rule and an Account Team give Eric access to the ABC Account. The sharing rule gives him Read access, and the account team gives him Read/Write access. Will Eric be able to edit the ABC Account? |
Yes. Eric will be able to edit ABC Account, because the account team gives him Read/Write access. When working with record access, the most permissive wins. |
|
|
If a field is marked as 'Read–Only' in Field–Level Security' and 'Required' on the page layout, then would the field be available to the end user as Visible (i.e. editable) or Read–Only ? |
When creating a record - the field will be blank, but allowing user to save the record. When editing a record - the field would be Read–Only |
|
|
Sharing rules can be more restrictive than the Organization Wide Default. True/False |
False |
|
|
Which are the 3 record access levels ? |
Read only, Read/write, Full access (this includes delete, change owner permissions) |
|
|
Which are the 3 values for Organization wide defaults ? |
Public read only, Public read/write, Private |
|
|
OWD of Account is private then OWD of Opportunity can be private or public read–only or public read/write. True/False |
False. If OWD of Account is private, then OWD of Opportunity is compulsorily private. |
|
|
Once a sharing rule has been created to share Account records with Public Group A with read/write access to the shared accounts, then this sharing rule can be modified to share the Account records with Public Group B with read–only access. True/False |
False. 'Shared With' cannot be changed once a sharing rule has been created. Only 'Access Level' can be changed after a sharing rule has been created. |
|
|
Becky belongs to profile ‘Custom – Recruiter’. At the profile level he does not have Read access on Account object. But yet he is able to view account records. He is not able to edit or delete account records. What could be the reason ? |
Becky has a Permission Set with Account Read access enabled |
|
|
Apex Sharing Reasons are available for standard and custom objects. True/False |
False. Apex Sharing Reasons are only available for custom objects. |
|
|
Since Apex Sharing Reasons are not available for standard objects, so sharing individual records of standard objects is not possible via Apex Sharing. True/False |
False. When an individual record of a standard object is shared, then the reason appears as 'Manual Sharing' automatically. |
|
|
The 'Sharing' button has been added to the page layout of 'Associate' custom object. On any 'Associate' record, the Sharing button is not visible for sharing that record. What could be the reason? |
OWD of Associate must be public read/write. So sharing is not required for any Associate record. So the Sharing button does not show up. |
|
|
'Sharing' button has been added to the page layout of the 'Account' object. OWD of account is public read/write. On an Account record, the Sharing button is still visible for sharing that record. What could be the reason? |
The OWD of the related opportunities, cases or contacts could be private or public read–only. So there is scope for sharing the account. |
|
|
If a record of 'Associate' custom object has been shared using an Apex Sharing Reason, then that Apex Sharing Reason cannot be deleted until the sharing of that record is changed to use some other Apex Sharing Reason. True/False |
False. The Apex Sharing Reason can be deleted. But deleting an Apex Sharing Reason will delete all sharing on the object that uses this reason. |
|
|
Until an Apex Sharing Reason is created, a record of a custom object cannot be shared manually on a one–off basis. True/False |
False. If a record of a custom object is shared manually on a one–off basis before creation of any Apex Sharing Reason for that custom object, then that record gets shared using the default manual sharing reason – 'Manual Sharing'. This default manual sharing reason continues to remain available as an option for manual one–off even after additional Apex Sharing Reasons are created for any custom object. |
|
|
OWD of child is always determined by OWD of parent. True/False |
False. This is true only for master–detail relationship, not for lookup relationship. |
|
|
'Modify All' if checked at the profile level, always overrides the OWD setting. True/False |
True |
|
|
'View All' has been checked at the profile level for a custom object 'Position'. OWD is private of the Position object. A user will be able to view Position records owned by other users. True/False |
True |
|
|
If a custom object is a child in a master–detail relationship, then what is OWD setting for this child object, if parent object's OWD is set to Public Read Only? |
OWD of a child object in a master-detail relationships is controlled by parent, so the access will be Public Read Only |
|
|
A manual sharing can be created using the Apex Data Loader. True/False |
True |
|
|
User A belongs to role 'Director Sales' and has Read, Edit, Create, Delete permission on Account at the profile level. User B belongs to role 'Sales'. OWD of Account is private and there is no sharing rule (manual or otherwise) on Account. On the Setup –> Security Controls –> Sharing Settings page, 'Grant Access Using Hierarchies' is unchecked for the Account object. User B has created an account record. User A who is senior to user B as per the role hierarchy will not be able to view this record. True/False |
This would have been True for any custom object, but in this situation, the answer is False, as 'Grant Access Using Hierarchies' cannot be unchecked for standard objects. |
|
|
For manual sharing of any account record, by default the owner of the record has Full Access to the account record and has Read/Write access on the related contacts, opportunities, cases. The Read/Write access on the related contacts, opportunities, cases can be made more restrictive for the owner like read–only by creating a new manual sharing rule for that account record and selecting the owner's name from within the Users list. True/False |
False. Sharing Rule opens up access and cannot restrict access. |
|
|
What is the name of the default public group to which all users are added ? |
All Internal Users |
|
|
How many permission sets can you have in an organization ? |
1,000 |
|
|
Why can't a User who has read/write access to an Account add Account Team Members with read/write access to Cases and/or Opportunities? Scenario: * User Zach has read/write access to Account “123” because of an Account sharing rule or a manual share on Account “123”* Zach is trying to add Account Team Members to Account “123” with read/write access to both Cases and Opportunities * When Zach adds Account Team Members he can give them read/write access to the Account but only has the option to give them read access on Cases and Opportunities in the UI |
This scenario can occur because the role of the Account Owner has the Case Access and Opportunity Access set to "Users in this role can view all cases/opportunities associated with accounts that they own, regardless of who owns the cases/opportunities ". In order for Zach to be able to add Account Team Members with read/write access to Cases and Opportunities, the role of the Account Owner would have to have the Case Access and Opportunity Access updated to "Users in this role can edit all cases/opportunities associated with accounts that they own, regardless of who owns the cases/opportunities." |
|
|
Can a User share an Opportunity with someone who can't see the associated Account? |
If a User is the Account owner, above the owner in the role hierarchy, or an administrator, he can share an Opportunity with someone who can't see the associated Account. The Account will be shared with Read access and w/o access to all the Opportunities on this Account. |
|
|
You can secure data at the organization level, using all of these methods, except: A. Limit Login IP addresses B. Limit Login Hours C. Set password policies D. Use hardware token |
D. Use hardware token |
|
|
Which of these is not a method for controlling record-level access? A. Organization-Wide Defaults B. Role Hierarchy C. Profiles D. Sharing Rules |
C. Profiles |
|
|
How can you control object-level access? Pick 2. A. Profiles B. Permission Sets C. Roles D. Groups E. OWD |
A. Profiles B. Permission Sets |
|
|
Which profiles listed are a standard Profile? (Select all that apply) A) Standard User B) Marketing User C) Invoice Manager D) Contract Manager |
A) Standard User B) Marketing User D) Contract Manager |
|
|
If the Org Wide Default is Public Read/Write, what feature in Salesforce is needed to restrict access to that object? A) Profile B) Role Hierarchy C) Record Type D) Page Layout |
A) Profile |
|
|
Is it possible to share a custom object record manually? A) True B) False |
A) True |
|
|
You want to give a profile access to a custom object. What would be the best way to do this? A) Create a new profile and grant access B) Clone a standard profile and grant additional access C) Edit a standard profile D) Create a permission set and assign it to relevant users |
B) Clone a standard profile and grant additional access |
|
|
What should a system administrator use to disable access to a custom application for a group of users? A) Profiles B) Sharing Rules C) Web Tabs D) Page Layouts |
A) Profiles |
|
|
You can restrict a profiles view to a certain field by using which feature? A) Profiles B) Roles C) Field Level Security D) Permission Sets |
C) Field Level Security |
|
|
It is possible for a user to own a record and not see it. A) True B) False |
A) True |
|
|
In which scenarios will the sharing button appear? A) When the sharing model for the object is private B) When the sharing model for the object is public read only C) When the sharing model for the object is public read/write D) It will always appear |
A) When the sharing model for the object is private |
|
|
A company’s Sales Intern created a List View for Account and she wants to share it with a colleague, however she cannot see the option to share her list view when she edits it. How can an Administrator correct this? A) Ensure the Sales Intern’s profile has the “Manage Public List Views” permission B) Ensure the Sales Intern’s profile has the “Create and Customize List Views” permission C) Ensure the Marketing User checkbox is ticked on her profile D) Ensure she has Read/Write permissions on the Account object |
A) Ensure the Sales Intern’s profile has the “Manage Public List Views” permission |
|
|
Your company has a private sharing model and a user is having trouble accessing a type of record they need to do their job. The user is at the bottom of the role hierarchy. What feature would be most suitable to grant this specific user access to this record type? A) Field Level Security B) Role Hierarchy C) Org Wide Defaults D) Sharing Rules |
D) Sharing Rules |
|
|
Email Templates folders in Salesforce can grant permissions to different sets of users. Which feature is not available when sharing Email Template folders? A) Public Groups B) Roles C) Roles & Subordinates D) Profiles |
D) Profiles |
|
|
You have recently setup a role hierarchy for your organisation to enable logical sharing through hierarchies. Managers are complaining that although they can see Opportunities of their team, they cannot edit them. What feature needs to be changed? A) Modify the Sharing Rule B) Change the Opportunity Access on the Managers Role C) Change the Opportunity Access on the Teams role D) Modify Org wide defaults to public read/write |
B) Change the Opportunity Access on the managers Role |
|
|
Your company have a requirement to grant the Finance team access to Salesforce. They need to have access to all data in Salesforce, ignoring all sharing. They do not need to edit. What would be the most appropriate way? A) Create a new profile and change all Org wide defaults to public read/only B) Create a new profile and grant the “View all” permission C) Add Finance users to the standard profile, Read Only. D) Create a new profile and additional sharing rule to grant access to all finance users. |
B) Create a new profile and grant the “View all” permission |
|
|
All users are currently using the “Standard User” profile in Salesforce. You have recently created a custom object which some users will need access to. How would you do this? A) Create a permission set granting access to the object, assign it to relevant users B) Modify the Standard User profile to grant relevant access to the object C) Create a new profile granting relevant access to the object, assign to the relevant users D) Set access on the custom object to grant access to the users |
C) Create a new profile granting relevant access to the object, assign to the relevant users |
|
|
A user is complaining that they cannot see a tab for an object after you have recently switched their profile. What could be the issue? (Select 2) A) The profile does not have access to the object B) The object’s tab is set to “Default Off” on the profile C) The tabs sharing settings have changed |
A) The profile does not have access to the objectB) The object’s tab is set to “Default Off” on the profile |
|
|
For the marketing team, several (but not all) executive users, and several (but not all) users from sales ops should be granted the ability to access several list views and a report folder. As the Salesforce administrator, how would you structure access? A. Specify the named users and roles within the sharing criteria for each list view and the report folder. B. Create a new role, and assign each user to this role. Specify the role within the sharing criteria for each list view and the report folder. C. Create a new public group, and assign each user to this group. Specify the public group within the sharing criteria for each list view and the report folder. D. Create a new permission set, and assign each user to the permission set. Specify access to the list views and report folder within the permission set. |
C. You need to create a public group in order to share folder and list view access with individual users. Creating a public group would be ideal in this scenario regardless, as you would be able manage the list of users in a centralized fashion (instead of making the change on each list view or folder). |
|
|
The operations team uses a field on account called “Delinquency Status” to indicate when an account is behind on payment. This field should be visible to only the following users: - The entire finance team - All sales managers - 2 named users of the 75 sales reps What is the best way to implement this scenario? A. Grant field-level visibility to the Delinquency Status field to the finance team, sales manager, and sales reps via role. B. Grant field-level visibility to the Delinquency Status field to the finance team, sales manager, and sales reps via permission set. C. Grant field-level visibility to the Delinquency Status field to the finance team, sales manager, and sales rep profiles. D. Grant field-level visibility to the Delinquency Status field to the finance team and sales manager profiles. Grant field-level visibility to the Delinquency Status field to the two sales reps via permission set. |
D. As the entire finance team and all sales managers need access to the Delinquency Status field, granting this access at the profile makes sense (as this establishes the baseline for these users). The baseline for sales users would not include access to the field, however. Using permission sets to grant access to specific users in this scenario makes sense. |
|
|
Customer service reps must be able to create cases, and edit cases that they own. However, they should not be able to view cases owned by any other users. Org-wide defaults for the case object must be set to which of the following? A. Public Read/Write B. Public Read Only C. Private D. Not Visible |
C. In order to restrict visibility to records that other users own, org-wide defaults must be set to private. ‘Not Visible’ is not a valid option. |
|
|
Julie and Jim are both sales reps in your organization, and are collaborating on an account “Squared Wireless”. Jim currently owns the account, and Julie cannot view the record in Salesforce. Jim would like for Julie to have the ability to view and edit the “Squared Wireless” account record. All other accounts records owned by Jim should remain not visible to Julie. Account collaboration is rare within your organization. Julie and Jim are assigned the same role and profile. How can this be solved? A. Instruct Jim to manually share the account record. B. Create a criteria-based sharing rule to grant access to records as needed. C. Set the org-wide default for accounts to read only. D. Add Julie and Jim to a public group "Sales Collaboration". Create a sharing rule that grants members of "Sales Collaboration" read/write access to account records owned by users in "Sales Collaboration". |
A. In this scenario, manual record sharing would allow Jim to easily share a single account record with Julie. If there were many record to share, then you might consider a sharing rule. |
