Question 1

Explain the Salesforce Architecture with a neat diagram

Answer

 Salesforce is a cloud company. Everything we offer resides in the trusted, multitenant

cloud.
 The Salesforce platform is the foundation of our services. It’s powered by metadata and
made up of different parts, like data services, artificial intelligence, and robust APIs
for development.
 All our apps sit on top of the platform. Our prebuilt offerings like Sales Cloud and
Marketing Cloud Engagement, along with apps you build using the platform, have
consistent, powerful functionality.
 Everything is integrated. Our platform technologies like predictive analytics and the
development framework are built into everything we offer and everything you build.
Question 2

Explain the concept of Sharing Is Caring in the Multitenant Cloud using Salesforce
software.

Answer

Salesforce is set up more like an apartment building. Your company has its own space in the
cloud, but you have all kinds of neighbors, from mom-and-pop shops to multinational
corporations.

This idea is multitenancy. Multitenancy is a great word for making you sound smart at dinner
parties, but really all it means is that you’re sharing resources. Salesforce provides a core set of
services to all our customers in the multitenant cloud. No matter the size of your business,
you get access to the same computing power, data storage, and core features.

Trust and multitenancy go hand in hand. Despite the fact that you’re sharing space with other
companies, you can trust Salesforce to keep your data secure. You can also trust that you’re
getting the latest and greatest features with automatic, seamless upgrades three times a
year. Since Salesforce is a cloud service, you never have to install new features or worry about
your hardware. All this is possible because of multitenancy.
Question 3

Explain the meaning of Metadata in Salesforce with an example

Answer

To put it simply, metadata is data about data. When we say data about data, we’re really talking
about the shells that hold the content related to any information you want to collect in your
Salesforce org.

Let’s think about an object like Property. When our friends at DreamHouse use Salesforce, they
input and view data about properties. For example, a property can be located in Boston, cost
$500,000, and have 3 bedrooms.

Now, imagine that on this Property record you delete Boston, $500,000, and the number 3 for
bedrooms. What are you left with? You are left with the Property object along with all its empty
fields, like the address field, the price field, and the number of bedrooms field. These fields are
metadata.

Now, let’s think about metadata in a bigger context. Metadata is also your page layouts, security
settings, and any other customizations you’ve made to the structure of your org that collect or
use your organization’s data.

All of these standard and custom configurations, functionality, and code in your org are
metadata. Part of the reason you can move so fast on the platform is that Salesforce knows how
to store and serve you that metadata immediately after you create it. Because metadata gives
structure to your org, it helps you know whether to enter a price vs a number, it can reference an
address using geolocation on a map, or collect information about a contact that can be related to
multiple objects.
Question 4

Elucidate the Scenario of an API in general day-to-day life using Salesforce

Answer

The application programming interface (API) allows different pieces of software to connect to
each other and exchange information.

If that sounds kind of abstract, take a quick look at the computer you’re working on right now.
You can probably find a series of ports of various shapes and sizes that support different kinds of
connections. These are like the hardware version of APIs. You don’t have to know how the USB
port works. All you have to understand is that when you plug your phone into a USB port, it
passes information to your computer.

APIs are similar. Without knowing the details, you can connect your apps with other apps
or software systems. The underlying technology takes care of the specifics of how
information passes throughout the system.

When you add a custom object or field, the platform automatically creates an API name that
serves as an access point between your org and the database. Salesforce uses that API name to
retrieve the metadata and data you’re looking for.

For example, we can use a contact’s Name field in a bunch of places, like the Salesforce mobile
app, a custom page, or even an email template. That’s all possible because of the API name.
Question 5

Draw the control data access flow-chart in Organization-Wide Sharing Defaults

Answer
Question 6

Explain the following terms in Salesforce

(i) User (ii) User license (iii) Profile (iv) Role (v) Permission set (vi) Permission
set groups

Answer

A user is anyone who logs in to Salesforce. Users are employees at your company, such as sales
reps, managers, and IT specialists, who need access to the company's records.

There are also external users, such as end customers, prospects, and partners who access
Experience Cloud sites. Each user has both a username and an email address. The username must
be formatted like an email address and must be unique across Salesforce. It can be the user’s
email address, so long as it’s unique. Each user account contains at least the following.
Username, Email Address, User's First Name (optional), User's Last Name, Alias, Nickname,
License, Profile, Role (optional)

User Licenses

A user license determines which features the user can access in Salesforce. For example, you can
allow users access to standard Salesforce features and Chatter with the standard Salesforce
license. But if you want to grant a user access to only some features in Salesforce, you have a
host of licenses to choose from. For example, if you have to grant a user access to Chatter
without allowing them to see any data in Salesforce, you can give them a Chatter Free license.

Profile

Each user has one profile that defines default settings. It’s possible to use profiles to grant
permissions and access to users. However, It is recommended to grant users the Minimum
Access - Salesforce profile, and then use permission sets and permission set groups to grant users
the permissions they require.

Roles

Roles determine what users can see in Salesforce based on where they’re located in the role
hierarchy. Users at the top of the hierarchy can see all the data owned by users below them.
Users at lower levels can't see data owned by users above them, or in other branches, unless
sharing rules grant them access.

