Cloud Computing Basics

What is Cloud?
The term Cloud refers to a Network or Internet. Cloud can provide services over network i.e. on public
networks or on private networks i.e. WAN, LAN.
Applications such as e-mail, web conferencing, customer relationship management (CRM), all run in cloud.

What is Cloud Computing?

It is defined as a mode for enabling convenient, on-demand network access to a shared pool of configurable
and reliable computing resources like networks, servers, storage, application, services etc. that can be
manipulated, configured and accessed remotely.
Cloud computing offers platform independency, as the software is not required to be installed locally on the
PC. Hence, the Cloud Computing is making our business applications, mobile and collaborative.

Cloud Computing Architecture

The Cloud Computing architecture comprises of many cloud components, each of them are loosely coupled
We can broadly divide the cloud architecture into two parts:

Front End
Front End refers to the client part of cloud computing system. It consist of interfaces and applications that are
required to access the cloud computing platforms. E.g. Web Browser

Back End
Back End refers to the cloud itself. It consist of all the resources required to provide cloud computing services.
It comprises of huge data storage, virtual machines, security mechanism, services, deployment models, servers
etc.

Deployment Models of Cloud

Deployment models define the type of access to the cloud, i.e., how the cloud is located?
There are 4 types of deployment models of cloud namely:
Public Cloud Model
The Public Cloud Model allows systems and services to be easily accessible to general public. E.g. Google
AppEngine, Amazon EC2.

Private Cloud Model

Private cloud allows system and service to be accessible within an organization. The private is operated only
within single organization, However it is managed internally or third_party

Community Cloud Model

The Community Cloud allows system and services to be accessible by group of organizations. It shares the
infrastructure between several organizations from a specific community. It may be managed internally or by
the third-party.

Hybrid Cloud Model

Hybrid Cloud Model is a mixture of public and private cloud. Non critical activities are performed using public
cloud while critical activities are performed using private cloud.

Cloud Service Models:

There are basically 3 types of cloud service models:
Infrastructure as a Service (laaS)
laaS provides access to fundamental resources such as physical machines, virtual machines, storage etc.

All of the above resources are made available to end user via server virtualization. Moreover, these
resources are accessed by the customers as if they own them.
Characteristics:
 Virtual machines with pre-installed software.
 Virtual machines with pre-installed Operating Systems such as windows, Linux, and Solaris.
 On demand availability of resources.
 The computing resources can be easily scaled up and down.

Platform as a Service (PaaS)

PaaS offers the run time environment for applications. It also offers development & deployment tools,
required to develop applications. PaaS has a feature of point-and-click tools that enables non-developers to
create web applications.
Force.com platform is an example of PaaS in salesforce.

Characteristics
 PaaS offers browser based development environment. It allows the developer to create database and edit
the application code either via Application Programming Interface or point-and-click tools.
 PaaS provides built-in security, scalability, and web service interfaces,
 PaaS also provides web services interfaces that allow us to connect the applications outside the
platform.

Software as a Service (SaaS)

Software as a Service (SaaS) makes the software available over the internet. This model allows to provide
software applications as a service to the end users. It refers to a software that is deployed on a hosted service
and is accessible via internet. There are several SaaS applications such as Billing and Invoicing System,
Customer Relationship Management (CRM) applications, Help Desk Applications, Human Resource (HR)
Solutions.
Characteristics
• Available on demand
• The Software are maintained by the vendor rather than where they are running and hence cost effective.
• The license to the software may be subscription based or usage based. And it is billed on recurring basis.
• Scaled up or down on demand.
• Automatically upgraded and updated
• SaaS offers share data model.
• All users are running on same version of the software.
Different types of Developer Edition and sandbox environment:
1. Full copy sandbox: When you copy data as well as customization
2. Partial copy sandbox: not all the data get copied only sample data gets copied.
3. Developer sandbox: No data will get copy. only customization will get copied.
4. Developer Pro sandbox: get more data storage as compared to developer sand box. only
customization will get copied, no data get copied from prod env.
5. Partner Developer edition: in developer edition we get 2 user and store only 5MB data and partner
dev ed is we get 20 user and can store 250 mb data.
 Dev Sandbox(first choice)

Dev Pro Sandbox (if need to

store more data)

Sandbox(if you need

existing data and Partial copy Sandbox( if
custamization) required only sample data)

Developer
environment
Full Copy Sandbox (if required
complete data of prod.env)
Developer Edition(2
uses,5MB data)
Partner dev. Editition (if need
more user and data)

