Data and Analytics Management

244 questions

Question 1Question

An administrator needs to configure a weekly automated backup of all organizational data using the native Salesforce Data Export Service. Arrange the steps in the correct chronological order to complete this setup.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence for scheduling a weekly data export is: 1) Navigate to Data Export in Setup, 2) Click Schedule Export, 3) Configure file encoding and attachment options, 4) Set the frequency to Weekly along with the date and time window, and 5) Select the object data to export and save the schedule.
To set up an automated recurring backup in Salesforce using the native Data Export Service, an administrator must first access Data Export in Setup, choose to Schedule Export, specify encoding and attachment settings, establish the weekly frequency window, and select the objects to export before saving.

Step-by-Step Solution

1
Locate the Data Export tool in Setup.
Opens the Data Export administration page.
Setup is the central hub for administrative tasks including backup configuration.
2
Click Schedule Export.
Opens the scheduling interface for automated backups.
Export Now performs an immediate run, whereas Schedule Export creates a recurring job.
3
Define file encoding and attachment inclusion settings.
Ensures document attachments and chatter files are included if required.
Attachment settings must be configured prior to specifying scheduled times.
4
Set frequency parameters.
Schedules the export service to run weekly within specified date ranges.
Salesforce requires a start/end date and preferred execution window.
5
Select data objects and save.
Persists the scheduled export job in Salesforce.
Saving completes the configuration process.

Key Concept

Data Export Service Scheduling
Estimated Time:1m 0s
Question 2Question

A Salesforce Administrator is designing a complex executive dashboard in Lightning Experience to monitor sales performance across multiple territories. The leadership team requests the ability to dynamically filter the dashboard by four independent fields: Opportunity Stage, Close Date Quarter, Account Industry, and Lead Source. Additionally, they want a component displaying a stacked bar chart to show total opportunity amount grouped simultaneously by Account Industry and Opportunity Stage. Which combination of constraints and requirements must the administrator consider when building this dashboard?

Show answer & explanation

Answer: Salesforce allows a maximum of 3 dynamic dashboard filters per dashboard, so all four requested filter fields cannot be added simultaneously; additionally, the source report for the stacked bar chart component must contain at least two levels of grouping.

Answer

Salesforce Lightning dashboards support a maximum of 3 dynamic dashboard filters per dashboard, preventing all four requested fields from being added at once. To display a stacked bar chart component, the underlying source report must contain at least two groupings (e.g., grouped by row and column).
The option stating that Salesforce allows a maximum of 3 dynamic dashboard filters and requires at least two groupings on the source report for stacked bar charts is correct. Lightning dashboards enforce a limit of 3 filters per dashboard. A stacked bar chart requires a primary grouping (x-axis) and a secondary grouping (stack criteria), which must be established in the underlying source report.

Step-by-Step Solution

1
Evaluate the limit on dynamic dashboard filters in Salesforce Lightning Experience.
Salesforce enforces a strict limit of 3 dashboard filters per dashboard.
The leadership team requested 4 dynamic filters (Stage, Quarter, Industry, Lead Source), which exceeds the platform limit of 3 filters.
2
Evaluate the component grouping requirement for a stacked bar chart.
A stacked bar chart visually represents two dimensions of data.
For a dashboard component chart to show two grouping levels (Account Industry and Stage), the underlying source report must have at least two groupings configured.
3
Combine the filter limit rule and component source report requirements to select the correct configuration path.
The administrator must inform stakeholders of the 3-filter restriction while ensuring the source report has two groupings.
This satisfies standard Salesforce administration capabilities and report-to-dashboard component alignment.

Key Concept

Dashboard filter limits (maximum 3 per dashboard) and source report grouping requirements for complex chart components.
Question 3Question

Universal Containers requires an analytics solution to evaluate cross-departmental customer metrics. The Leadership team needs to view a side-by-side comparative analysis of Account records, displaying related Opportunities in one section and related Cases in another. Both data sets must be grouped by Account Owner along the rows and Calendar Quarter along the columns. Standard single-object report types cannot combine these two independent related objects into a unified view. Which report configuration should an administrator implement to meet these requirements while respecting record-level security?

Show answer & explanation

Answer: Create a Joined Report using standard report types for Accounts with Opportunities and Accounts with Cases, adding both blocks and matching row and column groupings across blocks.

Answer

The administrator should create a Joined Report using standard report types for Accounts with Opportunities and Accounts with Cases, adding both blocks and aligning row and column groupings across blocks.
Joined Reports are specifically designed to combine data from different report types into blocks within a single report view. As long as the blocks share common fields (such as Account Owner and Date fields), they can be grouped across blocks along rows and columns, satisfying the requirement to present Opportunities and Cases side-by-side while respecting user access permissions.

