Admin Interview Questions:

1. What is CRM?
CRM, or Customer Relationship Management, is a way for businesses to manage
interactions with their customers. It uses software to store information about
customers, like their contact details and buying history, to improve how businesses
communicate with and serve them.

2. What is cloud Computing?

Cloud computing is like renting computing power and storage space on the internet
instead of buying and maintaining your own physical servers and infrastructure. It
allows you to access and use software, data storage, and computing resources over
the internet from anywhere, without having to worry about managing the underlying
hardware. Essentially, it's like using services and resources that are stored and
operated remotely, in the "cloud," rather than on your local computer or network.

3. What service model salesforce uses?

• Salesforce primarily utilizes the Software-as-a-Service (SaaS) model in cloud
computing. As a SaaS provider, Salesforce delivers its applications over the
internet, allowing users to access and use them via a web browser without
needing to install or maintain software on their own computers. This model
enables customers to access Salesforce's CRM platform and related services on a
subscription basis, with updates and maintenance handled by Salesforce.
• Salesforce also offers a Platform-as-a-Service (PaaS) model through its Salesforce
Platform. With PaaS, Salesforce provides a platform that allows developers to
build, customize, and deploy applications without having to worry about
managing the underlying infrastructure. Developers can use Salesforce's tools,
APIs, and services to create custom applications tailored to their specific business
needs, leveraging the scalability and reliability of the Salesforce infrastructure.
This allows businesses to focus on developing and innovating their applications
without the burden of managing hardware or software infrastructure.

4. What benefits are there using salesforce with utilization of cloud computing.
Salesforce's utilization of cloud computing offers several benefits:
• Scalability: Easily adjust resources based on needs.
• Accessibility: Accessible from anywhere with an internet connection.
• Cost-effectiveness: Pay-as-you-go model, avoiding upfront infrastructure costs.
• Reliability and Performance: High reliability, performance, and security.
• Updates and Maintenance: Salesforce manages updates and maintenance.
• Integration Capabilities: Seamlessly integrate with other systems.
• Customization and Flexibility: Customize to fit specific business needs.
 • Security: Cloud providers invest in robust security measures, often exceeding
what
individual organizations can achieve on their own.

Overall, Salesforce's utilization of cloud computing enables businesses to focus on

their core activities while leveraging a powerful, flexible, and scalable platform
for managing customer relationships and driving business growth.

5. What is Salesforce?
Salesforce is a company that provides software to help businesses manage their
relationships with customers. It offers tools for sales, marketing, and customer
service that are accessed over the internet, rather than being installed on individual
computers. This cloud-based approach makes it easier for businesses to organize
their customer information, communicate with clients, and track sales activities.

CRM Product of Salesforce.com

Co-founded by Marc Benoiff
On – Cloud & On – Demand
Standard Applications & Customizations
Force.com Platform
Easily Integrated To other platform / services / CRMs

6. Why salesforce consider as #1 CRM?

Salesforce is considered the top CRM (Customer Relationship Management) platform
for several reasons:

• Comprehensive Features: Salesforce offers a wide range of features and

functionalities that cater to various aspects of CRM, including sales, marketing,
customer service, and analytics. Its all-in-one platform allows businesses to
manage their customer interactions effectively across different channels.

• Scalability: Salesforce is highly scalable, meaning it can adapt to the needs of

businesses of all sizes, from startups to large enterprises. It can accommodate
growth without compromising performance or requiring significant changes to
infrastructure.

• Customization: Salesforce provides extensive customization options, allowing

businesses to tailor the platform to their specific requirements. This flexibility
enables companies to create personalized flows, reports, and applications that
align with their unique business processes.

• Integration Capabilities: Salesforce offers robust integration capabilities, allowing

businesses to connect their Salesforce instance with other applications and
 systems seamlessly. This enables data sharing and automation of processes
across different departments and platforms.

• Community and Ecosystem: Salesforce has a vibrant community of users,

developers, and partners who contribute to its ecosystem. This community-
driven approach fosters innovation, collaboration, and knowledge sharing,
enriching the Salesforce experience for users.

• Constant Innovation: Salesforce consistently invests in research and

development to innovate and enhance its platform. It regularly releases updates
and new features to address evolving business needs and technological
advancements, ensuring that its customers stay ahead in the competitive
landscape.

• Customer Success: Salesforce prioritizes customer success and satisfaction. It

provides comprehensive support, training resources, and a dedicated customer
success team to help businesses maximize the value they derive from the
platform.

These factors contribute to Salesforce's reputation as the top CRM platform, trusted
by businesses worldwide to drive growth, improve customer relationships, and
achieve their business objectives.

7. Why Salesforce So Popular and how it is Different from Traditional CRMs?

Salesforce's popularity can be attributed to several factors that set it apart from
traditional CRMs:

• Cloud-Based Model:
Salesforce: It is a cloud-based CRM, meaning it operates entirely on the internet.
Users can access Salesforce from any device with an internet connection,
eliminating the need for on-premises servers and infrastructure.
Traditional CRM: Many traditional CRM solutions are on-premises software,
which requires organizations to invest in and maintain their own servers. This can
lead to higher upfront costs and increased complexity.

• Scalability and Flexibility:

Salesforce: Offers scalability, allowing businesses to scale up or down based on
their needs. It provides a flexible platform with customizable features and
configurations.
Traditional CRM: Scaling traditional CRM solutions may involve significant
investments in hardware and software upgrades. Customization options may be
limited.
• Rapid Updates and Innovations:
Salesforce: Releases regular updates and innovations without requiring
customers to manually install patches or updates. This ensures that users always
have access to the latest features and improvements.
Traditional CRM: Updating traditional CRM software can be a more manual and
time-consuming process, potentially leading to delays in adopting new
functionalities.

• AppExchange Marketplace:
Salesforce: Features the AppExchange marketplace, offering a vast ecosystem of
third-party applications and integrations that seamlessly extend the platform's
capabilities.
Traditional CRM: The availability of third-party integrations may be more limited,
and integrating additional functionalities could be more challenging.

• Mobile Accessibility:
Salesforce: Provides robust mobile accessibility, allowing users to access CRM
data and features on the go through dedicated mobile apps.
Traditional CRM: Mobile access in traditional CRM systems might be limited or
require additional configurations.

• User-Friendly Interface:
Salesforce: Known for its user-friendly interface and intuitive design, making it
easier for users to adapt to the platform without extensive training.
Traditional CRM: Some traditional CRM systems may have interfaces that are
perceived as less user-friendly, potentially requiring more training for users.

• Comprehensive Platform:
Salesforce: Offers a comprehensive platform that goes beyond traditional CRM,
including capabilities for marketing automation, analytics, application
development, and more.
Traditional CRM: Some traditional CRM solutions may focus primarily on core
CRM functionalities without the extensive range of additional features.

• Strong Community and Support:

Salesforce: Has a large and active community of users, developers, and partners.
The availability of online resources, forums, and community support contributes
to a collaborative ecosystem.
Traditional CRM: Support and community engagement may vary among different
vendors, and some traditional CRM solutions might have a smaller user
community.
 Salesforce's success is also attributed to its early adoption of the Software as a
Service (SaaS) model, innovation in cloud technology, and a commitment to
customer success. These factors collectively make Salesforce a popular and widely
adopted CRM platform in the business world.

8. What different salesforce editions are there and purpose of use?

Starter Suite: Designed for small businesses with basic CRM needs.

Professional Edition: Offers core CRM functionality for small to medium-sized

businesses.

Enterprise Edition: Provides more advanced features and customization options for
larger businesses.

Unlimited Edition: Offers maximum flexibility and customization capabilities for large
enterprises with complex requirements.

Developer Edition: Free edition primarily used by developers for building and testing
Salesforce applications.

These editions vary in terms of features, pricing, and scalability, allowing businesses
to choose the one that best fits their size and requirements.

9. Explain salesforce Architecture

Salesforce architecture is built on a multi-tenant cloud computing model, where

multiple customers (tenants) share the same infrastructure and resources while
maintaining isolation and security. Here's an overview of Salesforce architecture:

Multi-Tenant Architecture: Salesforce's multi-tenant architecture allows multiple

organizations (tenants) to use the same instance of the application while keeping
their data and configurations separate. This approach maximizes resource utilization
and scalability, as resources are shared among multiple customers.

Metadata-Driven Platform: Salesforce is a metadata-driven platform, meaning that

most aspects of the application, such as custom objects, fields, workflows, and user
interfaces, are defined and configured using metadata rather than code. This allows
for greater flexibility and customization without requiring extensive programming.

Layers of Infrastructure: Salesforce architecture consists of several layers of

infrastructure, including:
 • Presentation Layer: The user interface accessed through web browsers or mobile
devices.
• Application Layer: This layer contains the business logic and functionality of the
Salesforce platform, including workflow automation, data processing, and
integration services.
• Data Layer: Salesforce uses a multi-tenant database architecture to store
customer data securely. Each organization's data is logically isolated and accessed
using unique identifiers.
• Integration Layer: Salesforce provides APIs (Application Programming Interfaces)
and tools for integrating with external systems, allowing for seamless data
exchange and interoperability.

Scalability and Reliability: Salesforce's architecture is designed for scalability and

reliability, with built-in redundancy, failover mechanisms, and elastic scaling to
accommodate fluctuating workloads and ensure high availability.

Security Model: Salesforce implements a robust security model to protect customer

data and ensure compliance with industry regulations. This includes role-based
access controls, data encryption, audit trails, and regular security updates.

Customization and Extensibility: Salesforce architecture supports extensive

customization and extensibility through declarative tools (point-and-click
configuration) and programmatic development (Apex code, Visualforce pages,
Lightning Web Components). This allows organizations to tailor the platform to their
specific business requirements.

AppExchange: Salesforce's architecture includes the AppExchange marketplace,

where third-party developers can publish and distribute applications and
components that extend the functionality of the Salesforce platform. This ecosystem
enhances the platform's capabilities and offers customers a wide range of pre-built
solutions to choose from.

Overall, Salesforce architecture provides a flexible, scalable, and secure platform for
building and deploying CRM solutions and business applications in the cloud.

10. Explain Sales process in salesforce, how you will be going to implement or track the
details or process for some of the product.

Product Details: Salesforce allows you to maintain detailed information about your
products or services in the product catalog. You can track product names,
descriptions, pricing, and other relevant details.

Target Market: Salesforce enables you to segment your target market using various
criteria, such as industry, geographic location, company size, or specific
demographics. You can create lists or reports to analyze and target specific segments
effectively.

Sales Team: Salesforce provides tools for managing your sales team, including user
profiles, roles, and permissions. You can assign territories, set up sales hierarchies,
and track individual performance using Salesforce's built-in reporting capabilities.

Campaigns: Salesforce allows you to create and manage marketing campaigns to

generate leads and opportunities. You can track campaign performance, analyze ROI,
and attribute revenue to specific campaigns using Salesforce's campaign
management features.

Prospects: In Salesforce, prospects are potential customers or organizations that

have shown interest in your products or services but have not yet been qualified as
leads. You can track prospect interactions and activities to nurture them into
qualified leads.

Leads: Leads are individuals or companies that have expressed interest in your
offerings. Salesforce allows you to capture lead information, qualify leads based on
predefined criteria, and convert them into accounts, contacts, and opportunities
when they become qualified prospects.

Account / Contact / Opportunities: Salesforce organizes customer information into

three main objects: accounts, contacts, and opportunities. Accounts represent
companies or organizations, contacts represent individuals associated with those
companies, and opportunities represent potential deals or sales opportunities.

Quotes: Salesforce enables you to create and manage quotes for potential deals or
opportunities. You can generate quotes, track revisions, and send them to customers
for review and approval.

Orders: Once a deal is closed, Salesforce allows you to generate and manage orders
for products or services purchased by customers. You can track order status, manage
order fulfillment, and integrate with external systems for inventory management and
order processing.

Invoices: Salesforce enables you to generate and manage invoices for products or
services sold to customers. You can track invoice status, record payments, and
integrate with accounting systems for billing and invoicing processes.

Cases: Salesforce's service cloud provides tools for managing customer support cases
or tickets. You can track customer inquiries, assign cases to support agents, and
monitor case resolution times to ensure timely and effective customer service.
Solutions: Salesforce allows you to create and manage knowledge articles, FAQs, and
other resources to help customers find answers to their questions or resolve issues
on their own. You can organize solutions by category, publish them to a customer-
facing portal, and track their usage and effectiveness.

Reports & Dashboards: Salesforce offers robust reporting and dashboard capabilities
to track sales performance, analyze trends, and monitor key metrics. You can create
custom reports and dashboards to visualize data, share insights with stakeholders,
and make data-driven decisions to drive business growth.

By leveraging these components within Salesforce, businesses can streamline their

sales processes, track customer interactions, and drive revenue growth effectively.

Let’s understand the same with example:

Product Details: In Salesforce, you can create a product record for the "Premium
Executive Pen." This record would include details such as the product name,
description, price, and available quantity.

Target Market: You define your target market for the Premium Executive Pen as
professionals in industries like finance, law, and business, who appreciate high-
quality writing instruments.

