🔵 Cloud Computing & Salesforce Basics

1. What is Cloud Computing?

Cloud computing is the delivery of computing services (servers, storage, databases, networking,
software, analytics) over the internet ("the cloud") to offer faster innovation, flexible resources,
and economies of scale.

2. What is PaaS, SaaS, IaaS?

 PaaS (Platform as a Service): Provides tools and services for application development
(e.g., Salesforce Platform, Heroku).

 SaaS (Software as a Service): Software hosted on the cloud and accessed via the
internet (e.g., Gmail, Salesforce CRM).

 IaaS (Infrastructure as a Service): Provides virtualized computing resources over the

internet (e.g., AWS EC2, Azure VM).

🔵 Sandbox in Salesforce

3. What is Sandbox and the types in Salesforce?

A sandbox is a copy of the production org used for development, testing, and training.

 Developer Sandbox – for coding & testing.

 Developer Pro Sandbox – more storage than Developer.

 Partial Copy Sandbox – includes sample data (config + subset of data).

 Full Sandbox – full copy of production (config + all data).

🔵 Salesforce Objects & Relationships

4. What is an Object in Salesforce?

Objects are database tables that allow you to store data specific to your organization (e.g.,
Account, Contact).

5. Different types of object relationships:

 Lookup Relationship

 Master-Detail Relationship

 Many-to-Many (via Junction Object)

  Hierarchical (only on User object)

6. What is Master-Detail Relationship?

A tightly coupled relationship where child records are dependent on the parent. If the parent is
deleted, the child is also deleted.

7. What is a Junction Object?

A custom object with two master-detail relationships, used to create many-to-many
relationships.

8. How many Lookup Relationship fields can be created in an object?

Up to 40 lookup relationship fields per object.

🔵 Fields & Security

9. What is a Roll-up Summary Field?

A field on the master record that calculates values (SUM, MIN, MAX, COUNT) from related child
records.

10. How many ways to create Roll-up Summary field?

 Standard Roll-up field (only in Master-Detail)

 Declarative Lookup Rollup Summaries (AppExchange tool)

 Apex trigger-based roll-ups

11. What is Field Dependency?

Controlling values in one picklist based on another (Controlling → Dependent field).

12. Difference between Role and Profile:

 Profile: Defines object-level and field-level access. Mandatory.

 Role: Defines record-level access through the role hierarchy. Optional.

13. What are Permission Sets?

A collection of settings and permissions to grant users access to functionality without changing
their profile.

14. Use of Muting Permission Set in Permission Set Group:

Used to remove (mute) specific permissions from a permission set group.

🔵 Sharing, Audit & Data

15. How many ways can we share a record?

 Role hierarchy

 Sharing rules

 Manual sharing

 Apex managed sharing

 Team access

 Territory sharing (if enabled)

16. What are Audit Fields in Salesforce?

System fields like CreatedDate, CreatedBy, LastModifiedDate, LastModifiedBy, etc.

17. What is an Audit Trail?

Tracks the 20 most recent setup changes for your org.

🔵 Queues, Groups, and Dashboards

18. What is a Queue in Salesforce?

A group of users that can own and work on records (Leads, Cases, etc.).

19. What is a Public Group?

A set of users, roles, or other groups used for record sharing, folder access, etc.

20. Static vs Dynamic Dashboards:

 Static: Shows data from a fixed user's perspective.

 Dynamic: Shows data according to the logged-in user.

🔵 Reports & Activities

21. Types of Reports:

 Tabular

 Summary

 Matrix

 Joined
22. What is Report Type?
Defines which objects and fields are available in a report.

23. WhoId vs WhatId in Activities:

 WhoId: Refers to a Contact or Lead.

 WhatId: Refers to an Account, Opportunity, or custom object.

24. What is a Bucket Field?

Used to group report records without a formula or field.

25. Ways to clean data in Salesforce:

 Duplicate Rules

 Validation Rules

 Data.com (Retired)

 Third-party tools (DemandTools, Cloudingo)

 Data loader cleanup

 Flows for mass update

🔵 Data Tools & Considerations

26. Import Wizard vs Data Loader:

 Import Wizard: UI-based, limited objects, up to 50,000 records.

 Data Loader: CLI & UI-based, all objects, up to 5 million records.

27. What is Data Skew?

Occurs when many records are assigned to one user or owner, causing performance issues.

28. What is Cascade Deletion?

In master-detail, when parent is deleted, all child records are also deleted.

🔵 Automation & Flow

29. What is a Flow?

A tool to automate business processes with clicks.

30. Types of Flows:

  Screen Flow

 Record-Triggered Flow

 Scheduled Flow

 Autolaunched Flow

 Platform Event-Triggered Flow