Roles are optional but each user can have only one. If there is an org with many users, you may
find it easier to assign roles when adding users. However, you can set up a role hierarchy and
assign roles to users at any time. Roles are only available in Professional, Enterprise, Unlimited,
Performance, and Developer editions of Salesforce.
Permission Sets

Permission sets are collections of settings and permissions that determine what users can do in
Salesforce. Use permission sets to grant access to objects, fields, tabs, and other features and
extend users’ access without changing their profiles. They allow to reuse smaller permission set
building blocks, you can avoid creating dozens or even hundreds of profiles for each user and job
function.

Permission Set Groups

Permission set groups are exactly what they sound like—groups of permission sets. Use
permission set groups to bundle permission sets together based on a job persona or role. You can
then assign a permission set group to users, rather than keep track of multiple permission set
assignments.
Question 7

Describe about the objects and fields in Salesforce

Answer

Objects are a crucial element in Salesforce as they provide a structure for storing data and are
incorporated into the interface, allowing users to interact with the data. It is similar to a database
table. Object fields are similar in concept to a database column while records are similar in
concept to a database row.

Standard objects

Standard objects are provided by Salesforce as a basic CRM structure. These include account,
contact, opportunity, lead, campaign and so on. These are the tables that contain the records in
any standard tabs, such as Accounts, Contacts, Opportunities, Leads, Campaigns, and so on.

Custom objects

In addition to standard objects, Salesforce allows you to create custom objects to store data
specific to your organization, which is not doable through standard objects. For example,
creating a custom object to store employee checking, saving account details to process biweekly
salary, and keeping employee account details private so that only the system administrator and
employee (who created the record) can access it. You can create reports and dashboards based on
the record data in your custom object. Custom objects are usually identified by a __c
suffix.Standard fields

Salesforce fields are simple but vital to the world of Salesforce configuration. Each field holds
separate pieces of data, allowing you to track and report on information related to your standard
or custom objects.

Standard fields

Standard fields are predefined fields that are included as standard within the Salesforce
application. Standard fields cannot be deleted, but non-required standard fields can be removed
from page layouts whenever needed. Both standard and custom objects contain a few common
standard fields, for example, Name, CreateDate, LastModifiedDate, and Owner fields.

Custom fields

Custom fields are unique to your business needs and not only can they be added and amended,
but also deleted. Creating custom fields allows you to store the information that is necessary for
your organization. Both standard and custom fields can be customized to include custom help
text, which helps users understand how to use the fields. Custom fields are usually identified by a
__c suffix.
Question 8

Explain a Lightning App with a neat diagram.

Answer

An app is a collection of items that work together to serve a particular function. In Lightning
Experience, Lightning apps give your users access to sets of objects, tabs, and other items all in
one convenient bundle in the navigation bar.

Lightning apps let you brand your apps with a custom color and logo. You can even include a
utility bar and Lightning page tabs in your Lightning app. Members of your org can work more
efficiently by easily switching between apps. Accounts, events, and organizations for sales
representatives. Reports and dashboards for sales managers. Each Lightning app has a navigation
bar at the top of the page, letting users to find what they need using item names for easy
recognition, complete actions and access recent records and lists with a single click, personalize
the navigation bar to suit the unique way they work.

Lightning app contains the following things:

(ii) Most standard objects, including Home, the main Chatter feed, Groups, and
People
(iii) Your org’s custom objects
(iv) Visualforce tabs
(v) Lightning component tabs
(vi) Canvas apps via Visualforce tabs
(vii) Web tabs
 The app name (1) displays on the left side of the navigation bar and custom colors and
branding (2) make each app unique and easy to identify.
 Your users can access other items and apps by clicking the App Launcher icon (3).
 Your users can create records and access recent records and lists directly from the
navigation bar (4) for items like Opportunities.
Question 9

Explain the aspects of data security in Salesforce

Answer

As organizations leverage the power of Salesforce to manage their customer relationships and
business operations, ensuring the confidentiality and integrity of the data stored within the
platform becomes paramount. There are four essential aspects of data security in Salesforce:
Role-based Access Control, Data Sharing Settings, Field-level Security, and Record Ownership
and Sharing Rules.

Role-based Access Control

Role-based Access Control (RBAC) is a fundamental concept in data security that governs who
can access what information within Salesforce. RBAC assigns roles to users in accordance with
their organizational responsibilities. These roles, often reflecting the hierarchical structure of the
company, dictate the level of access users have to different data and functionalities.

Users are given the proper access and permissions based on their responsibilities, thanks to
RBAC. For instance, sales representatives might access customer data relevant to their deals,
while managers could have broader access to monitor their team’s activities. This hierarchical
approach safeguards sensitive information and promotes efficient collaboration by giving users
access to perform their tasks effectively.

Data Sharing Settings

Salesforce provides a range of data-sharing settings that allow administrators to control how data
is shared among users. These settings determine whether data is private, shared on a read-only
basis, or editable by different users and groups. Collaboration and teamwork are made possible
by the adaptability of data-sharing settings, which guarantees that private information is only
accessible to those who have a genuine need to know.