Sales Team: Your sales team consists of sales representatives assigned to different
regions. Each sales representative has a Salesforce user profile with access to leads,
accounts, and opportunities related to the Premium Executive Pen.

Campaigns: You launch a marketing campaign targeting professionals in your defined

industries, promoting the Premium Executive Pen as a stylish and reliable writing
instrument for professionals.

Prospects: As a result of your marketing campaign, professionals who express

interest in the Premium Executive Pen become prospects. You track their interactions
and engagement with your campaign materials in Salesforce.

Leads: One of the prospects, John Smith, fills out a contact form on your website to
request more information about the Premium Executive Pen. His information is
captured as a lead in Salesforce.

Account / Contact / Opportunities: You qualify John Smith as a potential customer

and convert his lead record into an account, contact, and opportunity in Salesforce.
The account represents John's company, the contact represents John himself, and the
opportunity represents the potential sale of the Premium Executive Pen.
 Quotes: You create a quote for John Smith, detailing the pricing and terms for
purchasing the Premium Executive Pen. The quote is associated with the opportunity
in Salesforce for tracking purposes.

Orders: After John Smith approves the quote, you generate an order for the Premium
Executive Pen in Salesforce. The order confirms the purchase and initiates the order
fulfillment process.

Invoices: Once the order is fulfilled, you create an invoice for John Smith to bill him
for the purchase of the Premium Executive Pen. The invoice details the total amount
due and includes payment instructions.

Cases: After receiving the Premium Executive Pen, John Smith contacts your
customer support team with a question about the product's refill compatibility. A
support agent creates a case in Salesforce to address John's inquiry and provides him
with the necessary information.

Solutions: To help customers like John Smith find answers to common questions, you
create a knowledge article in Salesforce titled "Premium Executive Pen Refill
Compatibility." This article provides step-by-step instructions on how to identify and
purchase compatible pen refills.

Reports & Dashboards: You use Salesforce reports and dashboards to track sales
performance for the Premium Executive Pen, analyze trends in customer inquiries,
and monitor customer satisfaction levels based on support case resolution times.

By integrating the example product, the Premium Executive Pen, into the sales
process in Salesforce, you can effectively manage the end-to-end sales cycle, from
lead generation to customer support, while driving revenue growth for your
business.

Data Model in Salesforce

11. How to store data in salesforce ?

Or
What are objects in salesforce? How many types of objects are there to store data.

In Salesforce, objects are database tables that store specific types of data. They are
the fundamental building blocks for organizing and managing information within the
platform. Salesforce provides two main types of objects: standard objects and
custom objects.
 Standard Objects: These are predefined objects provided by Salesforce to support
common business functions. Examples of standard objects include:

Account: Represents a company, organization, or individual with whom you do

business.
Contact: Represents an individual associated with an account.
Opportunity: Represents a potential sale or deal with a customer.
Lead: Represents a person or entity that has expressed interest in your products or
services.
Case: Represents a customer inquiry, feedback, or support issue.
Task: Represents a specific action or activity that needs to be completed.
Event: Represents a scheduled appointment, meeting, or other calendar event.
Product: Represents a product or service offered by your organization.
Campaign: Represents a marketing campaign or initiative to generate leads or
opportunities.

Custom Objects: These are objects that you create to store data specific to your
organization's unique business needs. You can define custom fields, relationships,
and behaviors for custom objects. For example, you might create a custom object
called "Project" to track information about ongoing projects within your organization.

• Custom objects can be related to standard objects or other custom objects,

allowing you to establish relationships between different types of data.
• You can also create custom tabs, page layouts, and reports for custom objects to
tailor the user experience and functionality.

Overall, objects in Salesforce serve as containers for storing and organizing data,
providing a structured framework for managing business information across various
processes and use cases. They form the foundation of Salesforce's data model and
are essential for building custom applications, automating business processes, and
analyzing data to drive business insights.

12. What are fields in salesforce how they are used to store the data?
In Salesforce, fields are individual data elements that store specific pieces of
information within objects. Fields define the types of data that can be stored and
displayed for each record in an object.

Data Types: Salesforce offers a variety of data types for fields to accommodate
different types of information. Some common data types include:

Text: Stores alphanumeric characters, such as names, descriptions, or addresses.

Number: Stores numeric values, including integers, decimals, and currencies.
Date: Stores dates without a time component.
Date/Time: Stores both date and time values.
 Picklist: Provides a predefined list of values from which users can select.
Checkbox: Stores true/false or yes/no values.
Lookup Relationship: Establishes a relationship between two objects, allowing users
to link records from one object to another.
Formula: Calculates values based on expressions or formulas defined by the user.
Rich Text: Stores formatted text with styles, images, and hyperlinks.

Custom Fields: In addition to standard fields provided by Salesforce, you can create
custom fields to capture information specific to your organization's needs. Custom
fields can be added to both standard and custom objects and can be of any
supported data type.

Relationship Fields: Fields like Lookup Relationship and Master-Detail Relationship

establish connections between different objects in Salesforce. These fields allow you
to link records from one object to another, facilitating data relationships and
navigation.

Field-Level Security: Salesforce allows you to control access to fields at the object
level, profile level, and permission set level. You can define who can view, edit, or
delete specific fields based on user roles, profiles, or permissions.

Fields in Salesforce are essential for capturing, organizing, and analyzing data,
providing a structured framework for managing information across various business
processes and use cases. They play a crucial role in customizing Salesforce to meet
the specific needs of your organization and supporting your business objectives.

13. What are records in salesforce?

In Salesforce, records are individual pieces of data stored within the platform. Each
record represents a specific entity, like a customer, opportunity, or case, and contains
information stored in fields.
Records can be created, edited, and viewed by users, and they progress through
different stages as they move through business processes.
Records are uniquely identified by a system-generated ID and can be related to each
other through relationships.
They play a crucial role in managing and organizing data within Salesforce,
supporting various business activities and workflows.

14. What are different types of relationships available in salesforce?

Certainly! Let's explore each type of relationship in Salesforce with examples:

Master-Detail Relationship:

Definition: A master-detail relationship establishes a parent-child relationship

between two objects, where the child record inherits certain characteristics, such as
security and ownership, from the parent record. Deleting the parent record
automatically deletes related child records.

Example: Suppose you have two custom objects: "Account Plan" and "Opportunity
Plan." Each "Opportunity Plan" is associated with an "Account Plan" and represents a
detailed plan for a specific opportunity. Here, "Account Plan" would be the master
object, and "Opportunity Plan" would be the detail object. Deleting an "Account
Plan" record would also delete all related "Opportunity Plan" records.

Lookup Relationship:

Definition: A lookup relationship allows you to create a link between two objects,
where one object holds a reference (or "lookup") to another object. Unlike master-
detail relationships, lookup relationships do not enforce cascading behaviors or
sharing rules.
Example: In the standard Salesforce schema, the "Contact" object has a lookup
relationship with the "Account" object. Each contact record is associated with a
single account record, representing the company or organization the contact belongs
to. This relationship allows you to navigate from a contact record to its associated
account record.

Many-To-Many Relationships:

Definition: Many-to-many relationships represent a complex association between

two objects, allowing multiple records from each object to be associated with each
other. Many-to-many relationships are implemented using a junction object, which
serves as a bridge between the two related objects.
Example: Consider a scenario where you have two custom objects: "Product" and
"Opportunity." Each opportunity can be associated with multiple products, and each
product can be included in multiple opportunities. To model this many-to-many
relationship, you create a junction object called "Opportunity Product," which
contains fields linking it to both the "Opportunity" and "Product" objects. Each
record in the "Opportunity Product" junction object represents a specific product
included in a particular opportunity.

Self-Relationships:

Definition: Self relationships occur when an object has a relationship with itself. This
type of relationship is useful for modeling hierarchical or recursive structures within a
single object.
Example: In Salesforce, the "User" object has a standard self-relationship called the
"Manager" relationship. Each user record can have a manager, who is also a user in
the system. This self-relationship allows you to create hierarchies of users, where
each user reports to another user (their manager) within the organization.
 External Lookup Relationship:

Definition: An external lookup relationship allows you to link a Salesforce object to an

external object in an external system. This relationship enables you to access and
display data from an external system within Salesforce.
Example: Suppose you integrate Salesforce with an external ERP (Enterprise Resource
Planning) system. You can create an external lookup relationship between a custom
Salesforce object, such as "Sales Order," and a corresponding object in the ERP
system, such as "Order." This relationship allows you to view order details from the
ERP system directly within Salesforce, providing a unified view of customer data and
transactions.
These examples illustrate how different types of relationships in Salesforce allow you
to model complex data structures, establish connections between objects, and
integrate data from external systems, enhancing the flexibility and functionality of
your Salesforce implementation.

15. Differentiate between lookup and master detail relationships.

Lookup Relationship Master Detail Relationship

Loosely coupled. Strongly coupled.
Roll-up summary field not available. Roll-up summary field is available.
Parent record is not required when Parent record is required in order to
creating a child record. save a child record.
Lookup fields are not required on the Master-detail field is always required on
page layout of the detail record but if the page layout of the detail record
you make them a required field, it is (because of the point above).
advised!
Standard object record can be on the Standard object record cannot be a
detail side of a custom object in a child.
lookup relationship.
By default record ownership of child The parent controls the record
records is not controlled by the parent. 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.
You can have a child record without a You cannot have a child record without
parent. a parent.
You can have a maximum of 40 lookups You can have a maximum of two master
on an object. details on an object.
No cascade delete. Cascade delete.
 Business Logics

16. What are formula fields in salesforce?

Formula fields in Salesforce are special fields that calculate their values based on
formula expressions. Here's a brief overview:

• Calculation Logic: Formula fields perform calculations, manipulate text, and

generate dynamic content based on specified criteria.

• Field Types: They can return different types of data, like text, numbers, dates, or
references to other records.

Example: Suppose you have a custom object called "Invoice" with fields for "Unit
Price" and "Quantity." You can create a formula field called "Total Amount" that
calculates the total amount for each invoice using the formula: Unit Price * Quantity.

• Read-Only: Formula fields are read-only and automatically update when source
data changes.

• Use Cases:

Calculate derived values, such as total amounts, discounts, or commissions.

Manipulate text, such as formatting addresses or combining fields.
Evaluate conditions and return true/false values based on criteria.
Generate hyperlinks or URLs dynamically.
Perform date calculations, such as calculating the age of a lead or determining
elapsed time.
• Limitations: Formula fields have certain limitations, such as complexity limits on
formula size and the number of formula fields per object. Additionally, formula
fields cannot reference long text area, multi-select picklist, or binary fields.

Formula fields in Salesforce provide a powerful mechanism for automating

calculations, generating dynamic content, and enhancing data visibility within your
Salesforce organization. They allow you to customize your Salesforce implementation
to meet specific business requirements without the need for custom code.

17. What are rollup summaries fields in salesforce?

Roll-up summary fields in Salesforce are special fields used to calculate values from
related records and display aggregate data on a parent record. These fields are
enabled on parent if object is related with master detail relationships. Here's a
concise explanation:

Calculation Logic: Roll-up summary fields perform calculations, such as

 • Sum
• Count
• Min
• Max
• average,
based on the values of child records related to a parent record.

Field Types: They are limited to specific types of calculations, depending on the type
of relationship and the field being summarized.

Example: Suppose you have a parent object called "Account" and a child object called
"Opportunity." You can create a roll-up summary field on the "Account" object to
calculate the total amount of all related opportunities.

Automatic Calculation: Roll-up summary fields automatically recalculate their values

whenever child records are created, edited, or deleted, ensuring real-time accuracy.

Use Cases: They are commonly used to aggregate data from related records, such as
summing up opportunity amounts, counting related tasks, or finding the maximum
value of a custom field.

Roll-up summary fields in Salesforce provide a convenient way to summarize and

display aggregated data from child records on parent records, eliminating the need
for manual calculations and enhancing data visibility.

18. What are validation rules?

Validation rules in Salesforce are rules that you define to enforce data quality and
consistency by checking that data entered by users meets specified criteria before it
is saved.

Purpose: Validation rules ensure that data entered in Salesforce meets your
organization's requirements and adheres to predefined business rules.

Criteria: You define validation rules using a formula expression that evaluates to true
or false. The formula can reference fields on the record being saved, other related
records, or constants.
Always runs whenever record is inserted or updated.

Conditions: Validation rules can be based on various conditions, such as field values,
record types, user profiles, or related records.
 Error Messages: When a user attempts to save a record that violates a validation
rule, Salesforce displays an error message explaining the issue and preventing the
record from being saved until the data is corrected.

Examples: Common use cases for validation rules include enforcing field format (e.g.,
ensuring phone numbers are in a specific format), enforcing data ranges (e.g.,
preventing future dates in a birthdate field), or ensuring data consistency (e.g.,
requiring a contact to be associated with an account).

Deployment: Validation rules are deployed declaratively through the Salesforce setup
menu and are automatically enforced on all applicable records.