There are three types of org(user licences)

1. professional ($75/user/month)
2. Enterprise ($150/user/month)
3. Unlimited ($300/user/month)

Imp Note: first user of org is by- default system administrator. (which can do anything and everything in the
org). can add another user to this org.

Salesforce has two UI, older one is classic, and new one is lighting.
Classic UI not that much interactive , looks like simple HTML page, and when we click from one tab to another
it take time to reload.
Lighting UI is faster than Classic, it is not taking time to reload, it is lighting fast.

Tabs: tabs are nothing but an UI component which provide you a functionality.
App: The app in salesforce is nothing but name (of app), logo and setup tabs

To setup your Org: setup---home---in Quick find box---company information---

Virtualization & Benefits of Cloud Computing

The Multitenant architecture offers virtual isolation among the multiple tenants. Here multiple
clients share the same infrastructure under different logical ids according to their requirement.
Hence, the organizations can use and customize their application as though they each have their
instances running.
Topic: Data Modelling
Data Modeling in Salesforce refers to the process of defining how data is structured, stored, and
organized within the Salesforce platform. It involves creating a blueprint for managing and organizing
data to ensure efficient data handling, retrieval, and reporting. A well-designed data model is crucial
for making Salesforce applications scalable, efficient, and aligned with business processes.

Key Components of Data Modeling in Salesforce

1. Objects
o Standard Objects: Pre-built objects provided by Salesforce, such as Account,
Contact, Opportunity, Lead, and Case.
o Custom Objects: User-defined objects created to capture data specific to a business's
needs. For example, Project, Invoice, or Employee.
2. Fields
o Standard Fields: Pre-defined fields included in standard objects (e.g., Name, Created
Date, Owner).
o Custom Fields: User-created fields to capture additional data. You can choose from
different data types like Text, Number, Date, Checkbox, Picklist, etc.
3. Relationships
o Lookup Relationship: Creates a loose connection between two objects. For example,
linking a Contact to an Account.
o Master-Detail Relationship: A stronger connection where the child object is tightly
controlled by the parent object. Deleting the parent record also deletes the child records.
For example, Opportunity line items associated with a single Opportunity.
o Many-to-Many Relationship: Achieved using a junction object. For instance,
associating multiple Contacts with multiple Campaigns.
4. Schema Builder
o A visual tool in Salesforce that allows you to see and manage your data model. You can
create, modify, and understand object relationships easily through a drag-and-drop
interface.
5. Object Relationships
o Hierarchical Relationship: Special type of lookup relationship available only for the
User object, used to create a hierarchy within the users (e.g., reporting structure).
o Self-Relationship: An object can have a lookup relationship to itself. For example, a
Contact linked to another Contact.
6. Data Types
o Salesforce supports various field types, such as:
 Text: Holds string values.
 Number: Holds numerical values.
 Currency: Holds financial values.
 Date/Time: Captures date and time.
 Picklist: Offers predefined options for selection.
  Formula: Computes values based on other fields.
7. Validation Rules
o These are used to ensure data integrity by setting conditions that must be met before
data is saved. For instance, requiring that an Opportunity Amount must be greater than
zero.
8. Roll-Up Summary Fields
o Available only on master-detail relationships, these fields allow you to perform
calculations (sum, min, max, count) on related records. For example, summing up all
line items related to an Opportunity.
9. Record Types
o Allow different business processes, picklist values, and page layouts to be displayed
based on the record type. For instance, different Sales Processes for B2B and B2C
sales.
10. Page Layouts and Lightning Record Pages
o These control the layout of the data entry forms and detail views of records. This is
where you define which fields, related lists, and buttons are visible for different users.

Apps in Salesforce

 Definition: Collections of tabs, objects, and functionalities grouped together to serve a specific
business purpose.
 Examples:
o Sales (for managing sales processes)
o Service (for customer support)
o Marketing (for campaign management)
o Custom Apps (user-created for specific needs)

Tabs in Salesforce

 Definition: User interface elements that provide access to different objects and features within
an app.
 Types of Tabs:
o Standard Tabs: Access to built-in objects like Accounts, Contacts, Opportunities.
o Custom Tabs: Access to custom objects, Visualforce pages, or web content.
o Web Tabs: Links to external websites.
TOPIC:Relationship In salesforce
1. one to many
a)Lookup Relationship
b)Master-Detail Relationship
2. many to many
3. Hierarchical Relationship
1. Definitions of Salesforce Relationships
a) Lookup Relationship
 Definition: A loosely coupled relationship between two objects. Records in one object can be
