Practice Salesforce Exam Q's and A's Flashcards

Question

Mass Exports

Answer 1

- Converting several files into another format than the one they are currently in

Answer 2

1.) Setup -> Create -> Workflow and Approval -> Approval Process 2.) Select object for approval process to be written Click on Create New Approval Process Select Standard Setup Wizard from drop down Enter the Process name, Unique Name and description for your process Specify Entry criteria

Answer 3

1. ) Task 2. ) E-mail Alert 3. ) (Send an) Outbound Message 4. ) (Update a) Record

Answer 4

1. ) Org-Wide Defaults 2. ) Profile 3. ) Manual Sharing 4. ) Role Hierarchy 5. ) Sharing Rules

Answer 5

- The most restrictive sharing rules in Salesforce - Includes the following 5 settings: 1. ) Private: In this no one can see other data. This means Opportunity is set to private and if one Opportunity is created in the Org, nobody can go through that record 2. ) Public Read/Write: With this feature, everyone gets access on every record 3. ) Public full access: Everyone has access on every record with full access 4. ) Public Read/Write/Transfer: Everyone has access on every record and has the right to read, write, and transfer records 5. ) Controlled by Parent: Basically enabled for child records but has full control to its master record

Answer 6

- Defines how users access objects and data, and what they can do within the application - When I create users, I assign this to each one

Answer 7

- Gives other users access to certain types of records, including accounts, contacts, and leads - Sometimes, granting access to one record includes access to all its associated records - For example, if I grant another user access to an account, the user automatically has access to all the opportunities and cases associated with that account - To grant access to a record, I must be one of the following users. 1. ) The record owner 2. ) A user in a role above the owner in the hierarchy (if my org's sharing settings control access through hierarchies) 3. ) Any user granted Full Access to the record 4. ) An Admin - If a user transfers ownership of a record, Salesforce deletes any of these created by the original record owner, which can cause users to lose access - When account ownership is transferred, these created by the original account owner on child records, such as Opportunities and Cases, are also deleted - When the parent account for a contact associated with a portal or community user changes, these for custom object records that were shared with the portal or community user are deleted

Answer 8

- A mechanism to control the data access to the records on a SF object based on the job role of a user - For example, a manager needs to have access to all the data pertaining to the employees who report to him, but the employees have no access to the data that is only owned by their manager - In this manner, the access model looks similar to the org chart in an org but it doesn't need to be exactly the same as the Org chart - This automatically grants record access to users above the record owner in the hierarchy - This option is enabled for ALL objects by default

Answer 9

- This enables me to make automatic exceptions to my org-wide sharing settings for selected sets of users - Can be based on who owns the record or on the values of fields in the record - For example, use these to extend sharing access to users in public groups or roles - As with role hierarchies, these can never be stricter than my org-wide default settings - These just allow greater access for particular users - I can assign ONLY either Read-Only or Read/Write access

Answer 10

- A collection of settings and permissions that give users access to various tools and functions - These types of sets extend users’ functional access without changing their Profiles - Users can have only ONE Profile but, depending on the Salesforce edition, they can have multiple of these - I can assign these to various types of users, regardless of their Profiles - I can create these to grant access among logical groupings of users, regardless of their primary job function - For example, let’s say you have several users who must delete and transfer leads. I can create one of these type of sets based on the tasks that these users must perform and include this set within this type of sets groups based on job functions

Answer 11

- Allows an Admin to automate my org’s lead generation and support processes - Use these types of rules to specify how leads are assigned to users or queues - Use thse types of rules to determine how cases are assigned to users or put into queues - Lead assignment rules can assign leads regardless of whether leads are created manually, are generated from Web-to-Lead forms, or are imported using the Data Import Wizard - These types of rules can assign cases regardless of how cases are created - Cases can be created manually or automatically using Web-to-Case, Email-to-Case, On-Demand Email-to-Case, the Self-Service portal, the Customer Portal, Outlook, or Lotus Notes - Orgs typically use one rule for each overall purpose - For example, use one of these types of rules for importing leads and use a different lead assignment rule for web-generated leads. Or use one of these types of rules for standard use and one of these types of rules for holiday use - For each rule type, only ONE rule can be in effect at any time - Each rule consists of multiple rule entries that specify exactly how the leads or cases are assigned - For example, a standard rule can have two entries: cases with “Type equals Gold” are assigned to the “Gold Service” queue, and cases with “Type equals Silver” are assigned to the “Silver Service” queue