Salesforce Interview Questions Flashcards
1
Q
Salesforce
A
- A customer-facing CRM system
- A Cloud SaaS platform
- Used to record customer details and the org’s interactions with them
- Most popular products are Sales Cloud and Service Cloud
2
Q
Sales Cloud
A
- Designed to support businesses with their sales cycle
- Used by orgs to record initial interest from customers (Leads) and follow through a Sales cycle, taking customers through various steps to win their business
- Included with this Cloud:
1. ) Prospecting
2. ) Lead
3. ) Opportunity
4. ) Quoting
5. ) Forecasting
3
Q
Service Cloud
A
- Helps orgs with their customer support process
- Designed to support customer service teams from within a business
- Helps agents deal with customer queries, as well as solve issues
- When using this Cloud, customers initiate a support process by e-mailing, calling, or submitting an online form
- Once a case has been created in Salesforce, agents can use features such as a Knowledge base to help find answers to questions, milestones to ensure SLA (Service Level Agreements) are met, as well as features like live chat to talk to customers in real-time
4
Q
Cloud SaaS Platform
A
- Stands for “Software-as-a-service”
- Means I can access it through my web browser, as opposed to a desktop application
- Biggest benefits are:
1. ) Cost (don’t need to buy a ton of servers with this type of platform)
2. ) Upgrades (taken care of for me with this platform)
3. ) Mobility (can be accessed from anywhere)
5
Q
Salesforce Platform
A
- Formerly known as Force.com
- This enables me to create powerful customizations on top of Salesforce’s products, that allow me to completely tailor the applications to my org’s exact needs
- I can create customizations with clicks, not code
- Allows me to create custom fields and objects to store unique information related to my org
6
Q
Automation
A
- One of the most popular customization possibilities in Salesforce
- I can create this to pretty much do anything in Salesforce, update a field, create a record, send an e-mail, etc.
- These types of customizations can end up saving users alot of time
7
Q
Can I provide an example of a custom App I can build on the Salesforce platform?
A
- ) An HR application to help internal teams manage jobs and job applicants
- ) A finance system that can track invoices
- ) A goal-setting App that can help managers set targets and goals for their team
8
Q
Declarative Customizations
A
Point-and-click; allows non-developers to build powerful customizations by using a wizard to create custom fields, automation, and tables of data
9
Q
Programmatic Customizations
A
- Customizations built with code (ex: Apex)
10
Q
Lightning Development
A
Salesforce’s UI coding language; can be used to cerate completely custom screen layouts
11
Q
Can I explain how Salesforce releases work?
A
- Being a Saas platform, Salesforce delivers updates to my system automatically
- The major releases happen 3 times a year
- Some other, much smaller updates are delivered in between the major releases
12
Q
Salesforce Lightning Experience
A
- A new UI released in 2015
- Allows Salesforce Admins to easily control the layout of all pages
- Every single page of this is fully customizable
- I can customize the homepage, record layouts, and create dashboards to suit my specific needs
13
Q
6 Steps of the Sales Cloud process
A
- ) Qualify
- ) Discover
- ) Analysis
- ) Proposal
- ) Negotiation
- ) Closed Won (or Lost)
14
Q
‘Discovery’ phase
A
- 2nd phase in the Sales Cloud process
- Where the salesperson will find out more about the opportunity
15
Q
‘Analysis’ phase
A
- 3rd phase in the Sales Cloud process
- Where the salesperson will find out what kind of product will be suitable for the customer
16
Q
‘Proposal’ phase
A
- 4th phase in the Sales Cloud process
- Where the salesperson will present a proposal to the customer, with the suggested product and pricing
17
Q
‘Negotiation’ phase
A
- 5th phase of the Sales Cloud process
- Reserved for any negotiations that take place
- This could involve pricing negotiations or contract negotiations
18
Q
‘Closed Won (or Lost’ phase
A
- The 6th and final phase of the Sales Cloud process
- Where an option is chosen depending on the outcome of the opportunity
19
Q
5 Phases of the Service Cloud Process
A
- ) New
- ) Working
- ) Waiting on Customer
- ) Escalated
- ) Closed
20
Q
‘New’ Phase
A
- 1st phase in the Service Cloud process
- Used as a holding stage until a customer service agent picks up the case
21
Q
‘Working’ Phase
A
- 2nd phase in the Service Cloud process
- Used when an agent has picked up the case, and is working to solve it
22
Q
‘Waiting on Customer’ phase
A
- 3rd phase of the Service Cloud process
- Used once a reply has been sent to a customer
- This could be a question about the issue, or a resolution has been provided
23
Q
‘Escalated’ Phase
A
- 4th phase in the Service Cloud process
- May be used if a case needs to be escalated to a more senior team
24
Q
‘Closed’ Phase
A
- The 5th and final phase of the Service Cloud process
- This phase is used once the case has been resolved
25
Q
Object
A
- A table of data
- Will contain various fields and in turn, these fields contain information like e-mail address, phone number, or company name
- 2 types: Standard and Custom
26
Q
Standard Objects
A
- Objects that come out of the box with Salesforce products
- Ex: Accounts, Contacts
27
Q
Custom Objects
A
- Objects created by myself
- These are the objects that can be created as my foundation for building custom apps
28
Q
AppExchange
A
- Pre-built apps specifically for Salesforce
- Adds additional functionality in Salesforce
29
Q
How are changes tested in Salesforce before being deployed to Production?
A
By the use of Sandboxes (important: CHANGES SHOULD NEVER BE MADE IN PRODUCTION!!!!!!!!!!!!!!!!!!!!!!)
30
Q
Sandboxes
A
Salesforce feature which replicates my Production configuration, giving me a safe environment to test changes and implement new features
31
Q
4 Primary Salesforce Editions
A
- ) Essentials Edition
- ) Professional Edition
- ) Enterprise Edition
- ) Unlimited Edition
32
Q
Essentials Edition
A
- Preferred by small businesses
- Ready-to-go platform for small businesses to manage and grow their business effectively
- The businesses can leverage easy-t-use UI and intuitive walkthrough guides to customize and get started with their deployment
Includes:
1.) Customizable Sales Process
2.) Lead Management
3.) Multi-Channel Communication
4.) Full Offline Mobile Functionality
5.) Automated Routing
6.) Email Integration
7.) Ticket Management
8.) AppExchange and many more - Costs $25/month
33
Q
Professional Edition
A
- Preferred by small and medium-sized businesses
- Designed for businesses who demand a full-featured CRM functionality to manage their business
- The businesses can conveniently administer their entire sales cycle with with this edition
Includes:
1.) Comprehensive Lead Management
2.) Campaign Management
3.) Mass Emails
4.) Quotes and Orders
5.) Custom Dashboards
6.) Custom Reports
7.) Case Management
8.) Process Builders, and more - Costs $75/month
34
Q
Enterprise Edition
A
- Preferred by large and complex businesses
- Additionally helps large businesses to automate their complex business processes using workflow and approvals
- This edition offers advanced customization and management tools to support large-scale deployments
- Additionally, this edition also includes access to Salesforce API’s, so that the businesses can effortlessly integrate with back-office systems
- Includes:
1. ) Territory Management
2. ) Salesforce APIs
3. ) Workflows & Approvals
4. ) Sales Console App
5. ) Advanced Report Types
6. ) Unlimited profiles and roles per org
7. ) Unlimited processes and flows per org
8. ) Lead Registration, and more - Costs $150/month
35
Q
Unlimited Edition
A
- Preferred for large businesses (more than 1,000 users)
- Offers access to countless online training, 100+ admin services, and premier support
- With this edition, the businesses can build unlimited custom apps and tabs to tailor Salesforce as per their convenience and business requirements
- This edition presents new levels of platform flexibility to manage and share information on demand
- Additionally, the Admins can gain access to multiple sandboxes for development and testing with this edition
- Includes:
1. ) Developer Pro Sandbox
2. ) Workflow & Approvals
3. ) Web Services API
4. ) Increased Storage Limits
5. ) Unlimited Custom Apps
6. ) Full Mobile Access
7. ) 24*7 Toll-free support - Costs $300/month
36
Q
Change Sets
A
- A packaged set of components that can be created in one environment and moved across to another
- Most common way to move changes between environments
37
Q
Metadata
A
- Relates to the fields, configurations, code, logic and page layouts that go into building the information architecture and look and feel of your Salesforce environment
- The data that describes other data
38
Q
Data
A
Relates to the records that a business relies on, such as Users, Accounts, Contacts, to name a few
39
Q
Queue
A
- Holding areas in my CRM, where records wait for a user to pick them up, assign them to an owner, and work on processing them
- Used for record ownership rather than sharing rules
- Available on all custom objects and many standard objects
40
Q
Salesforce Customer 360
A
- Suite of products that allows users of its platofrm to see a 360-degree view of their customers
- This means that users of Salesforce can see every interaction with a customer, from the first enquiry through the website, to which products they have bought and what issues or queries they have with their products
- This helps businesses by allowing them to serve their customers better, by knowing everything about them and ensuring the businesses is working off a single source of truth
41
Q
Profiles
A
- Controls what a user can DO on the platform
- ALWAYS required
- Controls which objects and fields users can access
- These also determine whether users can create, edit, or delete records
- These also control individual permissions such as “Export Reports”, “Create Dashboard Folders”, or “Modify All Data”
42
Q
Roles
A
- Used to control what users can SEE
- Is predominantly about sharing records to users
- These are designed to open up access through a hierarchy so that more senior members of the organization can see more records
- For example, someone at the bottom of the hierarchy, like an Account Executive, might be only able to see their own accounts
- But the VP Sales US would be able to see all accounts owned by individuals below them
43
Q
Automation Tools
A
- Designed to be easy to use and enable businesses to automate complex processes
- This, in turn, helps users be more productive, allowing them to focus on revenue-generating activities instead of manual Admin work
- For example, once an Opportunity is closed won, I could easily create automation to create a case, which prompts the customer success team to get in touch with the customer to begin onboarding
- Further examples include Workflow, Process Builder, and Flow
44
Q
Look-up Relationships
A
- Loosely-coupled relationship
- Relationship where I can relate records easily to other records in a one-to-many fashion
- Roll-up Summary Fields is NOT available
- Parent record is NOT required when creating a Child record
- Lookup fields are NOT required on the page layout of the detail record
- Standard object record can be on the detail side of a custom object in this type of relationship
- By default, record ownership of Child records is NOT controlled by the Parent
- I CAN have a Child record without a Parent
- I can have a maximum of 40 lookups on an object
- No cascade delete
45
Q
Master-Detail Relationships
A
- Tightly coupled relationships; means that a child record CANNOT exist without a parent record, and if a Parent record is deleted, the Child also gets deleted with it
- Allows the Parent record to control Child record attributes such as sharing and visibility
- Whichever security setting I chose for the Parent record, the Child record inherits
- Roll-up Summary field IS available
- Parent record is required in order to save a Child record
- Master-Detail field is ALWAYS required on the page layout of the detail record
- Standard object record CANNOT be a child
- The Parent controls the record ownership of Child records. The Owner field is not available on the detail record in Master-Detail relationship queues, sharing rules, and manual sharing is not possible for detail records as it requires the Owner field
- I CANNOT have a Child record without a Parent
- I can have a maximum of 2 Master Details on an object
- Includes Cascade Delete
46
Q
Page Layouts
A
- Determines which fields are displayed to my users on a record
- Controls which fields are visible for a specific record
- These also allow me to add fields, sections, custom buttons and other features
- The “Details” tab contains a lot of the elements that are controlled by this
- Controls the user interface in various ways and can be used in conjunction with each other to create customized experiences for my users
47
Q
Record Types
A
- Allows me to create separate kinds of records for each object
- These control the page layouts, picklist values available, and other business logic
- Offers different business processes, picklist values, and page layouts to my users
- For example, one of the most common use cases of these would be to create 2 different sales processes on the Opportunity object. Each with different sales stages and Page Layouts
- This means that this can now apply multiple Page Layouts per object, per user profile
- Controls the user interface in various ways and can be used in conjunction with each other to create customized experiences for my users
48
Q
3 Tools that Account and Contact information can be imported into Salesforce
A
- ) Data Loader
- ) Data Import Wizard
- ) Dataloader.io
49
Q
Data Loader
A
- A staple of any Salesforce professionals toolkit
- Free downloadable client application
- This allows me to import, export, update and delete large amounts of records in a single operation
- This has to be downloaded to my desktop for use
50
Q
Data Import Wizard
A
- A simplified tool that allows me to import data into Salesforce
- This is accessed from within Salesforce and also has de-duplication features
51
Q
Dataloader.io
A
- An advanced, cloud-based data loader that is packed full of features
- Whilst this is primarily a paid product provided by Mulesoft, the free version allows a certain number of importing/exporting activities and is very useful for some more complex scenarios
52
Q
Junction Object
A
- Describes an object that is designed to have 2 different Parent objects (generally with Master-Detail relationships), which forms a many-to-many relationship
- There’s nothing with this label in SF; it’s a definition applied to an object based on its function in the data model
- Used to create many-to-many relationshps in Salesforce
- Used when a normal Parent-Child, or a One-To-Many relationship doesn’t work
53
Q
Experience Cloud
A
- A way to allow my customers and partners to access my Salesforce org
- With these special licenses, they can have user accounts and a special access portal, customized with a bevy of Lightning features that can be configured without any code
- It’s also very simple to layer in security so they can only see or edit the objects and records I want them to
- Salesforce product which can be used to provide my Partners with the ability to create Leads and Opportunities
- This allows me to create portals that connect to my Salesofrce instance, for a specific purpose
54
Q
2 Most Common Types of Portals
A
- ) Partner Portal
2. ) Customer Portal
55
Q
Partner Portal
A
- An area where my partners can create leads and manage the sales cycle of opportunities
- All activity can be viewed within my Salesforce Org, along with the provision of full reporting capabilities
56
Q
Customer Portal
A
- A common use case for this is to provide support as well as help articles
- Customers can log cases, as well as search knowledge bases for answers to their queries
- I can even go as far as to create a community that allows customers to interact with each other
57
Q
4 Types of Reports
A
- ) Tabular
- ) Summary
- ) Matrix
- ) Joined
58
Q
Tabular Reports
A
- Simplest of reports; suited just to show lines of data and nothing else
- Similar to an Excel spreadsheet
- If I just want to show data without the need to show totals, calculations or groups of data, then this is the report for me
- Best to use this report type if I am planning to export data
59
Q
Summary Reports
A
- As soon as you add a grouping, I will turn the report into this type of report
- These are probably the most commonly used reports and are great for showing groups of data (for example, if I want to see the number or value of opportunities per account, I would group my report by Account Name)
- I can also subgroup fields by dragging them under the initial group
60
Q
Matrix Reports
A
- Very similar to a Summary Report, but these types of reports allow me to group by rows as well as columns to see different totals
- For example, I might want to see the value of opportunities per account, by month. So I would see that Edge Communications has $100,000 of opportunities in January, $50,000 in February and so on
61
Q
Joined Reports
A
- Allows me to create two separate reports so that I can compare data
- I could use this type of report to show the total number of opportunities and cases per account, side by side
62
Q
Dynamic Dashboards
A
- A fantastic way to create a personalised experience for my users when viewing a certain dashboard
- This allows the data on a dashboard to change, based on the user who is viewing it
- For example, I could have a single, personal sales dashboard for sales reps
- Whenever a different user viewed this dashboard, it would only show their leads, opportunities and accounts. This works by using the “My” filter on all dashboards
63
Q
3 Ways to make Fields required
A
- ) Custom Field Settings
- ) Page Layout
- ) Validation Rules
64
Q
Custom Field Settings
A
- Whenever I create a new custom field, I have the option to make this required
- This is a “hard” limit and will be required whenever I am creating a new record inside of Salesforce or uploading via a data loader
65
Q
Page Layout
A
- With this, I have the option to make fields read-only, or required
- This is considered a “soft” limit, as it will only apply if you are creating a new record via the Salesforce interface, not when uploading via a data loader
66
Q
Validation Rules
A
- Allows me to enforce specific business logic to help with my org’s data integrity
- I can specify conditions on an object that aren’t allowed to exist
- These have much more advanced logic and can be built to only make a field required under a certain condition
- For example, if Opportunity Stage = Closed Won, make X field required
- These have a hard limit
67
Q
Salesforce Order of Execution
A
- A set of rules that describes what events happen when a record is saved in Salesforce
- For example, if I have validation rules, flows, Apex triggers, etc…there is a consistent sequence in which these events get triggered
68
Q
20 Steps of Salesforce Execution
A
- ) Loads Record
- ) Run System Validation
- ) Before Triggered Flows
- ) Before Triggers
- ) Custom Validation Rules
- ) Duplicate Rules
- ) Saves Record
- ) After Triggers
- ) Assignment Rules
- ) Auto-Response Rules
- ) Workflow Rules
- ) Escalation Rules
- ) Flow Automation
- ) Entitlement Rules
- ) After-Triggered Flows
- ) Roll-Up Summary/Cross-Object Workflow
- ) Grandparent Roll-Up Summary
- ) Criteria-Based Sharing
- ) Commits DML Operations
- ) Post-Commit Logic
69
Q
Apex
A
- Salesforce’s primary backend programming language
- This allows developers to write complex automation that runs on the Salesforce platform
- Examples for using this over declarative tools include:
1. ) Writing complex business processes logic that is not supported by declarative automation such as Flow
2. ) Integrating Salesforce into other systems
3. ) Creating custom e-mail services
70
Q
Visualforce
A
- Primarily used back in the Salesforce Classic “era” and based on tag-based markup language, similar to HTML
- Framework which can be used by developers to create completely custom user interfaces on Salesforce
71
Q
Lightning Development
A
- A modern, componentized UI Framework that uses HTML and Javascript
- Framework which can be used by developers to create completely custom user interfaces on Salesforce
72
Q
SOQL
A
- Stands for “Standard Object Query Language”
- Used to search Salesforce data when developers are writing custom logic
- Structured similar to SQL and can be used to retrieve data from a single object, or multiple objects that relate to one another
73
Q
Governor Limits
A
- A concept that allows Salesforce to set certain rules on the number of resources I can monopolize to ensure that everyone’s instances of Salesforce continue to run
- An example of a Governor Limit is “Per-Transaction Apex Limits”. This includes a number of rules that only allow me to run a certain number of queries within a single Apex transaction
74
Q
Mulesoft
A
- An integration platform that was acquired by Salesforce in 2018 for $6.5B
- Salesforce acquired this platform to better serve customers going through their digital transformations and required integration with backend systems such as HR, Finance or ERP
75
Q
Miulesoft Anypoint Platform
A
Allows me to integrate with other systems easily, with a set of templates that provide out-of-the-box API’s
76
Q
Mulesoft Composer
A
Designed to give Admin’s a declarative way to integrate with other systems
77
Q
Apex Trigger
A
Written by developers to fire logic before or after a record is saved
78
Q
When should Flow be used over Apex?
A
Whilst Apex has always reigned as the king, when it comes to complex automation, in recent years, Salesforce has rebuilt Flow to bring it close to Apex in functionality. Parker Harris, the CTO of Salesforce has even been quoted saying “Just Because It’s Possible to Write Code, Doesn’t Mean You Should Write Code”
As a general rule of thumb, if Flow can handle the use case and will not hit any limitations, it’s a good idea to build the automation in Flow. Flow has a simpler user interface and can be understood by a wider range of Salesforce professionals
79
Q
Apex Test Coverage
A
Where developers are required to write test classes that run through their code, ensuring that the code is of good quality and will run successfully in production
80
Q
Lightning Components
A
- Modular features that can be added, moved, or rearranged on Lightning Pages
- Released alongside Lightning Experience; this uses a standardized Javascript framework
81
Q
Lightning Web Components
A
- Released in 2019
- Uses an updated web standards-based framework. This provides easier accessibility for users who are unfamiliar with the Salesforce platform
- This utilizes standard technology such as CSS, HTML and updated Javascript
82
Q
SDLC
A
- Stands for ‘Software Development Lifecycle’
- A concept that defines the best practice way to implement IT systems, by following a series of stages
83
Q
6 Stages of the SDLC
A
- ) Planning
- ) Analysis
- ) Design
- ) Implementation
- ) Testing and Integration
- ) Maintenance
84
Q
Adoption
A
The simple act of enabling a user to use SF’s full CRM capabilities by creating strategies around onboarding, training, and continued development
85
Q
3 Ways of Improving User Adoption
A
- ) Training
- ) Feature Development
- ) Super Users
86
Q
Training
A
- First way to improve SF user adoption
- The act of showing new users how to use Salesforce and answering their questions
87
Q
Feature Development
A
- Second way to improve SF user adoption
- Where Salesforce professionals get feature requests from their users.
- Although not all of them will be possible, it’s important to address users’ issues and ensure that they feel heard
88
Q
Super Users
A
- Third way to improve SF user adoption
- “Champions” of SF
- Identifying these types of users can help drive user adoption
- Salesforce Admins won’t be available all the time to support users, so if I have a network of champions that can drive user adoption, answer questions and gather feedback, this can help
89
Q
Data Cleaning (a.k.a. Clean Data)
A
- The process of fixing or removing incorrect, corrupted, incorrectly formatted, duplicate, or incomplete data within a dataset
90
Q
3 Ways to Promote Clean Data
A
- ) Validation
- ) Duplicate Management
- ) Deduplication Tools
91
Q
Validation
A
- First way to promote clean data
- One of the most effective prevention methods for bad data
- This can come in a few different forms such as required fields, using picklists over free text fields, validation rules, as well as setting correct permissions
- All of the mentioned features are simply trying to ensure that users can only enter data they should be entering
92
Q
Duplicate Management
A
- 2nd way to promote clean data
- Managing this common issue for Users is important
- These can come from various sources including an initial data load, marketing leads (events/website), or users themselves manually entering them
- SF has various simple but powerful duplicate tools to prevent this
93
Q
Deduplication Tools
A
- 3rd way to promote clean data
- Use when bad data has become such a problem and is beyond repair
- Use AppExchange apps to help this issue (ex: DemandTools, Cloudingo)
94
Q
Person Accounts
A
Allows a User to access a new type of record (which is actually a combination of the Accounts and Contacts object) that can support a B2C business
95
Q
3 Ways of customizing Salesforce using Themes
A
- ) Change Logo
- ) Colors
- ) Background Image
96
Q
Lightning App Builder
A
- Key part of the Lightning Experience
- Allows me to edit the rest of a page layout
- I can do things such as move around components, add new components, and change the page template (number of columns/rows)
97
Q
How would I explain Salesforce to someone who has never used a CRM?
A
“CRM stands for Customer Relationship Management. All businesses in the entire world will have some form of CRM. The software simply records who your customers are, what interactions you’ve had with them and what products they have bought.
If you run a hairdressing salon, you might have a spreadsheet or a notebook of your regular customers – if you run a catering company, you will have the same, or if you run a 10,000 employee international conglomerate, you will have CRM software.”
98
Q
Release Date
A
The date the release actually happens, and can change depending on my Org location
99
Q
Sandbox Preview
A
- The date on which my own org’s sandboxes will be upgraded
- Very important for testing the new release against my own customizations
100
Q
Release Notes
A
- Notes which explain, in great detail, the main aspects of any release
101
Q
Scope Creep
A
- Refers to changes, continuous, or uncontrolled growth in a project’s scope, at any point after the project begins
- This can occur when the scope of a project is not properly defined, documented, or controlled
- This is generally considered harmful
102
Q
Permission Set
A
- Add-ons to profiles
- They generally have the same settings and are used to increase users’ permissions above what the profile provides
- The benefit is that I can give users slightly different permissions without having to create separate profiles.
- This reduces the overhead for SF Admins
- It’s useful to think of profiles as the base set of permissions that many users have in common while these are the ‘extra’ permissions that fewer users need
- I can can also group multiple of these together by job function via ______________ for simpler and more consistent administration
103
Q
Public Group
A
Groups of Users (named individually or by Roles) placed in a group where records can be shared
104
Q
Relationship Fields
A
Allows for users to specify how records affect each other and help with reporting
105
Q
Roll-Up Summary Field
A
- Available on the master side of a Master-Detail relationship
- This allows Admins to aggregate data from related detail records (count them, sum a numeric value on them, etc.) in real time
106
Q
Field Types
A
- Defines the type of information I expect users to enter for a field
- Ex: Text, Number, Date, Currency
- It’s important to match this to the data b/c it affects my ability to report on and analyze the data
- For example, I could store numbers in text fields, but that would make performing calculations on them needlessly challenging
107
Q
Flow
A
- An Admin’s primary declarative tool
- Can perform actions such as creating, updating, and deleting records as well as sending emails, outbound messages, launching other flows, and calling Apex code
- This is also the only declarative automation tool that allows admins to build custom screens to interact with users, and can greatly improve the user experience
- The most common ways for these to be triggered are via record changes, screens, or on a schedule
108
Q
Flow Trigger Explorer
A
- Allows Admins to determine the order in which multiple _____ run
109
Q
Flow Orchestrator
A
- Tool which allows Admins to develop multi-user, multi-step automation
110
Q
Approval Process
A
- Used for very specific automation use cases
- It’s used when something needs to be approved and tracks when and who approved or rejected something
- It covers notifying approvers, locking the record from edits, conditional logic for who should approve, and varied approval models (for example, all approvers or any approvers.)
111
Q
Guest Users
A
- People without user accounts in my org
- Also called unauthenticated users because they don’t need to log in
- I can make pages (and data!) publicly available
- These users can even create or edit records
112
Q
Managed Packages
A
- Packages that are locked down from being edited (like an app I install on my phone)
- These are widely used by SF partners to develop applications and sell them to customers
113
Q
Unmanaged Packages
A
These are used to define open source applications and these applications can be modified by the developers who install them into their org
114
Q
4 Types of Sandboxes
A
- ) Developer Sandbox
- ) Developer Pro Sandbox
- ) Partial Sandbox
- ) Full Sandbox
115
Q
Developer Sandbox
A
- Sandbox which is intended for development and testing in an isolated environment
- This includes a copy of my production org’s configuration (metadata)
- Has no data initially (and also differed in the amount of data it can contain)
- Can be refreshed daily
116
Q
Developer Pro Sandbox
A
- Sandbox which is intended for development and testing in an isolated environment and can host larger data sets than a Developer sandbox
- This type of sandbox includes a copy of my production org’s configuration (metadata) - Use this type of sandbox to handle more development and quality assurance tasks and for integration testing or user training
- Has no data intially (and differs in the amount of data it can contain)
- Can be refreshed daily
117
Q
Partial Sandbox
A
- Sandbox which is intended to be used as a testing environment
- This environment includes a copy of my production org’s configuration (metadata) and a sample of my production org’s data as defined by a sandbox template
- Use this type sandbox for quality assurance tasks such as user acceptance testing, integration testing, and training
- Starts with some or all of my Production data
- Refreshes every 5 days
118
Q
Full Sandbox
A
- Sandbox which is intended to be used as a testing environment
- Only these types of sandboxes support performance testing, load testing, and staging
- These types of sandboxes are a replica of my production org, including all data, such as object records and attachments, and metadata
- The length of the refresh interval makes it difficult to use these types of sandboxes for development
- Starts with some or all of my Production data
- Refreshed every 29 days
119
Q
List Views
A
- The queries I can present to my users to help them review the records that interest them
- Most often found when my Users click on a tab in an app, but they could also be displayed in via Lightning Components on other Lightning Pages
- These can be be filtered how they are needed and display whichever columns are relevant
- Users can also pin their default _________ on each tab
120
Q
Reports
A
- Similar to List Views, but I can do so much more with them
- These can group records and create summaries
121
Q
Dashboards
A
These allow for visualizations of the data
122
Q
Lightning Page
A
- Controls all of the other Lightning Components I can leverage
- Also allows me to make all of the components conditionally visible
