Admin Scenario’s Based Interview Questions

Steps to Recover Deleted Custom Objects

1. Check the Recycle Bin: Salesforce temporarily stores deleted custom objects and their data in the Recycle Bin for 15 days. First, check if the object and its records are still available and restore them.
2. Backup: If the object is not in the Recycle Bin, look for a recent backup of the data. This could be a Salesforce export file, a backup from a third-party tool, or a data export scheduled by Salesforce.
3. Recreate the Object: If no backup is available and the object cannot be restored, manually recreate the custom object using the same schema, then import the data from a backup or CSV file (if available).
4. Prevent Future Accidents: Review user permissions, implement regular data backup processes, and restrict deletion permissions on sensitive objects to avoid accidental loss.

1. Create a Roll-Up Summary Field: On the Account object, create a roll-up summary field.
2. Specify the Roll-Up Type: Set the roll-up type to SUM, selecting the Opportunity Amount field.
3. Apply Filter Criteria: Configure the filter to include only opportunities where the Stage equals "Closed-Won."
4. Validate and Test: Validate the setup and test by creating or updating opportunities to ensure the total is accurately reflected on the Account record.

1. Create Picklist Fields: Create two picklist fields on the Location object—one for "Country" and one for "City."
2. Set Up Field Dependency: Use Salesforce’s field dependency feature to make the City picklist dependent on the Country picklist.
3. Define Dependency Matrix: Configure the field dependency matrix by specifying which cities should be available for each country.
4. Test: After setting up the dependency, test it by creating or editing Location records to ensure the correct cities appear based on the selected country.

1. Check Field-Level Security: Ensure that the user’s profile or permission set doesn’t restrict access to specific fields on the object.
2. Record Ownership: Verify whether the user owns the records or has appropriate sharing permissions to edit records they do not own.
3. Sharing Settings: Review the object’s sharing rules and the organization-wide defaults to ensure they allow the user to edit the records in question.
4. Profile Permissions: Double-check the user's profile to confirm they have the correct object permissions for "Read/Write."
5. Record Type Assignment: Ensure the correct record type is assigned, and that the page layout allows the user to edit the fields.

1. Set Organization-Wide Defaults: Set the organization-wide defaults (OWD) for the custom object to “Private” to restrict access by default.
2. Create Sharing Rules: Set up sharing rules to grant access to records based on criteria, such as the user’s department (which could be stored as a custom field on the User record).
3. Role Hierarchy: Configure the role hierarchy to ensure that managers can see records of their subordinates, while peers cannot access each other’s records.
4. Manual Sharing: Allow users with higher-level permissions to manually share specific records with others as needed.

1. Use Data Loader: If the mistake affected many records, use Salesforce Data Loader or another data import tool to update the records with the correct information.
2. Field History Tracking: Review field history tracking (if enabled) to identify which records were modified and what the previous values were.
3. Manual Correction: For a small number of records, correct them manually using the Salesforce interface.
4. Validation Rules: Implement or review validation rules to prevent similar issues from occurring in the future.

1. Create Record Types: Create separate record types for each contract type (Sales, Service, Partnership).
2. Configure Page Layouts: Assign different page layouts to each record type to ensure that only the relevant fields are visible and editable.
3. Setup Validation Rules: Implement validation rules specific to each record type to enforce data integrity.
4. Automation: Use Workflow Rules, Process Builder, or Flow to trigger different automation processes based on the contract type.
5. Assign Record Types: Assign the appropriate record types to different user profiles, ensuring that users see only the contract types relevant to their roles.

1. Plan the Dependency: Start by planning the controlling and dependent values, possibly in a spreadsheet, to make the setup process smoother.
2. Use Field Dependency Matrix: Use the field dependency matrix in Salesforce, which allows  you to manage large lists by selecting multiple options and assigning them to the dependent field values.
3. Bulk Updates: If necessary, use tools like Data Loader or workbench for bulk updating  picklist values, especially if you need to adjust them after the initial setup.
4. Testing: After setting up, thoroughly

1. Create Record Types: Ensure that each record type is created for the "Service Request" object.
2. Create Picklist: Define the controlling and dependent picklists for each record type.
3. Set Up Field Dependencies: For each record type, go to the field dependency setup and configure the dependencies for that specific record type.

1. Create the Controlling and Dependent Fields: Set up the controlling picklist field and the dependent picklist field.
2. Set Up Field Dependency: Configure the field dependency so that only relevant values are available in the dependent field.
3. Conditional Field Visibility: Use dynamic forms (if available in your Salesforce edition) or page layouts to conditionally display the dependent picklist based on the controlling field's value.
4. Test: Validate by testing different scenarios to ensure the dependent field only appears when the specified value is selected in the controlling field.

1. Review Picklist Values: First, review the existing picklist values to see if any can be consolidated or removed.
2. Consider Alternative Solutions: If consolidation isn't possible, consider breaking down the picklist into two separate fields, each handling part of the value set, and use a combination of these fields to control the dependent picklist.
3. Custom Metadata or Custom Settings: As a last resort, consider using custom metadata or custom settings to simulate dependencies, though this may require more complex logic and customization.
4. Document and Test: Document the changes for future reference and thoroughly test the new setup to ensure it meets business requirements

1. Review Existing Users: Check if there are any inactive users who no longer need access and can be deactivated.
2. License Optimization: Evaluate if some users have a more powerful license than they need and consider downgrading their licenses if appropriate.
3. Request Additional Licenses: If necessary, coordinate with your Salesforce account representative to purchase additional licenses.
4. Temporary Workaround: If immediate addition is required and licenses are unavailable, consider using a shared login for non-sensitive tasks, ensuring compliance with Salesforce’s terms.

1. Use a Permission Set: Create a new permission set with the necessary additional permissions and assign it to the user.
2. Review Profile: Ensure the user’s profile remains unchanged, and only the permission set provides the additional access.
3. Manage Permission Sets: If multiple users require the same additional permissions, assign the permission set to all relevant users.

1. Check Login Hours: Verify the login hours set in the user’s profile. Adjust the login hours if necessary to allow access during the required times.
2. Review IP Restrictions: Ensure that the user’s login IP address falls within the permitted range set in their profile.
3. Adjust Settings: Modify the login hours or IP restrictions as needed to resolve the issue.

1. Review User Profile: Check the user’s profile to ensure they have the correct object-level and field-level permissions.
2. Check Permission Sets: Verify if the user has any assigned permission sets that might be restricting the action.
3. Review Sharing Settings: Ensure that the object’s sharing settings and any applicable sharing rules allow the user to perform the action.
4. Login as User: Use the "Login As" feature to see exactly what the user sees and replicate the issue.

1. Prepare User Data: Create a CSV file containing the necessary user information, including username, email, profile, and any other required fields.
2. Use Data Loader: Use Salesforce Data Loader or the Import Wizard to upload the CSV file and create the new users in bulk.
3. Assign Permission Sets: If needed, use Data Loader to assign permission sets to the new users.
4. Test Accounts: Ensure the new accounts are functioning correctly by logging in as one of the new users or verifying the setup.

1. Immediate Action: Temporarily deactivate the user to prevent access while you investigate.
2. Review Profile and Permission Sets: Check the user’s profile and any assigned permission sets to identify how they were granted access to sensitive data.
3. Revoke Access: Remove or adjust permissions in the profile or permission sets to restrict access to the sensitive data.
4. Reactivate User: Once access has been appropriately restricted, reactivate the user’s account.
5. Audit User Access: Conduct an audit of other users with similar access to ensure no other users have inappropriate access.