Validation rules in Salesforce provide a powerful mechanism for maintaining data

integrity and enforcing business rules, helping to ensure that your Salesforce data
remains accurate, consistent, and reliable.

User Interface

19. Explain Record Types and Page Layouts.

Page layouts and record types are essential components in Salesforce that help
customize the user interface and data visibility based on different criteria. Here's a
brief explanation of each:

Page Layouts:

Definition: Page layouts determine the layout and organization of fields, related lists,
button , quick action buttons, sections, etc. on a record detail page in Salesforce.

Customization: Administrators can customize page layouts for each object to control
which fields are displayed, their order, and whether they are required or read-only.

User-Specific: Page layouts can be assigned to different user profiles, ensuring that
users see relevant information based on their roles and responsibilities.

Use Cases: Page layouts are commonly used to streamline data entry, improve user
productivity, and tailor the user experience for different user groups or business
processes.

Record Types:

Definition: Record types allow you to define different sets of picklist values, page
layouts, and business processes for records of the same object.
 Customization: Administrators can create multiple record types for an object and
customize each record type with its own page layout, picklist values, and field
requirements.

Visibility Criteria: Record types can be assigned based on various criteria, such as
profile, user role, record owner, or even criteria-based rules.

Use Cases: Record types are commonly used to support different business scenarios,
such as sales stages, support processes, case classifications, or application forms.
They allow you to tailor the user experience and data entry requirements based on
specific use cases or requirements.

In summary, page layouts control the layout and organization of fields on record
detail pages, while record types allow you to define different sets of picklist values,
page layouts, and business processes for records of the same object. Together, they
enable administrators to customize the user interface and data visibility in Salesforce
to meet the needs of different users, roles, and business processes.

20. What are dynamic forms?

Dynamic forms in Salesforce are a feature introduced in Lightning Experience that
allow for more flexible and personalized user experiences by dynamically displaying
fields and sections on record detail pages based on specified criteria.

• Dynamic forms allow you to control the visibility of fields and sections on record
detail pages using the Lightning App Builder.
• With dynamic forms, you can create multiple variations of a single page layout
and assign visibility rules to determine which fields and sections are displayed to
users based on their profile, record type, or other criteria.
• Dynamic forms offer more granular control over the visibility of individual fields
and sections compared to traditional page layouts.
• Dynamic forms support personalized user experiences by displaying relevant
information and actions based on user context, such as their role, permissions, or
preferences.
• They help optimize screen real estate by showing only the most relevant fields
and sections to users, improving usability and reducing clutter on record detail
pages.

In summary, dynamic forms provide more dynamic and personalized user

experiences by allowing for granular control over the visibility of fields and
sections on record detail pages based on user context. They offer greater
flexibility and optimization compared to traditional page layouts, which have a
static configuration applied to all users assigned to a particular profile or record
type.
21. What different Lightning Pages available?
In Salesforce, Lightning Experience offers various types of Lightning pages that can be
customized to optimize user productivity and provide tailored user experiences. Here
are the different types of Lightning pages available:

• Home Page:
The Home page is the landing page for users when they first log in to Salesforce.
It provides a customizable dashboard-like layout with components such as charts,
lists, and recent records.
Users can personalize their Home page by adding, removing, or rearranging
components to suit their needs.

• Record Page:
Record pages are used to view, edit, and interact with individual records in
Salesforce.
They provide a dynamic layout that displays relevant information and related
records using components such as highlights panel, related lists, and related
record cards.
Record pages can be customized using the Lightning App Builder to tailor the
layout and components based on user roles, record types, and business
requirements.

• App Page:
App pages are used to organize and present collections of related records or
functionality within a specific app or module.
They can include custom components, dashboards, reports, and other tools to
streamline workflows and provide a unified user experience.
App pages are often used to create custom navigation menus, dashboards, or
landing pages for specific user groups or business processes.

22. What are listviews how we can customize them?

In Salesforce, list views are customizable displays of records from a specific object,
such as Leads, Contacts, Opportunities, or Cases or any custom object. They allow
users to see subsets of data based on defined criteria and are commonly used for:

Filtering Data: List views enable users to filter records based on various criteria, such
as record owner, record type, status, or custom fields. This helps users focus on
relevant subsets of data.

Sorting Data: Users can sort records within a list view based on specific fields, such as
creation date, last modified date, or custom fields. This allows for better organization
and prioritization of records.
 Customization: List views can be customized to display specific fields, columns, and
field widths, providing users with relevant information at a glance. Users can also
customize their own list views for their personal needs.

Mass Actions: List views support mass actions, allowing users to perform actions on
multiple records simultaneously, such as mass updating field values, sending email
templates, or assigning records to users.

Sharing and Visibility: List views can be shared with other users or groups, enabling
collaboration and visibility across the organization. Administrators can also control
visibility and access to list views based on user roles and permissions.

Reporting: List views serve as the basis for reports and dashboards in Salesforce.
Users can create reports and dashboards using the same criteria and filters defined in
list views to visualize data and gain insights.

Overall, list views are essential tools in Salesforce for organizing, filtering, and
managing records effectively. They provide users with customizable views of data
tailored to their specific needs and workflows, improving productivity and decision-
making across the organization.

Reports & Dashboards

23. What are reports in salesforce and different types of reports?

In Salesforce, reports are a way to organize and present data from your Salesforce
records. They provide valuable insights into your organization's data, helping users
analyze trends, monitor performance, and make informed decisions. There are
several types of reports in Salesforce:

Tabular Reports: These reports display data in a simple table format. They are useful
for viewing a list of records with their associated fields.

Summary Reports: Summary reports allow you to group data by a particular field,
such as by owner or by stage, and display subtotals and totals. They provide a higher-
level view of your data compared to tabular reports.

Matrix Reports: Matrix reports allow you to group data by both rows and columns,
providing a more comprehensive view of your data. They are useful for analyzing
data across multiple dimensions.

Joined Reports: Joined reports allow you to combine multiple reports into a single
report, each with its own set of data and columns. This is useful for comparing data
from different sources or for creating complex reports.
24. What are dashboards in salesforce?
In Salesforce, dashboards are a visual representation of your organization's data,
providing a snapshot of key metrics and performance indicators. They allow users to
quickly and easily analyze data, identify trends, and make informed decisions.
Dashboards typically consist of charts, graphs, tables, and other components that
display real-time or near-real-time data from Salesforce records.

Here are some key features and aspects of Salesforce dashboards:

Customization: Users can create custom dashboards tailored to their specific needs
and preferences. They can choose which metrics to display, how to visualize the data,
and the layout of the dashboard components.

Components: Dashboards can contain various components, such as bar charts, line
graphs, pie charts, tables, metrics, gauges, and more. Each component represents a
different aspect of the data and can be configured to display specific information.

Data Sources: Dashboard components are often based on underlying reports in

Salesforce. Users can select existing reports or create new ones to provide the data
for their dashboard components. This ensures that the data displayed on the
dashboard is up-to-date and relevant.

Real-Time Updates: Dashboards in Salesforce can show real-time or near-real-time

data, depending on the source of the data and the refresh settings. This allows users
to monitor performance and track metrics as they change over time.

Sharing and Collaboration: Users can share dashboards with others in their
organization, making it easy to collaborate and align on key metrics and goals.
Dashboards can be shared with specific users, groups, or roles, ensuring that each
user sees the most relevant information.

Mobile Access: Salesforce offers mobile capabilities, allowing users to access and
view dashboards from their mobile devices. This enables users to stay informed and
make decisions on the go.

25. What are dynamic and static dashboards?

Static Dashboards
A Static Dashboard appears the same to all people viewing it. It is, however, tied to
the user's profile and permissions. If they don't have permission to view certain
records or objects in Salesforce, they won't be able to view the information on the
dashboard or reports. A Static Dashboard is the default in Salesforce.
 Dynamic Dashboards
Dynamic Dashboards can be customized to each viewer's needs regardless of what
they have permission to see in Salesforce. For example, if users only have permission
to see their own Opportunities, you can create a Dynamic Dashboard that allows
them to see all Opportunities via the dashboard.

26. What are report types?

Report types define which objects and fields are available when creating a report.
Salesforce provides standard report types, but administrators can also create custom
report types to tailor reporting to specific business needs.

27. What is Report Builder in Salesforce?

The Report Builder is a drag-and-drop interface that allows users to create reports
without the need for advanced coding or technical skills. Users can add and arrange
report components, such as fields, filters, and grouping criteria.

28. Can we schedule the reports?

Yes, Users can schedule reports to run at specific times and subscribe to receive
report results via email. This helps in automating the process of staying informed
about important data.

29. Can we create custom formula fields also in reports to achieve the requirements?
Yes, Users can create custom formula fields and use them as filters to perform
calculations or manipulations on data before applying the filter conditions.

30. What are bucket fields in reports?

Bucket fields in Salesforce are a way to categorize or group report data based on
ranges, categories, or criteria that you define. They allow you to group together
related values from a single field into discrete "buckets" for easier analysis and
reporting.
Example you want to bucket the revenue based on the numbers
Bucket 1: $0 - $10,000
Bucket 2: $10,001 - $50,000
Bucket 3: $50,001 - $100,000
Bucket 4: $100,001 and above

31. How many reports we can add to the dashboards?

In Salesforce, the maximum number of reports you can add to a single dashboard
depends on the edition of Salesforce you're using:

Salesforce Professional Edition: In Professional Edition, you can add up to 20 reports

to a single dashboard.
 Salesforce Enterprise Edition: In Enterprise Edition, you can add up to 100 reports to
a single dashboard.

Salesforce Unlimited Edition: Unlimited Edition allows you to add up to 200 reports
to a single dashboard.

32. Explain data storage architecture that enables businesses to organize, manage, and
secure their data effectively, supporting various business processes and use cases.
In Salesforce, data is stored in a structured format within objects and records. Here's
how data storage works in Salesforce:

Objects: Objects are the fundamental building blocks for storing data in Salesforce.
Standard objects, such as Accounts, Contacts, Opportunities, and Cases, are provided
by Salesforce out of the box. Additionally, you can create custom objects to store
data specific to your business needs.

Fields: Each object in Salesforce contains fields that define the types of data that can
be stored. Standard fields, like Name, Email, Phone, and Address, are provided for
standard objects. For custom objects, you can create custom fields of various data
types, such as Text, Number, Date, Picklist, and Lookup.

Records: Records are individual instances of objects that store specific data. For
example, an Account record may contain information about a customer company,
such as its name, industry, and address. Similarly, a Contact record may contain
details about an individual associated with the account, such as their name, email,
and phone number.

Relationships: Relationships define the associations between objects in Salesforce.

For instance, an Account may have multiple related Contact records representing
different contacts associated with the account. Salesforce supports various types of
relationships, including one-to-one, one-to-many, and many-to-many relationships.

Data Import: Salesforce provides tools for importing data into the platform, allowing
you to migrate existing data from spreadsheets, databases, or other systems. You can
use tools like the Salesforce Data Loader, Data Import Wizard, or third-party
integration tools to import data efficiently.

Data Security: Salesforce offers robust data security features to control access to
data and ensure data privacy and compliance. You can define security settings, such
as object-level security, field-level security, record-level security, and sharing rules, to
restrict access to sensitive data based on user roles, profiles, and permissions.

Data Management: Salesforce provides tools for managing and maintaining data
quality, such as data cleansing, deduplication, and data validation rules. You can
 enforce data integrity rules to ensure that data entered into Salesforce is accurate,
consistent, and complete.

Backup and Recovery: Salesforce automatically backs up your data and provides
tools for data recovery in case of data loss or corruption. You can use features like
data export, data recovery service, and Salesforce's data retention policies to protect
your data and ensure business continuity.

Overall, Salesforce offers a robust and flexible data storage architecture that enables
businesses to organize, manage, and secure their data effectively, supporting various
business processes and use cases.

33. What are public groups in salesforce?

• Public groups in Salesforce are collections of users, other groups, or roles created
for easy collaboration, sharing, and permission management. They simplify
granting access to multiple users simultaneously and facilitate communication.
• They are used for sharing records, files, and resources, as well as for sending
group communications like emails and Chatter posts.
• Administrators can create, edit, and delete public groups to reflect changes in
organization structure or team assignments.

Use Cases:
Record Sharing: Public groups can be used to share records with a group of users
collectively, making it easier to manage sharing settings.
Collaboration: Public groups are often used in collaboration scenarios, such as
sending emails to a group or inviting a group to a Chatter group.
Access Control: Public groups can be assigned to profiles, permission sets, or
other groups to control access to various features and resources.

34. What are queues in Salesforce?

In Salesforce, queues are used to distribute tasks, cases, leads, or records among a
group of users for efficient handling. They promote collaboration, shared ownership,
and flexible assignment rules, ensuring timely resolution of work items.

Use Cases:
Case Assignment: Cases can be placed in queues to distribute work among a group
of support agents. Agents can take ownership of cases from the queue. Lead or
Opportunity Distribution: In sales scenarios, leads or opportunities can be placed in
queues for distribution among sales representatives.
Service Requests: For managing various service requests, such as IT support t ickets
or customer inquiries.
35. How public groups and queues are different from each other?
1. Functionality:
Public Groups: Primarily used for collaboration, record sharing, and access
control. Queues: Used for managing and distributing records that require action,
often in a shared or collaborative environment.

