**Ketan's SFDC Admin Master Guide**

**A Note from Your Guide:** Hello Ketan! These notes are your roadmap. Salesforce is vast,
but don't be overwhelmed. Learn one concept at a time, practice it in a Developer Edition org
(it's free!), and then move to the next. Consistency is key.

**Part 1: The Foundation - Why Cloud & Salesforce?**

**1. What is Cloud Computing?**

* **Simple Explanation:** Instead of installing software (like Microsoft Office) on your
computer, you access it over the internet. You don't own the servers; you rent the service.
* **Real-Time Example:** Think of Netflix. You don't buy DVDs; you stream movies from
Netflix's servers over the internet. Salesforce is the "Netflix" for business software (CRM).
* **Why it matters for you:** As an Admin, you work entirely in a web browser. You
configure, don't code. The infrastructure is managed by Salesforce, so you focus on building
solutions.

**2. What is Salesforce?**

* It's the world's #1 **Customer Relationship Management (CRM)** platform on the cloud.
* It helps companies manage all their customer information in one place: sales, marketing,
customer service, and more.

**3. Key Salesforce Products (The "Clouds"):**

* **Sales Cloud:** For managing the sales process (leads, opportunities, contacts).
* **Service Cloud:** For customer support (cases, knowledge base).
* **Marketing Cloud:** For email marketing and campaigns (separate platform).
* **Experience Cloud:** For creating customer/partner portals.
* **As an Admin,** you'll primarily work with Sales and Service Cloud.

---

### **Part 2: The Core Concepts - Building Blocks of Salesforce**

**1. Data Model: Objects, Fields, and Records**

* **Object:** Like a database table. It holds a specific type of information.
* **Example:** `Account` (Companies), `Contact` (People), `Opportunity` (Deals).
* **Field:** Like a column in a table. It's a specific piece of data.
* **Example:** On the `Account` object, fields are `Account Name`, `Phone`, `Industry`.
* **Record:** Like a row in a table. It's an actual instance of data.
* **Example:** A record in the `Account` object: `Account Name: "ABC Corp", Phone:
"123-456-7890", Industry: "Technology"`.
* **Real-Time Org Use:** Your sales team needs to track companies they sell to. You use
the standard `Account` object and maybe add a custom field `"Customer Tier"`.

**2. Standard vs. Custom Objects**

* **Standard Objects:** Provided by Salesforce out-of-the-box (e.g., Account, Contact,
Lead, Opportunity, Case).
* **Custom Objects:** Created by you for your business needs.
* **Real-Time Example:** A school needs to track `Student` information or `Course`
enrollment. Since Salesforce doesn't have these, you create custom objects `Student__c`
and `Course__c`.

**3. Relationship between Objects**

* How objects are linked. Crucial for data integrity.
* **Lookup Relationship:** A loose link. (e.g., linking a `Case` to an `Account` - if the
Account is deleted, the Case remains).
* **Master-Detail Relationship:** A tight, parent-child link. The child record cannot exist
without the parent. (e.g., `Opportunity Line Items` cannot exist without an `Opportunity`.
Deleting the Opportunity deletes all its Line Items).

---

### **Part 3: Making it Secure - The #1 Admin Job**

**1. Organization Security**

* **Login Policies:** Setting password complexity, session timeouts.
* **Network Security:** Restricting login to specific IP addresses (e.g., only from office
network).

**2. User Management**

* **Creating Users:** Adding people to your Salesforce org.
* **Profiles:** The *foundation* of security. It controls:
* **Object Permissions:** Can the user See, Create, Edit, Delete, View All, Modify All
records for an Object?
* **Field Permissions:** Can they See or Edit a specific field?
* **App Permissions:** Can they use Chatter, export data, etc.?
* **Real-Time Example:** A `Sales Profile` has Read/Write on Accounts, Contacts,
Opportunities. A `Read-Only Profile` has only Read access.

**3. Permission Sets**

* *Add-on* permissions to a user's profile. Used to grant extra access without changing
their main profile.
* **Real-Time Example:** Everyone has a `Standard User` profile. You grant a permission
set `"Export Data"` only to the managers who need to export reports.

**4. Field-Level Security (FLS)**

* Controls visibility and editability of individual fields, regardless of page layout. Defined in
Profiles/Permission Sets.

**5. Record-Level Security: The Big One**

* Who can see which records? Controlled by a combination of **Sharing Model** and
**Org-Wide Defaults (OWD)**.
* **Org-Wide Defaults (OWD):** The baseline access for all records. You set it to Private,
Public Read-Only, or Public Read/Write.
 * **Example:** OWD for `Opportunities` is set to `Private`. This means users can only
see opportunities they own, unless you grant more access.
* **Sharing Tools (to open up access beyond OWD):**
* **Role Hierarchy:** Users higher in the hierarchy (e.g., Managers) get access to
records owned by users below them (e.g., Reps).
* **Sharing Rules:** Exception-based sharing to share records between users in different
roles or public groups. (e.g., Share all `Cases` from the 'West' territory with all members of
the 'West Support Team' public group).
* **Manual Sharing:** An owner manually sharing a single record with another user or
group.
* **Real-Time Org Scenario:** OWD for `Cases` is `Private`. The `Support Manager` (top of
role hierarchy) can see all cases. A `Sharing Rule` shares all 'High' priority cases with the
'Premium Support Team' group for faster response.

---

### **Part 4: Making it Useful - Automation & Business Logic**

**1. Validation Rules**

* "Data quality police." They prevent users from saving bad data.
* **Real-Time Example:** Rule on `Opportunity`: "If Stage is 'Closed Won', then the `Close
Date` must be today or in the past." If a user tries to save a won opportunity with a future
date, an error message pops up.

**2. Formula Fields**

* A read-only field that calculates a value on the fly based on other fields.
* **Real-Time Example:** A `Contact` formula field named `"Full Name"` that automatically
concatenates `First Name` and `Last Name`.

**3. Approval Processes**

* Automates the process of getting a record approved.
* **Steps:** 1) Submit for approval, 2) Email sent to approver, 3) Approver
approves/rejects, 4) Record is updated based on outcome.
* **Real-Time Example:** Any discount on an `Opportunity` over 20% must be approved by
the Sales Director.

**4. Workflow Rules (Legacy - Being Phased Out)**

* Automated actions based on rules. (Use Flow instead for new automation).
* **Example:** When a `Case` status is changed to 'Escalated', send an email alert to the
manager.

**5. Process Builder (Legacy - Being Phased Out)**

* A more powerful, visual version of Workflow Rules.

**6. Flow: The Future of Automation**

* The most powerful and recommended tool. It's a visual tool for building complex business
processes.
* **Types:**
 * **Screen Flow:** Guides users through a series of screens to collect input and
create/update records. (e.g., a guided "New Customer Onboarding" form).
* **Record-Triggered Flow:** Runs in the background when a record is created, updated,
or deleted. (Replacing Workflow and Process Builder).
* **Real-Time Example:** When a new `Lead` from a specific website is created, a Flow
automatically assigns it to the right sales rep based on territory, creates a related Task, and
posts a Chatter message.

---

### **Part 5: Making it User-Friendly - The Interface**

**1. Apps**
* A grouped set of tabs and functionality for a specific purpose.
* **Real-Time Example:** You create a "Service Console" app for your support team
containing tabs for `Cases`, `Contacts`, `Knowledge`, and `Reports`.

**2. Page Layouts**

* Control the organization of fields, related lists, and sections on a record's detail page.
* **Real-Time Example:** The page layout for `Account` for the Sales team has the `Annual
Revenue` field, while the layout for the Support team hides that field and shows the `Open
Cases` related list more prominently.

**3. Record Types**

* Allow you to have different business processes, page layouts, and picklist values for the
same object.
* **Real-Time Example:** The `Account` object has two record types: `Customer` and
`Partner`. `Customer` accounts use one page layout and a sales process, while `Partner`
accounts use a different layout and a partnership process.

**4. Lightning App Builder**

* A drag-and-drop tool to build custom Home Pages and Record Pages with components
like Charts, Related Lists, and custom Lightning components.

---

### **Part 6: Making Sense of Data - Reports & Dashboards**

**1. Reports**
* How you get data out of Salesforce.
* **Tabular:** Simple list (like a spreadsheet).
* **Summary:** Group rows by a field (e.g., Opportunities summarized by Stage).
* **Matrix:** Group by both rows and columns (e.g., Opportunities by Owner (rows) and by
Stage (columns)).
* **Joined:** Combine data from two related objects.
* **Real-Time Org Use:** A `Summary Report` showing "All Open Opportunities grouped by
Sales Rep."
**2. Dashboards**
* A visual display of key reports with charts and metrics. Gives a real-time snapshot of the
business.
* **Real-Time Example:** A "Sales Manager Dashboard" with: a funnel chart of
opportunities by stage, a gauge showing total pipeline value, and a bar chart of sales by rep.

---

### **Part 7: Beyond the Basics - Key Additional Topics**

**1. Data Management**

* **Data Import Wizard:** Import data for standard objects (up to 50,000 records). Easy to
use.
* **Data Loader:** For large data imports (millions of records), updates, or deletions. More
powerful, command-line based.

**2. Sandboxes**
* Copies of your production (live) org used for testing and development. You NEVER test in
production.
* **Types:** Developer, Developer Pro, Partial Copy, Full Copy.

**3. Change Management (Deployment)**

* The process of moving configurations/code from a Sandbox to Production.
* **Change Sets:** The declarative (clicks-not-code) way to deploy. Good for small
changes.
* **DevOps Center / Salesforce CLI:** The modern, recommended way for larger teams
and more complex deployments.

**4. Lightning Experience vs. Salesforce Classic**

* **Classic:** The old interface.
* **Lightning Experience (LEX):** The modern, sleek, and powerful interface. This is what
you will admin and what companies use now. Focus all your learning here.

---

### **Part 8: Ketan's SFDC Admin Interview Prep (100+ Q&A)**

**Section A: General & foundational (10)**

1. **What is Salesforce?**
* A: A cloud-based CRM platform that helps businesses manage customer information,
sales, service, and marketing.
2. **What is a CRM?**
* A: Customer Relationship Management - a strategy and system for managing a
company's interactions with current and potential customers.
3. **What is the difference between a Profile and a Permission Set?**
* A: A Profile is the core set of permissions a user *must* have. A Permission Set is a
group of *additional* permissions that can be granted to users on top of their profile.
4. **What is a Role Hierarchy used for?**
 * A: It primarily controls record visibility. Users higher in the hierarchy automatically get
Read/Edit access to records owned by users below them.
5. **What are the different types of objects in Salesforce?**
* A: Standard Objects (pre-built by Salesforce) and Custom Objects (created by admins
for specific business needs).
6. **Explain the difference between a Lookup and a Master-Detail relationship.**
* A: Lookup is a loose relationship. Deleting the parent doesn't delete the child.
Master-Detail is a tight relationship where the child record cannot exist without the parent,
and it inherits sharing and security from the parent.
7. **What is a Validation Rule? Give an example.**
* A: It ensures data quality by preventing users from saving invalid data. Example:
`ISPICKVAL(Stage, "Closed Won") && CloseDate > TODAY()` would prevent saving a won
opportunity with a future close date.
8. **What is a Sandbox and why is it important?**
* A: A copy of the production org used for testing, development, and training. It's crucial
to test changes in a sandbox before deploying to production to avoid breaking the live
system.
9. **What is a Record Type?**
* A: It allows you to have different business processes, page layouts, and picklist values
for different categories of the same object.
10. **What is the difference between Lightning Experience and Classic?**
* A: Lightning Experience is the modern, component-based user interface with enhanced
productivity features. Classic is the older interface. Salesforce is innovating only in Lightning.

**Section B: Security & Access (15)**

11. **What are Organization-Wide Defaults (OWD)?**
* A: They define the baseline level of access users have to each other's records. They
can be set to Private, Public Read Only, or Public Read/Write.
12. **If OWD for an object is set to Private, how can you open up access?**
* A: Using Role Hierarchy, Sharing Rules, Territory Management, Teams, and Manual
Sharing.
13. **What is the purpose of a Sharing Rule?**
* A: To automatically make exceptions to the OWD to share records with users who
wouldn't normally have access, based on criteria (e.g., share all Accounts in the 'East'
territory with the 'East Sales' public group).
14. **What is Field-Level Security (FLS)?**
* A: It controls whether a user can see or edit a particular field on an object, regardless of
the page layout. It's controlled in Profiles and Permission Sets.
15. **What is the difference between "View All" and "Modify All" permissions at the object
level in a Profile?**
* A: "View All" allows a user to see all records of that object, overriding all sharing rules.
"Modify All" allows them to see and edit all records.
16. **What is a Public Group? Where is it used?**
* A: A collection of users, roles, territories, or other groups. It's primarily used as a
recipient in Sharing Rules.
17. **Explain how a record gets shared via the Role Hierarchy.**
* A: A Manager (higher in the hierarchy) will have Read/Edit access to all records owned
by their direct and indirect reports (users below them).
18. **What is a delegated admin?**
* A: A user who has permission to manage specific sets of users (e.g., reset passwords,
assign profiles) without needing full System Administrator permissions.
19. **What is the purpose of the "Grant Access Using Hierarchies" checkbox on OWD?**
* A: When checked, the role hierarchy is enforced. When unchecked, the hierarchy is
ignored for this object, and users can only see records they own or that are explicitly shared
with them.
20. **What are the different license types in Salesforce? Name a few.**
* A: Salesforce, Salesforce Platform, Identity, Company Community, Customer
Community, etc. A license determines which features and objects a user can access.
21. **How do you restrict login access to specific IP addresses?**
* A: Using the Network Security settings in Setup. You define trusted IP ranges.
22. **What is Two-Factor Authentication (2FA) and why is it important?**
* A: An extra layer of security requiring a password and a verification code from a mobile
app. It's crucial for protecting sensitive customer data.
23. **What is the difference between a permission set and a permission set group?**
* A: A permission set group is a collection of permission sets that can be assigned to
users together, making management easier.
24. **What is a restriction rule?**
* A: (Newer feature) It filters the records a user can access *from a permission set or
group*, even if other sharing rules would grant them access. It *only subtracts* access,
never adds it.
25. **How would you handle a scenario where a user can see an Account but not a Contact
related to that Account?**
* A: The most likely cause is that the OWD for Contact is Private, and the user is not the
owner of the Contact, nor do any sharing rules grant them access to it. The sharing is
controlled per object.

**Section C: Automation & Logic (20)**

26. **What is a Flow?**
* A: Salesforce's powerful automation tool for building complex business processes that
guide users or automate tasks in the background.
27. **What is the difference between a Before-Save and an After-Save record-triggered
flow?**
* A: Before-Save flows execute before the record is saved to the database. They are
faster and used for data validation and defaulting field values. After-Save flows execute after
the record is saved and can perform actions like creating related records or sending emails.
28. **What automation tool would you use to send an email when a field is updated?**
* A: A Record-Triggered Flow (After-Save).
29. **When would you use a Process Builder vs. a Flow?**
* A: For new automation, you should always use Flow. Process Builder is a legacy tool.
30. **What is the purpose of a Formula Field?**
* A: To display a read-only, calculated value based on other fields, expressions, or
functions.
31. **What is a Roll-Up Summary Field? On which relationship can it be created?**
* A: It performs calculations (COUNT, SUM, MIN, MAX) on the records of a child object.
It can only be created on a Master-Detail relationship.
32. **What is a Cross-Object Formula Field?**
 * A: A formula field that references fields from a parent record (via a lookup relationship).
33. **Name some common automation tools in Salesforce.**
* A: Flow, Process Builder, Workflow Rules, Validation Rules, Approval Processes,
Escalation Rules, Assignment Rules.
34. **What is an Approval Process?**
* A: An automated process for routing records to approvers and then taking action based
on their approval or rejection.
35. **What are the key steps in building an Approval Process?**
* A: Define entry criteria, specify approvers (e.g., manager, role, user), define approval
actions (what happens on approve/reject), and finally rejection actions.
36. **What is an Assignment Rule?**
* A: Used to automatically assign record ownership (e.g., Leads or Cases) to a user or
queue based on defined criteria.
37. **What is an Escalation Rule?**
* A: Used on Cases to automatically change the case owner or notify someone if a case
remains unaddressed for a specified time.
38. **Can a Flow call an Apex class?**
* A: Yes, an Autolaunched or Invocable Method flow can call an Apex class for more
complex logic that isn't possible declaratively.
39. **What is a Schedule-Triggered Flow?**
* A: A flow that runs at a specified time (e.g., daily, weekly) to perform actions on a batch
of records that meet certain criteria.
40. **What is the difference between a Screen Flow and a Record-Triggered Flow?**
* A: A Screen Flow has a user interface (screens, inputs, buttons) and is launched by a
user. A Record-Triggered Flow runs automatically in the background when a record is
created, updated, or deleted.
41. **How do you debug a Flow that isn't working?**
* A: Use the **Debug** button on the Flow builder. You can provide a test record ID and
step through the flow's execution to see where it fails.
42. **What is a Flow Trigger?**
* A: It's the order of execution for multiple automations (Flows, Processes, triggers) on
the same object and event. You can use the `Flow Trigger Explorer` to manage the order.
43. **What is a Custom Permission? How is it used?**
* A: A custom setting that defines a specific user ability. It can be assigned via
Permission Sets and then checked in Formulas, Flows, or Apex to control logic.
44. **What is a Dynamic Form? Dynamic Choice?**
* A: **Dynamic Form** allows you to show/hide fields and sections on a Lightning Record
Page based on rules. **Dynamic Choice** filters the available values in a picklist based on
rules. Both are features of the Lightning App Builder.
45. **What is an Action? Name the types.**
* A: Buttons or menu items that let users perform tasks. Types: Quick Actions,
Object-Specific Actions, Global Actions.

**Section D: Data Management & Analytics (15)**

46. **How would you import 50,000 Leads into Salesforce?**
* A: Use the **Data Loader** because the Data Import Wizard has a limit of 50,000
records for standard objects, and Data Loader is more robust for large volumes.
47. **What is the difference between the Data Import Wizard and Data Loader?**
 * A: The Wizard is a UI-based tool in Setup for simpler imports of up to 50k records. Data
Loader is a client application for large, complex data operations (import, export, update,
delete, upsert).
48. **What is an Upsert operation?**
* A: It either updates an existing record or inserts a new one if no match is found. It uses
an external ID field to match records.
49. **What is an External ID field?**
* A: A custom field marked as "External ID." It has unique indexing and is used to upsert
data and create relationships via Data Loader.
50. **What is a report type?**
* A: It defines the set of records and relationships available for a report (e.g., "Accounts
with Contacts" report type lets you report on fields from both objects).
51. **What is a Bucket Field in a report?**
* A: A way to group report values without creating a custom formula field on the object.
(e.g., you can bucket `Annual Revenue` into ranges like "Small," "Medium," "Large").
52. **What is a Joined Report?**
* A: A report that combines two or more report blocks (e.g., one block for Opportunities,
another for Cases) to show unrelated data side-by-side.
53. **How do you schedule a report to run and be emailed automatically?**
* A: From the report tab, use the "Subscribe" button to set a schedule and specify
recipients.
54. **What is a Dashboard Filter?**
* A: It allows viewers to change the context of the entire dashboard (e.g., filter the whole
dashboard by a specific date range or sales region).
55. **What is a Dynamic Dashboard?**
* A: A dashboard that displays data based on the viewing user's access and
permissions. Non-dynamic dashboards run under the security context of the dashboard
owner.
56. **How do you ensure a report only shows data a user is allowed to see?**
* A: Reports respect the org's sharing settings and security model. A user will only see
records in a report that their profile, permission sets, and sharing rules allow them to see.
57. **What is the purpose of the "Report Folder" security?**
* A: It controls who can view, edit, or manage the reports inside that folder. A user needs
access to the folder to see the reports within it.
58. **What are the options for exporting data from Salesforce?**
* A: The Export button on reports (for up to 50k records), the Data Export service in
Setup (weekly/monthly full backup), and Data Loader (for on-demand full exports).
59. **What is data validation, and why is it important before an import?**
* A: The process of checking your source data for errors (duplicates, wrong formats,
missing required fields) to ensure a clean, successful import.
60. **What is a duplicate rule?**
* A: A rule that prevents users from creating duplicate records by comparing new and
edited records with existing ones.

**Section E: User Interface & Experience (15)**

61. **What is a Lightning App?**
* A: A customized set of tabs and navigation for a particular group of users (e.g., a
"Recruiting App" for HR with tabs for Jobs and Candidates).
62. **What is the Lightning App Builder?**
* A: A drag-and-drop tool for building and customizing Home Pages and Record Pages
with components.
63. **What is the difference between a Home Page and a Record Page?**
* A: A Home Page is the landing page for an app. A Record Page is the layout for a
specific record type (e.g., the page you see when you view an Account).
64. **How do you assign a different page layout to different users?**
* A: Use **Record Types** and **Profiles**. You assign a page layout to a record type,
and then assign that record type to a profile.
65. **What is a List View?**
* A: A saved list of records that meet certain filter criteria (e.g., "My Open Opportunities").
66. **What is a Global Action?**
* A: A Quick Action that is available globally across the org, not tied to a specific object
(e.g., a "New Task" action available from the navigation bar).
67. **What is a Compact Layout?**
* A: Defines the key fields that appear in the highlights panel at the top of a record page
and in lookup search results.
68. **What is the Utility Bar?**
* A: A persistent bar at the bottom of the Service Console app that provides tools like a
Notes component, Calculator, or a custom utility item.
69. **What is a Kanban view?**
* A: A visual view of records (e.g., Opportunities) that you can drag and drop between
columns (e.g., stages like Prospecting, Negotiation, Closed Won).
70. **How do you make a field required?**
* A: Two ways: 1) Mark it as `Required` in the field definition (enforced at the database
level), or 2) Add it to the page layout and mark it as `Required` on the layout (enforced at the
UI level).
71. **What is the purpose of the "Lightning Experience" toggle in Setup?**
* A: To control which users can access Lightning Experience. You can hide the switch
and lock users into their preferred experience.
72. **What are AppExchange Packages?**
* A: Pre-built applications or components built by Salesforce partners that can be
installed into your org to extend functionality.
73. **What is a Managed Package vs. an Unmanaged Package?**
* A: A **Managed Package** is from the AppExchange and is upgradeable and protected
from modification. An **Unmanaged Package** is typically used for code/configuration
migration and is not protected or upgradeable.
74. **How would you improve user adoption of Salesforce?**
* A: By providing training, simplifying page layouts, creating useful automation to save
them time, building valuable reports/dashboards, and gathering continuous feedback.
75. **What is In-App Guidance?**
* A: Tools (like Walkthroughs and Checklists) that help you create interactive tutorials for
users directly within Lightning Experience, guiding them through processes.

**Section F: Deployment & Maintenance (10)**

76. **What is a Change Set?**
* A: A package of customizations (metadata) that can be sent from one sandbox to
another (usually to production) for deployment.
77. **What are the limitations of Change Sets?**
* A: They are one-directional (only from sandbox to production), don't track history well,
and are not ideal for team development or rollbacks.
78. **What is the DevOps Center?**
* A: A click-based, graphical interface for managing application lifecycle management
(ALM) and deployments, promoting collaboration between admins and developers.
79. **What is a Release Process?**
* A: A formal process for testing and deploying changes (e.g., Dev -> QA -> UAT ->
Production).
80. **What is a Test Class and why is it important for deployment?**
* A: Code that tests other Apex code. For any deployment containing Apex, you must
have at least 75% test coverage. (As an Admin, you'll work with developers on this).
81. **What is the purpose of the "Modify All Data" permission?**
* A: It gives a user the ability to perform all data operations (create, read, edit, delete,
export) on all data in the org, overriding all sharing settings. It is extremely powerful and
should be granted sparingly.
82. **How do you monitor user login history?**
* A: In Setup, use the `Login History` page. You can also create reports on the
`LoginEvent` object.
83. **What is Setup Audit Trail?**
* A: A log that tracks the last 6 months of changes made in Setup, including who made
the change and when. It's crucial for security and auditing.
84. **What is Health Check?**
* A: A tool that compares your org's security settings to Salesforce's baseline standards
and provides a score and recommendations for improvement.
85. **When would you use the "View Setup and Configuration" permission?**
* A: It allows a user to view Setup pages but not make changes. Useful for giving
auditors or managers read-only access to configuration.

**Section G: Scenario-Based / Real-World (15+)**

86. **A user says they can't see a recently created custom field. What do you check?**
* A: 1) Is the field added to their page layout? 2) Is FLS for that field set to "Visible" for
their Profile/Permission Set?
87. **A manager reports they cannot see the records of their subordinates. What do you
check?**
* A: 1) Check the Role Hierarchy - is the manager placed above their subordinates? 2)
Check the OWD for the object - is it Private? 3) Is the "Grant Access Using Hierarchies" box
checked for that object?
88. **A user complains about getting duplicate leads. How can you help?**
* A: Implement or tighten **Duplicate Rules** for the Lead object.
89. **How would you automate the creation of a follow-up task when an Opportunity is
closed won?**
* A: Create an **After-Save Record-Triggered Flow** on Opportunity. The entry condition
is `ISCHANGED(StageName) && ISPICKVAL(StageName, 'Closed Won')`. The flow action
would be to Create a new Task record.
90. **A sales rep wants a button to quickly update an Opportunity Stage to "Closed Lost"
and populate a reason. How do you build this?**
 * A: Create a **Screen Flow** with a picklist for the reason. Use the flow to update the
Opportunity record. Embed the flow on the Opportunity page layout using the **Flow**
component.
91. **Users are entering dates in the wrong format. How do you fix this?**
* A: Use a **Validation Rule** on the date field to enforce the correct format using the
`ISBLANK(DATEVALUE(field))` function or a regex in a formula.
92. **How would you build a report showing all Opportunities closed in the current quarter by
sales rep?**
* A: Create a report on Opportunities. Use a filter: `Close Date = THIS QUARTER`.
Group the report by `Owner Name` and use a chart to visualize.
93. **A new support agent should only be able to edit Cases they own, but view all Cases in
their queue. How do you set this up?**
* A: OWD for Cases = `Private`. Add the user to a **Queue**. Create a **Sharing Rule**
to share all cases owned by the queue with the queue members. The agent will see their
own cases (ownership) and all queue cases (via sharing rule).
94. **A custom object `Project__c` has a master-detail relationship to `Account`. Who can
see the `Project__c` records?**
* A: The visibility of the child (`Project__c`) is determined by the sharing settings of the
parent (`Account`). If a user can see the Account, they can see all its related Projects.
95. **How would you mass transfer all accounts from a rep who is leaving to a new rep?**
* A: Use the **Data Loader** to export all Accounts owned by the old rep, update the
`OwnerId` field to the new rep's ID, and then use the Data Loader to update the records.
96. **A formula field is not calculating correctly. What do you do?**
* A: Check for syntax errors. Check that all referenced fields are present and have data.
Use the "Check Syntax" button. Test the formula logic with sample data.
97. **A Flow is failing. What are your first steps to debug?**
* A: Use the **Debug** button in the Flow builder. Check the **Pause & Interview**
resources in Setup to see where past interviews have failed.
98. **What would you do in the first week as a new Salesforce Admin?**
* A: 1) Get login access and review current configuration (Objects, Fields, Flows). 2)
Review Security setup (Profiles, Permission Sets, OWD). 3) Meet with key business
stakeholders to understand their processes and pain points. 4) Explore the reports and
dashboards in use.
99. **How do you stay updated with Salesforce releases?**
* A: Review the **Release Notes** three times a year (Spring, Summer, Winter). Watch
`Trailhead` videos, attend local `User Groups`, and follow Salesforce influencers on social
media.
100. **Why do you want to be a Salesforce Admin?**
* A: (Your answer) I enjoy problem-solving, working with technology to make business
processes more efficient, and I find it rewarding to enable users to do their jobs better with
the platform.

---

### **Final Advice & The PDF**

Ketan, these notes are your foundation. To truly learn:

1. **Get Hands-On:** Sign up for a free [Developer Edition
org]([Link] Break things and fix them!
2. **Use Trailhead:** This is **non-negotiable**. It's Salesforce's free learning platform. Do
all the Admin beginner trails.
3. **Join the Community:** Sign up for the [Trailblazer
Community]([Link] Ask questions.

**Regarding the PDF:** I, as an AI, cannot directly generate a downloadable PDF file.
However, you can easily create one yourself.

* **Best Method:** Copy all this text.

* Open Google Docs or Microsoft Word and paste it in.
* Use the formatting tools to create headings, bullet points, and a table of contents.
* Once formatted, go to **File > Download > PDF (.pdf)**.

You now have your personalized guide. Good luck, Ketan! You can do this.