1. Create a New User Account: Set up a user account with a profile that grants the necessary access, typically using a Chatter External or Community license depending on the consultant’s needs.
2. Set Expiration Date: Use a permission set or time-based workflow to automatically deactivate the user after their contract period ends.
3. Monitor Access: Regularly review the external user’s activities to ensure compliance with your organization’s security policies.
4. Deactivate After Project Completion: Once the consultant’s work is finished, deactivate their account to prevent further access.

1. Identify the Users:◦ First, create a list of users that need to be deactivated. This can be done by running a report in Salesforce to identify users based on specific criteria such as role, department, or last login date.
2. Backup User Data: ◦ Before deactivating users, export relevant user data and their associated records to ensure you have a backup. This could be useful in case any information needs to be restored or reviewed later.
3. Reassign Records:◦ If the users own records (such as accounts, opportunities, cases), use the Mass Transfer Records tool in Salesforce to transfer these records to other active users. This ensures continuity of data ownership and prevents orphaned records.

◦ Go to Setup > Data Management > Mass Transfer Records and select the object to transfer records.

4) Deactivate Workflow and Approval Process Assignments:

◦ Review any workflows or approval processes that the users are part of. Reassign their

responsibilities to other users to avoid disruptions in business processes.

5) Deactivate Users:

◦ You can deactivate users in bulk using a Data Loader or a similar tool:

▪ Using Data Loader:

▪ Export the list of users you intend to deactivate, including their

  Salesforce User IDs.

▪ Update the IsActive field to False for each user in the CSV file.

▪ Perform an update operation in Data Loader to deactivate the users.

▪ Using the Salesforce UI:

▪ If the number of users is small, manually deactivate them by going to

  Setup > Users > Users and unchecking the Active checkbox next to  each user's name.

6) Verify Deactivation: After the deactivation process, run a report to ensure that all intended users have

been successfully deactivated. Double-check that there are no active users who

should have been deactivated.

7) Communicate the Change:  Inform relevant stakeholders, such as managers or team leads, about the

deactivation. Provide them with a list of deactivated users and any necessary next

steps (e.g., reassignment of tasks).

8) Review Licensing:  After deactivation, review your Salesforce licenses. Deactivating users frees up

licenses that can be reassigned to new users or help reduce licensing costs.

1. Field-Level Security: Check the field-level security settings for the user’s profile to ensure they have edit access to the necessary fields on the custom object.
2. Page Layout: Verify that the user’s profile has the correct page layout assigned, which includes the editable fields.
3. Record Type Assignment: Ensure that the profile is associated with the correct record type, which might affect the available fields and layouts.
4. Sharing Settings: Review the organization-wide defaults and sharing rules to ensure the user has the necessary permissions to edit the specific records.

1. Create a Temporary Permission Set: Instead of modifying the user’s profile, create a temporary permission set with the necessary administrative permissions.
2. Assign the Permission Set: Assign the permission set to the user for the duration required.
3. Monitor Activity: Monitor the user’s activity to ensure the permissions are used appropriately.
4. Remove the Permission Set: Once the tasks are completed, promptly remove the permission set from the user to revert their access back to normal.

1. Assign Record Types: Go to the profile settings and assign only the specific record types that the users with this profile should have access to.
2. Page Layout Assignment: Ensure the correct page layouts are associated with these record types for the profile.
3. Test Access: Test by logging in as a user with the profile to ensure they can only create and view the specified record types.
4. Adjust Sharing Rules: If necessary, adjust sharing rules to restrict access to records of other types.

1. Identify Unused Profiles: Run a report to identify profiles that have no users assigned or have not been used in a long time.
2. Review Permissions: Carefully review the permissions of these profiles to ensure they are truly redundant or obsolete.
3. Deactivate or Delete Profiles: Deactivate or delete the unused profiles, making sure to reassign any users (if applicable) to other appropriate profiles.
4. Consolidate Profiles: Where possible, consolidate profiles with similar permissions to reduce the total number of profiles and simplify management.

1. Modify Profile Permissions: Go to the profile settings and remove the "Delete" permission from each object for the relevant profile.
2. Test Permissions: Test by logging in as a user with the modified profile to ensure they cannot delete records on any object.
3. Use Permission Sets: If some users within the group still need to delete records on certain objects, create a permission set that grants "Delete" access only where necessary, and assign it selectively.

1. Create or Clone Profiles: Assess the new users' access needs and create or clone profiles as necessary to match their roles in the organization.
2. Use Data Loader for Mass Assignment: Prepare a CSV file with the new users' details and the appropriate profile assignments. Use Data Loader to perform a mass update or insert to assign profiles to the new users.
3. Review and Adjust Permissions: After importing the users, review their access and adjust any profiles or permission sets as needed.
4. Training and Communication: Ensure that the new users are informed about their profiles and the access it provides, and offer training if necessary.

1. Create a Permission Set: Create a new permission set that includes the necessary permissions for the custom object (e.g., Read, Create, Edit).
2. Assign the Permission Set: Assign the permission set to the user who requires the additional access.
3. Test Access: Log in as the user or ask the user to verify that they now have the required access to the custom object without needing to modify their profile.

1. Create a Permission Set: Create a permission set with the necessary permissions.
2. Use Data Loader: Export the list of users and their IDs. Prepare a CSV file with the User IDs and the permission set ID.
3. Mass Assign Permission Set: Use Data Loader to perform a mass insert, assigning the permission set to all the users at once.
4. Verify Assignments: After the bulk assignment, verify that the users have the permission set applied correctly.

1. Create a Permission Set Group: Use Salesforce's Permission Set Groups feature to combine multiple permission sets into a single group.
2. Add Permission Sets to the Group: Add all the relevant permission sets to the group.
3. Assign the Group: Assign the permission set group to users instead of assigning each permission set individually.
4. Test: Verify that the users have all the necessary permissions through the assigned group.

1. Assign to a Test User: Assign the new permission set to a test user account that mirrors the typical user’s profile.
2. Perform Test Cases: Log in as the test user and perform a series of test cases to verify that the permission set grants the correct access without providing unintended permissions.
3. Adjust as Necessary: If the tests reveal any issues, adjust the permission set before rolling it out to all users.
4. Document and Roll Out: Once confirmed, document the permissions granted by the set and proceed to assign it to the relevant users.

1. Create Multiple Page Layouts: Create separate page layouts for each profile, customizing the fields, sections, and related lists to meet the specific needs of each user group.
2. Assign Page Layouts to Profiles: Navigate to the object’s Page Layout Assignment section and assign the appropriate page layout to each profile.
3. Test the Layouts: Log in as a user from each profile to ensure they see the correct page layout with the relevant fields and sections.
4. Adjust as Needed: If any adjustments are required, modify the page layouts and reassign them as necessary.

1. Create Record Types: Create the necessary record types for the custom object.Admin Scenario Based Interview Questions
2. Create and Customize Page Layouts: Create different page layouts for each record type, customizing them according to the business needs.
3. Assign Page Layouts to Record Types and Profiles: Go to the Page Layout Assignment section and map each record type to the appropriate page layout and profile.
4. Test the Setup: Test by creating and viewing records of different types to ensure the correct page layout is displayed for each record type.

1. Create a Custom Page Layout: Clone the existing page layout and remove the fields that the user profile should not access.
2. Assign the Page Layout: Assign the custom page layout to the specific profile.
3. Review Field-Level Security: Ensure that field-level security settings are also configured to restrict access to these fields at the profile level.
4. Test the Layout: Log in as a user with the profile to confirm that the fields are hidden as expected.

1. Collect User Feedback: Gather detailed feedback from the users to understand which fields need to be reordered.
2. Edit Page Layout: Go to the page layout and reorder the fields in a more logical sequence, grouping related fields together for better flow.
3. Preview Changes: Use the preview feature to ensure that the new order improves the user experience.
4. Deploy and Monitor: Save the changes and monitor user feedback to ensure the new layout is more efficient.