2. Membership:
Public Groups: Comprise users, other groups, roles, or territories.
Queues: Comprise users or groups to whom records are assigned for processing.

3. Ownership:
Public Groups: Do not own records but can be used for sharing and access
control. Queues: Facilitate shared ownership of records among queue members.

4. Use Cases:
Public Groups: Collaboration, sharing settings, access control.
Queues: Case assignment, workload distribution, managing shared work items.

In summary, while both public groups and queues serve to streamline collaboration
and work distribution in Salesforce, they have distinct purposes. Public groups are
more focused on collaboration and access control, whereas queues are specifically
designed for managing and distributing records that require action.

36. What is feed tracking?

Feed Tracking in Salesforce refers to the ability to track changes and updates made to
records in Salesforce, such as accounts, contacts, opportunities, cases, and custom
objects. When feed tracking is enabled for a specific object and its fields, Salesforce
captures the changes made to those fields and displays them in the record's feed
(Chatter Feed).

Tracking Changes: Feed tracking allows Salesforce to capture changes made to

specific fields on records. These changes include updates to the field values, such as
modifications to text, numbers, dates, picklist selections, and more.

Record Feed: When feed tracking is enabled, the changes made to tracked fields are
displayed in the record's feed. The feed provides a chronological view of all activities
and updates related to the record, including field changes, comments, file
attachments, and system-generated events.

Customization: Salesforce administrators can customize feed tracking settings for

each object and choose which fields to track. They can also control who has access to
view and comment on the record feed, ensuring data privacy and security.
 In summary, feed tracking in Salesforce enables organizations to track and monitor
changes to record data, promoting transparency, collaboration, and informed
decision-making.

37. What is field history tracking?

Field History Tracking in Salesforce records changes made to specific fields over time.
When enabled, it creates a historical log for each modification, including old and new
values, user details, and timestamps. This feature aids in transparency, compliance,
and analysis of data changes.
Changes will be tracked from Object History related list.

Tracking Field Changes: Field History Tracking captures changes made to selected
fields on records. These changes include updates to the field values, such as
modifications to text, numbers, dates, picklist selections, and more.

Historical Records: Whenever a tracked field's value is changed, Salesforce creates a

new record in the Field History Tracking object to store the old and new field values,
along with additional metadata such as the user who made the change and the
date/time of the modification.

Reporting and Analysis: Organizations can leverage field history data for reporting
and analysis purposes. They can generate reports or dashboards to analyze trends,
track user activity, and monitor changes to critical data fields over time.

Customization: Salesforce administrators can customize field history tracking settings

for each object and choose which fields to track. They can also configure retention
policies to control how long historical data is retained in the system.

38. What are key differences between feed tracking and field history tracking?
The key difference between Field History Tracking and Feed Tracking in Salesforce lies
in the scope of the changes tracked and the presentation of those changes:

Scope of Changes Tracked:

Field History Tracking: It tracks changes made to specific fields on records. It

captures modifications to field values, such as updates to text, numbers, dates,
picklist selections, etc.
Feed Tracking: It captures a broader range of activities and updates related to
records, including changes to field values, comments, file attachments, system-
generated events, and more.
 Presentation of Changes:

Field History Tracking: It maintains a historical log of changes made to tracked fields,
storing old and new field values along with additional metadata. This log is typically
accessed through the Field History Tracking related list on records.
Feed Tracking: Changes tracked through feed tracking are displayed in the record's
feed, providing a chronological view of all activities and updates related to the
record, including field changes, comments, file attachments, etc.

Reporting and Analysis

Field History Tracking: We can generate reports or dashboards to analyze trends,

track user activity, and monitor changes to critical data fields over time.
Feed Tracking: Changes cannot be tracked in reports same as of field history tracking.

In summary, while both Field History Tracking and Feed Tracking capture changes
made to record data, Field History Tracking focuses specifically on changes to field
values and maintains a detailed historical log, whereas Feed Tracking captures a
broader range of activities and updates related to records and presents them in a
feed format.

Apex Code
Field History Tracking: You can quickly get the old value and new value of the fields
on which you have enabled the history tracking using SOQL.
Standard Object: SELECT OldValue, NewValue, Field FROM AccountHistory
Custom Object: SELECT OldValue, NewValue, Field FROM customObject__History

39. For how many fields tracking can be enabled per objects?
Up to 20 fields.

40. Can we also display feed activity for related objects also?
Yes, checkbox is available to enable same for all related objects.

41. What are audit trails in salesforce?

Audit trails in Salesforce track changes made to your organization's setup
configuration, including who made the change, when it was made, and what was
changed. They help ensure compliance, enhance security, aid in troubleshooting, and
provide a historical record of changes.

42. What are the valuable features of audit trails?

Compliance: It helps organizations comply with regulatory requirements by
maintaining a record of who made changes to sensitive data and when those
changes occurred.
 Security: It enhances security by allowing administrators to monitor and track
changes made to critical settings, helping to detect any unauthorized modifications.

Troubleshooting: It aids in troubleshooting issues by providing a chronological record

of changes, which can help administrators identify when and how problems may
have arisen.

Historical Tracking: It enables administrators to view historical data and understand

the evolution of their Salesforce setup over time.

43. What is retention period of audit trails?

The Audit Trail retains information about changes for up to 6 months. Administrators
can review historical data during this period to understand the evolution of their
Salesforce configuration.

44. What is activity component available for?

Salesforce has a robust set of features related to activities and tasks that can be
utilized and customized within the platform.

Salesforce allows users to manage their activities and tasks through the "Activities"
tab or related lists on relevant records (such as leads, contacts, and opportunities).
Users can create tasks and events, log calls, schedule appointments, and track
various interactions related to their work.

45. What can be the possibility that on object activity component is not available, how
we can enable and add this component.
Go to object details and check for checkbox Allow Activities.
If this is disabled then activity component will not be available on object once this is
enabled you can now go to the edit page and add the activity component on the
detail page.

46. What are field Dependencies in salesforce?

In Salesforce, field dependencies are a way to control the values that are available in
one picklist field based on the value selected in another picklist field.
Controlling and Dependent Values: The controlling field is the parent picklist, and the
dependent field is the child or dependent picklist. When a value is selected in the
controlling field, it filters the available options in the dependent field based on
predefined dependencies.

For example:

If "Electronics" is selected for the category, then the subcategory options might be
"Smartphones," "Laptops," "Cameras," etc.
 If "Clothing" is selected for the category, then the subcategory options might be
"Shirts," "Pants," "Dresses," etc.

47. Can we create controlling field as multi picklist?

No Controlling cannot be created with multi-picklist field.
But dependent can create with multi picklist.

48. What is restrict checkbox in picklist fields?

Checked (Enabled): When this checkbox is checked, users are restricted to selecting
only the values defined in the picklist. They cannot enter any custom values that are
not in the predefined list. This ensures data integrity and consistency within your
Salesforce org.

Unchecked (Disabled): If this checkbox is unchecked, users have the flexibility to

enter values that are not in the predefined picklist. While this provides more
freedom to users, it can lead to inconsistencies in data entry and reporting, as users
might enter variations of the same value or entirely new values.

49. What will happen if we convert Mult picklist to picklist field in salesforce?
If you convert a multi-select picklist field to a picklist field in Salesforce, the system
will remove all the values that were previously selected in the multi-select picklist.
Essentially, you'll lose the data stored in that field for existing records because a
picklist field can only store a single value, whereas a multi-select picklist can store
multiple values.

50. What are global valueset in salesforce?

In Salesforce, a global value set is a reusable collection of values that can be used
across multiple picklist fields. Instead of defining picklist values directly within each
field, you create a global value set and associate it with one or more picklist fields.
This allows you to maintain consistency and manage the values centrally.

51. What is the use of global valueset in salesforce?

Global value sets in Salesforce provide a centralized way to manage and reuse picklist
values across multiple fields and objects, ensuring consistency, efficiency, and easier
maintenance. They streamline administration tasks, support dependency
management, versioning, and can be packaged for distribution.

52. What is the schema builder in salesforce?

The Schema Builder in Salesforce is a graphical tool that allows users to view and
modify the schema of their Salesforce org visually. It provides a drag-and-drop
interface for building and modifying custom objects, fields, and relationships
between objects.
 Key Points :
Visual Representation
Drag-and-Drop Interface
Object Creation and Modification
Relationship Management
Field Configuration
Impact Analysis: Allows users to see how changes to the schema will affect other
parts of the org, such as reports, dashboards, and Apex code.

53. What are list views in salesforce?

List views in Salesforce are customizable views of records within an object that allow
users to filter, sort, and focus on specific subsets of data based on criteria such as
field values. They enable users to organize and interact with records efficiently, with
features like filtering, sorting, sharing, and mass actions.

54. With whom user can share the list views created by him.
In Salesforce, users can share the list views they create with specific individuals,
groups, roles, or roles and subordinates.

55. What is the difference between both

 In the Account List view, checkboxes are available, and we can also edit field values
directly from the list view itself.

However, in the case of the student object, checkboxes are not available, and we
cannot edit fields directly from the list view.

The reason behind this difference lies in the implementation of record types. When
record types are created on an object and users are given the choice to select record
types, checkboxes and field editing functionality are typically removed.

These options are only available when no record types are defined on the object.

56. What are matching rules in Salesforce?

Matching rules in Salesforce are used to determine if incoming records match
existing records in the database based on specific criteria. They define the conditions
that Salesforce uses to identify potential duplicates during record creation or update.

57. How do matching rules differ from duplicate rules?

Matching rules specify the criteria for identifying potential duplicates, while duplicate
rules define the actions to be taken when duplicates are found. Matching rules are
used to identify potential duplicates based on criteria, while duplicate rules
determine what actions should be taken (e.g., blocking record creation, showing an
alert, or allowing creation with manual review).

58. Can you explain how to create a matching rule in Salesforce?

To create a matching rule, you navigate to Setup > Data > Matching Rules and create
a new matching rule. You define the object to which the rule applies, set the
matching criteria (e.g., matching fields and conditions), and specify the matching
logic (e.g., exact match, fuzzy match).

59. What is a duplicate rule in Salesforce?

A duplicate rule in Salesforce specifies the actions to be taken when potential
duplicates are identified based on matching rules. It determines whether to allow
record creation, display an alert to users, or block creation altogether.

60. How can you enforce duplicate rules in Salesforce?

Once activated, the rules will be applied whenever new records are created or
updated, and potential duplicates are identified based on the matching criteria
defined in the matching rules.

61. How do matching and duplicate rules contribute to data quality in Salesforce?
Matching and duplicate rules help maintain data quality by identifying and
preventing the creation of duplicate records. By enforcing these rules, organizations
can reduce data redundancy, improve data accuracy, and enhance user productivity.
62. What are these two options in duplicate rules

Enforce Sharing Rules: In the context of record level security, such as sharing rules,
the system will respect the user's access permissions. When checking for duplicates,
it will only consider the records that the user has access to based on their sharing
rules and permissions. This means that duplicate checks will only be performed
within the subset of records that the user is permitted to view, rather than across all
records in the organization.

Bypass Sharing Rules: In this case, when checking for duplicates, the system will
disregard sharing rules and individual user permissions. Duplicate checks will be
performed across all records in the organization, regardless of whether a user has
access to a particular record or not.

63. What is the difference between exact match and fuzzy matching in matching rules?
Exact Match: Exact matching requires the values in the specified fields to be identical
to consider two records as potential duplicates. This means that each character and
space in the compared fields must match exactly for the records to be flagged as
duplicates. Exact matching is more stringent and is suitable for scenarios where
precise matches are necessary, such as when matching on unique identifiers like
email addresses or account numbers.

Fuzzy Matching: Fuzzy matching, on the other hand, allows for variations and
similarities in the values of the compared fields. It considers factors such as
typographical errors, abbreviations, misspellings, and slight variations in formatting.
Fuzzy matching uses algorithms to calculate a similarity score between the values in
the fields, and if the score exceeds a specified threshold, the records are considered
potential duplicates. Fuzzy matching is more flexible and can be useful when dealing
with data that may have inconsistencies or variations, such as names or addresses.

Example
Let's say you have a Salesforce org with a Contact object, and you want to identify
potential duplicate contacts based on their last names. You have two contacts with
the following last names:

Contact A: "Smith"
Contact B: "Smit"
 Using fuzzy matching, the system would compare the last names of these contacts
and calculate a similarity score based on factors such as the number of characters in
common, the position of characters, and the likelihood of typographical errors.

In this example, even though the last names "Smith" and "Smit" are not identical,
they are very similar, differing by only one character. Fuzzy matching algorithms
might assign a high similarity score to these two last names, indicating that they are
likely to be duplicates.

64. What are email templates in salesforce?