31. Common global variables in formulas/validations:

 $User, $Profile, $Organization, $RecordType, $Setup

32. Edit Read-Only fields?

Yes, using “Set Audit Fields and Update Records with Inactive Owners” permission during data
migration.

🔵 UI and UX Behavior

33. Object-Specific vs Global Actions:

 Object-Specific: Appears only on specific record pages.

 Global: Available throughout the app.

34. Impact before deleting a Role:

Users below that role might lose record access due to role hierarchy.

35. Circular hierarchy case:

If a1 is parent of a2, and you try to make a2 parent of a1, it will throw an error to prevent
circular reference.

36. Pass current record ID to screen flow:

Use flowName?recordId={!Record.Id} or RecordId variable in button.

37. Check org release version:

Go to Setup → Company Information → Instance → Trust.salesforce.com to check release.

🔵 Advanced Features

38. What is a Big Object? Example?

Used to store massive volumes of data.

 Example: FieldHistoryArchive (standard big object for field history).

39. Formula field in Roll-up Summary?
Yes, but only if the formula is on the child object and doesn’t reference another object.

40. Clone a record - default value on hidden field?

Default value is not applied during clone; the value from original record is copied.

41. Considerations before deleting approval process:

 Check related workflow/flow/record updates.

 Deactivate first before deleting.

42. What happens during lead merging?

Child objects are reassigned to master lead, duplicates are deleted, audit is retained on master.

🔵 Debugging & Admin Edge Cases

43. What is Apex Hammer?

Internal Salesforce process to test all Apex code in managed packages during releases.

44. Convert 15-digit to 18-digit ID in formula:

Use custom formula or external tools; native formula support is limited.

45. Hard delete with Data Loader?

Yes, use the "Hard Delete" option.

46. Validation error in screen flow?

Yes, using Display Text or Custom Validation with decision element.

47. Custom object not visible in report builder?

Ensure “Allow Reports” is checked in the object settings.

48. Permission Set Group statuses:

 Enabled, Muted, Disabled, Assigned

49. Enable Email Approval Response:

Enable from Process Automation Settings.
Keywords: Approve, Yes, Reject, No, Denied.

50. Can't create List Custom Settings:

Enable “Manage Custom Settings” permission.

51. View Converted Leads?

Yes, using “View and Edit Converted Leads” permission.
52. Can't convert Master-Detail to Lookup:
Conversion is blocked if child records exist or if the object is a junction.

53. User can't create Campaigns:

Check Marketing User checkbox on the User record.

54. Delete a Public Group:

You must remove it from sharing rules, queues, etc., or you'll get an error.

55. Delete a Queue:

Must unassign it from assignment rules, workflow rules, and ensure no records are assigned to
it.

🔷 CLOUD & SANDBOX BASICS

1. What is Cloud Computing?

Cloud computing is the delivery of computing services (servers, storage, databases, networking,
software) over the internet. Key benefits:

 On-demand access

 Pay-as-you-go

 Scalable infrastructure

2. What is IaaS (Infrastructure as a Service)?

Provides virtualized computing resources over the internet. Example: AWS EC2, Microsoft Azure
VM.

3. What is PaaS (Platform as a Service)?

Provides platforms for developers to build, test, and deploy applications. Example: Salesforce
Platform, Heroku.

4. What is SaaS (Software as a Service)?

Delivers software applications over the internet. Example: Salesforce CRM, Gmail.

🔷 SANDBOX IN SALESFORCE

5. What is Sandbox in Salesforce?

A copy of the production environment used for testing, development, and training.
6. Types of Sandbox:

 Developer Sandbox – Small data, for individual devs.

 Developer Pro – More storage than Developer.

 Partial Copy – Metadata + sample data.

 Full Sandbox – Exact replica with data.

🔷 OBJECT RELATIONSHIPS

7. Types of Object Relationships in Salesforce:

 Lookup Relationship (loosely coupled)

 Master-Detail Relationship (tightly coupled)

 Many-to-Many (via junction object)

 Hierarchical (on User object only)

8. What is a Junction Object?

A custom object with two master-detail relationships, used to model many-to-many

relationships.
Example: Course_Enrollment__c links Student__c and Course__c.

🔷 ROLES, SHARING, AND PERMISSIONS

9. Difference Between Roles and Profiles:

Feature Profile Role

Access Level Object/Field/Tab permissions Record-level access (data)

Mandatory Yes No

Hierarchy No Yes (controls visibility)

10. Ways to Share Records:

 Role Hierarchy

 Sharing Rules
  Manual Sharing

 Apex Sharing

 Owner-based sharing

 Team Sharing

 Territory Sharing

