ADM-201 domain - 17% of the exam

Data and Analytics Management

Data and Analytics Management is 17% of the ADM-201 exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

51
Practice questions
3
Objectives
51
Medium

Where people go wrong

  • Expecting a with-type report or field filter to find records with no children

    The wrong answers filter on an Opportunity field, use a report type such as Accounts with Opportunities, or add a WITH cross filter. Each of these only evaluates Accounts that already have related Opportunities, so Accounts with none are excluded before the filter applies. A cross filter set to Accounts WITHOUT Opportunities, or the Accounts without Opportunities report type, tests for the absence of related records and returns the dormant Accounts.

    See it in a sample question
  • Confusing matrix, summary and joined report formats

    The wrong answers offer a summary report, nested groupings or a joined report when the question asks for a grid with one grouping down the side and another across the top. Summary reports group only down the rows, and a joined report places separate blocks side by side. A matrix report groups by both row and column fields and shows a summarised value at each intersection. Tabular reports only list records.

    See it in a sample question
  • Swapping bucket fields and summary formulas

    Bucketing is offered for a percentage of a grand total, and a summary formula is offered for sorting Amount into Small, Medium and Large. A bucket field categorises the values of a column into named groups inside one report and performs no arithmetic. A summary formula calculates at group and grand-total level, using a function such as PARENTGROUPVAL, and returns numbers rather than text labels.

    See it in a sample question
  • Assuming a standard dashboard shows each viewer their own data

    The wrong answers expect a standard dashboard to scope figures per viewer, or choose run as the logged-in user when every viewer needs the same complete figures. A standard dashboard renders through one running user, so every viewer sees that user's data. Only a dynamic dashboard, set to run as the logged-in user, shows each viewer their own data. A specified user with full access gives uniform totals.

    See it in a sample question
  • Controlling dashboard access with something other than the folder

    The wrong answers adjust the running user, grant Run Reports, grant View All Data or share a personal dashboard directly. None of these controls who can open a dashboard. The running user decides whose data appears, View All Data over-grants record access, and personal folders cannot be shared. Access comes from the folder: move the dashboard into a shared folder and grant the audience Viewer access to that folder.

    See it in a sample question

Objectives in this domain

Sample questions from this domain

Free sampleData and Analytics Managementmedium

An administrator needs a report that lists only Accounts which have no related Opportunity records. Which report feature returns this set most directly?

  • AA standard field filter on the Opportunity Amount field set to equals zero.
  • BA cross filter set to Accounts without Opportunities. Correct
  • CA bucket field that groups accounts by their number of opportunities.
  • DFilter logic combining two Account field filters with OR.
Use a cross filter to include or exclude parent records based on the presence or absence of related child records. Cross filters evaluate related records with a with or without condition, so 'Accounts without Opportunities' directly returns parent accounts that have no matching child opportunity, which ordinary field filters cannot do.

Why A is wrong: This is tempting, but a field filter on a related Opportunity field only evaluates accounts that already have opportunities, so accounts with none are excluded rather than returned.

Why B is correct: Correct: a cross filter tests the presence or absence of related records, so Accounts without Opportunities returns exactly the accounts that have no related opportunity.

Why C is wrong: A bucket field categorises values of a field already in the report and cannot evaluate whether related opportunity records exist, so it cannot isolate accounts with none.

Why D is wrong: Filter logic only rearranges how field filters on the report's own fields combine; it cannot test for the absence of related opportunity records.

Free sampleData and Analytics Managementmedium

Which report format groups records by chosen fields down the rows and across the columns at the same time, so that values are summarised at the intersection of each row grouping and each column grouping?

  • AA tabular report, which lists each record on its own line with no grouping applied.
  • BA summary report, which groups records only into row groupings with subtotals.
  • CA matrix report, which groups records by both row and column fields and summarises at their intersection. Correct
  • DA joined report, which places several report blocks side by side for one object.
Recognise that the matrix format groups data by both rows and columns to summarise values at their intersection. The matrix format is defined by having both row groupings and column groupings, producing summarised values at each intersection; other formats group in one direction or not at all.

Why A is wrong: Tabular is tempting because it is the default and shows columns of data, but it simply lists records and cannot group by rows or columns at all.

Why B is wrong: Summary reports do group and subtotal, which sounds close, but they group only down the rows and cannot also group across columns.