Step-by-Step Solution

1
Analyze the reporting requirements and underlying data structure.
Identified two separate child objects (Opportunities and Cases) related to a common parent object (Account) needing side-by-side matrix comparison.
Standard report types focus on single primary objects or linear parent-child relationships, making them incapable of presenting two separate child object streams in one report.
2
Evaluate available Salesforce report formats for multi-object aggregation.
Selected Joined Report format because it supports up to 5 report blocks based on different report types.
Joined reports enable joining distinct data blocks around common fields (Account Owner and Calendar Quarter) for cross-block grouping.
3
Verify security and governance constraints.
Confirmed that Joined Reports honor Organization-Wide Defaults and sharing rules for the logged-in user.
Each block in a joined report executes standard report visibility rules based on user access.

Key Concept

Joined Report Format and Cross-Block Groupings
Question 4Question

A financial operations manager at a global logistics firm requires a Salesforce report to analyze individual billing transaction records against custom target benchmarks. The manager needs a calculated column evaluating a record-by-record variance formula (Transaction_AmountBenchmark_AmountTransaction\_Amount - Benchmark\_Amount) for every individual transaction row. Additionally, the final report must summarize total transaction values formatted in a multi-dimensional grid grouped by Region along rows and Billing Quarter along columns. Which configuration should the Salesforce Administrator implement to fulfill these requirements?

Show answer & explanation

Answer: Use a Matrix report format, define a row-level formula to compute the record-by-record variance, and group the data by Region on rows and Billing Quarter on columns.

Answer

Use a Matrix report format, define a row-level formula to compute the record-by-record variance, and group the data by Region on rows and Billing Quarter on columns.
The correct option combines a Matrix report format (which allows grouping by both rows and columns to form a grid) with a row-level formula (which computes calculations for each individual record row).

Step-by-Step Solution

1
Identify the calculation granularity requirement.
Determined that the formula must calculate Transaction_AmountBenchmark_AmountTransaction\_Amount - Benchmark\_Amount for every individual record row.
Row-level formulas evaluate each record individually, whereas summary formulas evaluate grouped aggregations.
2
Identify the layout and grouping requirement.
Determined that the report requires two-dimensional grouping (rows and columns).
Matrix reports allow grouping by both rows (Region) and columns (Billing Quarter) to create a grid view.
3
Combine the report features into a single solution.
Select Matrix report format with a row-level formula.
This combination addresses both row-by-row calculations and two-axis grid grouping.

Key Concept

Selecting Matrix report format for two-axis grouping and row-level formulas for record-by-record calculations.
Question 5Question

An administrator for a logistics organization is building a Lightning dashboard to analyze inventory performance across multiple fulfillment centers. The VP of Operations requests four dynamic dashboard filters: Fulfillment Region, Inventory Status, Product Family, and Supplier Tier. Additionally, the VP wants a stacked bar chart component that displays total inventory value grouped by Fulfillment Region and sub-grouped by Product Family. Which combination of configuration adjustments must the administrator make to successfully meet these requirements within standard Salesforce limits?

Show answer & explanation

Answer: Reduce the dynamic dashboard filters to a maximum of three criteria, and configure the source report with groupings by both Fulfillment Region and Product Family.

Answer

Reduce the dynamic dashboard filters to a maximum of three criteria, and configure the source report with groupings by both Fulfillment Region and Product Family.
Salesforce enforces a strict platform limit of up to 3 dynamic filters on any single Lightning dashboard. Additionally, to display a stacked bar chart component, the underlying source report must contain at least two levels of grouping (such as row and column groupings in a summary or matrix report) so that the chart can plot values on the main axis and stack them by a secondary category.

Step-by-Step Solution

1
Evaluate the dynamic dashboard filter requirements against Salesforce limits.
Salesforce Lightning dashboards allow a maximum of 3 dynamic filters per dashboard. The requested 4 filters exceed this limit, requiring consolidation or removal of one filter.
System limits on dynamic filters are fixed across all editions.
2
Evaluate component source report grouping requirements for a stacked bar chart.
A stacked bar chart requires two groupings: one for the primary axis (x-axis) and one for the stacked series (color breakdown).
Without at least two groupings (e.g., grouped by Fulfillment Region and Product Family), a stacked bar chart component cannot be rendered.
3
Combine the necessary adjustments into a single configuration plan.
The administrator must select the 3 most critical dynamic filters and format the source report as a summary or matrix report with 2 groupings.
This satisfies both the platform dashboard filter limits and component display prerequisites.