1. Edit the Page Layout: Go to the page layout editor for the object and locate the related list section.
2. Add the Related List: Drag the desired related list from the palette to the related lists section of the page layout.
3. Customize the Related List: Customize the related list by selecting the fields to display, setting filters, and choosing the sort order.
4. Save and Test: Save the layout and test by viewing a record to ensure the related list is displayed correctly.

1. Review and Prioritize Fields: Review the existing fields and sections with users to determine which ones are necessary and which can be removed or consolidated.
2. Simplify the Layout: Edit the page layout by removing or relocating less frequently used fields and merging sections where appropriate.
3. Group Related Fields: Group related fields together into logical sections to improve flow and usability.
4. Test the Simplified Layout: Roll out the changes and gather feedback from users to ensure the simplified layout meets their needs.

1. Create the Custom Button: If not already created, develop the custom button and add it tothe object’s button section.
2. Edit Page Layout: Add the custom button to the relevant page layouts where it shouldappear.
3. Assign Based on Profiles: Ensure that the page layouts with the custom button are only assigned to the profiles that should have access to the button.
4. Testing and Verification: Test by logging in as a user with the profile to ensure the button appears and functions as expected, and verify that it’s hidden for other profiles.

1. Create Record Types: Create separate record types for each account type (Customer, Partner, Vendor).
2. Customize Page Layouts: Create and customize different page layouts for each record type to display the relevant fields for each account type.
3. Assign Page Layouts: Assign the appropriate page layout to each record type for the relevant profiles.
4. Test the Setup: Create and view accounts to ensure that the correct page layout is displayed for each record type.

1. Modify Profile Settings: Go to the profile settings for each relevant profile and edit the record type settings.
2. Assign Record Types: Assign only the necessary record types to each profile, ensuring that users with that profile can only access the appropriate record types.
3. Test Access: Log in as a user with each profile to verify that they can only create and view records of the assigned record types.

1. Create Validation Rule: Create a validation rule that triggers when the specific record type is selected and the required fields are left blank.
2. Set Conditions: Use a formula to check both the record type and the field value. For
   • example, AND(ISPICKVAL(RecordType.Name, "Record Type Name"), ISBLANK(Field_Name__c)).
3. Test the Validation: Test by attempting to save records with the specific record type without filling in the required fields, ensuring the validation rule is enforced.
4. Adjust Error Messages: Customize the error message to clearly explain what fields need to be filled out based on the record type.

1. Ensure Data Completeness: Ensure that all existing "Invoice" records have a "Customer" linked, as master-detail relationships require child records to have a parent.
2. Edit the Relationship Field: Go to Object Manager > Invoice > Fields & Relationships and find the existing lookup relationship field. ◦ Change the field type from "Lookup Relationship" to "Master-Detail Relationship."
3. Configure Settings: Set the sharing settings, field-level security, and page layouts, ensuring they align with the master-detail relationship requirements.
4. Test the Conversion: Verify the conversion by creating new invoices linked to customers and checking that the master-detail relationship behaves as expected.

1. Create the Lookup Relationship: On "Custom Object A," create a lookup relationship field that references "Custom Object B."
2. Enable Cascading Delete: During the creation of the lookup relationship, enable the option for "Delete this record also" (cascading delete) to ensure that related records in "Custom Object A" are deleted when a parent record in "Custom Object B" is deleted.
3. Test the Setup: Create related records in both objects and then delete a record in "Custom Object B" to confirm that the associated records in "Custom Object A" are automatically deleted.

1. Understand the Deletion Cascade: In a master-detail relationship, deleting the master record will also delete all related detail (child) records.
2. Confirm Data Backup: Before deleting the master record, ensure that data is backed up if the related detail records need to be preserved.
3. Use Validation Rules (Optional): Implement a validation rule on the master object to prevent deletion if certain conditions are met (e.g., if there are active child records).
4. Test the Deletion: Test by deleting a master record and verify that all associated detail records are also deleted.

1. Review Roll-Up Summary Fields: Check if roll-up summary fields are causing performance issues due to the large data volume.
   • Why: Roll-up summary fields can impact performance when aggregating data from a large number of child records.
2. Consider Archiving Old Records: Archive old or inactive child records to reduce the number of related records under the master object.
3. Monitor Performance: Use Salesforce's performance monitoring tools to assess the impact of large data volumes on the master-detail relationship and adjust as necessary.
4. Test and Optimize: Test the system’s performance before and after implementing any changes to ensure the master-detail relationship operates efficiently.

1. Create a Validation Rule on the Master Object: Write a validation rule on the "Customer" object that checks for the existence of related "Order" records.
   • Example formula: NOT(ISBLANK(Orders__r.Id)).
2. Customize the Error Message: Provide a clear error message indicating that the "Customer" cannot be deleted if there are active "Order" records.
3. Test the Validation: Attempt to delete a "Customer" record with active orders to ensure the validation rule prevents the deletion.

1. Set Up Master-Detail Relationships:
   •  First, create a master-detail relationship between "Program" (master) and "Project" (detail).
   • Then, create another master-detail relationship between "Project" (master) and "Task" (detail).
   • Why: This structure ensures that tasks are associated with projects, and projects are associated with programs, maintaining a clear hierarchical relationship.
2. Customize Page Layouts: Ensure that related lists for "Projects" and "Tasks" are included on the appropriate page layouts for "Program" and "Project," respectively.
3. Test the Hierarchy: Create a few programs, projects, and tasks to ensure that each level of the hierarchy is correctly linked and that deleting a higher-level record cascades to lower levels.

1. Navigate to Validation Rules: Go to Setup > Object Manager > Case > Validation Rules.
2. Create a New Validation Rule: Create a rule that checks if the "Priority" field is set to "High" and whether the "Escalation Reason" field is blank.
   • Formula: AND(ISPICKVAL(Priority, "High"),
                             ISBLANK(Escalation_Reason__c))
3. Set the Error Message: Provide a clear error message, such as "Escalation Reason is required when the case is marked as High Priority."
4. Test the Validation Rule: Attempt to save a case with "High Priority" without filling in the "Escalation Reason" field to ensure the validation rule prevents the save and displays the error message.

1) Navigate to Validation Rules: Go to Setup > Object Manager > Project > Validation Rules.

2) Create a New Validation Rule: Write a rule that compares the "Start Date" and "End Date" fields to ensure the "End Date" is not earlier than the "Start Date.”

               ◦ Formula: End_Date__c < Start_Date__c

3) Set the Error Message: Provide an error message such as "End Date cannot be earlier than Start Date."

4) Test the Validation Rule: Attempt to enter an "End Date" that is earlier than the "Start Date" and ensure the validation rule blocks the save.

1. Navigate to Validation Rules: Go to Setup > Object Manager > Opportunity > Validation Rules.
2. Create a New Validation Rule: Write a rule that checks if the "Stage" is "Closed Won" and whether the "Closed Date" is today’s date.
   •  Formula: AND(ISPICKVAL(StageName, "Closed Won"), ClosedDate <> TODAY())
3. Set the Error Message: Provide an error message like "Closed Date must be today’s date when the Opportunity is marked as Closed Won.”
4. Test the Validation Rule: Try to change the stage to "Closed Won" with a different closed date to ensure the rule triggers.

1) Consider Using a Duplicate Rule: While a validation rule could check for duplicate entries within the context of a single record save, a Duplicate Rule is generally more               effective for this purpose.

                  ◦ Navigate to Setup > Duplicate Management > Duplicate Rules.

2) Create a Duplicate Rule: Set the rule to check for matching email addresses across all "Lead" records.

3) Create a Matching Rule: Define how the system should identify duplicates (e.g., exact matches on the "Email" field).