In Salesforce, email templates are pre-designed, reusable messages that you can
send to contacts, leads, users, or a specific set of recipients directly from Salesforce.
These templates help ensure consistency in communication, save t ime, and provide
a standardized format for various types of emails.

Classic Email Templates

o Text Email Templates
o HTML Email Templates
o Custom Email Templates
o Visualforce Email Templates

Lightning Email Templates

Lightning Email Templates are a type of email template specifically designed for
use in the Lightning Experience interface. They provide a modern and dynamic
way to create visually appealing and responsive emails within the Salesforce
platform. Lightning Email Templates are different from Classic Email Templates,
and they are optimized for the Lightning Experience.

65. What are email alerts in salesforce?

Email alerts are notifications sent to users or contacts based on predefined criteria in
Salesforce records. These alerts are part of workflow rules or process builder
processes, flows, and are triggered automatically when certain conditions are met.

66. Example differentiating between email alerts and email template in salesforce?
Scenario:
Suppose you're managing a sales team, and you want to notify the assigned sales
representative whenever a new high-priority lead is assigned to them.

Using Email Alerts:

Email Alert: You create an email alert workflow rule/PB/Salesforce Flow that triggers
whenever a new lead is created and meets the criteria of being high-priority.
Recipient: The email alert is configured to send an email notification to the assigned
sales representative when the lead meets the criteria.
 Dynamic Content: The email alert includes dynamic content such as the lead's name,
contact information, and any other relevant details pulled from the lead record.
Automation: This email alert is automated and requires no manual intervention.
Whenever a high-priority lead is created and assigned, the system automatically
sends an email notification to the respective sales representative.

Using Email Templates:

Email Template: You create an email template containing a standardized message to

be sent to leads when they are assigned to a sales representative.
Manual Sending: When a new lead is assigned to a sales representative, the user
manually selects the appropriate email template and sends an email to the lead.
Standardized Content: The email template ensures that the message sent to the lead
is consistent and includes all necessary information such as the sales representative's
contact details, company information, and next steps.
User Interaction: Unlike email alerts, using email templates requires manual
intervention by the user to select the template and send the email. It does not
involve automation triggered by specific criteria.

Summary:

Email Alert: Automatically sends notifications based on predefined criteria, with

dynamic content pulled from records. It's part of workflow automation and doesn't
require manual intervention.
Email Template: Provides standardized email content to be manually selected and
sent by users. It ensures consistency in communication but relies on user action
rather than automation.

Approval Processes:

67. What is an approval process in salesforce?

An approval process in Salesforce automates how records are approved in your
organization. It specifies each step of approval, including from whom to request
approval and what to do at each point of the process. This ensures that records are
reviewed and approved in a consistent manner.

68. How do you create an approval process in salesforce?

• Go to Setup.
• Enter Approval Processes in the Quick Find box and select it.
• Select the object you want to create an approval process for.
• Click on Create New Approval Process and choose Use Standard Setup Wizard or
Use Jump Start Wizard.
 • Define the entry criteria, approval steps, actions (such as email alerts, field
updates, and task assignments), and final approval or rejection actions.
• Activate the approval process.
69. What are the entry criteria in approval process?
Entry criteria are conditions that a record must meet to enter an approval process.
For example, you might require that an opportunity’s amount is greater than $10,000
before it enters the approval process. Entry criteria can be based on any field on the
record.

70. What are initial submission actions in an approval process?

Initial submission actions are actions that occur when a record is first submitted for
approval. These actions can include:

Sending an email alert

Updating a field on the record
Creating a task
Sending an outbound message

71. Can you submit a record for approval automatically?

Yes, you can submit a record for approval automatically using Process Builder, Flow or
Apex triggers. For example, you can use flow to automatically submit a record for
approval when it meets certain criteria, such as when a checkbox is checked or a field
value changes.

72. How do you configure approval requests to be sent to a queue?

To configure approval requests to be sent to a queue:

• In the approval process setup, select the step where you want to assign approval
requests to a queue.
• Choose Automatically assign to approver(s).
• Select Queue and choose the appropriate queue.
• Ensure the queue members are set up correctly so they can act on the approval
requests.

73. Can you recall an approval request once it's been submitted?
Yes, users can recall an approval request if the approval process is configured to allow
it. To enable this:

Go to the approval process setup.

Check the option Allow submitters to recall approval requests.

74. What happens if an approver rejects the record?

 If an approver rejects the record, the process can follow defined rejection actions,
such as:

Sending a rejection email to the submitter

Updating the record status or other fields
Creating tasks or other actions
The process then halts unless it’s designed to allow resubmission.

75. How do you notify users of approval requests?

You can notify users of approval requests using email alerts. During the approval
process setup:

• Define email templates for the notifications.

• In each approval step, specify the email alert action.
• The email alert can include details about the record and the required action, and
it is sent to the approvers when the record reaches their step in the approval
process.

76. What happens when an approval process is recalled?

The record returns to its previous state before the approval submission.
Any approval-related actions that were taken (such as field updates or task creations)
are typically reversed.
The submitter is notified that the record has been recalled, and they can make
necessary changes before resubmitting it for approval.

77. How do you handle approval escalations?

Approval escalations can be configured to automatically reassign approval requests if
they are not acted upon within a specified time frame. To set up escalations:

In the approval process setup, define an escalation rule.

Specify the time-based criteria (e.g., if not approved within 3 days).
Assign the record to another approver or queue.
Configure actions such as sending email notifications to alert the new approver or
original approver’s manager.

78. Can you include approval processes in Salesforce Flow?

Yes, you can include approval processes within Salesforce Flow to automate
submission and other related actions. Using Salesforce Flow:

Create a flow that triggers based on specified conditions (e.g., a record update or
creation).
Use the Submit for Approval action within the flow to submit the record to the
predefined approval process.
 Configure the flow to handle the outcomes of the approval process, such as updating
record statuses or sending notifications.

Salesforce Flows

79. What is Salesforce Flow, and how does it differ from Process Builder and Workflow
Rules?
Salesforce Flow is a powerful automation tool that allows users to build custom
processes in Salesforce, guiding users through a series of screens and performing
complex logic and actions.
Unlike Process Builder and Workflow Rules, which are primarily used for automating
simple processes based on record changes, Flow provides more flexibility and can
handle more complex scenarios involving user interaction, decision-making, and
looping.

80. Explain the different types of flows available in Salesforce and their use cases.
Salesforce offers three main types of flows: Autolaunched flows, screen flows, and
scheduled flows.
Autolaunched flows are triggered by record changes or platform events and run in
the background without user interaction.
Screen flows involve user interaction, guiding users through a series of screens to
collect information or perform actions.
Scheduled flows run on a predefined schedule to perform actions such as data
cleanup or sending email alerts.

81. Can you describe the components of a Flow?

A Flow consists of three main components: elements, resources, and connectors.
Elements are building blocks that perform specific actions or logic, such as displaying
a screen, updating records, or making decisions.
Resources are variables, formulas, and other resources used within the Flow.
Connectors enable interaction with external systems or services.

82. What are the advantages of using Salesforce Flow over other automation tools like
Workflow Rules or Process Builder?
Salesforce Flow offers greater flexibility and customization compared to Workflow
Rules and Process Builder. It can handle more complex business processes involving
user interaction, decision-making, and looping. Flow also provides better error
handling and debugging capabilities.
83. How do you debug and troubleshoot Flow errors?
Flow errors can be debugged using tools like debug logs, error emails, and the Flow
debugger. By analyzing debug logs and error messages, you can identify the source of
the problem and make necessary adjustments to the Flow logic or configuration.

84. Explain the concept of record-triggered flows and how they are different from
screen flows.
Record-triggered flows are triggered by record changes, such as when a record is
created or updated. They run in the background without user interaction and are
used for automating processes based on record data. Screen flows, on the other
hand, involve user interaction and guide users through a series of screens to collect
information or perform actions.

85. What are the different ways to launch a Flow in Salesforce?

Flows can be launched manually from a button or link, triggered automatically by
record changes or platform events, or scheduled to run at predefined times.

86. Describe how you would create a Flow to automate a business process in
Salesforce.
To automate a business process with Flow, I would start by identifying the specific
requirements and steps involved in the process. Then, I would use Flow Builder to
create the necessary elements, such as screens, decisions, and actions, to implement
the logic of the process. Finally, I would test the Flow thoroughly to ensure it meets
the requirements and functions correctly.

87. What are the limitations of Salesforce Flow, and how would you work around
them?
Some limitations of Salesforce Flow include complexity in handling large data
volumes, limitations in supported functionality compared to Apex code, and
limitations in integration capabilities. To work around these limitations, you can
optimize your Flow design, use Apex code where necessary, and leverage external
integrations through connectors or Apex callouts.

88. How do you handle bulk data processing within a Flow?

Bulk data processing within a Flow can be achieved by using collection variables and
looping elements such as loops and fast elements. By processing records in batches,
you can efficiently handle large volumes of data while minimizing resource
consumption.
89. Explain how you would use Flow to handle complex business logic or decision-
making processes.
To handle complex business logic or decision-making processes with Flow, I would
use decision elements, formula logic, and variables to evaluate conditions and make
decisions based on various factors such as record data, user input, or external data
sources. By breaking down the logic into smaller, manageable steps, I can design a
Flow that accurately reflects the business requirements.

90. Can you integrate external systems or services with Salesforce Flow? If so, how?
Yes, Salesforce Flow can integrate with external systems or services using connectors,
Apex code, or external services. Connectors provide pre-built integration with
popular services such as Salesforce Connect, REST API, and SOAP API. Apex code can
be used to create custom integrations using callouts to external APIs. External
services allow you to invoke external processes or services from within a Flow.

91. What are the best practices for designing and optimizing Flows in Salesforce?
Some best practices for designing and optimizing Flows include keeping Flows simple
and modular, minimizing the use of resources and elements, optimizing queries and
data retrieval, using bulk processing techniques for large data volumes, and
thoroughly testing Flows in a sandbox environment before deployment.

92. How do you handle errors and exceptions in a Flow?

Errors and exceptions in a Flow can be handled using error handling elements such as
fault connectors, fault paths, and try-catch blocks. By identifying potential points of
failure and implementing appropriate error handling logic, you can ensure that the
Flow behaves gracefully in the event of errors or exceptions.

93. Describe a scenario where you had to use a Flow to solve a specific business
problem.
In a previous project, we needed to automate the process of capturing customer
feedback after a service interaction. I created a Flow that triggered when a service
case was closed. The Flow guided the service agent through a series of screens to
collect feedback from the customer and update relevant records in Salesforce. This
streamlined the feedback collection process and provided valuable insights for
improving service quality.

94. What are Flow interviews, and how do they enhance user interaction in Salesforce?
Flow interviews allow users to interact with Flows through a custom user interface,
such as a Lightning component or Visualforce page. This enhances user interaction by
providing a more intuitive and guided experience, allowing users to input data, make
selections, and perform actions within the context of the Flow.
95. Explain the concept of subflows and when you would use them.
Subflows are reusable Flow components that can be called from other Flows or
processes. They encapsulate a set of actions or logic and can accept input variables
and return output values. Subflows are useful for modularizing Flow logic, promoting
reusability, and simplifying complex processes by breaking them down into smaller,
manageable components.

96. How do you deploy Flows between different Salesforce environments?

Flows can be deployed between different Salesforce environments using change sets,
Salesforce CLI, or Salesforce Packaging, GitHub. Change sets allow you to package
Flows along with other metadata components and deploy them from one org to
another. Salesforce CLI provides command-line tools for retrieving and deploying
Flows using source control. Salesforce Packaging allows you to package Flows into
managed or unmanaged packages for distribution and installation.

97. What considerations should you keep in mind when designing Flows for mobile
users?
When designing Flows for mobile users, it's important to consider factors such as
screen size, touch interactions, and network connectivity. Use responsive design
principles to ensure that Flows are optimized for mobile devices and provide a
seamless user experience. Minimize the use of large or complex screens, and
optimize data retrieval and processing to minimize network usage and improve
performance on mobile devices.

98. Describe the differences between Flow Builder and Cloud Flow Designer.
Flow Builder is the successor to Cloud Flow Designer and provides an enhanced user
interface and additional features for building Flows. Flow Builder offers a more
intuitive and streamlined design experience, with features such as a simplified
palette, improved layout options, and enhanced debugging capabilities. Additionally,
Flow Builder is tightly integrated with Lightning Experience and provides better
support for mobile devices compared to Cloud Flow Designer.

Salesforce Security Model

99. What is the Salesforce security model, and what are its key components?
The Salesforce security model refers to the framework of features and settings that
control access to data and functionality within the Salesforce platform. Key
components include profiles, permission sets, roles, role hierarchy, sharing rules,
organization-wide defaults (OWD), field-level security (FLS).

100. Can you explain the difference between profiles and permission sets in
Salesforce?
Profiles and permission sets are both used to control access to objects, fields, and
records in Salesforce, but they serve different purposes.
 Profiles are assigned to users and define their baseline permissions, such as object-
level and field-level access, record types, and page layouts.
Permission sets are additional sets of permissions that can be assigned to users to
extend their access beyond what is defined in their profile, without changing the
profile itself.