Key Concept

Dashboard Dynamic Filter Limits and Chart Component Grouping Requirements
Estimated Time:2m 0s
Question 6Question

A Salesforce Administrator is building an executive leadership dashboard in Lightning Experience to monitor cross-departmental operations. The dashboard includes components sourced from three distinct custom report types: 'Opportunities with Products', 'Accounts with Assets', and 'Cases with Solutions'. The administrator needs to configure global dashboard filters and visual component displays. Which TWO statements accurately describe the technical requirements and constraints for this dashboard configuration? (Select 2)

Select all that apply

Show answer & explanation

Answer: Source reports do not need to share identical field API names to be filtered by a single dashboard filter, as long as the administrator manually maps a compatible data type field from each report type.; A dashboard component configured as a stacked bar chart requires the underlying summary source report to have at least two levels of field groupings defined.

Answer

Source reports do not need to share identical field API names to be filtered by a single dashboard filter as long as compatible data types are mapped, and stacked bar chart components require the source report to have at least two levels of field groupings.
The correct options accurately identify that dashboard filters can map to different field API names across distinct source reports as long as data types are compatible, and that stacked bar chart components require two levels of grouping in the source report to display stacked segments.

Step-by-Step Solution

1
Evaluate dashboard filter mapping mechanics across different custom report types.
Confirm that each dashboard component allows the administrator to choose which field from its underlying source report maps to the global filter. The fields do not need matching API names across different report types as long as data types align.
Salesforce dashboard architecture decouples filter definition from individual source report field names to allow heterogeneous reports on a single dashboard.
2
Analyze grouping prerequisites for multi-dimensional chart components like stacked bar charts.
Determine that stacked bar charts require two grouping levels (X-axis grouping and bar segment stacking grouping).
Without a second grouping level in the underlying report, the component cannot separate data into stacked color segments.
3
Validate security rules for dynamic dashboards and filter limits.
Confirm that dynamic dashboards adhere to user record-level access and that dashboards are limited to 3 filters with 50 values each.
Dynamic dashboards ensure users only see data they are permitted to access based on standard Salesforce security models.

Key Concept

Salesforce Dashboard Component Groupings and Dashboard Filter Field Mapping Constraints
Question 7Question

A Salesforce Administrator is configuring a sales operations dashboard in Lightning Experience that incorporates components derived from both Account and Opportunity report types. The management team wants to filter the dashboard by Region and requires that managers see only the data they have permission to access. Which two considerations must the administrator keep in mind when configuring the dashboard components and dynamic filters? (Select 2)

Select all that apply

Show answer & explanation

Answer: A maximum of 3 filters can be added to a single dashboard, and fields must be mapped explicitly if the source report types do not share identical field names.; Configuring the dashboard to run as the logged-in user allows viewers to see data based on their own access permissions without granting access to restricted records.

Answer

The administrator must account for the limit of 3 dashboard filters with explicit field mapping across different report types, and understand that running dynamic dashboards as the logged-in user respects individual user record permissions.
The correct statements recognize that Salesforce imposes a hard limit of 3 filters per dashboard requiring explicit field mapping when source reports differ, and that running dynamic dashboards as the logged-in user strictly enforces existing record-level access control.

Step-by-Step Solution

1
Evaluate dashboard filter limits and mapping rules for multiple report types.
Salesforce limits dashboards to 3 filters, and components using different report types require explicit field mapping for the filter to work across all components.
Different source reports may reference distinct objects (Accounts vs. Opportunities), so explicit field mapping tells the dashboard engine which field to filter on for each component.
2
Analyze security and dynamic running user settings.
Dynamic dashboards running as the logged-in user restrict displayed data strictly to what each user has permissions to view.
Dynamic dashboards adapt visibility to the viewing user's security context without altering OWD or sharing access.

Key Concept

Dashboard Filters and Dynamic Dashboard Security
Question 8Question

A Salesforce Administrator at Ursa Major Solar is creating an Account report to target key clients for an upcoming marketing campaign. The report must satisfy the following business requirements:

1. Include Accounts where the Type is either 'Customer - Direct' or 'Customer - Channel'.
2. Include Accounts that have at least one Closed Won Opportunity with an Amount exceeding $50,000.
3. Exclude any Accounts that currently have open Cases with a Priority of 'High'.

The administrator has created the following initial standard field filters on the Account report:
1. Account Type equals 'Customer - Direct'
2. Account Type equals 'Customer - Channel'

Which combination of filter logic and cross filters should the administrator configure to meet these requirements?

Show answer & explanation