4) Test the Duplicate Rule: Attempt to create leads with the same email address to ensure the system prevents duplicates.

1. Navigate to Validation Rules: Go to Setup > Object Manager > Account > Validation Rules.
2. Create a New Validation Rule: Write a rule that checks if there are any related "Opportunities" with a status of "Open" and prevents the deletion of the account. NOT(ISBLANK(Opportunities__r.Id)),
   • Formula: AND(ISCHANGED(IsDeleted), ISPICKVAL(Opportunities__r.StageName, “Open"))
3. Set the Error Message: Provide an error message like "You cannot delete an Account with Open Opportunities."
4. Test the Validation Rule: Attempt to delete an account with open opportunities to ensure the rule prevents the deletion.

1. Navigate to Validation Rules: Go to Setup > Object Manager > Opportunity > Validation Rules.
2. Create a New Validation Rule: Write a rule that checks if the record type is "New Business" and whether the "Referral Source" field is blank.
   • Formula: AND($RecordType.Name = "New Business", ISBLANK(Referral_Source__c))
3. Set the Error Message: Provide an error message like "Referral Source is required for New Business opportunities."
4. Test the Validation Rule: Try saving a "New Business" opportunity without filling in the "Referral Source" to ensure the rule works as expected.

1) Navigate to Validation Rules: Go to Setup > Object Manager > Opportunity > Validation Rules.

2) Create a New Validation Rule: Write a rule that checks if the "Stage" is "Proposal/Price Quote" and the "Discount" is greater than 20%.

             ◦ Formula: AND(ISPICKVAL(StageName, "Proposal/Price Quote"), Discount__c > 0.2)

3) Set the Error Message: Provide an error message like "Discount cannot exceed 20% at the Proposal/Price Quote stage."

4) Test the Validation Rule: Try to set a discount greater than 20% at the specified stage to ensure the rule blocks the save.

1) Navigate to Validation Rules: Go to Setup > Object Manager > Contact > Validation Rules.

2) Create a New Validation Rule: Write a rule that checks if the "Birthdate" is greater than today’s date.

               ◦ Formula: Birthdate > TODAY()

3) Set the Error Message: Provide an error message like "Birthdate cannot be in the future.”

4) Test the Validation Rule: Try setting the birthdate to a future date to ensure the rule prevents the save.

1) Create Validation Rule: AND(ISPICKVAL(Priority, "High"), ISBLANK(Escalation_Reason__c))

2) Error Message: "Escalation Reason is required when the case is marked as High Priority.”

1. Create Validation Rule: End_Date__c < Start_Date__c
2. Error Message: "End Date cannot be earlier than Start Date.”

1. Create Validation Rule: ISBLANK(Phone) && ISBLANK(Email)
2. Error Message: "Please enter either a phone number or an email address.”

1. Create Validation Rule: AND(ISPICKVAL(StageName, "Closed Won"), ClosedDate <> TODAY())
2. Error Message: "Closed Date must be today’s date when the Opportunity is marked as Closed Won.”

1. Use Duplicate Rules: Set up a Duplicate Rule to check for matching email addresses.
2. Error Message: Customize the error message to notify the user about duplicate leads.

1. Create Validation Rule: AND(Custom_Field_A__c = TRUE, ISBLANK(Custom_Field_B__c))
2. Error Message: "Custom Field B must be populated when Custom Field A is checked.”

1. Create Validation Rule: AND(Discount__c > 0.3, Amount < 100000)

2. Error Message: "Discount cannot exceed 30% for opportunities less than $100,000.”

1. Create Validation Rule: AND(ISPICKVAL(Custom_Picklist__c, "Specific Value"), ISBLANK(Another_Field__c))
2. Error Message: "Specific Value can only be selected if Another Field is populated.”

1. Create Validation Rule: AND(ISCHANGED(IsDeleted), NOT(ISBLANK(Opportunities__r.Id)),
   • ISPICKVAL(Opportunities__r.StageName, "Open"))
2. Error Message: "You cannot delete an Account with Open Opportunities.”

1. Create Validation Rule: NOT(REGEX(Phone, "\\(\\d{3}\\) \\d{3}-\\d{4}"))
2. Error Message: "Phone number must be in the format (XXX) XXX-XXXX."

1. Create Validation Rule: Quantity__c < 1
2. Error Message: "Quantity cannot be less than 1.”

1. Create Validation Rule: CloseDate > (Account.CreatedDate + 30)
2. Error Message: "Opportunity Close Date must be within 30 days of Account Creation Date.”

1. Create Validation Rule: AND(ISPICKVAL(Custom_Picklist__c, "Restricted Value"),
   • $Profile.Name <> "Specific Profile")
2. Error Message: "You are not authorized to select this value.”

1. Create Validation Rule: AND(NOT(ISBLANK(Street__c)), OR(ISBLANK(City__c),
   • ISBLANK(State__c), ISBLANK(Zip_Code__c)))
2. Error Message: "Please complete all address fields if any field is filled."

1. Create Validation Rule: AND(ISPICKVAL(Controlling_Field__c, "Controlling Value"),
   • ISBLANK(Dependent_Field__c))
2. Error Message: "Dependent picklist value must be selected if the controlling value is chosen."

1. Create Validation Rule: ISBLANK(Multi_Select_Picklist__c)
2. Error Message: "Please select at least one option."

1. Create Validation Rule: LEN(Description__c) > 255
2. Error Message: "Description cannot exceed 255 characters.”

1. Create Validation Rule: AND(ISPICKVAL(Custom_Picklist__c, "Restricted Value"),
   • $RecordType.Name = "Specific Record Type")
2. Error Message: "This picklist value is not allowed for this record type."

1. Create Validation Rule: AND($RecordType.Name = "Specific Record Type",
   • ISBLANK(Specific_Field__c))
2. Error Message: "This field is required for the selected record type."