101. How do you control access to records in Salesforce? What are the different
levels of record access?
Access to records in Salesforce is controlled through a combination of settings,
including organization-wide defaults (OWD), role hierarchy, sharing rules, manual
sharing, and criteria-based sharing.
The different levels of record access are private, public read-only, public read/write,
and controlled by parent.

102. What is the role hierarchy, and how does it impact record access in
Salesforce?
The role hierarchy is a representation of the reporting structure within an
organization. It determines the level of access users have to records owned by users
below them in the hierarchy. Users at higher levels in the hierarchy have access to
records owned by users at lower levels, based on their position in the hierarchy.

103. How do you restrict access to certain fields on a Salesforce object?

Field-level security (FLS) allows administrators to restrict access to certain fields on a
Salesforce object. By setting field-level security, administrators can control which
fields users can view and edit, based on their profile or permission set.

104. What is field-level security, and how is it enforced in Salesforce?

Field-level security (FLS) is enforced in Salesforce by controlling access to individual
fields on objects. Administrators can set field-level security permissions for each
profile or permission set, specifying whether users can view or edit each field.

105. Can you describe the purpose of sharing rules and how they are used to
extend record access in Salesforce?
Sharing rules in Salesforce are used to extend record access to users who do not have
access through the role hierarchy or organization-wide defaults. They allow
administrators to define criteria-based or owner-based rules to grant additional
access to specific records.

106. What are the different types of sharing rules available in Salesforce, and
when would you use each type?
There are three types of sharing rules in Salesforce: criteria-based sharing rules,
owner-based sharing rules, and manual sharing. Criteria-based sharing rules use
criteria to determine which records are shared, owner-based sharing rules share
 records owned by certain users, and manual sharing allows users to share individual
records with others.

107. How do you implement object-level security in Salesforce using profiles and
permission sets?
Object-level security in Salesforce is implemented using profiles and permission sets.
Profiles control access to objects, fields, and related records, while permission sets
extend permissions beyond what is defined in profiles. By assigning profiles and
permission sets, administrators can control who can view, create, edit, and delete
records of a particular object.

108. What is the difference between OWD (Organization-Wide Defaults) and

sharing rules in Salesforce security?
OWD (Organization-Wide Defaults) and sharing rules both control record access in
Salesforce, but they operate at different levels. OWD defines the baseline level of
access for all records of an object, while sharing rules provide additional access to
specific records based on criteria or ownership.

109. How do you enforce data security in Salesforce when integrating with
external systems?
Data security when integrating with external systems in Salesforce can be enforced
by using secure APIs, authentication mechanisms such as OAuth or SAML, and data
encryption techniques. Additionally, administrators can control access to external
data sources using profiles, permission sets, and IP whitelisting.

110. What is the difference between CRUD and FLS in Salesforce security?
CRUD (Create, Read, Update, Delete) and FLS (Field-Level Security) are both aspects
of data security in Salesforce. CRUD permissions control the ability to perform basic
operations on objects (such as creating, reading, updating, and deleting records),
while FLS permissions control access to individual fields on objects.

111. How do you audit and monitor user access and changes to data in
Salesforce?
Audit trails in Salesforce allow administrators to monitor user activity and changes to
data. They provide a record of login attempts, successful logins, and changes made to
records by users. Audit trails help organizations track user behaviour and maintain
data integrity.

112. Can you explain the concept of Field Dependency and its role in security?
Field Dependency is a feature in Salesforce that allows administrators to specify
dependencies between fields on an object. This can be used to control visibility and
editability of fields based on the value of another field. Field Dependency can play a
 role in security by ensuring that sensitive fields are only visible when specific
conditions are met.

113. How do you ensure secure data transmission and storage in Salesforce?
Secure data transmission and storage in Salesforce are achieved through various
mechanisms, including encryption, secure sockets layer (SSL) encryption for data in
transit, and field-level encryption for sensitive data at rest. Salesforce also complies
with industry-standard security certifications and undergoes regular security audits
to ensure data protection.

Scenario Based Questions/ FAQ:

114. In a large organization, different departments need varying levels of access

to customer records. How would you design security to ensure that sales
representatives can only view and edit customer records assigned to their region,
while managers have access to all records within their department?
• Define a role hierarchy that reflects the organizational structure, with roles for
sales representatives and managers at appropriate levels.

• Implement OWD (Organization-Wide Defaults) to restrict access to records based

on criteria such as region or department.

• Utilize criteria-based sharing rules to automatically grant access to records

meeting specific conditions.

• Ensure that role hierarchy and sharing rules are regularly reviewed and adjusted
as organizational structure or business requirements change.

115. A sales team is collaborating on a major account, and multiple individuals

need access to the account record. How would you grant access to specific users,
ensuring that only authorized team members can view and modify the account
details?
• Create sharing rules to automatically grant access to the account record based on
criteria such as ownership or record attributes.

• Use manual sharing to explicitly grant access to specific users or roles on an ad-
hoc basis.

116. Certain sensitive fields, such as Social Security numbers and financial
information, should only be accessible to designated users within the finance
 department. How would you configure security to restrict access to these fields,
ensuring that only authorized personnel can view or modify sensitive information?
• Define profiles with appropriate permissions, including field-level security
settings to restrict access to sensitive fields.

• Assign users to profiles based on their roles and responsibilities within the
organization.

• Now using the permission sets, you can authorize the sensitive fields data to user.

117. You company has multiple business units, and you need to ensure that each
unit can only access their own data, with certain users needing access to all data
across all units. How do you set this up?
• First setup OWD as private so that each unit can only access their own data.

• Set up role hierarchies based on business units and use sharing rules or add
specific users to a public group with wider access as needed.

118. Two users, A and B are assigned with same profile and under same role
hierarchy. How can you restrict the records of A from B and vice a versa.
• Using OWD

• Ensure that OWD is private and make sure that users should not have “view All”
& “modify All” permissions on their profile or permission sets that could override
the record level security.

119. You have a large sales team and want to ensure that sales managers can
only see the data if the sales representatives that report to them. How would you
accomplish this in salesforce?
• Implement the role hierarchies where sales representatives are positioned under
their respective sales managers in the hierarchy to naturally control record
visibility base on roles.

120. Your company has recently acquired another company that uses different
salesforce org. How do you ensure that the data is shared between two orgs while
maintaining appropriate security levels?
• Utilize salesforce to salesforce connect to integrate the two orgs, ensuring base
level permissions are defined for data visibility and access.

121. You have a team of sales representatives who need access to certain
customer data but you want to restrict their access to sensitive information such as
credit card numbers. How do you achieve this?
 Use field level security to hide the sensitive fields like account number, password
for those user’s profile and permission sets.

122. What are the condition on which we can see this manual sharing button on
page.
OWD needs to be restrictive then only we can see manual sharing button on
page.
Either private or Read-only then only manual sharing button will be available, for
Public Read/Write manual sharing button will not be available on page.

123. What are the different ways to create the records if object tab is not visible
or available.

124. External auditors need temporary read-only access to the financial records
in the Financials object for an audit. How would you set this up?
• Create a profile or permission set with 'Read-Only' access to the Financials object.
• Use sharing rules to grant read-only access to auditors during the audit period.
• Set an expiration date on the sharing rules or permission set assignments to
ensure access is revoked after the audit is complete.

125. A specific project in the Projects object is highly confidential and should
only be accessible to the project team members. How would you set up the
security for this?
• Set the organization-wide default for the Projects object to 'Private'.
• Manually share the project record with the specific team members.
• Create a public group for the project team and share the project record with this
group.
• Ensure only project team members' profiles have 'Read' and 'Edit' permissions on
the Projects object.

126. A specific project in the Projects object is highly confidential and should
only be accessible to the project team members. How would you set up the
security for this?
• Set the organization-wide default for the Projects object to 'Private'.
• Manually share the project record with the specific team members.
• Create a public group for the project team and share the project record with this
group.
• Ensure only project team members' profiles have 'Read' and 'Edit' permissions on
the Projects object.
127. You need to ensure that sales representatives can only see and edit
opportunities that belong to their own region, while sales managers can see all
opportunities. How would you configure this?
• Set up a role hierarchy where sales representatives report to sales managers.
• Set the organization-wide default for opportunities to 'Private'.
• Create sharing rules to share opportunities with users in the same region.
• Ensure sales managers have the necessary permissions to view and edit all
opportunities.

128. You need to restrict access to salary information in the Employee object so
that only HR personnel can view and edit it. How would you implement this?
• Create a custom profile for HR personnel.
• Assign 'Read' and 'Edit' permissions on the Salary field in the Employee object to
the HR profile.
• Ensure the Salary field is set to 'Visible' and 'Read-Only' for other profiles.
• Define sharing rules if necessary to share records with HR personnel based on
criteria.

129. What is Data skew in Salesforce?

In Salesforce, data skew refers to a situation where the distribution of records
within an object is uneven, leading to performance issues and potential data
access problems. There are three types of data skew

• Account Data Skew: This occurs when a single user owns more than 10,000
account records. Because of the way Salesforce handles sharing rules and record
ownership, having one user own a disproportionately large number of records
can lead to performance degradation and sharing recalculation delays.
• Lookup Skew: Lookup skew happens when a single parent record (such as an
Account or Case) has more than 10,000 child records related to it. This can lead
to locking issues and performance degradation when multiple users attempt to
access or modify related child records.
• Ownership Skew: Ownership skew arises when a single user owns more than
10,000 records of a specific object. Similar to account data skew, this can lead to
performance issues and sharing recalculation delays due to the large number of
records owned by a single user.

130. Two objects are available, and there are a few records present in both
objects. Now, I want to relate both with a master-detail relationship. Will
Salesforce allow me, or will it give some error? If so, how can I achieve this
requirement?
Salesforce will not allow you to create a master-detail relationship directly if
already there are records in either of the objects. This is because master-detail
relationships in Salesforce require a parent-child hierarchy, where the child
 records are dependent on the existence of parent records. If records already exist
in either object, Salesforce cannot establish this hierarchy.

To achieve this requirement, we will first relate both the objects with lookup
relationship now will fill lookup value in each record, once done now we will
convert this lookup relationship to master detail relationship.

131. Master-detail relationship exists between two objects A and B, now the
requirement is that each parent should only have one child related to it. If a user
tries to create more than one child, then they should receive an error indicating
that they cannot create more than one child.
We will achieve this requirement with the combination of rollup summary and
validation rule.

As master detail exist between two objects means we can now take help of rollup
summaries (as can only be created if relationship is master detail).
We will create roll up summary field on master object which give me count of
child records.

Now we will create one validation rule on child object where we will check the
value in the count rollup summary field. Will add the formula if count >1 then we
will throw a validation that already one child exists you cannot create more.

132. Object A contains a picklist field with five different values. The requirement
is that User A should only be able to see the first three values of this picklist out of
the five, while User B should only be able to see the remaining two values. How
can we achieve this?
We will achieve this using the record types.
When we create the Record Types at the time of creation it gives us the option to
edit the picklist fields where you can select the values which you want to make
visible for this record type.
Now based on the user we will assign him record Type permission on profile &
permission sets.

133. What is the difference between deactivate and freeze a user in salesforce?
Deactivate User: When you deactivate a user in Salesforce, you are essentially
disabling their user account. Deactivating a user prevents them from logging into
Salesforce and accessing any records or features within the system. This action is
typically used when an employee leaves the company or no longer requires
access to Salesforce.

Freeze User: Freezing a user is a security feature in Salesforce that temporarily

suspends a user's access to the system, usually due to suspicious activity or to
prevent unauthorized access. When you freeze a user, they are logged out of
 Salesforce immediately, and they cannot log in again until they are unfrozen.
However, their user account remains active, and all their permissions and settings
are preserved. Freezing is often used in response to security breaches or when
investigating potentially fraudulent activity.

134. Can we delete a user in salesforce?

No, deletion of user is not possible in salesforce we can only freeze or deactivate
a user from salesforce.

135. Can a user have more than one role assigned to him?
No, a user can be assigned with single role at a time. Multiple roles cannot be
assigned to a single user at same time.

136. I have 2 users in same role, user A can see the records of user B but user B
cannot see the records of user A. What can be the possible reasons.

Sharing Rules: There might be sharing rules in place that explicitly grant access to
User A for certain records owned by User B. However, no reciprocal sharing rules
might exist for User B to access records owned by User A.
Manual Sharing: User A might have manually shared their records with User B, or
with a group that User B is a member of. However, User B may not have
reciprocated this sharing.
Criteria-Based Sharing: There could be criteria-based sharing rules or criteria-
based sharing settings on objects that grant access to User A based on specific
criteria that are not met for User B's records.
Role Hierarchy: Although both users are in the same role, the role hierarchy
could still be affecting access. Ensure that the role hierarchy is configured
correctly and that User B is not below User A in the hierarchy.

137. How you will be going to make sure that validation rule either only fires at
the time of insertion of records or at the time of updating of records.
Using ISNEW() and ISCHNAGED(), both functions are available in validation
formula.
ISNEW() ensure that to show and error whenever record is new or created.
ISCHANGED() ensure that the existing data or record values are changed so only
fire at the time of updating.

