Certified Administrator

The Support Process defines which Case Status values are available for a given record type. If “Closed” is not included in the Support Process being used, users won’t see it as an option.

A. The record type may control available picklist values, but the real control for Case Status comes from the Support Process.

C. The Close Case layout is only used to capture information, not to make the Closed status appear.

D. That checkbox affects reporting and visibility, but not the ability to select “Closed”.

Manage Cases permission gives users the ability to transfer case ownership.

System Administrators have full permissions, including managing and reassigning cases.

A manager role above the agent does not automatically grant ownership change rights unless specific sharing rules are in place.

Read permission on the account is not sufficient to change case ownership.

Criteria-based sharing rules allow administrators to automatically share records that meet specific conditions with other roles, groups, or teams.

Since both sales teams are peers under the same manager role, hierarchy alone will not grant access between them.

Manual sharing is not efficient for large teams.

Owner-based sharing is limited to record owners and their hierarchy, not peer-to-peer access.

Auto-response rules are designed to automatically send different email notifications based on criteria such as case priority.

The best approach is to create one auto-response rule with three rule entries, each filtered by case priority (Low, Medium, High).

Workflow rules cannot directly manage multiple templates for different criteria in this case.

Assignment rules are used to assign cases, not send confirmation emails.

Option C suggests creating three separate auto-response rules, but the recommended approach is one rule with multiple entries.

A Chatter Broadcast Group allows only group owners and managers to post updates, while all other members can only respond with comments.

This fits the requirement because the employee engagement committee can publish updates, and employees can engage without posting new updates.

Unlisted Group is for privacy but doesn’t control posting.

Recommendations is a feature for suggested connections/content, not posting.

Chatter Stream is for aggregating feeds, not restricting posting rights.

Escalation Rules are designed to automatically reassign or notify users when a case meets certain criteria, such as being open longer than a set period (in this case, 7 days).

Auto-Response Rules send automatic email responses, not ownership changes.

Assignment Rules work only at case creation, not after 7 days.

Validation Rules prevent saving invalid data but do not handle case ownership.

The correct setting for receiving notifications about unsuccessful data imports is “Import Completion Activity Notification Settings.” This configuration ensures that the responsible user is notified if the import process fails and action is required to maintain compliance.

A Dashboard Filter allows users to dynamically filter data in the dashboard by specific fields such as Case Origin, Status, or Owner, without needing to create multiple dashboards.

Bucket Column is used in reports to group values into categories, not to filter dashboards.

Dashboard Component is simply a visualization (chart, table, metric) but does not provide filtering capability.

Combination Chart is a type of chart, not a filtering option.

Therefore, the correct way to let agents drill down into the dashboard by fields like origin, status, or owner is to add a Dashboard Filter.

Permission Sets are the best practice when granting additional access to a specific group of users without modifying their profiles.

A Role (A) only controls record visibility in the role hierarchy; it does not provide object-level access.

Manual Sharing (B) is for sharing specific records, not granting access to an entire object.

New Profiles (D) would be too restrictive and hard to maintain compared to permission sets. Salesforce recommends profiles for base access and permission sets for exceptions or additional access.

The Lightning App Builder is used to create and customize:

– Record Pages → custom layouts for objects like Account, Opportunity, etc.

– App Pages → custom landing pages with components (like dashboards, reports, lists, etc.).

User page (B) doesn’t exist as a Lightning page type.

Dashboard page (D) is created in Reports & Dashboards, not in Lightning App Builder.

Record Types + Page Layouts are the tools in Salesforce to show different picklist values depending on the user.

B: With two record types (Sales, Marketing) and one picklist, you can configure record type-specific picklist values.

D: You can also have two page layouts with different picklists (Sales layout vs. Marketing layout) assigned by profile.

A: Permission sets do not control picklist values.

C: Having only one record type won’t allow controlling different picklist values.

When you need different stages (picklist values) for opportunities and different page layouts, the correct approach is to use Record Types + Sales Processes.

Sales Process defines which Stage picklist values are available.

Record Types link Sales Processes with Page Layouts and Profiles.

B (Public Groups) is about sharing, not record type/picklist management.

C is partially true (page layouts help) but it doesn’t control Stage values. That requires Sales Processes.

D (Validation Rules) ensures data quality, but doesn’t meet the need for separate sales processes.

In Salesforce, you can change a field from Auto Number to Text without losing the existing values. All current Auto Number values are kept as they are; however, once converted to Text, new records will not auto-generate a number — they will require manual entry or automation to populate the field.

Option A is misleading because there is no conversion; values are simply preserved as-is.

Option B is incorrect because Salesforce allows changing Auto Number to Text.

Option C is incorrect because the values are not deleted when changing from Auto Number to Text.

Flow Builder can be used to create an automation that updates related records — in this case, Opportunity Products — when certain conditions are met, such as when the Opportunity stage changes to “Closed Won.” The flow could:

1. Trigger when an Opportunity is updated to Closed Won.

2. Retrieve related Opportunity Product records.

3. Update each product’s discount field with the value from the Opportunity record.

– Approval Process is for routing records for approval, not mass-updating related records.