1. Validation Rule: NOT(REGEX(Email, “^[A-Z0-9._%+-]+@[A-Z0-9.-]+\\.[A-Z]{2,4}$"))
2. Error Message: "Please enter a valid email address.”

AND() - Returns true if all specified conditions are true.

OR() - Returns true if any of the specified conditions are true.

NOT() - Returns the logical opposite of a given condition.

ISBLANK() - Returns true if the specified field is blank.

ISCHANGED() - Returns true if the value of a field has been modified.

ISPICKVAL() - Returns true if a picklist field matches the specified value.

TEXT() - Converts a field value to text.

LEN() - Returns the number of characters in a text field.

REGEX() - Validates whether a text field matches a specified pattern.

CONTAINS() - Returns true if the specified text is found within another text.

INCLUDES() - Returns true if a multi-select picklist field includes the specified value.

PRIORVALUE() - Returns the previous value of a field before the current save.

BLANKVALUE() - Returns a substitute expression if a field is blank, otherwise returns the field

value.

CASE() - Evaluates a series of conditions and returns a corresponding value.

IF() - Returns a value based on whether a condition is true or false.

ABS() - Returns the absolute value of a number.

ISNUMBER() - Returns true if a text value can be converted to a number.

DATEVALUE() - Converts a date/time or text expression to a date.

NOW() - Returns the current date and time.

TODAY() - Returns the current date without time.

1. Navigate to Data Loader: Download and open Salesforce Data Loader.
2. Choose Upsert Operation: Select the "Upsert" operation to update existing records and insert new ones.
3. Map Fields: Map the CSV file fields to the corresponding Salesforce fields.
4. Set External ID: Use a unique identifier like Email or Salesforce ID to match existing records.
5. Run and Verify: Perform the upsert and verify the import results in Salesforce to ensure no duplicates were created.

1. Export Data for Backup: Use Data Loader to export the lead records to a CSV file for backup.
2. Filter Records: Apply filters to identify the specific old leads to delete.
3. Perform Mass Deletion: Use Data Loader's "Delete" operation to remove the filtered records.
4. Verify Deletion: Confirm that only the intended leads were deleted by checking Salesforce records post-deletion.

1. Navigate to Duplicate Management: Go to Setup > Duplicate Management > Duplicate Rules.
2. Create a Duplicate Rule: Define rules for identifying duplicates based on key fields like Account Name and Email.
3. Merge Duplicates: Use the "Find Duplicates" feature to review and merge duplicate accounts.
4. Use Matching Rules: Set up matching rules to prevent future duplicates from being created.

1. Navigate to Data Export Wizard: Go to Setup > Data Export Wizard.
2. Select Objects: Choose the objects and fields required for the report.
3. Export Data: Export the data to a CSV file.
4. Combine Data (if needed): Use Excel or another tool to combine data from multiple objects and deliver the report.

1. Schedule Regular Exports: Use Salesforce’s Data Export service to schedule weekly or monthly backups.
2. Use a Third-Party Backup Tool: Consider implementing a third-party backup solution that offers automated backups and easy recovery options.
3. Test Recovery Process: Periodically test the recovery process to ensure backups can be restored when necessary.

1. Map Data Fields: Map fields from the old CRM system to Salesforce fields.
2. Cleanse Data: Remove duplicates and irrelevant records before migration.Admin Scenario Based Interview Questions
3. Use Data Loader: Perform the migration in batches using Data Loader, validating data at each stage.
4. Verify Migration: Check records in Salesforce to ensure data integrity post-migration.

1. Archive Old Cases: Use Salesforce’s data archiving tools to move old cases to external storage.
2. Optimize Fields: Review and remove unnecessary fields or related lists from the "Cases" object.
3. Monitor Performance: Use Salesforce's performance monitoring tools to assess the impact and ensure improved performance.

1. Use Field-Level Security: Set up field-level security to restrict access to the Social Security Number field.
2. Adjust Profiles and Permission Sets: Ensure only authorized users have access by modifying profiles and permission sets.
3. Use Encryption: Apply Salesforce Shield or other encryption methods for additional security.

Pre-requisites for Salesforce Data Migration

1) Data Mapping:

     ◦ Field Mapping: Clearly map fields from the source system to the corresponding.  fields in Salesforce. Ensure that all necessary fields exist in Salesforce.

     ◦ Object Mapping: Understand the relationship between objects in both systems (e.g., Accounts, Contacts, Opportunities) and how they correspond.

2) Data Cleanliness:

     ◦ Data Cleansing: Remove duplicates, correct errors, and standardize data formats in the source system before migration.Admin Scenario Based Interview Questions

     ◦ Data Validation: Ensure that all required fields have values and that data meets Salesforce’s validation rules.

3) User Permissions:

     ◦ Profile and Permission Set Configuration: Ensure that the user performing the migration has the necessary permissions to create, update, and delete records in

        Salesforce.

     ◦ API Access: Verify that API access is enabled for the user performing the data migration.

4) Backup and Export:

     ◦ Backup Source Data: Export and backup all source data before beginning the migration process to avoid data loss.

     ◦  Salesforce Data Backup: Consider backing up existing Salesforce data if the migration involves updating or merging existing records.

5) Sandbox Testing:

    ◦ Test in Sandbox: Before migrating data into the production environment, perform the migration in a Salesforce sandbox to test for issues and ensure data integrity.

     ◦ Dry Run: Conduct a dry run of the migration process using a small subset of data to identify potential issues.

6) Data Loader or Tool Setup:

     ◦ Data Loader Configuration: Ensure Data Loader (or your preferred migration tool) is installed and configured correctly, including login credentials and settings.

     ◦ Batch Size Settings: Set appropriate batch sizes in Data Loader to prevent timeouts or API limits from being exceeded.

1. Validate in Change Sets: Create a change set in the sandbox, add the custom objects, fields, and Apex classes, and validate the deployment in production to catch any errors without committing changes.
2. Perform User Acceptance Testing (UAT): Ensure UAT is completed in the sandbox before deployment.
3. Deploy Change Set: After validation, deploy the change set to production.
4. Post-Deployment Testing: Verify that all components are working correctly in production and that there are no post-deployment issues.

1. Review Validation Rules: Identify which validation rules caused the errors and temporarily deactivate them if necessary.
2. Fix Test Failures: Review the test classes to identify and fix any failures or modify the test data setup to align with the current data structure.
3. Retry Deployment: After addressing the issues, re-run the deployment process and ensure it passes successfully.

1. Include Profiles in Change Set: Add profiles and permission sets to the change set along with the components they need to access.
2. Review Profile Settings: Before deployment, review the profiles to ensure they contain the correct field-level security, object permissions, and user permissions.
3. Post-Deployment Verification: After deployment, verify that users have the expected access and no permissions are inadvertently changed.

1. Roll Back Changes (If Possible): If the deployment introduced critical issues, roll back to the previous state using backup or by redeploying the previous version.
2. Check Logs and Error Messages: Review debug logs and error messages to identify the root cause.
3. Fix the Issue: Make necessary corrections in the sandbox, thoroughly test them, and redeploy the fixed components to production.

1. Automate Testing: Ensure that all Apex tests are automatically run as part of the CI process, and no deployment occurs unless all tests pass.
2. Use Version Control: Keep all code and metadata in a version control system (e.g., Git) to track changes and manage deployments.
3. Monitor Build Process: Continuously monitor the CI build process for any errors or issues, and address them promptly.

1. Deploy in Stages: First, deploy from the development sandbox to the UAT sandbox, ensuring all components work as expected.
2. UAT Testing: Conduct thorough testing in the UAT environment and gather feedback.
3. Final Deployment: After successful UAT, deploy the same components to production, ensuring the process is identical to the UAT deployment.

1. Backup Production Data: Before deployment, back up production data and metadata.
2. Use Version Control: Revert the codebase to the previous stable version using your version control system.
3. Redeploy Previous Version: Use the previous version of your change set or metadata to redeploy the last known good configuration.
4. Communicate with Stakeholders: Inform stakeholders of the rollback and any potential impact on the system.

1. Use Record-Triggered Flow: Create a Record-Triggered Flow that triggers when a new Case is created.
2. Add a Condition: Set the condition to check if the "Priority" field equals "High."
3. Create Task Record: Use the "Create Records" element to automatically create a new Task with relevant details.
4. Activate the Flow: Test the flow with different case scenarios to ensure it works as expected.

1. Use Record-Triggered Flow: Set up a Record-Triggered Flow that runs when an Opportunity is updated.
2. Add Condition: Use a decision element to check if the "Stage" is set to "Closed Won."
3. Send Email: Use the "Send Email" action to send an email alert to the Account Owner.
4. Activate and Test: Test the flow to ensure the email is sent correctly when the Opportunity stage changes.

1. Use Record-Triggered Flow: Create a flow triggered when the Account record is updated.
2. Query Related Records: Use the "Get Records" element to retrieve all related Contacts.
3. Update Records: Use the "Update Records" element to update the desired fields on the Contacts.
4. Activate and Validate: Ensure that the flow correctly updates all related contacts when the Account is modified.

1. Use Scheduled Flow: Set up a Scheduled Flow that runs periodically.
2. Query Old Events: Use the "Get Records" element to find Event records with a date older than one year.
3. Delete Records: Use the "Delete Records" element to remove the selected events.
4. Activate and Monitor: Test and monitor the flow to ensure it runs as expected without impacting performance.

1. Use Fault Connectors: Add fault connectors to the "Send Email" action to handle errors gracefully.
2. Log Errors: Use the "Create Records" element to log errors in a custom object.
3. Continue Flow Execution: Ensure the flow continues with the next step even if an error occurs in sending the email.
4. Test Error Scenarios: Test the flow by simulating an email failure and verifying error logging.