11. What are Sharing Rules?

Automated rules to extend record access to users in public groups, roles, or territories.

12. What is Manual Sharing?

Manually granting access to a record from the record's sharing button.

13. What is Apex Sharing?

Programmatic way to share records using Apex code. Useful for complex or dynamic sharing.

🔷 AUTOMATION: FLOWS VS APEX

14. Types of Flows:

 Screen Flow

 Record-Triggered Flow

 Autolaunched Flow

 Scheduled Flow

 Platform Event-Triggered Flow

15. Flow vs Apex - When to Use What:

Criteria Flow Apex

Complexity Low to medium High (complex logic/loops)

Admin-friendly Yes No (Developer required)

Governor Limits Better optimized Manual handling required

Maintenance Easier Harder to maintain

16. Best Practices for Flow:

  Limit DML & SOQL in loops

 Use Subflows for reusability

 Handle errors with fault paths

 Use entry conditions & filters

🔷 APEX & TRIGGERS

17. What is Apex?

Object-oriented programming language in Salesforce used for business logic execution on the
platform.

18. When to Use Apex Over Flow?

 When business logic is too complex for Flows

 Integration with external systems

 Bulk processing

 Custom web services

19. Apex Best Practices:

 Avoid hard-coded values

 Use bulkified code (handle collections)

 Limit SOQL/DML in loops

 Write test classes with >75% coverage

 Use try/catch for error handling

20. What is Apex Trigger?

Apex code that executes before/after insert, update, delete, etc. on a record.

21. When to Use Triggers?

 Automate field updates

 Create related records

 Call external systems on record change

🔷 APEX TRIGGER DESIGN

22. What is Apex Trigger Handler Pattern?

A best practice to move logic out of trigger into a handler class for readability and reuse.

23. What is Trigger Framework?

Organized approach to managing multiple triggers using patterns.

Popular frameworks:

 TDTM (Power of Us)

 Kevin O’Hara’s Framework

 Custom Handler-based Frameworks

🔷 ASYNCHRONOUS APEX

24. What is Async Apex?

Processes that run separately from the main thread to avoid limits and allow longer operations.

25. Ways to Perform Async Processing:

 Future Methods

 Queueable Apex

 Batch Apex

 Scheduled Apex

 @AuraEnabled(cacheable=true)

 Platform Events

26. What is Batch Apex?

Used to process large volumes of data asynchronously in batches.

27. Stateful vs Stateless Batch Jobs:

 Stateless (default): No state is maintained between batches.

 Stateful: Keeps state using Database.Stateful interface.

🔷 DML & PERFORMANCE

28. What is Mixed DML Error?

Occurs when you try to perform DML on setup and non-setup objects in the same transaction.

29. What is Lightning Data Service (LDS)?

It provides record data to Lightning components without needing Apex.

Benefits:

 No Apex call

 Automatic cache management

 Reacts to changes in record data

🔷 LWC COMMUNICATION & FEATURES

30. How to Communicate Between LWCs?

 Parent to Child: Props

 Child to Parent: Custom Events

 Sibling to Sibling: PubSub pattern or Lightning Message Service (LMS)

31. How to Call Apex in LWC & When to Use Each:

 @wire – for reactive data loading

 Imperative Call – for on-demand or conditional calls

32. App Event vs Component Event (Aura):

 Component Event: Bubble up to parent

 Application Event: Broadcast to all components

33. What is Lightning Messaging Service (LMS)?

Facilitates communication between Aura, LWC, and VF across DOM hierarchies using channels.

34. What is Lazy Loading in LWC?

Loading data/components only when needed (e.g., scroll to bottom).

Use case: Performance optimization for large lists.
35. What are Design Attributes in LWC?

They define configurable properties exposed to App Builder.

Defined using @api + design file.

🔷 INTEGRATION

36. What is Web Services?

Methods for communication between two systems over a network. Salesforce supports SOAP
and REST APIs.

37. SOAP vs REST:

Feature SOAP REST

Protocol Strict XML-based Lightweight, supports JSON/XML

Performance Slower Faster

WSDL Required Not required

Flexibility Less flexible More flexible

38. Enterprise vs Partner WSDL:

 Enterprise WSDL – Bound to a specific Salesforce org schema.

 Partner WSDL – Dynamic, works across multiple orgs.

39. Integration Patterns:

 Remote Process Invocation – Request & Reply (e.g., Apex callout)

 Remote Process Invocation – Fire & Forget

 Batch Data Synchronization

 UI Update Based on Data Changes

 Data Virtualization (External Objects)

✅ Basic Questions
1. What is Salesforce Flow, and why is it important in automation?