138. What data type of fields can be marked as external id?

Text, Auto Number, Number, Email

139. There is record type for which user U1 is not having the access. Will the user
still be able to see the records which are created by the same user U1 and are
assigned to record type to which user is not having access?
 In Salesforce, if a user does not have access to a particular record type, they will
not be able to view or edit records assigned to that record type, even if those
records were created by users who do have access to that record type.

140. What happens to the related opportunities and contact records when
account is deleted?
Related contacts and opportunities for that account also get deleted with
account.

141. What happens to the related opportunities and contact records when the
account record is undeleted.
Related Contact and opportunities also get undeleted.

142. Who can see the manual sharing button on record page?
System Admin
Record Owner
User Up in Role Hierarchy.
User with ModifyAll and ViewAll access for that object.

143. Can we restrict a user from deleting the record?

Yes, we can here be the possible ways
1. Salesforce Flows
2. Using Apex Triggers
3. By managing delete permission from Profiles and Permission Sets.

144. Different ways to manage the field level security?

1. From Profiles
2. Permission Sets
3. Field Accessibility Settings
4. Using Dynamic Forms

145. What are public groups in salesforce? Why we need them?

Public groups in Salesforce are collections of users, roles, or other groups, created
by administrators to simplify access management and facilitate collaboration.
They are used for sharing records, files, and communication among multiple
users simultaneously.

146. Who is user in salesforce?

A user in Salesforce is an individual who has access to the Salesforce platform.
Users can log in to Salesforce to perform various tasks based on their assigned
permissions, such as accessing records, creating reports, and managing data.
 Each user has a unique username and password and can be assigned to different
roles, profiles, and permission sets, determining their level of access and
functionality within the system.

147. Can we convert Master detail relationship to lookup relationship? If yes,

what factors we need to keep in mind.
Yes, we can do so but we need to take care of points like,
• Make sure that while converting no rollup summary fields are available as they
can only be accessible if relation among objects is master details. If available you
need to delete the same after storing their values/data in some text fields.
• You need to adjust or reconsider all sharing rules and ownerships, as earlier all
are inherited from the master object but in lookup you can also change them.

148. Can we convert lookup relationship to master details relationship? If yes,

what factors we need to keep in mind.
Yes, we can do so. Things to take care of
• Each lookup field should have a value, as in master detail parent is mandatory.
• Cascade delete will be there now in master details so make sure while deleting
any parent record as it will delete related child’s also.

149. Where Public groups are stored?

In Salesforce, public groups are stored in the Group object.

150. If OWD is set as public read/write, can we still create the sharing rules?
No if already OWD is set as public Read/Write this means you already given full
access to users at the base level itself.
Now there is no use of sharing rules and manual sharing.

151. What are different ways to import data in salesforce?

1. Data Import Wizard
2. Data Loader
3. External Objects and External Data Sources
4. Third-Party Tools and Integration Platforms

152. What is junction object in salesforce instead of master detail can we create
junction object using lookup relationship?
Imagine you have two objects in Salesforce: "Student" and "Course." Each
student can enrol in multiple courses, and each course can have multiple
students enrolled.

To represent this relationship, you would create a junction object, let's call it
"Enrolment."
 The "Enrolment" object would have two master-detail relationships:

One to the "Student" object.

Another to the "Course" object.
So, for each enrolment record in the "Enrolment" object, you'd have a specific
student associated with a specific course.

This allows you to manage the many-to-many relationship between students and
courses efficiently. You could also include additional information in the
"Enrolment" object, like enrolment date or grade, to track details specific to each
student's enrolment in a course.

Yes, you can create a junction object using a lookup relationship instead of a
master-detail relationship in Salesforce. However, you won't get features like
automatic ownership and cascade delete, roll-up summary fields, and there
might be differences in performance.

153. Can sharing rule used to restrict the access?

No, sharing rule used to extend the access if OWD is either private or read only.
Base level or the most restrictive access we can provide on OWD for records and
with remaining we can only extend.

154. Can user have different licences if profile assigned to them is same?
Yes, user can be assigned with different licenses even if their profiles are same.

155. How licenses are different from the profiles in salesforce?

Profiles define how users access objects and data, and what they can do within
the application.

A user license determines the baseline of features that the user can access.

Let’s say you have a Sales Cloud license in Salesforce, which grants you access to
sales-related features like leads, opportunities, and forecasts. However, your
profile might restrict you from deleting opportunities or exporting sensitive data.
So, while your license allows you to use Sales Cloud features, your profile
determines exactly what you can do within those features.

156. Explain viewAll and modifyAll permission in salesforce.

We can grant viewAll or modifyAll permission for an object on a profile or using a
permission set. It is an object permission that is found in profiles and allow access
to all records of the object.

View All grants read access to the object and read only access to all records
associated with a given object across the organization.
 Modify All grants read, edit, and delete access to the object and full access to
records within that object.

The “View All” and “Modify All” permissions ignore sharing rules and settings.

157. Two users are there assigned with same profile P1 and Object A is there, for
which read access is given to profile P1 , additional permission set is also assigned
to both users where edit and delete permission is given.
Now the issue is user U1 can delete the record but user U2 is not able to delete
the records. What can be the reason behind this?
Possible reason can be the muting concept.
It might be possible that the user who is still not able to delete the record must
be assigned with the permission set group where muting for the delete access is
done. If yes then the user will not be able to delete the records.

158. Can we create master detail relationship between custom and standard
object?
Yes, we can make but the things which to make sure is that master will always be
standard object here it cannot be child for custom object.

159. What are the different ways to make field mandatory from UI in salesforce?
1. Using Required checkbox at the time of field creation
2. From the page Layout we can make field mandatory
3. Using dynamic forms
4. Validation Rules

160. A profile and object A is there, on profile no CRUD permission is given for
object A but still user able to create the records. What can be the possible reasons
for same?
Permission Set assigned to user where for object A read and create permission is
given, other than this no other possibility because from profile and permission
set, we manage the object level security.

161. Object A is there and profile P1. Same profile is assigned to two user, user
U1 and U2. OWD set for object A is public read and write. Still users are not able to
create the records for object A. What can be the possible reasons?
Will check for the object level permissions i. e profile and permission sets first. If
on object level permission read & create access are not given then record level
security settings will not matter.

162. Object A is there with total 5 fields, now the requirement is whenever user
creates a record all 5 fields should be visible to him and once the record is saved
 now on detail page only 3 fields should be visible to him. How will going to achieve
this?
With the help of page layout and record types will going to achieve this plus with
small automation to change the record type automatically on save.

Create second page layout showing only 3 fields now and record type.
Now as soon as record saves/inserted run a record triggered flow where we will
now change the record type to which page layout assigned showing 3 fields.

163. What is the difference between 15 digit and 18 digits record id in

salesforce?
15-digit character id is a case sensitive version which is referenced in the
salesforce user interface. You can use this ID while performing data operations
through the user interface.

18-character ID is the case insensitive version which is referenced through the

API’s. The case – insensitive ID is identical to the 15-character case sensitive ID,
but with extra characters appended to indicate the casing of each of the original
15 characters.

You will need 18-digit Ids while using tools like Data loader and workbench. The
API tools will accept the 15-character IDs as input but it will always provide you
the 18-character Id when you export data.

It is a salesforce best practices to use 18-character IDs in APIs, formula or as

reference due to its case insensitive nature.

164. No automations are implemented on account record but still the user is not
able to delete the account record. What can be the possible reason?
It might be possible because of the following reasons:
• Account has related opportunities with the status closed won. If yes you cannot
delete the account record.
• Account might be having some related cases which are open if yes again you
cannot delete the account record.

165. A sales representative accidentally deletes a set of important leads. What

steps would you take to recover the deleted records?
I would first check the Recycle Bin to see if the deleted leads are recoverable
from there. If not, I would use Salesforce's data recovery service to restore the
records from a specific point in time, ensuring minimal data loss.

166. A new department needs access to certain reports and dashboards. How
would you ensure that they have the appropriate access without compromising
security?
 I would create a new permission set or profile for the new department and assign
the necessary permissions to access the required reports and dashboards.
Additionally, I would review and adjust sharing settings to ensure that the data
remains secure.

167. A company wants to implement a new custom object to track customer

feedback. How would you go about designing and implementing this object in
Salesforce?
I would start by gathering requirements from stakeholders regarding the fields
and relationships needed for the customer feedback object. Then, I would use
Salesforce's point-and-click tools to create the custom object, fields, page layouts,
and any necessary validation rules or workflows.

168. The marketing team wants to automate the process of sending follow-up
emails to leads who have not responded to previous communications. How would
you set up an automated workflow for this scenario?
I would create a flow that triggers when a lead's status remains unchanged for a
specified period. The rule would then automatically send a predefined email
template to the lead, reminding them to respond. Additionally, I would schedule
regular flow evaluations to ensure timely follow-ups.

169. The company uses an external ERP system to manage inventory. How would
you integrate Salesforce with the ERP system to ensure that inventory data is
synchronized between the two systems?
I would explore options such as using Salesforce Connect, custom integrations
using APIs, or middleware solutions like MuleSoft to establish seamless
integration between Salesforce and the ERP system. I would prioritize data
consistency and real-time synchronization to ensure accurate inventory
management.

170. A new employee joins the company and needs training on using Salesforce.
How would you approach training and supporting the user to ensure they are
proficient in using the platform?
I would develop a comprehensive training plan covering basic navigation, data
entry, and advanced features relevant to the user's role. Additionally, I would
provide access to training resources such as documentation, videos, and sandbox
environments for hands-on practice. Ongoing support would be available through
a dedicated help desk or community forum.

171. Users have been experiencing slow performance when working with large
datasets in Salesforce. How would you diagnose and address this performance
issue?
I would analyse the data model, reports, and customizations to identify any
bottlenecks or inefficiencies. Potential optimizations could include indexing
 frequently used fields, optimizing SOQL queries, reducing the number of
workflow rules or process builder flows, and leveraging caching mechanisms.

172. The company operates in a highly regulated industry and needs to ensure
compliance with data protection regulations. How would you configure Salesforce
to meet these compliance requirements?
I would configure Salesforce's built-in security features such as field-level security,
object permissions, and data encryption to ensure compliance. Additionally, I
would implement audit trails and regularly review security policies to maintain
compliance.

173. The sales manager needs a report that shows the conversion rates at each
stage of the sales pipeline. How would you create this report using Salesforce's
reporting tools?
I would create a custom report using Salesforce's report builder, selecting the
appropriate fields and filtering criteria to analyse the sales pipeline stages. I
would use summary and matrix reports to visualize conversion rates at each
stage, allowing the sales manager to identify areas for improvement.

174. A user reports that they are unable to log in to Salesforce. How would you
troubleshoot and resolve this issue?
I would first check if the user's login credentials are correct and if there are any
active login restrictions or IP restrictions in place. If the issue persists, I would
review login history and debug logs to identify any errors or issues with
authentication. Depending on the cause, I would take appropriate actions such as
resetting the user's password or contacting Salesforce support for further
assistance.

175. A company wants to track donations from individual donors and

organizations separately. How would you design the data model to accommodate
this requirement while maintaining a unified view of donations?
I would create two separate custom objects for individual donors and
organizations, both related to a new custom object for donations. Each donation
record would have a lookup relationship to either the individual donor or
organization, allowing for distinct tracking while still providing a unified view of
donations.

176. A company has a custom object for projects and wants to link them to
customer accounts. Would you use a master-detail or lookup relationship between
the project and account objects? Explain your reasoning.
I would use a lookup relationship between the project and account objects.
Master-detail relationships imply a stronger parent-child dependency and would
not be suitable if projects can exist independently of customer accounts.
177. The company is migrating data from a legacy system into Salesforce. How
would you ensure data integrity and consistency during the import process,
especially for related records with complex relationships?
I would carefully map fields from the legacy system to corresponding fields in
Salesforce, ensuring data consistency and integrity. For related records, I would
use external IDs or unique identifiers to maintain relationships during the import
process.

178. The company wants to track employee hierarchies, including reporting

relationships and organizational structure. How would you design the data model
to represent this hierarchy effectively?
I would create a custom object for employees and use a self-referential lookup
relationship to represent reporting relationships. Additionally, I would consider
using Salesforce's built-in hierarchy features or third-party apps for visualizing
and navigating the organizational structure.

179. A company wants to track warranty information for products sold to

customers. How would you establish relationships between the product, customer,
and warranty objects to ensure accurate tracking and reporting?
I would create a lookup relationship between the product and customer objects
to associate products with specific customers. For tracking warranty information,
I would create a separate custom object for warranties with a lookup relationship
to both the product and customer objects.

180. The company's Salesforce org is reaching its data storage limit. How would
you implement a data archiving strategy to retain historical data while reducing
storage usage and improving system performance?
I would use Salesforce's Data Archiving feature to archive older records based on
predefined criteria such as creation date or last modified date. Archived data
would be retained for compliance purposes while reducing storage usage and
improving system performance.