– Prebuilt Macros are used in Service Console for repetitive UI tasks, not for automated record updates.

– Formula Field calculates values dynamically but cannot perform mass updates on existing related records — it would just display the discount without physically storing it.

When creating a validation rule in Salesforce, there are two main components you must define:

1. Error Condition Formula — This is the formula logic that determines when the validation rule should trigger (evaluates to TRUE).

2. Error Message Location — This specifies where the error message should appear (either at the top of the page or next to a specific field).

– Formula return type is not a setting in the Validation Rule creation process; the rule formula always returns a Boolean value (TRUE or FALSE).

– Rule active date is not a feature of validation rules; activation is controlled by activating/deactivating the rule itself, not by a date field.

Email-to-Case is the standard Salesforce feature for automatically converting incoming customer emails into cases. When configuring Email-to-Case, the administrator can associate different email addresses with specific case queues. This ensures that incoming cases are routed directly to the correct queue without the need for additional automation.

Option A (custom email service) is unnecessary because Salesforce already provides Email-to-Case.

Option B (Flow) could be used for more complex routing, but it is not needed when queues can be set directly in Email-to-Case.

Option C (Escalation Rules) are for handling cases that remain open too long, not for initial assignment.

When a scheduled action is created in Process Builder (or Flow with scheduled paths), it is queued to run only if the criteria are still true at the scheduled time. If the record is updated and the criteria are no longer met, Salesforce automatically cancels the pending action.

In this case:

The criteria required that the job posting status ≠ Interviewing.

On the 10th, the status changed to Interviewing.

Because the criteria are no longer true, the scheduled Chatter post will be canceled.

Option A is incorrect: there is no “pause” feature for scheduled actions.

Option B is incorrect: the action is not executed immediately when the status changes.

Option C is incorrect: it won’t send in 30 days because the condition is no longer valid.

When Salesforce users need to access data stored in an external system, the best approach is to use External Objects through Salesforce Connect. External objects mirror data that resides outside of Salesforce (such as shipment information), and administrators can expose them in the UI by adding a custom tab.
This way, support agents can seamlessly view shipment records inside Salesforce without needing to duplicate or import the data.

Option A is irrelevant; split views are for record navigation, not for connecting external systems.

Option C (Manage List Views) only allows more control over list views, not external data integration.

Option D (filter by record type) assumes shipment records exist in Salesforce, which is not the case here.