1. Use Record-Triggered Flow: Set up a flow triggered when an Opportunity is updated with a discount greater than a specified percentage.
2. Submit for Approval: Use the "Submit for Approval" action to send the Opportunity for approval automatically.
3. Notify Approver: Use the "Send Email" action to notify the approver of the pending approval request.
4. Test the Process: Simulate different scenarios to ensure the approval process works as expected.

1. Create a Screen Flow: Start with a Screen Flow that prompts the user for necessary Opportunity details.
2. Add Dynamic Screens: Include additional screens for selecting related products and quantities.
3. Create Records: Use the "Create Records" element to create the Opportunity and related Product records.
4. Test User Experience: Run the flow in a sandbox to ensure that it guides users correctly and creates all necessary records.

1. Use Record-Triggered Flow: Set up a flow triggered when the custom object is created or updated.
2. Lookup Record: Use the "Get Records" element to find the related record based on the field value.
3. Update Lookup Field: Use the "Update Records" element to populate the lookup field with the ID of the found record.
4. Activate and Test: Ensure that the flow correctly updates the lookup field under various conditions.

1. Use Record-Triggered Flow: Create a flow triggered by changes to the Customer's active status.
2. Get Related Orders: Use the "Get Records" element to retrieve all Orders associated with the Customer.
3. Use Loop Element: Loop through each Order record to update its status to "Cancelled" or another relevant value.
4. Test the Flow: Test with different Customers to ensure all related Orders are updated appropriately.

1. Create a Screen Flow: Start by creating a Screen Flow that includes a dropdown list for the first selection.
2. Use Dynamic Choice: Use the "Get Records" element to populate the second dropdown list based on the first selection dynamically.
3. Use Conditional Logic: Apply conditional logic in the flow to guide users based on their selections.
4. Test the Flow: Verify that the flow correctly updates the dynamic choices based on the user's input.

1. Report Type: Use the "Opportunities with Accounts" report type.
2. Group by Account: In the report builder, group the report by the "Account Name" field.
3. Summarize Sales: Add a summary field to calculate the sum of the "Amount" field for each account.
4. Run and Save: Run the report to ensure it shows the total sales per account, then save it for future use.

1. Report Type: Choose the "Opportunities" report type.
2. Filter Criteria: Add a filter for the "Close Date" field, setting it to "Last Quarter."
3. Run Report: Run the report to display only the opportunities closed in the specified time frame.
4. Save the Report: Save the report with a descriptive name for future access.

1. Create the Report: Start with an Opportunities report.
2. Add Conditional Formatting: In the report builder, use the conditional formatting option to apply a color highlight to the "Probability" field where the value is less than 50%.
3. Run the Report: Review the report to ensure the highlighting works as expected.
4. Save the Report: Save the report with the conditional formatting applied.

1. Report Type: Use the "Cases" report type.
2. Row Grouping: Group the rows by "Account Name."
3. Column Grouping: Group the columns by "Case Type.”
4. Summarize by Count: Add a summary to count the number of cases for each intersection of Account and Case Type.
5. Run and Review: Run the report to ensure it displays the data in a matrix format.

1. Use Joined Report: Create a joined report with two blocks—one using the "Accounts without Opportunities" report type and another with the "Accounts with Opportunities" report type.
2. Configure Report Blocks: Ensure that the two blocks are correctly configured to show the relevant data for each scenario.
3. Run and Compare: Run the report to compare accounts with and without opportunities in a single view.

1. Report Type: Use the "Opportunities with Users" report type.
2. Group by Sales Rep: Group the report by "Owner Name" (Sales Rep).
3. Add a Summary Formula: Create a custom summary formula to calculate the average deal size by dividing the sum of "Amount" by the count of opportunities.
4. Run the Report: Ensure the report shows the average deal size per sales rep.

1. Create the Report: Start with a summary report grouped by "Region" and summarized by "Amount."
2. Create Dashboard: Go to the Dashboard tab and create a new dashboard.
3. Add Report to Dashboard: Add the report to the dashboard as a component, choosing the appropriate chart type (e.g., bar chart).
4. Configure Component: Customize the component to display the total revenue by region.
5. Save the Dashboard: Save the dashboard with the new component.

1. Open Report: Access the report you want to schedule.
2. Schedule Report: Use the "Subscribe" or "Schedule Future Runs" option to set the report to run every Monday at a specified time.
3. Add Recipients: Enter the email addresses of the users who should receive the report.
4. Save the Schedule: Confirm the schedule and save it.

1. Create the Report: Use the "Tasks and Events" report type.
2. Add Filter for Owner: Add a filter for the "Task Owner" field and set it to "Current User."
3. Run and Save: Run the report to verify that it shows only the tasks for the logged-in user, and then save it.

1. Custom Report Type: Create a custom report type with "Accounts" as the primary object and "Subscriptions" as the related object.
2. Build the Report: Use this custom report type to create a summary report grouped by "Account Name" and summarized by the "Revenue" field from the "Subscriptions" object.Admin Scenario Based Interview Questions
3. Run and Review: Run the report to ensure it accurately shows the revenue per account.
4. Save the Report: Save the report for future use.

1. Select Report Types: Create reports that summarize sales data by region, such as total revenue and number of closed deals.
2. Create Dashboard Components: Add components to the dashboard for each key metric, using charts like bar charts for revenue by region.
3. Filter by Region: Use dashboard filters to allow users to filter the view by specific regions.
4. Save and Share: Save the dashboard and share it with relevant stakeholders.

1. Create Reports: Create summary reports that show actual sales and sales targets.
2. Use Gauge Charts: Add gauge components to the dashboard to visually display performance against targets.
3. Set Ranges: Define ranges in the gauge charts to highlight whether the performance is below, meeting, or exceeding targets.
4. Deploy Dashboard: Save and deploy the dashboard to sales managers.

1. Create Dynamic Dashboards: Use the "View dashboard as" setting to create a dynamic dashboard that displays data according to the logged-in user's role.
2. Adjust Filters and Components: Customize filters and components to show relevant data for each role.
3. Assign Dashboard: Assign the dashboard to the appropriate user groups and test it to ensure it displays correctly for each role.

1. Use Real-Time Reports: Ensure the reports added to the dashboard are based on real-time data.
2. Enable Auto-Refresh: Set the dashboard to automatically refresh at a defined interval (e.g., every 15 minutes).
3. Choose the Right Components: Use components like tables and charts that can easily reflect real-time data changes.
4. Deploy Dashboard: Share the real-time dashboard with users who need immediate insights.

1. Create Joined Reports: Build joined reports that combine data from Leads and Opportunities.
2. Add Components: Use different dashboard components to display data from the joined report, such as pipeline stages for Opportunities and lead conversion rates.
3. Visualize Combined Data: Ensure the dashboard shows how Leads progress into Opportunities and the related outcomes.
4. Deploy Dashboard: After testing, share the dashboard with the sales team for insights into lead-to-opportunity conversion.

1. Reduce Report Complexity: Simplify the reports used in the dashboard by limiting the amount of data they pull.
2. Limit the Number of Components: Reduce the number of components in the dashboard to decrease load times.
3. Use Filters Wisely: Apply filters at the report level to ensure only necessary data is retrieved.
4. Schedule Dashboard Refresh: Set the dashboard to refresh at off-peak hours to improve performance during business hours.

1. Set OWD to Private: Go to Setup > Security > Sharing Settings, and set the OWD for Opportunities to "Private."
2. Enable Role Hierarchy: Ensure that "Grant Access Using Hierarchies" is enabled so that managers can access their subordinates' records.
3. Test Access: Verify that only record owners and their managers have access to Opportunity records.

