Salesforce Interview Question

1. What is an object in Salesforce?

An object in Salesforce is akin to a database table, composed of rows and columns. The columns are referred to as fields, while the rows are known as records.  There are two main types of objects: standard objects, which are provided by Salesforce, and custom objects, which can be tailored to fit the specific needs of an organization.

2. What is a Master-Detail relationship?

A Master-Detail relationship in Salesforce signifies a tightly coupled relationship between two objects, where one object serves as the parent (master) and the other as the child (detail). If a parent record is deleted, all associated child records are also deleted. Roll-Up Summary fields, which calculate values such as sum, average, or minimum from child records, can only be created on Master-Detail relationships. Additionally, up to two Master-Detail relationships are allowed per object, and access to parent records determines access to child records.

3. Can a Master-Detail relationship be created if a custom object already contains records?

No, a Master-Detail relationship cannot be directly created if a custom object contains existing records.

First, a relationship must be established, the lookup field populated with data in all records, and then the relationship type can be changed to a Master-Detail relationship.

4. What is a Lookup relationship?

A Lookup relationship is used to create a linkage between two objects without creating a strict dependency on the parent object. It is a more loosely coupled relationship compared to Master-Detail relationships, allowing greater flexibility.

5. What is the difference between Lookup and Master-Detail relationships?

Lookup relationships are loosely coupled, while Master-Detail relationships are tightly coupled. Unlike Master-Detail relationships, Roll-Up Summary fields cannot be created on Lookup relationships. Additionally, in Lookup relationships, the presence of parent records is not mandatory when creating child records, and lookup fields are not required on the page layout of detail records. Standard object records can be on the detail side of a custom object in a Lookup relationship. Unlike Master-Detail relationships, ownership of child records is not controlled by the parent, and there is no cascade delete in Lookup relationships.

6. What is a Roll-Up Summary field?

A Roll-Up Summary field in Salesforce is a read-only field that displays the sum, minimum, or maximum value of a field in a related list or the record count of all records listed in a related list.

7. What is OWD (Organization-Wide Default)?

OWD stands for Organization-Wide Default, which defines the default level of access users have to records in Salesforce. The options include Private, Public Read Only, Public Read/Write, Public Read/Write/Transfer, Controlled by Parent, and Public Full Access.

8. What is "Grant Access Using Hierarchy" in Salesforce?

Grant Access Using Hierarchy is a feature in Salesforce that allows users higher in the role hierarchy to access the records of users below them. It helps to control record-level access and organization reporting based on role hierarchies.

9. When OWD is set to Private, how can access be opened up?

When OWD is set to Private, access can be opened up by utilizing the Role Hierarchy in Salesforce. The Role Hierarchy enables administrators to control record access based on the roles of users within the organization.

10. What is the difference between Role and Profile in Salesforce?

Roles in Salesforce control record-level access, determining which records users can view and edit based on their position in the organizational hierarchy. Profiles, on the other hand, define what users can do within the application, including permissions, object-level security, and settings such as login hours and IP restrictions.

11 what is Multitenant Architecture ?

Multitenant architecture in Salesforce refers to the underlying structure that allows multiple organizations (tenants) to use the same instance of Salesforce simultaneously while keeping their data and configurations isolated from each other.

In a multitenant architecture:

Shared Infrastructure: All organizations (tenants) share the same physical infrastructure, including servers, storage, and networking resources. This shared infrastructure helps reduce costs and simplifies maintenance for Salesforce.

Isolated Databases: Despite sharing the same infrastructure, each organization has its own isolated database within the Salesforce platform. This ensures that the data of one organization is kept separate from the data of another, maintaining data security and privacy.
Customization and Configuration:  Each organization can customize and configure its instance of Salesforce according to its specific requirements, including creating custom objects, fields, workflows, and user interfaces. These customizations are unique to each organization and do not affect other tenants.
Upgrade and Maintenance:  Salesforce manages upgrades and maintenance centrally for all organizations on its platform. This means that when Salesforce releases new features, enhancements, or patches, they are automatically applied to all organizations without requiring individual installations or updates.

Scalability and Performance: Multitenancy allows Salesforce to efficiently scale its infrastructure to accommodate the growing needs of multiple organizations. It also helps ensure consistent performance across all tenants, as resources are dynamically allocated based on demand.Overall, multitenant architecture in Salesforce enables efficient resource utilization, scalability, and flexibility, while ensuring data isolation and security for each organization using the platform.