By configuring sharing settings, organizations can balance data security and operational
efficiency. This is particularly crucial when dealing with cross-functional teams that require
access to specific data to fulfill their responsibilities without compromising the integrity of other
data sets.

Field-level Security
It allows administrators to control which fields within records are visible or editable for different
users. This level of control is valuable in scenarios where records contain a mix of sensitive and
non-sensitive information.

For instance, a contact record might contain personal phone numbers and email addresses that
should be accessible only to authorized personnel. Through field-level security, administrators
can restrict access to these fields, ensuring that only those with the appropriate permissions can
view or modify such sensitive data.

Record Ownership and Sharing Rules

Every record within Salesforce is associated with an owner. This owner is typically the user who
created the record or has been assigned ownership subsequently. Record Ownership is a
fundamental concept that forms the basis of data security.

On the other hand, Sharing Rules allow organizations to extend or restrict access to records
beyond the scope of role-based access and sharing settings. Sharing Rules can be defined to
automatically grant access to certain documents based on criteria, ensuring that relevant
stakeholders have access to pertinent information while maintaining security.
Question 10

Describe the essential ways to enhance security in Salesforce

Answer

Security Best Practices

As organizations increasingly rely on Salesforce to streamline their data collection workflows,

maintaining robust security measures is crucial to safeguard sensitive information.

1. Data Encryption and Secure Transmission

Data encryption is a cornerstone of modern data security practices. When entering Salesforce,
data must be encrypted both in transit and at rest. By encrypting the data, you may make sure
that even in the case of unauthorized access, it will be impossible to read it without the required
decryption keys. In transit, employing secure communication protocols like HTTPS (Hypertext
Transfer Protocol Secure) guarantees that data exchanged between users’ devices and Salesforce
servers is encrypted, preventing potential eavesdropping and data interception.

2. Role-based Access Control and User Authentication

Leveraging Role-based Access Control (RBAC) within Salesforce data collection workflows is
pivotal. Organizations can control who can access and manipulate collected data by assigning
users to specific roles based on their responsibilities. By limiting access to only those who need
it, the danger of unauthorized access and data breaches is reduced. Implementing strong user
authentication practices further fortifies security. An additional layer of security is provided by
multi-factor authentication (MFA), which asks users for many forms of identification before
granting access to Salesforce.

3. Regular Security Audits and Monitoring

Continuous monitoring and regular security audits are indispensable components of a

comprehensive security strategy. Organizations should regularly review user access, permissions,
and data-sharing settings to identify anomalies or unauthorized access attempts. Moreover,
Salesforce provides tools and features that enable administrators to monitor user activity, track
changes to data, and set up alerts for suspicious behaviour. Organizations may avoid data
breaches and guarantee the continuous integrity of their data-gathering operations by proactively
identifying and addressing any security vulnerabilities.
4. Shield Platform Encryption

Shield Platform Encryption is a robust solution provided by Salesforce to safeguard sensitive

data stored in the platform. It employs advanced encryption techniques to render data unreadable
without the corresponding decryption keys, even those with authorized access. The encrypted
data cannot be decoded without the encryption keys, even if unauthorized persons get to access
it.

5. Salesforce Identity

Salesforce Identity is a comprehensive solution that enhances user management, authentication,

and access control within and across integrated applications. It enables businesses to create a
central location for maintaining user IDs, ensuring that only those with permission can access
important information and features. Single Sign-On (SSO) functionality is one of Salesforce
Identity’s distinguishing features. A single set of credentials can be used by users to log into
various applications and services thanks to SSO. This lessens the requirement for users to
remember and maintain many passwords, decreasing the possibility of using reused or weak
passwords.
Question 11

Describe the Salesforce Role Hierarchy with an example in Tree View.

Answer

The Salesforce Role Hierarchy allows you to define and manage data visibility and access for
users within your organization. Based on their role, you can control who can view or edit certain
records, such as accounts, leads, opportunities, and other objects. Role Hierarchies give access to
users higher in the hierarchy to all records owned by users below them in the hierarchy. Each
role in the hierarchy represents the level of data access that users in that role should have.

Benefits

Access Control: A role hierarchy allows your company to control access to data and
functionality within Salesforce. You can grant each role specific permissions, which cascade
down to the users in the roles beneath it. You can ensure that individuals can only access
authorized data and perform authorized actions.

Reporting: The role hierarchy also allows you to report based on roles. You can see how many
opportunities, leads, or cases each role in the hierarchy is working. This information can help
management make informed decisions about resource allocation and identify areas for
improvement.

Sales Management: Sales teams can use the role hierarchy to manage their pipeline. Each role
in the hierarchy can be responsible for a different stage of the sales process, and managers can
track progress and identify bottlenecks.

Territory Management: You can use the role hierarchy to manage territories too. You can
assign each role in the hierarchy to a different region and use the hierarchy to ensure that sales
reps only work on accounts within their assigned territories.
Tree View – Role Hierarchy of a typical company