1. Set OWD to Private: In the Sharing Settings, set the OWD for Cases to "Private."
2. Review Role Hierarchy: Ensure that the role hierarchy does not grant additional access beyond the owner if that's the requirement.Admin Scenario Based Interview Questions
3. Test the Configuration: Confirm that only the case owner can view and edit their cases, with no access to other users

1. Set OWD to Public Read-Only: In the Sharing Settings, set the OWD for Accounts to "Public Read-Only.”
2. Test Access: Ensure that all users can view account records but only the owners (or users with special permissions) can edit them.

1. Set OWD to Private: Set the OWD for the "Project" custom object to "Private."
2. Use Role Hierarchy: Ensure that "Grant Access Using Hierarchies" is enabled so that managers can access their subordinates' project records.
3. Verify Access: Test to ensure that only the record owner and their direct manager have access to the Project records.

1. Set OWD to Public Read/Write: In Sharing Settings, set the OWD for Leads to "Public Read/Write."
2. Test Access: Confirm that all users can view and edit lead records, promoting collaboration across the organization.

1. Set OWD for Contacts: Set the OWD for Contacts to "Public Read-Only" or "Public Read/ Write" depending on the level of access required.
2. Set OWD for Opportunities: Set the OWD for Opportunities to "Private."
3. Validate Settings: Ensure that all users can see Contacts, but only owners can see their Opportunities.

1. Set OWD for Cases: Set the OWD for Cases to "Public Read/Write."
2. Set OWD for Contracts: Set the OWD for Contracts to "Private."
3. Use Role Hierarchy: Ensure that the role hierarchy allows managers to access their team's contracts.
4. Check Access: Validate that users can collaborate on cases while maintaining restricted access to contracts.

1. Set OWD for Partners: Set the OWD for Accounts and Opportunities to "Private."
2. Use Sharing Rules: Create sharing rules to grant broader access to internal users while restricting partner users to only their records.
3. Test the Portal: Verify that partner users see only their records, while internal users have broader access.

1. Initial OWD Setting: Set the OWD for Vendor Agreements to "Private."
2. Create a Sharing Rule: After 30 days, manually or automatically create a sharing rule that changes access to "Public Read-Only" or "Public Read/Write."
3. Automation (Optional): Use a time-based workflow or scheduled Apex to automate the change in sharing rules after 30 days.
4. Verify Access Changes: Ensure that records change visibility correctly after the specified time period.

1. Set OWD to Private: Set the OWD for "Employee Records" to "Private."
2. Use Sharing Rules or Manual Sharing: Create sharing rules or manually share records only with the HR role or profile.
3. Restrict Field Access: Ensure that sensitive fields within Employee Records are further restricted using field-level security.
4. Test Access: Confirm that only HR personnel can access Employee Records, while others are completely restricted.

1. Create a Sharing Rule: Go to Setup > Sharing Settings > Opportunity Sharing Rules.
2. Criteria-Based Sharing: Set the rule type to "Based on Criteria" if specific conditions need to be met or "Based on Record Owner" to share all opportunities.
3. Define Access: Share the records with the "Sales Manager" role and set the access level (e.g., Read/Write).
4. Save and Test: Implement the rule and verify that all opportunities are accessible to users in the "Sales Manager" role.

1. Create a Public Group: Ensure that a public group named "Marketing Team" exists.
2. Create a Sharing Rule: Go to Setup > Sharing Settings > Account Sharing Rules.
3. Rule Type: Choose "Based on Record Owner" or "Criteria" depending on the requirement.
4. Share with Public Group: Select "Marketing Team" as the group and set the access level to "Read Only."
5. Validate the Rule: Test the sharing rule by checking if members of the Marketing Team can view the accounts.

1. Create Sharing Rule: Navigate to Sharing Settings > Project Sharing Rules.
2. Criteria-Based Rule: Set the sharing rule to be based on the "Status" field being equal to "In Progress."
3. Assign Access: Share with the "Project Managers" role and set the access level to "Read/ Write" or "Read Only" as required.
4. Test the Configuration: Ensure that when the status changes to "In Progress," the Project Managers role gains access.

1. Create a Public Group: Confirm that a public group named "Support Team" exists.
2. Create a Sharing Rule: Go to Setup > Sharing Settings > Case Sharing Rules.
3. Criteria-Based Sharing: Define the rule to share cases where "Case Type" equals a specific value (e.g., "Technical").
4. Assign to Public Group: Share the cases with the "Support Team" group, granting the desired access level.
5. Verify Access: Test to ensure the Support Team group members can access the cases based on the type.

1. Create Role Hierarchies: Ensure that both teams are part of a role hierarchy where the higher-level role can access lower-level records.
2. Create a Sharing Rule: Set up a sharing rule in Sharing Settings > Contact Sharing Rules.
3. Owner-Based Sharing: Define a rule based on record owner and specify the roles or public groups that need access.
4. Apply Access: Set the access level to "Read/Write" or "Read Only" as needed.
5. Test Hierarchical Sharing: Verify that the higher-level team can access the Contact records owned by the lower-level team.

1. OWD Settings: First, set the OWD for Contracts to "Private."
2. Create Sharing Rule: Go to Sharing Settings > Contract Sharing Rules.Admin Scenario Based Interview Questions
3. Role-Based Sharing: Create a rule to share all Contract records with the "Legal" role.
4. Restrict Others: Ensure no other sharing rules inadvertently grant access to non-Legal users.
5. Test Restricted Access: Verify that only users in the Legal role can view the Contract records.

1. Create Public Group: Create a public group for the project team if one doesn't exist.
2. Create a Sharing Rule: Define a sharing rule in Sharing Settings > Opportunity Sharing Rules.
3. Time-Based Workflow: Use a time-based workflow or Apex to revoke the sharing rule or manually remove it after the project ends.
4. Test Temporary Access: Ensure that the project team has access during the project and that access is revoked afterward.

1. Create Partner Roles: Ensure external users are assigned to partner roles with restricted access.
2. Create Sharing Rules: Define sharing rules based on ownership or criteria in Sharing
   • Settings > Account and Opportunity Sharing Rules.
3. Set Access for Partner Roles: Share the records with the partner roles, ensuring they only get access to their related records.
4. Validate External Access: Test the sharing settings from an external user's perspective to confirm they see only their data.

1. Create Assignment Rule: Go to Setup > Lead Assignment Rules and create a new rule.
2. Define Criteria: Set criteria to assign leads based on the "Country" or "State" field values.
3. Assign to Queues/Users: Map each geographic region to the corresponding sales team's queue or user.
4. Activate Rule: Activate the assignment rule and test by creating leads from different regions to ensure they are routed correctly.

1. Create Assignment Rule: Navigate to Setup > Case Assignment Rules and create a new rule.
2. Define Criteria: Set criteria based on the "Priority" field (e.g., High, Medium, Low).
3. Assign to Support Tiers: Assign high-priority cases to Tier 1, medium to Tier 2, and low to Tier 3 support queues or users.
4. Test and Activate: Test the rule by creating cases with different priorities and activate the rule to ensure proper assignment.

1. Create Assignment Rule: Set up a Lead Assignment Rule with criteria based on the "Last. Modified Date" and status (e.g., "New" or "Open").
2. Time-Based Workflow: Use a time-based workflow or a scheduled process to check for leads not updated in 48 hours.
3. Reassign Leads: Define the rule to reassign these leads to a different sales rep or queue.
4. Test Automation: Ensure the rule works by simulating leads that are not contacted within the timeframe.

1. Create Case Assignment Rule: Navigate to Setup > Case Assignment Rules and create a new rule.
2. Define Priority Criteria: Set criteria where "Priority" equals "High."
3. Assign to Senior Team: Map the assignment rule to the senior support team’s queue or user.
4. Test Escalation: Test the rule by creating high-priority cases and ensure they are escalated to the senior team.