Answer: Set Filter Logic to '1 OR 2'. Add a Cross Filter for Accounts WITH Opportunities, filtered by Stage equals 'Closed Won' and Amount greater than '50000'. Add a second Cross Filter for Accounts WITHOUT Cases, filtered by Priority equals 'High'.

Answer

Set Filter Logic to '1 OR 2' on the Account Type standard filters, add a Cross Filter for Accounts WITH Opportunities (sub-filtered by Stage equals 'Closed Won' and Amount > 50000), and add a second Cross Filter for Accounts WITHOUT Cases (sub-filtered by Priority equals 'High').
Applying custom Filter Logic '1 OR 2' ensures that accounts matching either 'Customer - Direct' or 'Customer - Channel' are selected. Cross Filters evaluate relationship criteria between parent and child objects without requiring schema modifications. Adding 'Accounts WITH Opportunities' sub-filtered by Stage equals 'Closed Won' and Amount > 50,000 isolates high-value deals. Adding 'Accounts WITHOUT Cases' sub-filtered by Priority equals 'High' excludes accounts with active critical issues. Multiple Cross Filters automatically join via AND logic with standard field filters.

Step-by-Step Solution

1
Group standard field filters using Filter Logic
Filter Logic '1 OR 2' evaluates Account Type for either 'Customer - Direct' or 'Customer - Channel'.
Standard field filters handle picklist field filtering on the primary report object.
2
Add a Cross Filter for related Opportunities
Configured 'Accounts WITH Opportunities' with sub-filters Stage equals 'Closed Won' and Amount > 50000.
Cross Filters with sub-filters restrict parent records based on specific child record criteria.
3
Add a Cross Filter for related Cases
Configured 'Accounts WITHOUT Cases' with sub-filter Priority equals 'High'.
The WITHOUT operator excludes parent records that have matching child records.

Key Concept

Combining standard Boolean Filter Logic with multiple WITH/WITHOUT Cross Filters and sub-filters
Question 9Question

A Salesforce Administrator is configuring a Custom Report Type to analyze relationships between Accounts (Primary Object) and Partner Surveys (Secondary Custom Object). The management team wants full flexibility to traverse lookup relationships for field selection and ensure accurate record inclusion based on survey responses. Which TWO configuration capabilities or constraints apply when defining the object relationships and field layout for this Custom Report Type? (Select TWO answers)

Select all that apply

Show answer & explanation

Answer: Fields from objects up to four levels away linked via lookup relationships can be explicitly added to the report layout using the 'Add fields related via lookup' feature.; Configuring the object relationship as 'Each record must have at least one related record' (with relationship) excludes parent Account records that have no associated Partner Surveys from appearing in reports.

Answer

The two correct statements are that fields up to four levels away via lookup relationships can be added to the layout using 'Add fields related via lookup', and that choosing the 'with' relationship ('Each record must have at least one related record') excludes parent records without matching child records.
Custom Report Types allow administrators to traverse up to four levels of lookup relationships to pull related object fields directly into the report layout using the 'Add fields related via lookup' feature. Additionally, setting the object relationship to 'Each record must have at least one related record' creates an inner join, requiring parent records to have corresponding child records to be displayed in reports.

Step-by-Step Solution

1
Evaluate object relationship join behavior
Selecting 'Each record must have at least one related record' acts as an inner join, filtering out Accounts that lack associated Partner Survey records.
Custom report types offer inner join ('with') and outer join ('with or without') options controlling record visibility.
2
Evaluate lookup field expansion capabilities
Administrators can click 'Add fields related via lookup' in the layout editor to reference fields up to 4 levels away from the primary/secondary objects.
This allows reports built on the custom report type to display referenced lookup object fields without creating redundant formula fields.

Key Concept

Custom Report Type Object Relationships and Layout Field Customization
Question 10Question

A Salesforce Administrator at a nationwide logistics provider needs to configure a custom Cases report to analyze service operations. The report must satisfy the following business requirements:
1. Categorize records into three resolution timeframe categories based on the numeric custom field 'Age (Days)': 'Critical' (greater than 14 days), 'Moderate' (5 to 14 days), and 'Prompt' (less than 5 days).
2. Display only Accounts that have closed cases with a Priority of 'High', while explicitly excluding Accounts that currently have any open Escalated cases.

Which two report builder configurations should the administrator implement to meet these requirements? (Select two.)

Select all that apply

Show answer & explanation

Answer: Add a Bucket Field based on the numeric 'Age (Days)' field, defining ranges for 'Critical', 'Moderate', and 'Prompt'.; Add two Cross Filters on the report: 'Accounts with Cases' filtered by Status equals Closed and Priority equals High, and 'Accounts without Cases' filtered by Escalated equals True and Closed equals False.