Salesforce Flow is a point-and-click automation tool that enables users to collect data, update
records, send emails, and integrate with external systems without code.
It’s crucial because:

 Reduces manual tasks

 Ensures data consistency

 Improves user experience

 Supports both declarative and programmatic logic

2. What are the different types of Salesforce Flows available?

 Screen Flow

 Record-Triggered Flow

 Autolaunched Flow

 Scheduled Flow

 Platform Event-Triggered Flow

3. What is the difference between Screen Flow and Autolaunched Flow?

Feature Screen Flow Autolaunched Flow

UI Has user interaction screens Runs in background

Trigger Method Button, Lightning page Process Builder, Apex, etc.

Use Case Data collection, guided UI Data manipulation, integration

4. How do you trigger a Record-Triggered Flow?

A Record-Triggered Flow runs automatically when a record is:

 Created

 Updated
  Deleted
You define the object, entry conditions, and when it should fire (before/after save).

5. What are Flow Elements, and examples?

Flow elements are building blocks in Flow. Examples:

 Screen – collects user input

 Assignment – sets variable values

 Decision – adds conditional logic

 Loop – iterates through data

 Get/Update/Create/Delete Records

 Apex Action – invokes Apex code

✅ Intermediate Questions

6. How do you optimize performance in a Flow?

 Use Before-Save Flows when possible

 Avoid unnecessary elements (like extra Gets)

 Use entry conditions to limit Flow execution

 Minimize use of Loops with DML

 Use Subflows to modularize

7. Difference Between Before-Save & After-Save Flows?

Type When it runs Use Case Can modify triggering record?

Before-Save Before DML Simple field updates ✅ Yes

After-Save After DML Related record creation, callouts ❌ No

8. What are Subflows & how to use them?

Subflows are Flows embedded into other Flows for modularity and reuse.
Use case: Common logic like address formatting or logging.

9. Scenario for Screen Flow Use:

Example: A guided account creation form with contact details and related tasks using user input.

10. Why use Assignment Elements in Flow?

 Set values to variables

 Accumulate counters

 Prepare data for decisions or DML actions

11. How to implement a loop in Flow?

1. Use a Collection variable (from Get Records)

2. Use a Loop element

3. Use Assignment inside the loop

4. Optionally, build a new collection for Create/Update actions

✅ Advanced Questions

12. How to integrate Apex with Flows?

 Use Apex-Defined Data Types

 Use Invocable Methods in Apex

 Add via Apex Action element in Flow

13. How to handle bulk record processing in Flows?

 Use Record-Triggered Flow (Before-Save)

 Use Collection Variables

  Minimize DML inside loops

 Group logic using Assignment & Collection Actions

14. How to manage transactions and rollbacks in Flow?

Flows share the same transaction context. If any element fails (e.g., DML error), the entire
transaction rolls back automatically. Use Fault paths for graceful error handling.

15. What is a Decision Element?

A conditional branching element that checks if criteria are met and guides the Flow path
accordingly.

✅ Scenario-Based Questions

16. Flow to automate lead assignment by region:

 Use a Record-Triggered Flow on Lead object

 Add Decision element to evaluate Region field

 Use Assignment element to assign Lead Owner

 Use Update Records to save changes

17. Scenario: Record-Triggered Flow to automate task:

On Opportunity Closed Won → Create a follow-up task for the account owner.

18. Handle errors in automated email Flow:

 Add Fault paths to Send Email action

 Log the error to a custom object or send admin alert email

 Wrap actions in Decision elements to prevent empty/null records

19. Create a Flow triggered on record deletion:

  Use Record-Triggered Flow with ‘Deleted’ option

 Use it to clean related records, audit logs, etc.

✅ Best Practices & Optimization

20. Best practices for naming Flows:

 Use clear naming: Object_Action_Type

 Example: Opportunity_CloseTask_AutoFlow

 Use version control and descriptions

21. Ensure data integrity in Flows:

 Use Decision elements before DML

 Avoid hardcoding IDs

 Validate required fields

 Use validation rules along with Flows

22. Strategies to maintain/update Flows:

 Use Subflows to isolate logic

 Document versions and purpose

 Disable or Deactivate unused Flows

 Test in Sandbox before deployment

23. How to test a Flow before deploying:

 Use Debug Mode in Flow Builder

 Create test records in Sandbox

 Use Flow Test (GA in latest releases)

 Write unit tests if invoked via Apex

24. Common pitfalls to avoid in Flows:

 Not bulkifying (using too many DMLs in loop)

 Missing error handling

 Overuse of Get/Update in one Flow

 Not testing thoroughly in different scenarios

 Hardcoded values (like IDs)