181. The company wants to ensure that all opportunities have a minimum of
three associated products. How would you enforce this requirement using data
validation rules?
I would create a validation rule on the opportunity object that checks if the count
of associated opportunity products is less than three. If the count is less than
three, the validation rule would display an error message prompting users to add
more products before saving the opportunity.

182. The company experiences slow performance when querying large datasets
due to a complex data model. How would you optimize the data model to improve
query performance without sacrificing functionality?
 I would review the data model to identify any unnecessary relationships or fields
that could be removed or optimized. Additionally, I would consider denormalizing
data or using external objects to offload data storage and processing to improve
query performance.

183. The company offers both products and services and wants to capture
different sets of information for each type of offering. How would you use record
types and page layouts to customize the user experience based on the type of
offering being sold?
I would create separate record types for products and services and customize
page layouts for each record type to display relevant fields and related lists. This
would provide a tailored user experience based on the type of offering being
sold.

184. The company is merging with another organization, and there is a need to
consolidate data from both Salesforce orgs into a single org. How would you
approach migrating and transforming data to ensure compatibility and consistency
across systems?
I would develop a data migration plan outlining the steps for extracting,
transforming, and loading data from both Salesforce orgs into the target org. This
may involve data cleansing, mapping fields between systems, and using tools like
Data Loader or Salesforce's Import Wizard to facilitate the migration process.
Additionally, I would conduct thorough testing to ensure data accuracy and
consistency post-migration.

185. The sales team wants incoming leads to be assigned to sales representatives
in a round-robin fashion to ensure equitable distribution. How would you configure
a lead assignment rule to achieve this?
Create a custom field on the Lead object to calculate the next sales
representative in the round-robin sequence, this field can be updated with the
date and time of lead assigned and accordingly give him the order (like 1,2,3…).
Then, use a lead assignment rule that assigns leads to the sales representative
based on the order which is calculated using date and time lead assigned.

186. Leads should be assigned to sales representatives based on their expertise

and the qualification level of the lead. For example, highly qualified leads should be
assigned to senior sales representatives. How would you configure lead assignment
rules to handle this scenario?
Create lead qualification criteria based on factors such as lead score, lead source,
and demographic information. Use assignment rules that route leads to sales
representatives based on their qualification level and expertise.
187. Leads coming from different sources (e.g., website inquiries, trade shows,
referrals) should be assigned to different sales representatives or teams based on
the lead source. How would you set up lead assignment rules based on lead
source?
Create lead assignment rules with criteria based on lead source fields. Specify the
appropriate sales representative or team for each lead source category to ensure
leads are routed accordingly.
Like for Website inquires – Team A
For Trade show – Team B

Based on the source value assign teams or sales reps

188. Certain leads are more valuable or urgent than others and should be
prioritized for immediate follow-up. How would you configure lead assignment
rules to ensure that high-priority leads are assigned first?
Define lead priority levels based on criteria such as lead score, urgency, and
potential value. Configure lead assignment rules to prioritize high-priority leads
for immediate assignment to sales representatives.

189. Leads should be assigned to sales representatives based on their availability

or workload at specific times. For example, leads received outside of business
hours should be assigned to the on-call sales representative. How would you
configure lead assignment rules to handle time-based assignments?
Configure lead assignment rules with time-based criteria to determine when
leads should be assigned to sales representatives. Use salesforce flows to trigger
lead assignment based on predefined time intervals or business hours.

190. A company is implementing Salesforce for the first time and needs to
migrate existing customer data from their legacy CRM system into Salesforce. How
would you plan and execute the initial data migration process to ensure a smooth
transition?
Use Salesforce data import tools such as Data Loader or Import Wizard to map
and import data from the legacy CRM system into Salesforce. Prioritize data fields
based on business requirements and perform data validation checks to ensure
accuracy.
191. The company's Salesforce org contains duplicate or outdated records that
need to be cleaned up before migrating to a new system or org. How would you
identify and eliminate duplicate records and ensure data quality during the
migration process?
 Use data cleansing tools and techniques to identify and remove duplicate or
outdated records. You can also use the merge DML operations to merge the
duplicates.
Implement data quality rules, duplicates, matching rules, and validation checks to
prevent duplicate data from being entered in the future.

192. Before finalizing the data migration, the company wants to ensure that the
migrated data is accurate and complete. How would you plan and conduct data
validation and testing to identify and resolve any issues or discrepancies?
Develop test plans and scenarios to validate the migrated data against source
data and business requirements. Use Salesforce's data validation tools and
reports to identify and resolve data discrepancies. Involve stakeholders in user
acceptance testing to ensure data accuracy and completeness.

193. After completing the data migration, the company encounters issues or
discrepancies with the migrated data. How would you provide ongoing support and
troubleshooting to address any post-migration issues and ensure data consistency
and integrity?
Provide training and support to users to address any issues or discrepancies with
the migrated data. Establish a process for ongoing data maintenance and cleanup
to prevent data quality issues in the future. Utilize Salesforce's support resources
and community forums to troubleshoot and resolve post-migration issues.

194. What are the factors based on which you will decide whether to establish
master detail or lookup relation between objects.
Here are the key factors:

1. Data Dependency
Master-Detail: Provides strict data dependency where detail records are
owned by master records.
Lookup: Offers more flexibility as child records can exist independently of the
parent.

2. Data Integrity & Security

Master-Detail: Ensures strong data integrity and inherits security settings
from the master object.
Lookup: Provides separate security settings for each object and less tight data
coupling.

3. Roll Up Summary Fields

Master-Detail: Supports roll-up summary fields for calculating aggregate data
from related records.
Lookup: Requires alternative methods for achieving roll-up functionality.
 4. Hierarchical Relationships
Master-Detail: Supports up to two levels of hierarchy.
Lookup: Does not inherently support hierarchical relationships.

5. Flexibility and Limitations:

Master-Detail: More restrictive in terms of field and relationship
modifications.
Lookup: Offers greater flexibility for modifying relationships and fields.

USER STORIES

195. Explain how will you create a cab booking system in Salesforce which
involves setting up a combination of objects, relationships, automation, and logic
to handle the booking process, user management, and discount application.

1. Define Objects & Relationships

User: Standard Salesforce object to represent cab drivers.

Contact: Standard salesforce object to represent customers.

Cab: Custom object to represent the available cabs.

Fields: Cab ID, Model, Capacity, Registration Number, Availability Status.

Booking: Custom object to handle cab bookings.

Fields: Booking ID, Customer (Lookup to Contact), Cab Driver (Lookup to User),
Cab (Lookup to Cab), Pickup Location, Drop Location, Booking Date, Status, Fare.

Discount: Custom object to manage discounts.

Fields: Discount ID, Discount Type (e.g., Percentage, Fixed Amount), Discount
Value, Validity Period, Conditions (e.g., special discounts for specific users).

2. Setup Relationships

Contact-Booking Relationship: Create a Lookup relationship from the Booking

object to the Contact object. This links each booking to a specific customer.

User-Booking Relationship: Create a Lookup relationship from the Booking object

to the User object. This links each booking to a specific cab driver.
 Cab-Booking Relationship: Create a Lookup relationship from the Booking object
to the Cab object. This links each booking to a specific cab.

Contact-Discount Relationship: Create a Lookup relationship (if discounts are

specific to customers) or a junction object to manage many-to-many relationships
if a discount can apply to multiple customers.

3. Create Fields & Logic Discounts

Discount Application:
Use Formula fields or Apex triggers to calculate the discount based on conditions.
Example Formula Field on Booking Object for Discounted Fare.

IF(
NOT(ISBLANK(Discount__c)),
Fare__c - (Fare__c * Discount__r.Discount_Value__c / 100),
Fare__c
)

4. Automate Discount Allocation

Setup Rules like:

Create a rule to automatically apply a discount based on certain conditions (e.g.,
customer category, booking amount).
Example: Apply a 10% discount if the customer is marked as a 'VIP'.
Condition: Customer__r.Category__c = 'VIP'
Action: Update Booking record to set Discount lookup to the relevant discount
record.

5. User Interface
Customize Lightning Record Pages for Contact, User, Booking, and Cab objects to
provide a user-friendly interface for managing bookings and viewing discounts.

6. Reports & Dashboards

Reports:

Create reports to track bookings, revenue, and discounts.

Example: Total discounts given in a month, bookings per customer, revenue from
VIP customers.

Dashboards:
 Create dashboards to visualize key metrics like booking trends, cab utilization,
and discount impacts.

7. Testing & Deployments

• Thoroughly test the system with various user scenarios to ensure the discounts
are applied correctly.
• Use Salesforce's Change Sets or other deployment tools to move your
configurations from a sandbox to production.

196. As an HR manager, I want to manage employee records and track

performance reviews.

1. Object and Field Setup:

Employee: Custom object to manage employee information.

Fields: Employee ID, Name, Department, Job Title, Hire Date, Manager (Lookup to
Employee), Performance Rating.
Performance Review: Custom object to track performance reviews.
Fields: Review Date, Employee (Lookup to Employee), Reviewer, Comments, Rating.

2. Automation:

Flow to remind managers of upcoming performance reviews.

Email Alerts to notify employees and managers when a review is completed.
User Interface:

Employee Management App: A custom Lightning App to view and manage employee
records and performance reviews.

Lightning Record Pages: Customized pages for Employee and Performance Review
objects for easy access and updates.

3. Reporting:

Create reports to track employee performance, review completion rates, and

department-wise performance trends.
Dashboard: Display key HR metrics such as headcount, average performance rating,
and review compliance.

197. As a project manager, I want to track project progress, tasks, and team
collaboration.
1. Object and Field Setup:

Project: Custom object to manage projects.

Fields: Project Name, Start Date, End Date, Status, Budget, Description.

Task: Standard Salesforce object to manage project tasks.

Fields: Task Name, Project (Lookup to Project), Assigned To, Due Date, Status,
Priority.

2. Automation:

Flow to automate task assignment and send notifications when tasks are due or
overdue.
Setup Approval Processes for project budgets or milestone completions.

3. User Interface:

Project Management App: A custom Lightning App to track project timelines, task
status, and team collaboration.
Chatter: Use Chatter for team communication and document sharing within project
records.

4. Reporting:

Create reports to track project progress, task completion rates, and resource
utilization.
Dashboard: Visualize project health with metrics such as project status, completed
vs. pending tasks, and budget vs. actual spend.

198. As a marketing manager, I want to segment my leads and run targeted email
campaigns.

1. Object and Field Setup:

Lead: Standard Salesforce object to manage potential customers.

Fields: Lead Source, Status, Rating, Industry, Email, Campaign (Lookup to Campaign).

2. Automation:

Lead Assignment Rules to distribute leads to the appropriate sales reps based on
criteria such as geography or product interest.
Email Alerts to notify reps when they receive new leads.

3. User Interface:
Marketing Cloud Integration: Connect Salesforce with Marketing Cloud to manage
email campaigns and track engagement.
Lead Views and Reports: Create custom list views and reports to segment leads
based on demographics, behaviour, or lead score.

4. Campaign Management:

Campaigns: Use the Campaign object to manage marketing initiatives, track

responses, and calculate ROI.
Reports: Measure campaign effectiveness by tracking metrics such as open rates,
click-through rates, and conversion rates.
Dashboard: Display key marketing metrics and campaign performance.

199. As a sales manager, I want to track the performance of my sales team and
forecast future sales.

1. Object and Field Setup:

Opportunity: Standard Salesforce object to track sales deals.

Fields: Opportunity Name, Account (Lookup to Account), Stage, Close Date, Amount,
Probability, Forecast Category.

2. Automation:

Sales Process: Define stages for opportunities (e.g., Prospecting, Qualification,

Proposal, Negotiation, Closed Won).
Validation Rules to ensure critical fields are populated before an opportunity can
move to the next stage.
3. User Interface:

Sales Console: A customized Lightning App for sales reps to manage their pipeline,
log activities, and update opportunity stages.

4. Forecasting and Reporting:

Sales Forecasting: Use Salesforce’s forecasting tools to project future sales based on
current pipeline data.
Create reports to track team performance, win rates, and revenue by region.
Dashboard: Visualize sales KPIs such as total pipeline value, closed revenue, and
forecast accuracy.
200. As a customer service representative, I want to manage and resolve customer
complaints efficiently.

1. Object and Field Setup:

Case: Standard Salesforce object to manage customer complaints.

Fields: Case Number, Customer (Lookup to Contact), Subject, Description, Status,
Priority, Resolution Date.

2. Automation:

Case Assignment Rules to automatically assign cases to the appropriate support team
based on criteria such as case type or priority.
Email Alerts to notify the customer when a case is created, updated, or closed.

3. User Interface:

Service Console: A customized Lightning App providing a single interface for

customer service reps to manage cases, access knowledge articles, and view
customer details.

4. Reporting:

Create reports to track case resolution times, open cases by priority, and customer
satisfaction scores.
Dashboard: Display key metrics such as average resolution time and case backlog.

ALL THE BEST…!