Answer

The administrator should add a Bucket Field on the numeric 'Age (Days)' field to group resolution timeframes into ranges, and add two Cross Filters ('Accounts with Cases' and 'Accounts without Cases') with appropriate subfilters to evaluate related case relationships.
Adding a Bucket Field on the numeric 'Age (Days)' field effectively categorizes numerical ranges into custom categories without formulas. Utilizing two Cross Filters ('Accounts with Cases' with secondary subfilters for closed high-priority cases, and 'Accounts without Cases' with secondary subfilters for open escalated cases) correctly evaluates parent-child record relationships.

Step-by-Step Solution

1
Configure record bucketing for numerical ranges
Created a Bucket Field on the numeric 'Age (Days)' field specifying ranges: >14 ('Critical'), 5 to 14 ('Moderate'), and <5 ('Prompt').
Bucket fields support numeric data types and allow administrators to quickly group ranges of values without creating custom fields or formulas.
2
Apply the first Cross Filter for qualifying related records
Added Cross Filter 'Accounts with Cases' with subfilters: Status = Closed and Priority = High.
Ensures the report only includes parent Account records that have at least one matching closed high-priority case.
3
Apply the second Cross Filter for excluding related records
Added Cross Filter 'Accounts without Cases' with subfilters: Escalated = True and Closed = False.
Excludes parent Account records that have open escalated cases.

Key Concept

Report Filtering, Filter Logic, and Bucketing
Question 11Question

Aegis Solar Solutions enforces a Private sharing model for Opportunities. A Salesforce administrator configures an executive sales dashboard to run as a static user, specifically the VP of Sales. When sales representatives view this dashboard and interact with its components, which two statements accurately describe how data visibility and security are applied? (Select 2 options.)

Select all that apply

Show answer & explanation

Answer: Dashboard components display summarized metrics reflecting all records accessible to the static running user, regardless of the viewer's individual sharing access.; Clicking a dashboard component opens the underlying source report, which displays only the records accessible to the logged-in viewer based on their own record-level security.

Answer

The correct statements are that dashboard components display summarized metrics reflecting all records accessible to the static running user, and clicking a component to open the source report restricts the detailed view to records accessible under the logged-in user's security context.
When a dashboard is set to run as a static user, the component summaries display data based on that running user's permissions, enabling viewers to see aggregated metrics for records beyond their personal sharing access. However, source reports always run under the logged-in user's security context. Therefore, when a user clicks a component to view the source report, Salesforce enforces the viewer's own Organization-Wide Defaults and sharing rules, displaying only the individual records they are authorized to see.

Step-by-Step Solution

1
Analyze how a static running user affects dashboard component visibility.
Dashboard components calculate and display aggregated data based strictly on the specified running user's (VP of Sales) object, field, and record access.
Static running users allow users with restrictive access to view high-level team performance metrics without granting broad record access.
2
Analyze what happens when a viewer drills down into the source report.
The source report executes under the logged-in user's context, evaluating Organization-Wide Defaults (OWD), sharing rules, and role hierarchy for that specific viewer.
Source reports never execute as the dashboard running user; they always enforce the active user's standard record-level security.

Key Concept

Static Dashboard Running User vs. Source Report Execution Context
Question 12Question

An enterprise administrator needs to bulk-import thousands of new child Service Contract records and automatically link them to existing parent Account records using Data Loader. The parent Account records already contain a unique custom External ID field named Legacy_Account_ID__c. What is the correct sequence of steps the administrator must follow to successfully map and relate the child records to parent Accounts using Data Loader?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence starts with verifying parent record External IDs in Salesforce, preparing the child CSV file with parent External ID foreign keys, initializing the Data Loader Insert operation, mapping the CSV column to the Account:Legacy_Account_ID__c relationship reference field, and concluding with executing the operation and inspecting success/error logs.
The workflow requires establishing prerequisites first (ensuring parent External IDs exist in Salesforce), preparing the child CSV file with those external keys, configuring Data Loader for the child object insert, mapping the CSV key column to the related parent External ID syntax (Account:Legacy_Account_ID__c), and finally running the import while checking the execution log files.

Step-by-Step Solution