Why C is correct: Correct: a matrix report groups by at least one row field and one column field and shows summarised values where each row grouping meets each column grouping.

Why D is wrong: Joined reports do arrange multiple blocks side by side, which can look grid-like, but they combine separate blocks rather than crossing row and column groupings of one dataset.

Free sampleData and Analytics Managementmedium

A report is grouped by Account Owner, and the administrator wants a column that shows each owner's total amount as a percentage of the grand total. Which report calculation is designed for this?

  • AA row-level formula, which calculates a separate value for each individual record row.
  • BA bucket field applied to the Amount column to split it into ranges.
  • CA summary formula using a function such as PARENTGROUPVAL to compare a group's summary value against a higher-level total. Correct
  • DA cross filter on the Account Owner field to limit the rows returned.
Choose a summary formula with a grouping function when a calculation must reference group subtotals or the grand total. Summary formulas evaluate at grouping and grand-total level, and functions such as PARENTGROUPVAL reference a parent grouping's value, which is exactly what a percentage-of-total column requires, unlike a per-row calculation.

Why A is wrong: A row-level formula is tempting because it adds a calculated column, but it computes per record and cannot reference a group subtotal or the grand total.

Why B is wrong: Bucketing only sorts amounts into named ranges and performs no arithmetic, so it cannot express one group's share of the grand total.

Why C is correct: Correct: a summary formula operates on grouped subtotals and grand totals, and PARENTGROUPVAL lets it express each owner's amount as a proportion of the grand total.

Why D is wrong: A cross filter only includes or excludes records by related-record presence; it filters rows and computes no percentage against a total.

Free sampleData and Analytics Managementmedium

At Kalamunda Insurance, a support dashboard must show the same organisation-wide case metrics to every viewer, including team leads who do not have access to most case records. The administrator wants all viewers to see the complete figures. How should the running user be configured on this standard dashboard?

  • ASet the running user to the logged-in user so that each viewer sees the figures scoped to what they can access
  • BAdd each team lead into the case owners' role so they inherit access to the underlying records
  • CSet the running user to a specified user who has access to all case records, so every viewer sees the same full figures Correct
  • DGrant every viewer the View All Data permission through their profile so the case figures are complete
A standard dashboard shows all viewers the data visible to its single specified running user. Because a standard dashboard evaluates its source reports through one running user, setting that user to someone with access to all case records lets every viewer see identical, complete figures without altering their own record access.

Why A is wrong: Running as the logged-in user would show each team lead only the cases they can access, producing partial or empty figures rather than the complete organisation-wide metrics required.

Why B is wrong: Restructuring the role hierarchy is a heavy change that widens each lead's record access broadly, which is unnecessary when the running user alone can present the full figures.

Why C is correct: A standard dashboard renders through its single running user, so choosing one specified user with full case access lets every viewer see the complete metrics regardless of their own record access.

Why D is wrong: View All Data is tempting because it would surface all cases, but it exposes every object across the org to those users, a far broader and riskier change than the dashboard needs.

Free sampleData and Analytics Managementmedium

Which statement correctly describes how access to a dashboard is controlled in Salesforce?

  • AAccess is granted per dashboard through individual record-level sharing on each dashboard.
  • BAny user with the Run Reports permission can open every dashboard in the org.
  • CAccess is controlled by sharing the folder in which the dashboard is stored. Correct
  • DAccess follows the organisation-wide default set for the Dashboard object.
Dashboard visibility is governed by sharing the folder that contains the dashboard, not by record-level sharing. Salesforce stores dashboards in folders and controls who can access them through folder sharing levels, so managing the folder is how an administrator grants or restricts dashboard access.

Why A is wrong: Dashboards are not shared as individual records the way an Account is. Access is managed at the folder level, so per-dashboard record sharing is inaccurate.

Why B is wrong: Run Reports is necessary but does not by itself expose every dashboard. Folder access still gates visibility, so a system permission alone is not enough.

Why C is correct: Dashboards live in folders, and folder sharing settings determine who can view or manage them, which is the correct access mechanism.

Why D is wrong: There is no org-wide default that governs dashboard visibility. Folder sharing, not an OWD, controls access, so this misapplies the record-access model.

Other domains in this exam

See also the ADM-201 cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by Salesforce. Original, blueprint-aligned practice material only.