linked to records in another object, but they do not depend on each other for deletion or
ownership.
 Maximum lookup created in an object is 40
 we cant create rollup summary field in lookup relationship.
 Use Case Example: An Account can have a Lookup Relationship with Contact. This means a
Contact can exist independently of the Account.

Hands-on Practice (Salesforce Developer Org)

a) Create Lookup Relationship

1. Objects: Transport (Custom Object) and Employee (Custom Object).

2. Steps:
o Go to Object Manager in Salesforce.
o Create a new custom object named Transport.
o Create another custom object named Employee.

(object manager— Employee -- Fields & Relationships—New—select data type(Lookup

Relationship)— Select the other object to which this object is related.( Transport)—next—
next—next—save)

Check on you UI, when you create employee it will ask for transport field. But it is not a
mandatory field, as it is loosely coupled. We can have employee without transport field.
b) Master-Detail Relationship

 Definition: A tightly coupled relationship where one object (Detail) is entirely dependent on
another (Master). If the master record is deleted, all its related detail records are also deleted.
 Use Case Example: Invoice Line Items can be linked to an Invoice object through a
Master-Detail Relationship. If the Invoice is deleted, all its associated Invoice Line Items
are also deleted.
 Relationship always created on child object.
 Only 2 master detail can created in an object.
 If two objects hold MD relationship, we can create rollup summary field.
 Roll up summary field always created on parent field.
(Roll up summary: A read-only field that displays the sum, minimum, or maximum value of a
field in a related list or the record count of all records listed in a related list.)

Hands-on Practice (Salesforce Developer Org)

1. Objects: Department (Master) and EmployeeMD (Detail).

2. Steps:
o Create custom objects Department and Employee
o On the EmployeeMD object, create a new field of type Master-Detail Relationship that
links to Department.

(object manager—EmployeeMD-- Fields & Relationships—New—select data

type(Master-Detail Relationship)— Select the other object to which this object is
related.(department)—next—next—next—save)

Check on UI if you create employee it will ask for department while creating
employeeMD and it is mandatory field as it is tightly coupled. You cannot create
employee without department
If you go to the parent(master) tab(department), in related tab all the child details shown

If you open child object the associate parent details shown. No need to go to the related tab.

Roll up summary:
object manager—Department(parent object)-- Fields & Relationships—New—select data
type(Roll up summary)—next-- Select the other object to which this object is related.—next—
field label—make it visible—next—next—save

Check on UI you can see the count of employee in department tab

 Outcome: Deleting an Department will delete all associated Employee.

c) Many-to-Many Relationship (using Junction Objects)

 Definition: Allows a many-to-many relationship between two objects using a third object
called a Junction Object.
 Use Case Example: Students and Courses can be linked using a Course Enrollment
junction object. This allows a single Student to enroll in multiple Courses and vice versa.

Hands-on Practice (Salesforce Developer Org)

Create a Many-to-Many Relationship

1. Objects: Course and Student with a Junction Object Course Enrollment.

2. Steps:
o Create custom objects Course and Student.
o Create a new custom object Course Enrollment.
o Create two Master-Detail Relationships: one linking Course Enrollment to Course
and another to Student.

object manager— Course Enrollment (junction object)-- Fields & Relationships—New—

select data type(Master-Detail Relationships)—next-- Select the other object to which this
object is related.—next—field label—make it visible—next—next—save

We have created third junction object(course enrolment) to achieve many to many relationship
between course and student.
But when you go to related tab of course and student it should show to which object it has Many to
many relationship, means in related tab of course, students visible and vice vera.
But in both course and student junction object name(course enrolment) is visible.

To achieve our requiremt, edit junction object, bcoz all relation we done there.

Edit object-- Fields & Relationships---edit course master detail field-- change related field labal to
student—save

Do the same for student master detail field and save.

3. Outcome: You can now assign multiple students to multiple courses.

d) Hierarchical Relationship

 Definition: A special type of Lookup Relationship, specifically for the User object, used to
create a hierarchy among users (e.g., manager-subordinate relationships).
 Use Case Example: An organization’s structure where a User can be assigned a manager,
creating a hierarchy.
4. Considerations and Limitations

Relationship Type Considerations/Limitations