1
Ensure parent Account External IDs exist in Salesforce
Salesforce Accounts are properly indexed and ready for external key matching
Data Loader cannot resolve foreign key relationships if the target external identifier field is blank or missing on parent records.
2
Prepare child record CSV with parent External ID column
Source CSV contains accurate foreign key references for each child row
Data Loader relies on foreign key values in the import file to determine which Account each Service Contract belongs to.
3
Initialize Data Loader Insert wizard for Service Contract
Data Loader parses CSV headers and connects to the Service Contract object schema
Selecting the proper object and file establishes the baseline schema mapping context.
4
Map foreign key column to Account:Legacy_Account_ID__c
Field mapping establishes a relational lookup using the parent External ID
Data Loader syntax requires selecting the related object's External ID field (Account:Legacy_Account_ID__c) rather than standard Account ID.
5
Run operation and analyze output log files
Service Contract records are created in Salesforce linked to appropriate parent Accounts
Post-execution audit ensures all rows succeeded and errors are isolated for remediation.

Key Concept

Relating Child Records via External ID in Data Loader Mass Operations
Question 13Question

A system administrator at a logistics enterprise is tasked with executing two data maintenance operations: importing 80,000 custom object records named Equipment_Track__c, and deleting 5,000 obsolete Opportunity records from the org. Which two operational constraints dictate that Data Loader MUST be used instead of the Data Import Wizard? (Choose 2 options)

Select all that apply

Show answer & explanation

Answer: The Data Import Wizard cannot process data load operations exceeding 50,000 total records in a single job.; The Data Import Wizard does not support delete operations or object management for Opportunities.

Answer

Data Loader must be used because the Data Import Wizard cannot process more than 50,000 records and cannot perform delete operations or process Opportunity records.
Data Loader is mandatory for this scenario because the Data Import Wizard is strictly limited to 50,000 records per job (making it unsuitable for 80,000 records) and lacks support for delete operations as well as unsupported standard objects like Opportunities.

Step-by-Step Solution

1
Evaluate record volume requirements against tool limits
The import batch consists of 80,000 records, which exceeds the maximum limit of 50,000 records supported by the Data Import Wizard, requiring Data Loader.
Data Import Wizard handles up to 50,000 records, while Data Loader supports up to 5,000,000 records.
2
Evaluate object and operation support requirements
The job requires deleting 5,000 Opportunity records. The Data Import Wizard does not support delete operations and does not support Opportunities.
Data Import Wizard supports insert, update, and upsert for specific standard objects (Accounts, Contacts, Leads, Solutions, Campaign Members) and custom objects, but does not perform record deletions or support Opportunities.

Key Concept

Data Import Wizard vs Data Loader Selection Criteria
Question 14Question

A Salesforce administrator is setting up an automated weekly data backup for an enterprise organization using the native Data Export Service. Which two statements represent key capabilities or limitations of the Data Export Service that the administrator must consider? (Select 2 options)

Select all that apply

Show answer & explanation

Answer: Exported zip files are retained for download for a limited window of 48 hours before being deleted from Salesforce servers.; Calculated fields, such as formula fields and roll-up summary fields, are excluded from the generated export files.

Answer

The two correct considerations are that exported zip files are deleted 48 hours after completion and dynamically calculated fields (such as formulas and roll-up summaries) are excluded from the exported CSV files.
The Data Export Service enforces a strict 48-hour availability window for generated zip files and excludes non-stored, dynamically calculated fields like formula fields and roll-up summaries from the CSV extract.

Step-by-Step Solution

1
Analyze the retention policy for the native Data Export Service.
Salesforce retains weekly or monthly export files for exactly 48 hours following generation, after which the files are permanently purged.
Administrators must plan downloads within this 48-hour window to maintain offline archives.
2
Evaluate field types included in the data backup.
Data Export extracts baseline database field values and excludes derived values like formula fields and roll-up summaries.
Calculated field values are derived dynamically at runtime and can be reconstructed from the underlying field data.

Key Concept

Salesforce Data Export Service Retention Window and Field Exclusions
Question 15Question

An organization requires a bulk cleanup of 500,000 obsolete custom log records while maintaining strict data governance compliance. What is the correct sequence of administrative steps to safely back up the data and permanently purge the records using Salesforce native tools and Data Loader?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order of operations is: 1) Generate and download a full offline backup using Data Export Service, 2) Assign the 'Bulk API Hard Delete' permission, 3) Export a CSV file containing the target Record IDs, 4) Execute a Hard Delete operation in Data Loader with Bulk API enabled, and 5) Monitor the Bulk API Job status page and review log files.
Enterprise data governance dictates that full offline backups must be generated before executing mass deletion jobs. Next, administrative permissions for 'Bulk API Hard Delete' must be granted. The administrator then extracts the exact Record IDs into a CSV file. Using Data Loader with the Bulk API, the Hard Delete operation is executed to bypass the Recycle Bin. Finally, auditing the Bulk API Monitoring page and success/error logs ensures complete processing verification.