1. Set Up Auto-Response Rule: Navigate to Setup > Auto-Response Rules > Lead Auto- Response Rules.
2. Create a New Rule: Create a rule with criteria that triggers for all Web-to-Lead submissions.
3. Select Email Template: Choose or create an email template for the acknowledgment email.
4. Activate the Rule: Activate the auto-response rule and test by submitting a Web-to-Lead form to ensure the email is sent.

1. Create Multiple Rule Entries: In the Lead Auto-Response Rule, create separate rule entries based on the "Product Interest" field.

2. Assign Email Templates: Assign specific email templates for each product-related rule entry.

3. Activate the Rule: Test the auto-response by submitting leads with different product interests to ensure the correct email is sent.

1. Create Case Auto-Response Rule: Go to Setup > Auto-Response Rules > Case Auto- Response Rules.
2. Define Criteria: Create rule entries based on the "Case Origin" field (e.g., Email, Phone, Web).
3. Select Email Templates: Assign different email templates for each case origin.
4. Test the Response: Ensure cases from different origins receive the appropriate auto- response email.

1. Create Rule Entries by Country: In the Lead Auto-Response Rule, create rule entries based on the "Country" field.
2. Assign Language-Specific Templates: Assign email templates in the appropriate language for each country.
3. Activate the Rule: Test the auto-response by submitting leads from different countries to ensure emails are sent in the correct language.

1. Create Time-Based Criteria: Set up criteria in the auto-response rule to detect submissions outside of business hours.
2. Use Off-Hours Template: Assign an email template that informs the user of the next business day’s response time.
3. Test After Hours: Test by submitting leads or cases during off-hours to verify the correct auto-response is sent.

1. Order Rule Entries: Arrange the rule entries within the auto-response rule so that the most specific criteria are listed first.
2. Test Rule Priority: Submit records that meet multiple criteria to ensure the system applies the intended rule first.
3. Adjust as Needed: Reorder entries if the wrong auto-response is triggered.

1. Create an Escalation Rule: Go to Setup > Escalation Rules and create a new rule for cases.
2. Define Rule Entry: Set the criteria to escalate cases where "Priority" equals "High" and the case is not closed within 4 hours.
3. Assign Escalation Actions: Specify the action to notify a higher-level support team or manager.
4. Activate and Test: Activate the rule and simulate high-priority cases to ensure they are escalated after 4 hours.

1. Create the Escalation Rule: Navigate to Setup > Escalation Rules and create a new rule for cases.
2. Set the Criteria: Define the criteria to check if a case has been open for more than 24 hours.
3. Notify the Manager: Set the escalation action to notify the case owner’s manager or a specific user.
4. Test Escalation: Test the rule by creating a case and monitoring if it escalates after 24 hours.

1. Create the Escalation Rule: Set up a new escalation rule in Setup > Escalation Rules.
2. Define Multiple Rule Entries: Create rule entries for different time intervals (e.g., 4 hours, 8 hours) with escalating actions.
3. Assign Actions to Support Levels: Assign the escalation actions to different support levels or teams based on the time the case remains unresolved.
4. Test Multi-Level Escalation: Test the rule by creating cases and allowing them to remain open to trigger the different escalation levels.

1. Create Business Hours: Define the business hours in Setup > Company Profile > Business Hours.
2. Set Up Escalation Rule: Create an escalation rule that accounts for the defined business hours.
3. Off-Hours Escalation: Set criteria to trigger escalation actions for cases that remain unresolved outside of business hours.
4. Test the Configuration: Test by creating cases that remain open during off-hours to ensure proper escalation.

1. Create the Escalation Rule: Go to Setup > Escalation Rules and create a new rule.
2. Criteria Based on Priority and Time: Define criteria for different priorities and set the time- dependent triggers (e.g., 2 hours for High priority, 4 hours for Medium).
3. Set Escalation Actions: Assign actions based on the priority level to notify appropriate users or teams.
4. Test Time-Dependent Escalation: Simulate cases with different priorities to ensure they escalate correctly based on time.

1. Define Business Hours: Set up business hours for each time zone relevant to your cases.
2. Create Escalation Rule: Set up the rule with criteria that consider the time zone-specific business hours.
3. Time Zone-Based Escalation: Set the escalation actions to trigger based on the case's time zone.
4. Test Across Time Zones: Test the rule by creating cases across different time zones to ensure proper escalation timing.

1. Create a Matching Rule: Go to Setup > Matching Rules and create a new rule for Leads using the "Email" field.
2. Create a Duplicate Rule: Set up a Duplicate Rule for Leads that uses the matching rule created.
3. Block or Alert: Configure the rule to either block the creation of a duplicate lead or alert the user.
4. Test the Rule: Create test leads with the same email to ensure duplicates are either blocked or an alert is triggered.

1. Create a Matching Rule: Set up a matching rule for Contacts that includes both "Email" and "Phone Number" fields.
2. Create a Duplicate Rule: Create a Duplicate Rule for Contacts that references the matching rule.
3. Configure Alerts: Set the rule to alert users if a duplicate contact is found across different accounts.
4. Test the Rule: Create test contacts with the same email and phone number under different accounts to verify the rule

1. Create a Matching Rule: Set up a matching rule for Leads that identifies duplicates based on key fields (e.g., Email, Phone).
2. Create a Duplicate Rule: Configure a Duplicate Rule to run during the import process.
3. Set the Action: Choose whether to block duplicates, allow them, or alert users during the import.
4. Test with a Sample Import: Import a small sample dataset to ensure the rule correctly identifies duplicates.

1. Create a Duplicate Rule: Set up a Duplicate Rule for the relevant object (e.g., Leads, Contacts).
2. Set Action to Alert: Configure the rule to alert users of a potential duplicate without blocking the record creation.
3. Allow Override: Ensure the setting allows users to bypass the alert and create the record if they confirm the need.
4. Test the Override: Verify the functionality by attempting to create duplicates and overriding the alert.

1. Enable Duplicate Management: Ensure that Duplicate Management is enabled and configured to alert users.
2. Use the Merge Function: When duplicates are detected, use Salesforce's native merge functionality to combine records.
3. Data Retention: Choose which data to retain from the duplicate records during the merge.
4. Test the Process: Create duplicate contacts and follow the merge process to ensure data integrity is maintained.

1. Create Separate Matching Rules: Create individual matching rules tailored to the specific fields important to each record type.
2. Create Multiple Duplicate Rules: Set up separate Duplicate Rules for each record type, applying the appropriate matching rule to each.
3. Test Across Record Types: Create test records for each record type to ensure the duplicate rules work as intended for each scenario.

1. Create a Matching Rule: Set up a matching rule based on fields common to both Salesforce and the third-party data (e.g., Email, Name).
2. Create a Duplicate Rule: Implement a Duplicate Rule that checks for matches during data integration.
3. Integration Considerations: Ensure the third-party integration respects the duplicate rules set in Salesforce.
4. Test the Integration: Run a test import from the third-party system to confirm that duplicates are identified and handled appropriately.

1. Create and Activate Matching Rule: Ensure a relevant matching rule is created and activated for the object being imported (e.g., Leads, Contacts).
2. Configure Import Settings: Use Data Loader or Import Wizard and enable duplicate detection using the matching rule.
3. Run a Test Import: Import a sample dataset to verify that duplicates are identified based on the matching rule.

1. Create a Matching Rule: Set up a new matching rule for the relevant object (e.g., Contacts).
2. Multiple Matching Criteria: Use "First Name," "Last Name," and "Phone Number" as matching criteria with an exact match.
3. Test for Duplicates: Create records with the same combination of these fields to ensure they are flagged as duplicates.