- Allows optional linking.
Lookup Relationship - No impact on record ownership.
- Can convert to Master-Detail if certain conditions are met.
- Child records inherit the parent's sharing settings.
Master-Detail - Deleting the parent deletes all child records.
- Roll-Up Summary fields available.
- Requires a Junction Object.
Many-to-Many - Complex sharing settings.
- Can’t have Roll-Up Summary fields on junction objects directly.
- Only available for User object.
Hierarchical - Useful for representing organizational hierarchies.
- Cannot be used for standard objects like Accounts.

5. Roll-Up Summary Fields (Bonus)

 Definition: Roll-Up Summary Fields allow aggregation of data (SUM, MIN, MAX, COUNT)
from child records in a Master-Detail relationship to the parent record.
 Example: A Project object can have a Roll-Up Summary Field that shows the total
Estimated Hours from all related Tasks.

6. Hierarchical Relationship (Bonus)

 Use Case: You can set up a manager hierarchy for user records in Salesforce. For example,
the CEO is at the top, with managers and employees reporting to them. This is useful for
approval processes and reporting.

Topic: User Management

User Management in Salesforce Admin involves handling users' access to the Salesforce platform. It
include creating users, managing permissions, ensuring data security, and optimizing user experience.

Key Components of Salesforce User Management

1. Users
 Each person who needs access to Salesforce must have a user account.
 A User Account includes information like username, email, profile, role, license type,
etc.
 Users can be created, deactivated, or frozen based on their status in the organization.
2. Profiles
 Profiles control what users can do within Salesforce (object permissions, field
permissions, tab settings, etc.).
 Every user is assigned one profile, which dictates their baseline access.
 Profiles can be Standard (predefined by Salesforce) or Custom (tailored to your
organization’s needs).
3. Roles
 Roles control what users can see in terms of data (i.e., record-level security).
  A Role Hierarchy allows data to roll up from users to their managers, providing
visibility to higher-level roles.
 Roles are optional but useful for organizations needing structured data visibility.
4. Permission Sets
 Permission Sets provide additional permissions to users without changing their profile.
 They are great for granting specific permissions temporarily or adding access to
individual users beyond their profiles.
 Permission Set Groups can bundle multiple permission sets for easier management.
5. Licenses
 User Licenses define the baseline features available to a user (like Salesforce,
Salesforce Platform, Chatter Free, etc.).
 Each user needs an available license to be activated in Salesforce.
6. Login Access
 Salesforce Admins can monitor and manage user logins to ensure security.
 Login History shows details of user access, which is helpful for troubleshooting login
issues.
 Login Hours and IP Address Ranges can be set to control when and where users can
log in.
7. Delegated Administration
 Allows Salesforce Admins to assign specific admin privileges to non-admin users.
 Helps decentralize user management by allowing specific users to manage subsets of
users or data.

Hands-on Practice (Salesforce Developer Org)

1. Creating a New User

 Setup ➔ Users ➔ Users ➔ Click on “New Use
Fill in Required Fields:
First Name, Last Name: The user's name.
Email: The user's work email (used as their default communication method).
Username: Must be unique across all Salesforce orgs (often the same as their email).
Role: Assign based on data visibility needs.
Profile: Assign based on functionality and permissions.
License: Choose the appropriate license type (e.g., Salesforce, Chatter, etc.).
Click “Save”.

Go to email inbox and verify account.

When I login as spandan Badekar im not able to see any application of my account like
institute app, recruitment app etc.
In standard profile we cannot have access to use custom object and apps. So we as per our
requirement we can go for custom profile. So that we give permission to see app and edit
fields.

Go to profile (in sarika account)---standard user—clone (or u can create from scratch)—give
the profile name—save
Go to user—click Spandan Badekar—edit –select team lead—save

Now you edit the give permission on fields to CRUD operation

_______________________________________________________________________
To switch from one account to another you need not to logout from one and login to another,
You can provide the button to login from profile to another

Go to profile(Spandan)—settings--Grant Account Login Access—save

Go to sarika account—user—you can see log in button to log in spandan profile directly

In salesforce you cannot delete a user , we can only freeze or deactivate

the user:

when account is freeze you cannot log in to org but u will get the mails from salesforce, but if
ur info like email is used in any automation tool anywhere that still be in used.

When the company got the replacement of any employee then they will deactivate you. And
they will get free licences. And profile is associate with the licences

Interview ques: What is the difference between freeze and decativate