Step-by-Step Solution

1
Perform data backup.
A complete data backup zip archive is created and stored offline.
Data governance policies require securing a complete backup before performing destructive mass operations.
2
Configure administrative security permissions.
The user is granted the 'Bulk API Hard Delete' system permission.
Hard delete capability is restricted by default and must be explicitly enabled on the user's profile or permission set.
3
Extract target record identifiers.
A CSV file containing the exact Record IDs of the records to purge is generated.
Data Loader mass deletion operations require a CSV file specifying the 15-character or 18-character Record IDs.
4
Run Hard Delete in Data Loader.
Target records are deleted immediately without being sent to the Recycle Bin.
Using Bulk API with Hard Delete enabled purges high-volume data asynchronously without filling the Recycle Bin storage.
5
Audit job execution.
Completion status and error logs are verified in Salesforce Setup.
Reviewing Bulk API job monitoring logs validates that all 500,000 records processed successfully without batch failures.

Key Concept

Mass Data Operations and Hard Deletion Sequence
Estimated Time:3m 0s
Question 16Question

An enterprise administrator is performing data maintenance and planning mass deletion operations across multiple standard objects in a Salesforce org. Management requires clarification on data recovery safety nets and storage behaviors associated with deleted records. Which statement accurately describes the retention policy and capacity behavior of the Salesforce Recycle Bin?

Show answer & explanation

Answer: Deleted records are stored in the Recycle Bin for up to 15 days, but may be automatically purged earlier if the organization's Recycle Bin storage capacity is reached.

Answer

Deleted records are stored in the Recycle Bin for up to 15 days, but may be automatically purged earlier if the organization's Recycle Bin storage capacity is reached.
The correct option accurately identifies both key constraints of the Salesforce Recycle Bin: the maximum 15-day retention period and the automatic purging mechanism triggered when organization Recycle Bin storage limits are exceeded.

Step-by-Step Solution

1
Evaluate the standard retention limit for soft-deleted records in Salesforce.
Salesforce soft-deletes records to the Recycle Bin where they are kept for up to 15 days.
15 days is the maximum time window provided by Salesforce for record restoration before permanent deletion.
2
Analyze the org-wide Recycle Bin capacity thresholds.
If total deleted data volume exceeds the calculated org limit (based on overall storage allocated), Salesforce automatically purges the oldest records.
Storage limit enforcement overrides the 15-day time window to prevent org storage overages.

Key Concept

Salesforce Recycle Bin Retention and Capacity Limits
Question 17Question

A Salesforce Administrator is configuring a customer support dashboard containing multiple components built from case reports. The administrator wants to add dashboard filters so managers can dynamically slice the displayed data by Case Origin and Case Priority.

Which two limits or requirements apply when configuring dashboard filters? (Select 2)

Select all that apply

Show answer & explanation

Answer: A dashboard can have a maximum of 3 dashboard filters.; Each dashboard filter allows a maximum of 50 filter options (values).

Answer

The two correct constraints are that a dashboard can have a maximum of 3 filters, and each filter supports up to 50 filter options (values).
In Salesforce Lightning Experience, a single dashboard can contain a maximum of 3 dashboard filters, and each filter supports up to 50 filter options (values). These limits ensure dashboard performance remains optimized across source reports.

Step-by-Step Solution

1
Evaluate standard Salesforce Lightning dashboard governor limits regarding dynamic filters.
Identify that Salesforce restricts each dashboard to a maximum of 3 dashboard filters.
This platform constraint applies universally across all standard dashboard components.
2
Examine the capacity limits within an individual dashboard filter configuration.
Confirm that each filter can contain up to 50 options/values.
Administrators can specify up to 50 distinct filter criteria choices per filter.
3
Assess security and profile-based exceptions.
Determine that filter limits cannot be expanded by altering running user settings and filters do not bypass security.
Field-level security and sharing settings remain strictly enforced regardless of filter interactions.

Key Concept

Salesforce Dashboard Filter Limits and Security
Question 18Question

A Salesforce administrator at a healthcare company needs to insert 75,000 Opportunity records into Salesforce while linking them to existing Account records using a custom External ID field. Which data utility should the administrator use to complete this requirement?

Show answer & explanation

Answer: Data Loader, because it supports Opportunity records and handles record volumes exceeding 50,000.

Answer

Data Loader, because it supports Opportunity records and handles record volumes exceeding 50,000.
The correct answer identifies Data Loader as the appropriate tool because the Data Import Wizard cannot be used for Opportunity records and is capped at 50,000 records per operation. Data Loader supports up to 5,000,000 records for all standard and custom objects.

