Salesforce Administrator Interview Questions and Answers
Salesforce Administrator Interview Questions and Answers
1. What is a Profile?
Profiles and roles work together to determine which records users can see and what they can do
with them. Profiles are always required and control which objects and fields users can access.
They also determine whether users can create, edit, or delete records.
2. What is a Role?
Roles are technically optional, but it’s a good practice to use them. Roles are predominately about
sharing records with users. When organization-wide default sharing is set to lower than Public
Read/Write for an object, you can use roles in sharing rules to determine which records (and
whether they’re Read-Only or Read/Write) users can view. Roles also have a hierarchy like an
organization chart so that the sharing can cascade beyond records users need, but also for
managers to access their team’s records.
Permission sets are 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 you can give users
slightly different permissions without having to create separate profiles. This reduces the
overhead for administrators. It’s useful to think of profiles as the base set of permissions that
many users have in common, while permission sets are the ‘extra’ permissions that fewer users
need. You can also group multiple permission sets together by job function via Permission Set
Groups for simpler and more consistent administration. Salesforce and Trailhead have useful
articles on the subject.
Salesforce have announced that permissions on profiles will be retired as end of life (EOL) as of
the Spring ‘26 release. Profiles will still exist; however, permissions on profiles will be retired and
permissions will be available only on permission sets.
Administrators can now begin to change the security model in preparation for the ultimate
change by migrating permissions from profiles to permission sets and enabling Field-Level
Security for Permission Sets During Field Creation under User Management Settings.
Public groups are similar to roles what permission sets are to profiles. An administrator can create
ad hoc groups of users (naming them individually or by roles) to be able to share records to them.
A common use case is to share records with users of a similar level, say directors. As directors are
probably spread throughout the organization, they aren’t likely to be under each other in the role
hierarchy. However, an admin could create a public group with all of the director roles in it and
share records with the group. Queues are similar to public groups in that they are bespoke
groupings of users (named individually or via roles), but they are used for record ownership
rather than sharing rules. The classic use is for cases – where you’d want to assign an open one
to a team of people so that whoever is available first handles it. Queues are available on all
custom objects and many standard objects.
A lookup relationship allows you to relate records to each other, creating a parent-child schema.
Generally, this is done between the different objects (such as accounts and contacts), but it can
be one object (such as parent accounts). Relationship fields allow for users to specify how records
affect each other and help with reporting.
Master-detail relationships are similar to lookup relationships but have a few special features.
First, master-detail allows for roll-up summary fields to be created. This relationship type also
affects security in that the detail (or child) record does not have a record owner. It inherits its
visibility from the master (or parent) record. That can be very beneficial or limiting, depending
on your use case.
A roll-up summary field is available on the master side of a master-detail relationship. It allows
administrators to aggregate data from related detail records (count them, sum a numeric value
on them, etc.) in real time. The ability to have roll-up summary fields is the top reason why you’d
consider a master-detail relationship.
Field types define the type of information you expect users to enter for that field. Examples
include text, number, date, currency, etc. It’s important to match the field type to the data
because it affects your ability to report on and analyse the data. For example, you could store
numbers in text fields, but that would make performing calculations on them needlessly
challenging.
Validation rules allow you to enforce specific business logic to help with your org’s data integrity.
You can specify conditions on an object that aren’t allowed to exist. For example, if you don’t
want a user to mark an Opportunity as Closed Won if the account doesn’t have a billing address,
you can add a validation rule so that when a user tries, it won’t update the Opportunity record
and displays an error message explaining what they need to do.
Sometimes, you’d like to aggregate child data on a parent record, but you can’t use master-detail
due to the security limitations not aligning with your use case. In those situations, you could write
code or use Flow Builder to replicate the functionality of roll-up summary fields. Most likely,
however, you’ll want an app from the AppExchange to make configuration easy. In fact, an app
like this is one of the first things you should look to install in your org (in a sandbox first, of
course.)
A junction object is a term to describe an object that is designed to have two different parent
objects (generally with master-detail relationships), which forms a many-to-many relationship.
There is nothing labelled “junction object” within Salesforce – it’s a definition applied to an object
based on its function in the data model. A common use case is something like classes in a school.
The school will offer many courses and have many students, and each of them will be connected
to many classes.
Flow is an admin’s primary declarative automation tool. Flow can perform actions such as
creating, updating, and deleting records, as well as sending emails, outbound messages,
launching other flows, and calling Apex code. Flow 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 flows to be triggered are via record changes,
screens, or on a schedule. Flow Trigger Explorer allows admins to determine the order in which
flows run so that automation can be efficient and not create conflicts. There’s also a tool called
Flow Orchestrator that allows admins to develop multi-user, multi-step automation.
If you’re interested in learning more, don’t forget to check out the following resources:
Salesforce has announced the retirement of workflow rules and process builder. Both declarative
tools were predecessors to Flow and are no longer necessary (now that Flow can do everything
they can do!). It’s important to know that existing workflow rules and processes continue to
operate as they have (and can be edited and activated/deactivated) but can no longer be created
as of Winter ‘23 and Summer ‘23, respectively. There are Migrate to Flow tools available, and
admins should thoroughly review options and considerations. Because an admin can expect to
work with orgs that have existing workflow rules and processes in place, understanding them
remains vital. For further reading, check out Workflow Rules vs. Process Builder (Feat. APEX &
Flow) and Process Builder vs. Flows – Become the Ultimate Admin.
Salesforce have had a suite of Einstein AI products for years, which have largely served as
analytical and predictive tools. Recent AI advancements have led to GPT tools, which are
generative AI – meaning that they can create auto-generated content. Probably the most
important thing to know is that GPT products use what is called large language models (LLMs) to
learn. Salesforce’s AI Cloud uses the Einstein GPT Trust Layer, which allows data within a
Salesforce org to be used by the AI while protecting it. Several GPT products are now available,
and we can anticipate more to come at Dreamforce 2023 and beyond.
An approval process is for very specific automation use cases. Naturally, 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.)
Apex is the language in which Salesforce code is written. While a tool more for developers than
admins, it’s important to know that code can extend your org to do pretty much anything you
need.
Experience Cloud (formerly Community) is a way to allow your customers and partners to access
your 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 you
want them to. Check out the Experience Cloud Basics module for further context.
Guest users are people without user accounts in your org. They are also called unauthenticated
users because they don’t need to log in. You can make pages (and data!) publicly available. These
users can even create or edit records. Naturally, there are a lot of considerations and limitations
to evaluate, but leveraging this feature can solve many use cases and do so economically, as
guest user licenses are free. Take a look at how the National Aquarium leverages guest users
licenses to allow constituents to manage email preferences. Admins can combine Experience
Cloud, guest users, and screen flow to solve some fairly complex use cases, such as the National
Aquarium reservation and education experience applications.
Applications you install from the AppExchange are in the form of packages — a collection of all
of the elements required to make the app function correctly. The creator of the app decides
whether the package is managed or not. At a high level, unmanaged packages, once installed,
behave like things you have created yourself in the org. Whereas components of managed
packages are locked down from being edited, kind of like apps you install on your smartphone.
While not exactly the same as an AppExchange package, a change set is quite similar. It’s a
collection of components you want to migrate between related orgs (generally from a sandbox
to production, but also sandbox to sandbox and other configurations). Salesforce has also
launched the DevOps centre, which “makes it easier to collaboratively build, test, and deploy
custom solutions across Salesforce – including automations, applications, and experiences – that
connect to real-time customer data.”
There are Developer, Developer Pro, Partial, and Full sandboxes. The difference is what data is
included in the sandbox when it is created or refreshed. The developer ones have no data initially
(they differ in the amount of data it can contain), and the partial and full start with some or all of
your production data. It’s important to note that they also differ in how often they can be
refreshed: developer daily, partial every five days, full every 29 days.
Record types allow you to create separate kinds of records for each object. They control the page
layouts, picklist values available, and other business logic. A good example is a call centre – you’d
likely need different fields visible and required for cases involving customers’ mortgages
compared to car loans.
• Here’s a tip: I almost always create a record type when creating a new object, even if I only
plan to use one type. It’s so much easier to add a second one when you need them than to
go back and introduce records types to an object that already has records.
List views are the queries you can present to your users to help them review the records that
interest them. Most often found when they click on a tab in an app, but they could also be
displayed via Lightning components on other Lightning pages. List views can be filtered on how
they are needed and display whichever columns are relevant. Users can also pin their default list
view on each tab.
Reports are similar to list views, but they can do so much more. They can group records and
create summaries. Dashboards allow for visualizations of the data.
At a high level, a page layout controls which fields are visible for a specific record, but they control
more than that. They can also control which fields are editable or required. Additionally, page
layouts control buttons, related lists, and some other elements.
Lightning components are where the magic of Lightning Experience really comes alive. They are
modular features that can be added, moved, or rearranged on Lightning pages. They are the
record details, Chatter elements, highlights panel, path display, etc. There are dozens of standard
Lightning components, and you can also create your own custom Lightning components or get
them from the AppExchange.
28. What is the difference between a Page Layout and a Lightning Page?
In Lightning Experience, page layouts are basically represented by Lightning components that
display its content (mostly the details and related list components), but Lightning record pages’
house so much more! The Lightning page controls all of the other Lightning components you can
leverage. You can also make all of the components conditionally visible. The conditions can be
based on things like the user’s profile or data in the record. There are also other types of Lightning
pages: home pages and app pages. Those pages won’t have any individual records but could
enhance the user experience by containing things like charts, list views, Lightning screen flows,
and more! The limit is almost anything you can think of to make things better for your users. You
can even make Lightning pages’ function differently between desktop and mobile instances.
There are many ways to import and export data in bulk from Salesforce (including Import Wizard,
exporting reports, and third-party tools such as dataloader.io), but the Salesforce Data Loader is
the original. It’s a downloadable client application that’s free and provides all of the options you
need. You may want to take a look at the Data Management Trailhead module.
Once a tool primarily for developers, custom metadata types have increasingly become useful
for admins. Custom metadata is kind of like custom objects – but rather than store data for your
organization, it’s data about your organization. Things like discount rates, blackout dates, sales
goals, etc. are good use cases. The metadata becomes available to you in formulas, automation,
etc. Also, because it’s metadata and not data, it’s automatically available in all sandboxes you
create or refresh.
Salesforce Administrators manage and maintain the Salesforce platform, making them an integral
part of an organization’s technology team. Successful Salesforce Administrators possess technical
proficiency, analytical skills, effective communication, problem-solving skills, attention to detail,
and a commitment to continuous learning. They use data to make informed decisions that
optimize the platform’s performance and drive business success. Salesforce Administrators
troubleshoot and solve problems related to the platform and ensure that the data is accurate
and up-to-date, as it forms the basis for critical business decisions. They collaborate effectively
with different teams and explain technical concepts in simple terms.
The expansion of CRM is ‘Customer Relationship Management.’ CRM is an application that helps
automate systems or digitize marketing functions. With this software, companies can plan to
increase their profits and revenues. This strategy of incrementing revenue and profit is made by
attracting customers, clients, and sales. The important concept of CRM is customer value.
• Customer acquisition
• Customer retention
• Customer churn
• Customer win-back
• Customer portal: It enables us to utilize the capabilities of the web as the ideal channel to
deliver superior self-service.
• Partner portal: It allows partner users to log in to Salesforce via a separate website than
that is used by non-partner users.
• Self-service portal: Customers will be able to search for details about the organization using
this portal.
In Salesforce.com, a list of tabs is placed in the Tab menu. Tabs are used to access an object’s
data.
• Custom tab
• Visualforce tab
• Web tab
• Standard User
• Solution Manager
• Marketing User
• Read-only
• System Administrator
• Profiles: Object and field-level access may be created using profiles, such as general
permissions, tab-level permissions, read & write permissions, and so on.
• Role: We may offer record-level access using roles, such as organization-wide defaults, Role
hierarchy, sharing rules, and manual sharing. Simply put, record-level access is influenced
by responsibilities.
39. Mention the ways to store files, documents, and images in Salesforce.com.
• Attachments
• Documents
• Google Drive
• Libraries
• Chatter Files
In Salesforce, Field Dependencies are filters that will let the users modify their content and
control the value of one field dependent on the value of another. There are two other fields in
Field dependency which are.
• Controlling Field.
• Dependent field.
There are a few sharing rules in Salesforce available which are as follows:
• It can be created for a Master-Detail relationship but not for a Lookup relationship.
• Auto numbers are not available here.
• We cannot change the field type in a roll-up summary field.
• It derives data from the Child object.
• Count
• Sum
• Min
• Max
• Tabular Report: It is similar to a spreadsheet and is the simplest and fastest way to see data.
Tabular reports are the best to create lists of records.
• Summary Report: It is similar to a tabular report but allows users to group rows of data,
view subtotals, and create charts.
• Matrix Report: It is similar to a summary report, but it allows users to group and summarize
data by both rows and columns.
• Joined Report: Joined reports let us create multiple report blocks that provide different
views of our data and each block acts as a sub report.
• Role Hierarchy
• Organization Wide Defaults
• Manual Sharing
• Criteria-Based Sharing Rules
• Apex Sharing
Without the need for any sophisticated algorithms or custom fields, a bucket field allows you to
combine related data together by ranges and segments. Bucketing is a method of grouping,
filtering, and arranging report data. You must define numerous categories (buckets) that are used
to group report values when creating a bucket field.
Dynamic dashboards help us display the set of metrics in an organization. They are created to
provide security settings for dashboards at Salesforce.com.
Workflow in Salesforce is business logic that helps you to automate your organization’s normal
processes and procedures, saving you a significant amount of time. Workflow allows records to
carry out tasks like changing data or notifying individuals or external systems. We can automate
tasks like assigning tasks, sending emails, updating fields, and sending outbound messages.
• Workflow Rules
• Workflow Tasks
• Workflow Email Alerts
• Workflow Field Updates
• Workflow Outbound Messages
There are the various relationship types in Salesforce that users can create. Which are:
• Self-relationship
• Lookup
• Indirect lookup
• External lookup
• Many-to-many (junction object)
• Hierarchical
• Master-detail relationship
• Oracle CRM
• Microsoft Dynamics CRM
• Salesforce CRM
• SAP CRM
• NetSuite CRM
• Sage CRM
• SugarCRM
• Visual page
• Web service
• Triggers
• Email services
A Formula field is a read-only field that is coupled with a formula or expression from which its
value is calculated. With the corresponding modification in the formula or expression, the value
of this type of field is immediately changed. This field can be created using both standard and
custom objects.
Salesforce Data Loader is a client application that allows you to import or export data in bulk.
One can insert, update, remove, or export Salesforce records with this tool. Data Loader reads,
extracts, and loads data from comma-separated values (CSV) files or a database connection for
importing data. It creates CSV files for exporting data.
• When we need to insert, update, delete, or upset large volumes of records in Salesforce
(more than 50,000 records).
• When you need to load data into an object that is not yet supported by web-based
importing, such as the Chatter free data license object or custom objects with complex
relationships.
• When you want to save multiple mapping files for future use or share them with other
users.
• When you want to export data from Salesforce for backup or migration purposes.
• When you want to prevent duplicates by uploading records with a unique external ID field.
There are two data management tools available in Salesforce which are:
In Software as a Service (SaaS), the cloud service provides software that we need to develop an
application, saving us from purchasing it. SaaS supports web services and service-oriented
architecture.
• Aliquot
• Accepts
• Akamai
• AppDynamics
• Apprenda
In Platform as a Service (PaaS), the cloud service provides an operating system (OS), hardware,
storage, and network services through the cloud, but we have to pay the service providers based
on our subscription, like the rental services.
In Infrastructure as a Service (IaaS), the cloud service provides the infrastructure, such as servers,
hosting service, and storage.
• AWS
• AT&T
• CA Technologies
• Cloud scaling
• Blue lock
• Eucalyptus
integrate it with other technologies and applications. Also, the edition consists of those
features that are present in the Enterprise edition.
Salesforce tabs allow users to see information at a glance. In the program, it shows the data of
objects and other web material.
Field-level security helps control the accessibility of a user to a particular data field. Suppose, if
an organization is providing a user with the access to see, edit, manipulate, or delete a data object
specific to the user’s field of work, it can hide other data objects from the user.
To control the field-level security, we use to profile and permission sets. The attributes of profile
and permission sets are mentioned below:
• Profiles
o Page layouts
o IP ranges
o Login hours
o Desktop
o Client access
• Permission
o App permissions
o Record types
o Tab settings
o Assigned apps
o Object permissions
o Field-level security
o Apex classes
o Visualforce pages
Org Limits There is no limit for the The packages set limits for
usage of apps, tabs, and the usage of apps, tabs, and
objects objects
66. What is OWD and Do you know how many accesses are available in OWD?
The default level of access to data records for all users in an organization is defined by the
Organization’s defaults. Defaults are used to limit data access across the organization (Records).
For both Standard and Custom Objects, Organization-Wide Defaults (OWD) can be set.
In Organization-Wide Default, around 13 various accesses are available. They are as follows:
67. What exactly is a trigger? What are the different kinds of Triggers?
Triggers are the custom actions done in Salesforce before and after changes are made to a record.
Insertions, updates, and deletions are examples of these activities. Triggers may be used to call
Apex, and a trigger is just Apex code that runs before and after the next set of activities.
• Before trigger, used to update or validate records before saving into the database
• After trigger, used to access field values that are set by the system.
Cloud computing is a way to access information and applications online instead of having to build,
manage, and maintain them on your own hard drive or servers. It’s fast, efficient, and secure.
Simply put, cloud computing is a way of accessing services on the internet instead of on your
computer. You can use the cloud to access applications, data, and development tools from
virtually anywhere. Whether you’re working on your phone from a crowded train in Chicago or
on your laptop at a hotel in Hong Kong, you can access the same information because it all lives
online.
• Developer Sandbox
• Developer Pro Sandbox
• Partial Copy
• Full Sandbox
Master-Detail relationship is a relationship between a parent and child where the master
represents the parent and the detail represents a child. This relationship can be used when we
want to control the display of detail records based on the value present in the master record.
The master object completely takes control of the behaviour of the Detail object. The survival of
the child is dependent on the parent, because if the parent gets deleted then the child
automatically gets deleted. You can create Roll-up summary fields in master records which will
calculate the SUM, AVG, and MIN of the child records. Consider an example of a courier company
model, where a delivery schedule is always linked to a delivery location. If we delete a delivery
location from our list, then all the related delivery schedules should also be removed. Such a
dependency can be achieved only through a Master-Detail relationship
Junction objects are useful in building many-to-many relationships between objects in Salesforce.
Take an example of recruiting application, where a position for a job is linked to many candidates
or a candidate can apply for many other jobs. Here object “job application” is referred to as a
junction object in order to connect the data model. In this example, “job application” is the
junction object.
If the default Max Roll-Up Summary Field limit per object increased from 10 to 25 in the Winter
’16 release. Hard-coded limit for roll-up summary fields is 40 per object.
Role Profile
The role helps in defining data visibility A profile sets the limitation for what a
for a particular user. user can do in the organization.
A Permission Set is a collection of settings or permissions that is used to give access to numerous
tools and functions for the user. You can use permission sets for different types of users to extend
functional access without changing their profiles. Instead of creating a separate profile each time,
you could easily create a Permission Set.
By Adding Muting Permission in permission set group we can switch off/turn off/remove
particular permission/Setting within a group without affecting the rest of the permission sets
within the group.
Audit Fields in Salesforce are special fields that track information about your records that can be
valuable for audit purposes. Typically, these fields include: CreatedByID. Created Date
The Audit trail in Salesforce is a unique feature that helps in tracking the changes that have been
made in the organization by you and other administrators. It would be helpful for the
organization with more administrators. This audit trail shows you the information of the twenty
most recently made changes in your organization.
Prioritize and assign records to teams that share workloads. There’s no limit to the number of
queues you can create, and you can choose when queue members receive email notifications.
Groups are sets of users. They can contain individual users, other groups, the users in a particular
role or territory, and/or the users in a particular role or territory plus all of the users below that
role or territory in the hierarchy.
As part of the management process, the reports are used to track progress towards the
company's various goals, control its expenditures, as well as increase its revenues. Reports play
a crucial role in forecasting trends and can therefore increase profits. Reports can be created in
Salesforce.com in a variety of ways and can be scheduled as well. You can organize, view, and
analyse your data with Salesforce's suite of analytic tools.
Report formats in Salesforce can be classified into four different types as follows:
• Tabular Reports: This is the most basic of all report formats and it simply displays the
records in a table without a grand total. Tabular reports are ideal for when you need a
simple list or a list of items without a grand total.
• Summary Reports: As the name implies, this type of report displays a listing of data with
groupings and subtotals at the bottom.
• Matrix Reports: Unlike other types of reports, this one gives you the option to group
records both by row and by column. Furthermore, this report can be used to generate
dashboards as well.
• Joined Reports: These types of reports allow us to create different views of the data from
the different types of reports. In a joined report, the data are organized into blocks. Each
block is a sub-report containing its columns, own fields, sorting, and filtering.
Database.com is the primary enterprise database storage platform for Salesforce, and Salesforce
data is stored in the cloud via this platform. The database.com product is a vast data storage
facility that allows users to safely store millions of records, retrieve them for use in developing
apps, and create flawless transactions in a fraction of a second. Database.com provides a
powerful cloud infrastructure that provides a means to efficiently store, retrieve, and manipulate
information. Listed below are some of the valuable features that Database.com provides:
87. In what ways are files, images, and documents stored in Salesforce.com? List them out.
Salesforce.com allows us to store files, images, and documents in the following ways:
• Attachments
• Documents
• Google Drive
• Libraries
• Chatter Files
Chatter is a Salesforce application that makes it easy for your users to communicate, collaborate,
and share information in real-time. Chatter can be used by individuals of all roles and locations
in the organization to connect, engage, and motivate them to work efficiently.
Approval processes are types of workflows that require work to pass through a series of steps to
be approved. This process typically involves reviewing the work and approving or rejecting it by
various departments with employees from different positions involved in the process. After this,
the workflows in both directions, either back to the previous step for editing, or on to the next
step for further approval, depending on whether the work has been accepted or rejected by one
department. Currently, many companies use computers to automate their approval processes,
however, some firms still use manual approval procedures, such as passing paper documents
from department to department.
When working on a real-time project, there are some situations where we do not need to execute
the task immediately. Time-dependent actions can help in these cases. Time-dependent actions
are performed at a specific time, such as 10 hours or 10 days (time triggers) before the closing
date of a record. The workflow rule evaluates the record after that period has passed to ensure
that it still meets the rules. If so, the workflow rule performs those actions. In Salesforce, a time
trigger indicates after how many hours or days we want this action to be performed.
• Task: It is a simple way of assigning a task to an individual user, a team member, or a role.
The assignee can be notified via email when a task is automatically assigned.
• Email Alert: It uses an email template to send automated email messages. Salesforce allows
users to create an email template that can be used to send emails when they need to.
• Field update: Field updates are used to automatically change the value of a field on a record
that was initially triggered by the workflow rule.
• Outbound Message: Outbound messages are those that are sent to a designated endpoint,
such as an external service. Listening to these types of messages is possible using a SOAP
(Standard Communication Protocol System) API.
• Manual Sharing.
• Apex Sharing.
• Role Hierarchy.
• Criteria Based Sharing Rules.
• Organization-Wide Defaults (OWD).
Permission sets are essentially collections of settings and permissions that allow users access to
certain features and tools. In other words, permission sets can extend the functional access of
users without modifying their profiles. A Salesforce user can only have one profile, although
depending on the Salesforce edition, they may have several permission sets. Permission sets may
be assigned to various types of users regardless of their profile.
Salesforce is the most popular customer relationship management (CRM) platform available
today. It provides cloud-based CRM applications designed for use in sales, service, marketing,
and much more. Businesses use Salesforce to manage business relationships and their associated
data.
CRM is an acronym for Customer Relationship Management, and it describes an application that
helps businesses automate and digitize sales and marketing activity to manage (and increase)
revenue. Sales and marketing professionals leverage CRM’s features to attract and retain
customers and clients, thereby increasing sales.
• Handle normal administrator functions and routine tasks, including user account
maintenance, dashboards and reports, and workflows.
• Perform routine internal system audits and prepare the system for possible upgrades
• Help train new Salesforce users and help the staff increase their Salesforce skills.
• Oversee Salesforce data feeds
• Function as a liaison between users, vendors, and development teams
• Work with the organization’s management teams to establish appropriate processes that
benefit all administrative, change management, and development activities
97. Explain cloud computing, including the different forms available.
Cloud computing is a scalable, on-demand networked system of remote servers hosted on the
internet that enables users to store, retrieve, manage, and process information remotely,
replacing on-site infrastructure.
99. How many different editions does Salesforce have, and how often do they release
updates annually?
• Customer portal
• Partner portal
• Self-service portal