Practice Salesforce Exam Q's and A's Flashcards
2 Standard Objects related to Account records:
- ) Cases
2. ) Opportunities
3 Objects related to Campaign Members:
- ) Contact
- ) Lead
- ) Person
3 Branding Options
- ) Brand Color
- ) Loading Page Color
- ) Loading Page Logo
Northern Trail Outfitters has web form for cases.
If the case assignment rules are inactive, who will be assigned ownership when the case is created?
A. The system administrator will be assigned.
B. The case will be assigned to a default case queue.
C. The case will be assigned to the default workflow user.
D. The default case owner will be assigned
D. The default case owner will be assigned
Northern Trail Outfitters has two sales groups. Each group has its own unique sales process. Management wants to ensure that the sales groups see their relevant sales process when working on opportunities.
How should an administrator meet this requirement?
A. Page Layouts
B. Enable Paths
C. Opportunity Teams
D. Record types
D. Record Types
Northern Trail Outfitters wants to backup administrator set up for their org. Once the administrator is set up, they report that they are unable to perform any of the administrative duties.
What are two possible reasons for the access issues? (Choose two.)
A. The role needs to be specified on the user record.
B. The System Administrator profile is unavailable under the Salesforce Platform license.
C. The active checkbox is unchecked by default.
D. The user was given the delegated administrator group access.
A. The role needs to be specified on the user record.
B. The System Administrator profile is unavailable under the Salesforce Platform license.
2 Times when to use Lookup Filters
- ) To improve user efficiency by limiting the number of available options in a lookup search dialog
- ) To improve user efficiency by automating filters on lookup search dialogs that your users manually set
2 Times when to use Validation Rules
- ) If I’m close to the maximum number of lookup filters allowed.
- ) To implement a complex business rule that requires me to use a formula. Formulas can reference fields that basic filter criteria can’t reference, such as fields on the parent of the source object. Formulas can also use functions. For example, use ISNEW to apply the rule only on record creation, or ISCHANGED to apply the rule only when a field changes.
Case Feed
Shows a Chatter feed of all case interactions, including Chatter posts, case emails, questions related to the case, and attachments
3 Things to specify on the Company Information page:
- ) Org Name
- ) Default Time Zone
- ) Default Language
Data Categories
- Used in Salesforce Knowledge (articles and article translations), Ideas, Answers, and Chatter Answers to help find and classify articles, questions, or ideas
- I can also use these to control access to a particular set of articles, questions, or ideas
- Article access can be controlled as well
4 Small and Large Data Backup Methods
- ) Data Loader Exports
- ) Report Exports
- ) Weekly Data Export Service
- ) Mass Exports
Data Loader Exports
Use this tool to extract data from a Salesforce object
Report Exports
To work with report data in a dedicated tool, such as a spreadsheet, export report data as a Microsoft Excel (.xlsx or .xls) file or comma-separated values (.csv) file
Data Export Service
- An in-browser service, accessible through the Setup menu
- It allows an Admin to export data manually once every 7 days (for weekly export) or 29 days (for monthly export)
- I can also export data automatically at weekly or monthly intervals
- Weekly exports are available in Enterprise, Performance, and Unlimited Editions
- In Professional Edition and Developer Edition, I can generate backup files only every 29 days, or automatically at monthly intervals only
Price Book
- A list of products and their prices
- Includes standard and custom books
Standard Price Books
- The master list of all my products and their default standard prices
- Salesforce creates these types of books when I start creating product records
- It includes all of my products and their standard prices regardless of any custom price books that include those products
Custom Price Book
- A separate list of products with custom prices, called list prices
- These types of books are ideal for offering products at different prices to different market segments, regions, or other subsets of my customers
- It’s recommended to create a separate book for each set of customers that I want to address
- For example, if I have one set of prices for domestic customers and another for international customers, create a domestic price book and an international one
Price Book Entry
- A product with its price as listed in a price book
- Each of these specifies a currency for the price
Standard Price Book Entry
- The default (standard) prices for the products and services in the standard price book
- When I create a product record, Salesforce creates this
- I can mark this as active or inactive, depending, for example, on whether I intend to start selling the product right away
Custom Price Book Entries
- The custom (list) prices for the products and services in my custom price books
- These entries can be created only for products with active standard price book entries
Sites using Experience Cloud (formerly Communities)
- Great way to share information and collaborate with people who are key to my business processes, such as customers, partners, or employees
- This also includes collaboration between customers
Setup Audit Trail
- Tracks field history; best to use to discover who added a field to an Account page layout
- Tracks all changes made or actions performed within a org for a period of time
- The 2 changes this tracks are:
1. ) Using the Data Import Wizard
2. ) Resetting a User’s password
2 Fields for Validation Rules
- ) Error Condition Formula
2. ) Error Message
Mass Exports
- Converting several files into another format than the one they are currently in
Salesforce Approval Process
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
4 Rule Actions Allowed in Workflow Rules
- ) Task
- ) E-mail Alert
- ) (Send an) Outbound Message
- ) (Update a) Record
Salesforce Sharing Rules diagram
- ) Org-Wide Defaults
- ) Profile
- ) Manual Sharing
- ) Role Hierarchy
- ) Sharing Rules
Org-Wide Defaults
- 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
Profile
- 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
Manual Sharing
- 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
Role Hierarchy
- 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
Sharing Rules
- 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
Permission Sets
- 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
Case Assignment Rules
- 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