Step-by-Step Solution

1
Evaluate record volume requirement
The requirement specifies 75,000 records, which exceeds the Data Import Wizard limit of 50,000 records.
Data Import Wizard is restricted to a maximum of 50,000 records per import job.
2
Evaluate object support requirement
The target object is Opportunity, which is not supported by the Data Import Wizard.
Data Import Wizard only supports Accounts, Contacts, Leads, Solutions, Campaign Members, and Custom Objects.
3
Select appropriate utility tool
Data Loader must be used because it supports Opportunities and up to 5,000,000 records.
Data Loader satisfies both the object support requirement and the high volume threshold.

Key Concept

Data Import Wizard vs Data Loader selection criteria based on record volume and object support
Question 19Question

A Salesforce administrator needs to insert 80,000 new Contact records into Salesforce from a CSV file. Which tool should the administrator use to complete this task?

Show answer & explanation

Answer: Data Loader, because the record volume exceeds the 50,000 record limit of the Data Import Wizard.

Answer

Data Loader should be used because the total volume of 80,000 records exceeds the 50,000 record limit of the Data Import Wizard.
Data Loader can process up to 5,000,000 records at a time, making it the correct choice for an 80,000 record import. The Data Import Wizard is limited to a maximum of 50,000 records per job.

Step-by-Step Solution

1
Identify the data volume required for the operation.
The requirement calls for importing 80,000 Contact records.
Data volume is a primary decision vector when choosing between Salesforce data utilities.
2
Compare the record capacity limits of Data Import Wizard and Data Loader.
Data Import Wizard supports up to 50,000 records, whereas Data Loader supports up to 5,000,000 records.
Since 80,000 exceeds 50,000, the Data Import Wizard cannot be used.

Key Concept

Selecting data migration utilities based on record volume limits
Question 20Question

A Salesforce administrator is reviewing data management requests across different departments. Match each operational requirement on the left with the appropriate native Salesforce data tool or configuration on the right.

Click a left item, then click its matching right item

Items

Upsert 4,000 Contact records while applying active matching rules to prevent duplicates and executing workflow rules directly within a browser interface.
Insert 75,000 Opportunity records from an external system mapped using a custom External ID field.
Permanently delete 120,000 archived Case records from the Salesforce database, completely bypassing the Recycle Bin.
Execute an unattended, scheduled nightly export of Account data saved directly to a local directory server file.

Matches

Show answer & explanation

Answer

1. Upserting 4,000 Contacts with browser-based duplicate detection and workflow rules matches Data Import Wizard.
2. Inserting 75,000 Opportunities using an External ID matches Data Loader Desktop User Interface.
3. Permanently deleting 120,000 Cases bypassing the Recycle Bin matches Data Loader using Bulk API with Hard Delete enabled.
4. Scheduled unattended nightly exports match Data Loader Command Line Interface (CLI).
Each requirement directly aligns with key operational distinctions between native Salesforce utilities: Data Import Wizard is ideal for browser-driven tasks under 50,000 records with duplicate checking; Data Loader UI supports larger volumes (>50,000) and objects like Opportunities; Data Loader with Bulk API is required for hard deletes; and Data Loader CLI is required for scheduled automated script execution.

Step-by-Step Solution

1
Analyze requirement 1 (4,000 Contacts, duplicate checking, browser-based, workflow execution).
Identify Data Import Wizard as the tool matching <50,000 volume limit, browser access, native Contact duplicate prevention, and workflow triggering.
Data Import Wizard is designed for browser-based operations under 50,000 records for specific standard objects (Accounts, Contacts, Leads, Solutions) and custom objects.
2
Analyze requirement 2 (75,000 Opportunities, External ID mapping).
Identify Data Loader Desktop UI because Opportunity is an unsupported standard object in Data Import Wizard, and the record volume exceeds 50,000.
Data Import Wizard cannot load Opportunities and has a hard limit of 50,000 records.
3
Analyze requirement 3 (120,000 soft-deleted Cases, purge from Recycle Bin).
Identify Data Loader using Bulk API with Hard Delete enabled.
Data Import Wizard cannot perform hard deletes. Hard delete requires Bulk API enabled in Data Loader settings along with administrative permissions.
4
Analyze requirement 4 (Unattended, automated nightly scheduled export).
Identify Data Loader CLI.
Data Import Wizard does not support command-line automation or scheduled background execution.

Key Concept

Selecting between Data Import Wizard and Data Loader based on record limits, supported objects, automation capabilities, operation types, and execution modes.
Estimated Time:3m 0s
Page 1 / 13Next