When an organization deploys My Domain, Salesforce recommends using the branded login URL (e.g., https://nto.my.salesforce.com). However, during the transition period, users may still attempt to log in using https://login.salesforce.com.

To allow a grace period while ensuring users are guided to update their bookmarks, the administrator should configure the Redirect Policy to Redirect with a warning. This way:

Users attempting to log in through the old login page are automatically redirected to the branded domain.

They see a warning that informs them to update their bookmarks.

Option A would simply not redirect, which does not help with enforcing the branded domain.

Option B and C would block logins from the old URL, not giving users a transition period.

Option D is the correct balance: redirect + warning = grace period.

Case Assignment Rules allow administrators to automatically assign new cases to a queue or a user based on criteria such as account fields, case origin, or custom fields.

In this scenario:

Cases from Silver/Gold accounts → Regular Support Queue

Cases from Platinum accounts → Priority Support Queue

This is exactly what Assignment Rules are designed to do.

Workflow Rules can update fields or send notifications but cannot assign cases to queues.

Case Rules is not a Salesforce feature (the exam may include it as a distractor).

Escalation Rules manage cases that remain open too long; they don’t handle initial assignment.

When creating a case manually in Salesforce, there is a checkbox labeled “Assign using active assignment rules.” If this checkbox is selected, Salesforce will apply the assignment rules — even for manually created cases.

In this scenario, the administrator’s assignment rule is moving cases into the Automated Cases Queue, which is why manually created cases also end up with the wrong owner.

Option A is incorrect because assignment rules don’t stack like that; only one rule set runs at a time.

Option C is irrelevant; the issue isn’t with missing fields on forms.

Option D is incorrect because escalation rules don’t reassign ownership at case creation — they only apply after a case has been open too long.

Campaign Hierarchy allows you to link multiple related campaigns (e.g., each monthly event) under a parent campaign (e.g., “2025 Networking Series”).

This enables you to report individually (by month) and cumulatively (entire series), including ROI.

Record Types (A) do not help with ROI reporting, they’re for layout/fields.

Individual Campaigns with same name (B) creates confusion and reporting issues.

Campaign Member Statuses (D) track engagement (invited, attended, no show), not ROI per month.

A user cannot be deactivated if:

– They are the only recipient of a workflow email alert. (There must be another recipient assigned first.)

– They are referenced in a custom hierarchy field (like “Approver” fields).

Being the highest role in the role hierarchy (B) does not prevent deactivation; the role can stay empty.

Being part of a territory hierarchy (D) also does not block deactivation; they can be removed.

The best practice is to use Record Types + Page Layouts.

This way, when an agent creates a record for a house, they see one page layout with the appropriate fields.

When it’s a condominium, the record type will display a different page layout with the extra steps (fields) required for that scenario.

Business processes (A) and just fields (B) are not sufficient, because they don’t allow different layouts with different steps.

Option D is close, but it still uses one page layout, which means the extra steps would show for all records, not just condominiums.

Flow Builder allows admins to create guided screen flows that walk users step by step through data entry.

Instead of overwhelming users with many fields at once, a screen flow can present fields in smaller groups, validate input, and automate actions in the background.

Validation Rules (A) enforce data quality but don’t simplify the form.

Workflow Rules (B) are limited and can’t guide the UI (and they are deprecated in favour of Flow).

Approval Processes (D) are for requesting approvals, not for simplifying data entry.

The company wants to differentiate the leads entered by interns from existing leads.

The best way is to use a record type, which allows categorizing records (for example, “Intern Lead” vs. “Standard Lead”).

Then you can filter in reports, dashboards, or processes to easily identify intern-created leads.

A (Lightning App) only changes UI, doesn’t mark records.

B (Web-to-Lead) is for capturing leads from a website, not relevant here.

D (Assignment Rules) are for routing leads, not identifying who created them.

The Geolocation field type stores latitude and longitude coordinates, making it the right choice to track product shipments or map locations.

External lookup is for linking external data sources (not for coordinates).

Custom address stores addresses (street, city, etc.), but not precise lat/long coordinates.

Geofence is not a Salesforce field type.

To track multiple designs for one product, the correct approach is to create a custom object (Shoe Designs).

Then, establish a master-detail relationship between Shoe Designs and Product, so that each design is related to a specific product.

This also allows roll-up summary fields (e.g., to count how many designs a product has).

B (lookup field) could technically relate objects, but master-detail is the best option here since you want roll-up summary and tighter dependency.

C is invalid because Salesforce does not have a standard object for designs.

Flow Builder is the only automation tool in Salesforce that can create screen flows — interactive screens that allow users to input and see data in real time. In this case, a discount calculator requires user interaction, which cannot be achieved with Process Builder, Workflow Rules, or Platform Events.

Process Builder and Workflow Rules are designed for automated background actions, not for displaying screens.

Platform Events are used for event-driven architecture, not for creating UI elements.

A fault connector in Flow Builder allows administrators to handle errors gracefully by guiding the user when something goes wrong. Instead of showing a default, technical error message, the administrator can configure a screen that clearly explains what caused the error and how to fix it — in this case, prompting the user to enter more account information before starting the flow.

Option A (Permission set) does not fix the underlying data issue.

Option B (Removing validation rules) is not recommended because it bypasses important data quality checks.

Option C only hides error messages but does not improve the user experience or solve the issue.

The most common reason for an error in approval processes is that the next approver is not valid (either inactive, missing, or incorrectly configured).

B (field-level security) affects visibility, but not whether the approval goes through.

C (delegated approver) is useful, but it’s not the first step in troubleshooting. The issue is usually with the primary approver.

D (page layout) is not relevant for system errors in approval routing.

When integrating Salesforce with external systems (like a data warehouse), the best practice is to use an External ID field to uniquely identify and match records between systems.

A (Unique ID) is internal to Salesforce and not ideal for cross-system matching.

B (External object) is used for real-time access via Salesforce Connect, but here the requirement is updating data, not just referencing.

C (Data Loader) is a tool to perform the update, but the actual matching mechanism still requires an External ID field.

Salesforce provides the feature Contacts to Multiple Accounts, which allows a single contact to be linked to multiple accounts without creating duplicate records.

This is perfect for independent contractors who may work with different agencies over time while keeping their history intact.

A (junction object) is unnecessary because Salesforce already supports this via standard functionality.

B would cause duplicate contact records, which is against best practices.

D (partner community) is for external collaboration, not tracking historical relationships.

To share records with a group in Chatter, you must first create a collaboration group (done manually by an admin or users with the right permission, not automatic).

For users to add records to a group, the Add Record action needs to be available in the group publisher.

B is incorrect because Salesforce does not create groups automatically for each department.

D is not required specifically to enable sharing; it’s just a UI enhancement.

A Validation Rule can enforce business logic by preventing users from saving a record when it does not meet defined criteria — in this case, when they try to move a Case status backwards.

Dependent Picklists are for controlling available values based on another field, not restricting backward movement.

Global Value Picklists only standardize picklist values across objects, but don’t enforce sequence.

Predefined Field Values are defaults for new records, not restrictions.

A Validation Rule is the best option because it allows enforcing conditions when saving a record.

In this case, the condition is: if Stage = “Closed Won”, then Lead Source must not be blank.

If users try to save an Opportunity as “Closed Won” without filling Lead Source, Salesforce will show an error message and prevent saving.

A. Lead Source cannot be made a dependent picklist of Opportunity Stage, since Stage is a standard field that cannot act as a controlling field.

C. Making Opportunity Stage read-only on the page layout would always block changes, not just under the required condition.

D. Opportunity Stage also cannot be a dependent picklist controlled by Lead Source.

C. Add the Campaign Member Statuses related list to the Page Layout: You manage Campaign Member Status values from the Campaign record (Lightning: related list; Classic: Advanced Setup). If that related list isn’t on the layout, you can’t get to the UI that lets you add/edit statuses. So this step is needed so you (or Marketing) can access and maintain the values.

D. Modify the picklist value on the Campaign Member Statuses related list: This is where you actually add, rename, set default, and reorder the statuses (e.g., add “Upsell Promo”). Those changes then apply per campaign, and you can choose to replace existing members’ statuses if needed.

A. Edit the picklist values for the Campaign Status in Object Manager: The “Status” on Campaign Member isn’t managed like a normal object picklist. You don’t add the usable values in Object Manager; you manage them from the Campaign’s Campaign Member Statuses UI.

B. Mass modify the Campaign Member Statuses related list: There’s no native “mass modify values” feature for defining statuses here. (You can bulk-update members’ statuses, but that’s different from adding/editing the list of available statuses.)

The field High Value Customer is a checkbox field. Checkbox fields are Boolean and can only have two values: True or False.

To evaluate them in a Flow Decision element, the correct approach is:

– Field: High Value Customer

– Operator: Equals

– Value: {!$GlobalConstant.True}

This ensures the flow checks if the checkbox is selected (True), and if so, skips the first screen and continues to the second.

A: Contains operator is used for text collections, not checkboxes.

B: “High Value Customer” is the field name, not a Boolean value.

C: Same issue as A, “contains” is not valid for Booleans.

B. Field-Level Security: Ensures that the sales manager can see the necessary fields in the report. If FLS hides the fields, even if they have access to the records, the data won’t display.

D. Folder Access: The report is stored in a report folder. To view it, the manager needs permission to access the folder.

E. Role Hierarchy: Since OWD is Private, the role hierarchy allows the sales manager (higher in the hierarchy) to see the records owned by their subordinates (sales reps).

A. Report Subscription: This only schedules and emails the report; it does not provide access.

C. Custom Report Type: Used to define which objects and fields are available in reports, but it doesn’t control access to data or reports.

External ID: This is the correct choice because it allows Salesforce to match records using an identifier from another system (like a financial or ERP system). It ensures that records can be inserted, updated, or upserted correctly without relying on Salesforce-generated IDs.

Rich Text field: Not suitable as it is for formatted text, not for unique identifiers.

Auto-Number field: Generates unique numbers within Salesforce, but it is not linked to an external system’s identifiers.

Record ID: While unique in Salesforce, it cannot be used reliably across external systems since those systems don’t have Salesforce record IDs.

A. From the fields palette, drag the field into the same position: Correct, because removing a field from a page layout does not delete the field. You can always re-add it from the palette.

D. Restore original page layout from a sandbox: Correct, because you can deploy or copy the layout back from a sandbox if needed.

B. Restore from the recycle bin within 15 days: Incorrect, because removing a field from the layout does not delete it, so it never goes to the recycle bin.

C. Clone the layout from a different profile and use save as: Incorrect, because cloning another layout does not guarantee restoring the exact previous state of this layout.

C. Currency Locale: Correct, because company settings include the default currency locale for the organization.

D. Default Language: Correct, because company settings also include the default language for the org.

A. Login Hours: Incorrect, this is configured at the profile level, not in company settings.

B. Password Policy: Incorrect, this is also configured separately, not part of company-wide company information settings.

A. Mark fields required on the page layout: Ensures that users cannot save the record without completing key fields.

C. Use validation rules: Adds logical conditions to enforce business rules and prevent saving incomplete or invalid data.

E. Configure Opportunity Path: Guides users through each stage of the sales process and highlights key fields at the right stage.

B. Use Flow to mark fields required: Incorrect, flows are not typically used for this requirement; validation rules and page layouts are more direct.

D. Enable guided selling: Incorrect, guided selling in CPQ is different and not used for standard Opportunity management.

The best way to make a screen flow available from a Case record is to embed it in the Lightning Record Page for the Case object.

This ensures that service reps can access and run the flow directly from the Case without needing to navigate elsewhere.

Home Page is incorrect because the flow needs to be specific to Cases.

Page Layout is incorrect because layouts don’t directly embed flows, they manage fields and sections.

Component Filter is incorrect because it only controls visibility, not distribution.

When different picklist values should be available depending on the kind of Opportunity, the administrator must manage this through Record Types.

Record Types allow assigning different picklist value sets to different business processes or record categories.

Fields and relationships is where you define the field, but it doesn’t control which values appear for each kind of opportunity.

Picklist value sets define the global set of values but not their conditional availability.

Related lookup filters only control lookup fields, not picklists.

Omni-Channel allows cases (and other work items) to be routed to agents automatically based on capacity (how much work they can handle) and skills (who is best qualified to handle the case).

Territory Management is for accounts and opportunities, not case routing.

Escalation Rules reassign cases after certain conditions or time limits, but they don’t consider agent workload or skill set.

Knowledge Management provides access to articles and resources but does not assign cases.

When the Restricted Picklist option is unchecked, Salesforce allows values that are not defined in the picklist (like “Unrated”) to be imported and saved.

If the field was a restricted picklist, importing a value not defined (such as “Unrated”) would have caused an error.

Options B and C are related to availability and visibility but do not affect the ability to import non-listed values.

Option D (global value set) does not explain why “Unrated” was accepted.

A validation rule is the best way to enforce conditional requirements, such as requiring “Loss Reason” only when the stage is Closed Lost.

Option A is incorrect because workflow rules cannot display error messages.

Options C and D (making the field required) would make “Loss Reason” mandatory in all situations, not just when the opportunity is lost.

Validation rules allow precise control of when the field must be filled.

The evaluation criteria for workflow rules always include when a record was created.

Lightning Sync can be used to synchronize contacts and events between Salesforce and Microsoft Exchange. However, emails cannot be synchronized using Lightning Sync. Nevertheless, emails can be attached to multiple contacts or records.

To ensure that all users must fill in a field at the time of record creation, whether manually or through a loading or automated process, the field should be set as required at the field-level security.

Using sharing rules, permissions can be granted to groups of users so they can view records of other users or roles not assigned to their hierarchy.

Through escalation rules, you can automate actions based on the time marked without a case being resolved. It will be possible to change the owner of a case or create notifications for the users responsible.

Through assignment rules, you can automate the creation of a case to either a user or a queue based on specified conditions.

To automate sending communications to customers in a Salesforce environment, first, you need to create a custom email template branded with the company’s identity. Second, you should create auto-response rules to automate the sending of emails once a case has been created.

The native Salesforce mobile app allows users to perform the same actions and view the same information as in the desktop version. The only functionality that cannot be accessed is the development console, which is focused on code usage.

Since standard profiles cannot be deleted or modified, to meet this requirement, it will be necessary to create a new profile where the ability to delete account records is disabled. Then, this profile should be associated with the corresponding users.

Through the Master-Detail relationship, a dependency is created between records of the objects. In this way, to create a record of a child object, it needs to be associated with a parent object obligatorily. Similarly, if a record of the parent object is deleted, in this case, the record of the child object will be deleted as well.

Users who have permission to create or edit an object, as well as administrators, will be able to update a record that has an inactive user as the owner.

Once a custom field is deleted, it can be recovered within a 15-day period. The deletion of custom fields can be expedited by using the “full deletion” to release the custom field allocation earlier.

With the support of joined reports in Lightning Experience, you will be able to create and convert unjoined reports into joined reports, rename and rearrange the order of report blocks, create cross-block summary formulas, which are formula fields that can access and use values from any of the reports available in the joined reports.

A personal account is an individual consumer with whom business is conducted. Personal accounts are used by organizations that operate with a B2C (business-to-consumer) business model. Additionally, accounts can be used as customers or as competitors.

A case assignment rule can have multiple entry criteria. Only one assignment rule can be active at a time. When activating one assignment rule, it will automatically deactivate another one.

Since collaboration rules are what is needed in this scenario, and collaboration rules cannot be created to share records with specific users, a public group with the user included has to be created. Additionally, since only some records need to be shared, the collaboration rule has to be based on criteria specified by the Sales Director.

When a Lead is qualified and converted, existing accounts and contacts can be selected, or new records can be created. Creating an opportunity is optional.

Leads can be contacts related to an account or individual consumers. Additionally, they can be imported through a file or automatically generated via a Web-to-Lead, for example.

A duplicate rule uses a matching rule to identify contacts that are considered duplicates, and multiple duplicate rules can be activated at the same time on the same object. Multiple fields can be used in matching rules. The actions of blocking or allowing are set in the duplicate rule.

The time field type can store a time value not linked to a date. You can select a specific time of the day. In this case, two fields would be created: one for the entry time and another for the exit time.

Assignment rules are used to specify which cases need to be assigned to specific users or queues. Escalation rules, on the other hand, are used to reassign cases or send notifications when cases are not resolved.

If the object collaboration rule for ‘Account’ is marked as ‘private,’ the records of the object will only be visible to the record owners. However, enabling ‘Allow Access Using Hierarchy’ will grant access to users who are higher up in the role hierarchy.

Since it cannot be disabled for standard objects, the hierarchy will need to be configured in a way that the global Sales Director role is not at the top of the hierarchy. Otherwise, the global Sales Director will have visibility of all accounts.

When setting up a single user, the email and username can be different. When setting up multiple users, the email becomes the username. The available profiles depend on the assigned license.
A user can have only one role and one profile assigned.

Matching via an external ID is possible on any object that has an external ID and can be imported through the Data Import Wizard. When the option to match via the external ID is selected, the Data Import Wizard detects existing records in Salesforce with an external ID that matches the specified values in the data load file.

An administrator can navigate to ‘Time-Based Workflow’ through Setup to view and cancel any pending time-based actions of a Workflow that are in the queue.

In Salesforce Classic, an administrator can make search filters either required or optional. In Lightning Experience, all search filters are required, even if they are marked as optional. If a search filter is defined on a search field, it is “required” in Lightning Experience, meaning a user can only select a value that meets the filter criteria.

Search filters are used to narrow down the records to be displayed. They can reference fields from both the source and target objects. Search filters can also reference fields from related records to the target object or fields related to the user.

Components can be added, edited, rearranged, or removed from a page layout using the Lightning App Builder.
Generally, components cannot be resized unless the property is enabled.

In Lightning Experience, the options “Manage Campaign Members” and “Import Leads and Contacts” will appear as options in the Data Import Wizard. The Data Import Wizard can be used to add or update up to 50,000 campaign member records.

A flow can be used to change the record type of an Opportunity when the stage field is updated to ‘Closed Won’. A page layout that does not have the delete button assigned to it can be assigned to the record type for all profiles except for the VP of Sales.
To prevent a record from being deleted in a related list, a validation rule can be used. The validation rule on a parent object would use roll-up summary fields to compare the number of closed opportunities before and after the record is deleted, and if it is different, prevent the deletion.

Backup & Restore is a Salesforce product that allows you to generate backups and restore data in the event of integration errors, malicious attacks, or incorrect data updates. It is compatible with both standard and custom objects.

The values in a picklist can be defined separately for each record type; they do not have to be added to all record types. When the values of a picklist are added, they are included as active and do not need to be activated.

In Lightning Experience, users can work with the Activities object through a related list or the “Activity Calendar”. The Salesforce administrator can set a default view for activities, but users can change it in their personal settings. If “Einstein Activity Capture” is enabled, the “Activity Calendar” becomes mandatory.
If a task is created on a contact record, the task will appear in the contact’s and the related account’s “Activity Calendar”. It can also be viewed in the “My Tasks” list view.

If a user is logged in and their session time expires, the user will still be able to view the information on the current page. However, when they try to perform any action, they will be logged out of the environment.

The Master-detail relationship is used to create a many-to-many relationship model between objects. A junction object is a custom object that is related to two Master-detail relationships and is used to establish a relationship between two objects.
Both are necessary to build a many-to-many relationship between two custom objects. The junction object is used to relate two objects that need to have a many-to-many relationship. The junction object has a Master-detail field with each of the objects it relates to.

My Domain” allows Salesforce administrators to define subdomains for the URL of their environment. The defined subdomain replaces the instance pod in all URLs within the org. My Domain is required for some functionalities like Single Sign-On and certain custom Lightning components, as well as some managed packages.

When an event is manually created from Gmail using the Gmail Integration, any matching record will be automatically selected if Salesforce is configured for activity sharing. An administrator must ensure that the “Allow users to relate multiple contacts to tasks and events” option is enabled within Salesforce Setup under the “Activity Settings”. It is possible to relate an activity to up to 50 contacts or one lead. However, the integration only displays the first 15 records in the order they appear in the event.
All invitees can be included in a Salesforce record’s event by confirming that the “Attendees” field is available on the Event object’s page layout.
It is not possible to link events with internal users.

The Email template needs to be marked as “available for use” for users to be able to use it. Email templates can be created to be available for all users or only for specific user groups or roles based on the access granted to the Email template folders.

The sales path displays the status of the opportunity, key fields to fill in, and relevant information for each stage, such as links to Chatter, posts, and files. The opportunity automatically moves to the next stage once the current stage is marked as completed.

A custom URL can be created for a dashboard by adding parameters to the URL of the original dashboard. When a user accesses the custom URL, the dashboard opens with the pre-set filters. To add a filter to the original dashboard, you can add the parameter (fv0) and the value (=100000). The ‘fv’ value is set for the filter value. The number (0) in the parameter indicates the order in which the dashboard appears. Since there is only one filter, ‘fv0’ should be used as the parameter for the filter. The ‘&’ character denotes a new parameter in the URL. As a result, the modified URL should appear as ‘https://my-domain-name.lightning.force.com/lightning/r/Dashboard/01>6g00000Rw4zEAC/view?queryScope=userFolders&fv0=100000′.

To fulfill this requirement, a flow variable named “recordid” needs to be created in the flow. This variable should be available as an input. The quick action on the Lightning page should pass the record to this flow variable. The flow can then access the record to retrieve the required information for sending the email, so there is no need to add the “get record” action to the flow to fetch the record from the store.

The objects Candidates, Campaigns, Opportunities, and Orders are related to sales. The remaining objects mentioned, such as Cases or Service Contracts, are support objects.

The default localization is found in the company information and determines how dates, times, and numbers are displayed in the environment. It is set in the company information but can be modified by each user.
Given this statement, the most efficient approach would be to notify the affected users and have them change their localization in their user settings.

Workflow actions include updating fields, creating tasks, sending email alerts, and outbound messages. There are no workflow actions to create events, create records, or use email templates.
Starting from Winter ’23 Salesforce update, it is recommended to use Flows for creating automated actions on the platform.

Following the execution order established by Salesforce, the order would be: validation rules, auto-response rules, workflow rules, and escalation rules.

The first step that must always be followed for this type of requirement is to go to Salesforce’s own marketplace for applications, AppExchange.

Email alerts use email templates that need to be configured before creating the alert. Email alerts can be sent to users, roles, record owners, or public groups.

By using the functionality to include null values using Data Loader, fields without information can be loaded. Blank fields in a .csv file are treated as fields that do not need to be modified by Data Loader, and therefore the value would not change from existing to empty.
This option is unchecked by default and needs to be enabled.

The owner of a case can be modified by the current owner of the case, any user with a higher role, and by other users who have the “Modify All” option enabled for the case object in their profile, such as the System Administrator.

Enabling the “Hide Report Information” feature in the auto-response configuration of Web-to-Case is the only requirement that can be hidden so that a customer does not enter data when case creation fails.

You can create a matrix report and group the Opportunity Stage and Owner fields in rows and columns. The fiscal period field can be included in both rows and columns.

Public groups can contain a combination of users, roles, users assigned to specific territories, and roles and subordinates.
Profiles and permission sets cannot be assigned to public groups.

A user can be reactivated by checking the “Active” checkbox again.

Global Value Sets allow you to define a set of picklist values once and reuse them in custom picklist fields. Common and reusable picklist values do not exist as features. Master picklists are a feature used with record types to define all possible values that can be used in any record type.

Lightning App Builder can be used to modify existing record pages or create new page layouts. The Sales Path is a standard component that can be removed from the opportunity record page. The “Set Component Visibility” option of the Sales Path can be adjusted based on filtering criteria. This filtering criterion will hide the Sales Path for users with the Sales profile.

The steps to follow when creating a new custom field are:

– Choose the field type.
– Enter the field details and help text.
– Choose the field security for each profile.
– Choose the page layouts that will have access to the field.

Macros can be compatible with all objects with feed-based page layouts. By enabling macros, customer service agents can perform multiple tasks more efficiently with just a click.

Of the actions included in the statement, the one that allows entering information in Flows is the Screen action. Quick Actions cannot be used in Flows.

The combination of creating a picklist with the values that users can choose from and adding a validation rule that requires the field to be filled in when necessary is the best option to ensure correct information and accurate reports. The field can be created alone, but without the validation rule, there is no guarantee that the field will always have the required information.

Any custom object, such as Cases, Leads, Orders, Service Contracts, and Articles, can be assigned to queues. Once queues are activated, a list view is created for Cases, Leads, and Custom objects when they are assigned to queues. An object can be manually assigned to a queue by a user, and for Leads and Cases, it can also be done through assignment rules. Lastly, only members of a queue can accept records associated with that queue.

The business process related to opportunities is the “Sales Process”. The other processes mentioned are related to different objects.

When a Salesforce environment is configured as private, each user will only be able to view the information of the records they own. This also applies to reports, which will be tailored to display information based on the records owned by the user.

“To enable multiple accounts to be related to a single contact, the ‘Contacts to Multiple Accounts’ functionality must be enabled. Once enabled, the related list of Related Accounts needs to be added to the contact page layout, and the related list of Related Contacts needs to be added to the account page layout. The related list of Contacts on the account object can be removed as the new related list ‘Related Contacts’ will include both directly and indirectly related contacts.”

Salesforce workflow rules can be evaluated using these three valid criteria:

• Created: Triggers only when a new record is created.
• Created, and every time it’s edited: Triggers on creation and on every edit, regardless of whether the record meets the criteria again.
• Created, and any time it’s edited to subsequently meet criteria: Triggers on creation and when a record transitions from not meeting to meeting the rule criteria.

Reports in Salesforce can be exported in two different ways: Detail-Only Report or Formatted Report. If exported as “Detail-Only,” it can be exported in .xls, .xlsx, or .csv formats. On the other hand, if it is exported as “Formatted,” it can only be exported as .xlsx.

The Sales Dialer allows you to make and receive calls, add notes to the call, and record information about the calls. Calls can be made by clicking on any phone field in the Contact, Lead objects, and list views.
It is only available in the Lightning version. It also allows call recording, and this feature does not require an additional plugin.

CTI can receive calls, record them, and store them for compliance purposes. It can also identify the caller and display their information.
For outbound calls, it can offer automatic dialing and click-to-call functionality.
IVR (Interactive Voice Response) can be used to automate voice messages.
As advanced features, it is possible to display actions or recommendations based on the topics of the conversation.

When a custom field is deleted in Salesforce, some of its properties are lost and need to be set again. If the field is recovered, the relationship becomes a Lookup, so it would need to be changed to a Master-Detail relationship if necessary.
The same applies if the field was required; it would need to be marked as required again once it is recovered from the recycle bin, if necessary.

To connect a LinkedIn account with Salesforce, you need to set up the account through the Setup section, specifically the LinkedIn Lead Gen section. Salesforce will connect to the LinkedIn Ads account. Once the connection is established, you need to map the fields from the LinkedIn forms to the Salesforce Lead fields so that they are directly created in the Salesforce platform from LinkedIn.

In the Lightning version, the use of folders and subfolders provides users with better organization when working with reports and dashboards. Within reports and dashboards, the action to create folders is located at the top right and can only be created in the ‘User Created’ section.
Additionally, folders and subfolders can be deleted and renamed.

During the configuration process of an approval process, it is possible to establish whether the record can be modified by a system administrator and/or the approver.

While “Public Read/Write/Transfer” only affects Case and Lead objects, the rest of the options are not correct, as they are available regardless of the object type. They are available for both standard and custom objects.

These two options allow an opportunity to be linked to a campaign effectively:

Primary Campaign Source: used to indicate the main campaign that generated the opportunity.

Campaign Influence Related List: enables multiple campaigns that may have influenced the opportunity to be associated with it, which is useful for marketing analysis.

In the process of converting a Lead, a new Account and Contact will always be created (provided that the Company field within the Lead is populated), and optionally, an Opportunity may be created or not.

Through the configuration, users can be granted permission to include rich text in their Chatter posts, questions, or file attachments. Rich text allows users to input values in bold, italics, or lists. It is also possible to add hyperlinks and graphics in the posts.

With record types, we can differentiate between different sales processes, values of picklist fields, and have different page layouts within an object. The configuration of record types can be done on any object, both standard and custom. The information will be displayed based on the permissions configured in the profile assigned to each user.

Formula fields are the best choice when you want to bring information from a “parent” object field to a “child” object. Through this field, the “child” object retrieves the information from the fields of the “parent” object, always keeping them updated with the value of the “parent” object.

During the conversion process of a Lead, a new Account and Contact will always be created (provided that the Company field within the Lead is filled), and optionally, an Opportunity can also be created or not. Additionally, the owner of the record can be selected.

When converting a lead in Salesforce, you can choose to associate it with an existing Account and/or Contact. This allows the system to merge the lead’s information into those existing records. However:

• Opportunities: You can create a new opportunity during conversion, but you cannot update an existing one.
• Custom objects: These are not part of the standard lead conversion process.

This option allows Sales Managers to view and report on all data, including opportunity records, without needing access to custom objects such as personal time-off requests. In a private sharing model, it is the only option that ensures full access to the necessary data for company-wide reporting, without altering permissions on unrelated custom objects.

If you’d like to polish it for an official document or training guide, I can give it an extra touch.

Search layouts are sets of fields displayed when searching for a record. In the search layout, you can configure which fields can appear and the display order.

You cannot delete any standard profile; the best option is to clone a standard profile and customize it according to the requested needs. In this case, you will clone a standard profile and remove the ability to delete contacts. Additionally, you will create a permission set that adds that functionality and assign it to the users who need to perform it. This way, you can maintain the profiles created in an environment more easily.

There are two possibilities to carry out the mentioned automatic actions in this option. On one hand, you can create a Process Builder that combines both actions (it is not necessary to create two separate ones); on the other hand, through a record-triggered flow, you could also create the requested actions.

El Path está disponible tanto en la versión escritorio como en la versión móvil y puede ser utilizado tanto en los objetos custom como en Leads, Opportunities, Quotes, Contracts u Orders.
También, el Path puede ser definido por tipo de registro dentro de un objeto.

When a screen flow, auto-launched flow, or scheduled flow fails to execute in the platform, the error is saved in the platform and an email is automatically sent, including a link where you can access the flow and run a debug process to view the flow in more detail.
However, for event-triggered flows, errors are not stored in the platform, and if it comes from a managed package and is not a template, the error is displayed as an Apex test method.

Creating filters, grouping, and adding charts is possible during the creation of a report. Subscription-related actions are available once the report has been saved and executed.

Through Flow Builder, it is possible to assign an action to a Flow called “Send Survey Invitation”. Through this action, surveys can be automatically sent to Leads, Contacts, or Users.

Whenever possible, it is recommended to use the actions that Flow offers natively rather than those developed or coming from a managed package.

Both 15-character and 18-character Salesforce IDs, with case sensitivity, can be used as identifiers in Data Loader.

All the options mentioned can be set in the Organization-Wide Defaults configuration, but to fulfill the requirement stated in the statement, the correct option is “Controlled by Parent.”
The private option is restrictive to only the contacts where the users are the owners, while the other options apply to all users in the platform.

If the user creating a ListView has permission to make that List View public, they will have the ability to share it with any user, public groups, or roles in the platform. If they do not have that permission, they cannot share it with anyone.

Users can add their own identification method for the recipients of the email.

The “Mute Post” option removes all post notifications from the news feed and Chatter. It also mutes any notifications related to the post.

What is being requested in this statement is the ability to export records from the platform. To do this, it needs to be done through the “Export All” function of Data Loader.

Deleted records in the platform are stored in the recycle bin for 15 days.

Users can repeat an event daily, weekly, monthly, or as needed by selecting the “Repeat” checkbox in the Event object. This action is called an “Event Series” and cannot be configured from the activities settings.

Only a Custom Picklist and a Multi-select Picklist can be dependent fields in a field dependency relationship.

The approval process allows Salesforce users to establish control criteria that require another user to approve a budget. It can be configured on any standard or custom object.

By default, all users have their localization settings set to the company information, but each user can modify their own localization settings.

To be able to create a survey on the platform, it needs to be enabled in the “Survey Setup”. Once enabled, the quickest and easiest way to send a survey is through the existing action in Flows, setting the criteria of “Case Origin” and “Case Reason” as marked in the statement.

The requirement at this point is the automatic assignment of records to users. Through assignment rules, case assignments to users and queues can be automated on the platform.

A multiple-entry, multiple-queue case assignment rule is the way to define case routing in Salesforce.