ADX-211 Administer, Extend, and Automate Salesforce Exam Topics and Questions
These Salesforce Administer, Extend, and Automate Salesforce (ADX-211) exam topics are organized according to official exam domains to help candidates quickly verify coverage and focus on assessment rather than theory. Each domain is paired with topic-wise ADX-211 sample questions that reflect how objectives are tested in the actual exam. This structure enables efficient review, targeted self-assessment, and rapid identification of weak areas when preparing for the Salesforce Administer, Extend, and Automate Salesforce certification exam.
Let's Practice Free Salesforce ADX-211 Questions Aligned with Official Exam Topics
Data Security is where the exam starts, and for good reason: get the access model wrong and everything built on top of it fails. This topic tests your ability to layer Salesforce's security model correctly, from org-level login controls down through object permissions, record sharing, and delegated admin rights. The traps are subtle because the layers interact, and a gap at one level can silently override a restriction set at another. β Getting into the org and controlling objects Org...
Data Security is where the exam starts, and for good reason: get the access model wrong and everything built on top of it fails. This topic tests your ability to layer Salesforce's security model correctly, from org-level login controls down through object permissions, record sharing, and delegated admin rights. The traps are subtle because the layers interact, and a gap at one level can silently override a restriction set at another.
β Getting into the org and controlling objects
Org access covers the controls that determine whether a user can log in at all: authentication settings, login hours, IP restrictions, and session policies. These sit above everything else in the stack, so a misconfiguration here renders all downstream permissions irrelevant. Object permissions sit one level down and define what a user can do once inside: read, create, edit, delete, view all, modify all. The exam expects you to know which permission vehicle (profile versus permission set versus permission set group) is the right tool for a given requirement, and why granting Modify All on an object is a fundamentally different commitment than granting Edit. The distinction between what a profile allows by default and what a permission set adds on top is a consistent source of exam pressure.
β Sharing and delegation
Sharing determines which records a user can see, and the exam tests your ability to predict the outcome when multiple sharing mechanisms are in play simultaneously. Org-wide defaults set the floor, role hierarchy opens records upward, sharing rules extend access sideways, and manual sharing adds one-off exceptions. Knowing that sharing can only open access wider than the OWD, never restrict it further, is the kind of rule that changes which option you pick. Delegated administration lets a non-admin user manage a defined subset of users, profiles, and permission sets. The exam focuses on the boundaries of delegation: what a delegated admin can do and, critically, what they cannot do regardless of how the delegation is configured. Both sharing and delegation questions reward precision over general familiarity.
How Data Security is tested
Items in this topic present a business scenario describing a user's access problem and ask you to identify the cause or the fix. The demand is layered: you must hold the entire access stack in your head simultaneously and reason about which layer is responsible for the behaviour described. A user who can see a record type but cannot edit a specific field is a different problem from a user who cannot see the record at all, and the exam expects you to tell them apart cleanly.
The most common trap is confusing record visibility with field-level security, or assuming that a higher role automatically grants object permissions it does not actually include. Delegation questions often describe a scenario where a delegated admin is blocked from doing something that sounds like it should be within scope, and items reward knowing the hard limits on delegation rather than reasoning from intuition. Sharing rule questions reward knowing whether a rule opens access to a role, a role and subordinates, or a public group, because those distinctions drive different outcomes.
The ITExamsTopics practice test covers all four sub-areas of Data Security with enough volume that you can spot exactly which layer of the access model you keep misreading. Working through a set of timed items on sharing and delegation is a faster diagnostic than re-reading the documentation.
The question below puts a specific access scenario in front of you and asks you to pinpoint where in the security stack the issue originates.
Cloud Kicks wants to force its users to set a value for a custom called Tier by answering a series of questions.
What two functions should the administrator use to ensure that users cannot bypass answering these questions in order to determine their Tier value.
Choose 2 answers
Once the access model is settled, the next pressure point is the data model itself. This topic tests your ability to make structural decisions that are hard or impossible to reverse: relationship type, field type, and object configuration choices that lock in behaviour across the whole org. The exam rewards candidates who understand the downstream consequences of a choice, not just the mechanics of making it. β Custom objects and field configuration Creating a custom object involves more than naming...
Once the access model is settled, the next pressure point is the data model itself. This topic tests your ability to make structural decisions that are hard or impossible to reverse: relationship type, field type, and object configuration choices that lock in behaviour across the whole org. The exam rewards candidates who understand the downstream consequences of a choice, not just the mechanics of making it.
β Custom objects and field configuration
Creating a custom object involves more than naming it. The exam probes decisions like whether to allow activities, whether to enable search, and which sharing model to assign at creation time. These settings affect what users can do with the object later, and some cannot be changed after data exists. Field customisation questions focus on field type selection: the difference between a currency field and a number field, or between a text area and a rich text area, matters when data must be used in formulas or rolled up. You also need to know which field types support certain features, such as which can be used as external IDs, which can be made required at the field level versus only in a page layout, and what happens when you change a field type after records already exist.
β Relationship types and their consequences
The relationship questions are where most candidates lose marks in this topic. Master-detail and lookup relationships look similar on the surface but behave very differently. Master-detail drives roll-up summary fields, cascade deletes, and sharing inheritance, while lookup is more permissive and independent. The exam tests whether you know when each is appropriate and what you give up by choosing one over the other.
Beyond those two, you need to understand many-to-many relationships via junction objects, self-relationships, and hierarchical relationships. Each has a specific use case and a specific set of constraints. Items reward knowing what a relationship type enables, not just what it is called. A question about whether a roll-up summary field is possible is really a question about whether the relationship is master-detail, and the exam writes it that way deliberately.
How Objects, Fields, and Relationships is tested
This topic generates scenario-based items where the scenario describes a business need and you must select the right structural choice to meet it. The trap is that multiple options often look plausible at a surface level. A lookup relationship will technically work in many situations where a master-detail relationship is the right answer, and the exam exploits that.
Items on relationship benefits reward knowing the specific capabilities each relationship type unlocks, such as roll-up summaries or cascade delete, rather than general descriptions of how relationships work. Field-type questions often describe data behaviour that rules out certain types, and items reward eliminating the wrong types systematically rather than picking the first one that sounds right. Custom object creation questions tend to focus on the settings that govern sharing and activity tracking, because those are the ones that bite administrators after the fact. Candidates who treat object and field creation as purely mechanical steps consistently underperform on this topic.
Seeing how relationship and field-type questions are phrased across a full bank of items helps you recognise the pattern before the real exam. The ITExamsTopics PDF and practice test both cover this topic so you can work through it in whatever format fits your schedule.
The question below tests a specific relationship decision where the business requirement makes one structure clearly more appropriate than the alternatives.
Ursa Major Solar (UMS) wants to improve Its customers' ability to search for knowledge articles. UMS has already created categories for articles.
Which two additional chances should be made to improve search capabilities?
Choose 2 answers
With the data model in place, the next layer is the user-facing experience. This topic covers the configuration tools that shape what users see and what they can do from a record page: app setup, tab selection, page layouts, quick actions, and record types tied to business processes. The exam tests your ability to match each tool to the right problem, because administrators who reach for a page layout when a quick action is needed, or a record type when...
With the data model in place, the next layer is the user-facing experience. This topic covers the configuration tools that shape what users see and what they can do from a record page: app setup, tab selection, page layouts, quick actions, and record types tied to business processes. The exam tests your ability to match each tool to the right problem, because administrators who reach for a page layout when a quick action is needed, or a record type when a page layout would do, fail items that a well-mapped candidate answers quickly.
β Apps, tabs, and what users navigate
A Lightning app is the container that determines which tabs a user sees and in what order, which utility bar items appear, and which navigation style applies. The exam tests the relationship between apps and profiles: an app can be assigned to specific profiles, and users see only the apps assigned to them. Tab selection within an app is a separate decision from whether the object itself is visible to the user, and conflating the two is a reliable way to miss items on this sub-topic. You need to know the difference between a tab being hidden in an app and the underlying object being inaccessible, because those produce different user experiences and different fixes.
β Layouts, actions, and business processes
Page layout editor controls field placement, required fields at the layout level, related lists, and which buttons appear on a record. The exam distinguishes between making a field required in the layout versus required at the field level, because the two have different effects and different overrides. Quick actions extend what users can do from a record or the global action menu without navigating away, and the exam tests which action types exist, where they appear, and how they are added to a page.
Record types and business processes work together to give different user groups different picklist values and different sales or support process stages. The exam tests the configuration sequence: you define the process, create the record type, associate the two, and assign the record type to profiles. Getting that sequence wrong in a scenario question means picking a step that is either out of order or unnecessary, and items reward knowing the exact dependency chain.
How Efficiency with Lightning Apps is tested
Items here almost always describe a user complaint or an administrator requirement and ask which configuration change resolves it. The demand is that you map the symptom to the correct tool, because several tools can superficially address the same complaint.
Quick action questions reward knowing the difference between object-specific actions and global actions, and which one belongs on a Lightning record page versus the global action menu. Page layout questions often describe a field that users can see but should not be able to edit, or vice versa, and items reward knowing whether that is a layout problem, a field-level security problem, or a profile problem. Record type questions reward understanding that record types control picklist values and page layout assignment, while business processes control stage or status values, and the two are linked but distinct. Candidates who treat all of these tools as interchangeable lose marks consistently across this topic.
The ITExamsTopics practice test lets you check your coverage across every sub-area of this topic under timed conditions, which is where configuration sequence questions become harder than they look when you are reading at your own pace.
The question below presents a user experience problem and asks you to select the configuration tool that addresses it at the right level.
Good configuration means nothing if the data it manages is unreliable. Data Quality shifts the exam's focus from structure to governance: how you prevent bad data from entering, detect it when it does, and eliminate the duplicates that accumulate over time. This topic rewards candidates who understand that data quality is enforced at multiple points in Salesforce, and that choosing the wrong enforcement point lets problems through that the right one would have caught. β The lifecycle and enforcement mechanisms...
Good configuration means nothing if the data it manages is unreliable. Data Quality shifts the exam's focus from structure to governance: how you prevent bad data from entering, detect it when it does, and eliminate the duplicates that accumulate over time. This topic rewards candidates who understand that data quality is enforced at multiple points in Salesforce, and that choosing the wrong enforcement point lets problems through that the right one would have caught.
β The lifecycle and enforcement mechanisms
The data quality lifecycle describes how data enters, ages, and degrades in an org, and the exam tests whether you understand which stage a given problem belongs to. Enforcement mechanisms include required fields, field-level defaults, picklist restrictions, and validation rules. Each operates at a different point and with different scope. A required field on a page layout can be bypassed by an API insert or a flow; a required field at the object level cannot. The exam exploits that distinction regularly. Picklist restrictions prevent free-text entry but do not validate against existing records. Knowing what each mechanism actually prevents, rather than what it is intended to prevent, is the examinable skill.
β Validation rules, formula functions, and deduplication
Validation rules fire when a record is saved and block the save if the formula evaluates to true. The exam tests your ability to read a validation rule formula and predict whether it fires in a given scenario, which means you need to know the key formula functions: ISBLANK, ISNEW, ISCHANGED, PRIORVALUE, and how logical operators combine them. A rule using ISNEW fires only on record creation; adding ISCHANGED changes the behaviour entirely. Candidates who memorise function names without understanding their evaluation logic consistently misread scenario questions.
Duplicate management in Salesforce uses matching rules and duplicate rules in combination. The matching rule defines what counts as a match; the duplicate rule defines what happens when one is found: allow with a warning, block, or report. The exam tests the relationship between the two and rewards knowing that a duplicate rule does nothing without an active matching rule underneath it.
How Data Quality is tested
Items in this topic frequently present a validation rule formula and describe a save scenario, then ask whether the rule fires. The demand is formula literacy, not just conceptual familiarity. You need to trace the logic, account for field state (new record versus existing, changed versus unchanged), and reach the right conclusion without second-guessing yourself.
The duplicate management questions reward knowing the configuration dependency between matching rules and duplicate rules, and understanding what each action setting (allow, block, report) actually does to the user experience. A common trap is assuming that a duplicate rule set to alert will prevent the save; it does not, and items are written to catch that assumption.
Data quality lifecycle questions reward knowing at which point in the data entry or import process a given control applies. Candidates who think of validation rules as the only enforcement tool miss scenarios where a required field or a picklist restriction is the more appropriate answer. Breadth across all four sub-areas matters here.
A broad bank of Data Quality items from ITExamsTopics is particularly useful here because validation rule formula questions vary widely in how they combine functions, and reading enough of them builds the pattern recognition that re-reading documentation alone does not.
The question below gives you a specific data scenario and asks you to determine which quality control applies and what outcome it produces.
Automation is where the exam's complexity increases sharply. Salesforce Flow covers the strategic layer of automation: which tool to use, how Flow fits into the broader Salesforce automation landscape, how to migrate legacy automation to Flow, and how the order of execution governs what happens when multiple automations run on the same record. Candidates who understand Flow conceptually but cannot reason about execution order or migration trade-offs lose marks on items that reward exactly that reasoning. β Tool selection and...
Automation is where the exam's complexity increases sharply. Salesforce Flow covers the strategic layer of automation: which tool to use, how Flow fits into the broader Salesforce automation landscape, how to migrate legacy automation to Flow, and how the order of execution governs what happens when multiple automations run on the same record. Candidates who understand Flow conceptually but cannot reason about execution order or migration trade-offs lose marks on items that reward exactly that reasoning.
β Tool selection and Flow fundamentals
Salesforce has retired or deprecated several automation tools in favour of Flow, and the exam tests whether you know which tool is appropriate for a given requirement today. Workflow rules and process builder are legacy; Flow is the current answer for most declarative automation needs. The exam does not ask you to build workflow rules but it does ask you to recognise what they did and why Flow replaces them. Flow itself comes in several types: screen flows, record-triggered flows, scheduled flows, autolaunched flows, and platform event-triggered flows. Knowing which type fits which requirement is a baseline skill. The exam tests the distinctions between types, not just the existence of each.
β Migration and order of execution
Migration to Flow questions describe a process builder or workflow rule scenario and ask how you would replicate it in Flow, or ask about the implications of running both simultaneously during a migration period. The exam rewards knowing that running a legacy automation and a Flow on the same object at the same time can cause duplicate actions or recursive loops, and that migration planning must account for that.
Order of execution is one of the most consistently tested concepts in this topic. When a record is saved, Salesforce runs validation rules, assignment rules, auto-response rules, workflow rules, and Flow triggers in a defined sequence. Items reward knowing where in that sequence a record-triggered Flow fires relative to other automations, and what happens when a Flow update causes another save event. Candidates who treat order of execution as background knowledge rather than exam-critical detail pay for it.
How Salesforce Flow is tested
Tool selection items reward precise matching of a business requirement to a flow type, and the trap is almost always that two flow types could technically work but one is the better fit for the described trigger or user interaction. The exam writes these scenarios carefully to make the wrong option look reasonable.
Order of execution items are the most demanding in this topic. They describe a multi-automation environment and ask what happens when a specific event fires. Items reward holding the full execution sequence in order and applying it to the scenario, rather than reasoning from general principles. Migration items reward knowing the specific risks of running legacy and Flow automation in parallel, not just knowing that migration is possible. Candidates who can identify the right tool but cannot reason about execution consequences typically score below their expectation on this topic.
Working through ITExamsTopics items on Flow tool selection and order of execution under timed conditions reveals whether you can apply the execution sequence under pressure, which is different from knowing it in the abstract.
The question below describes an automation requirement and asks you to select the Flow type and configuration that meets it correctly.
Where the previous topic covered Flow strategy, this one tests hands-on construction. The exam expects you to know how a Flow is actually assembled: the elements you use, the resources you create, how collections are managed, and the decisions that determine whether a Flow runs correctly or fails silently. Candidates who have only watched Flow demos and never built one from requirements tend to struggle here, because the questions are grounded in builder-level decisions. β Foundations: elements and the builder...
Where the previous topic covered Flow strategy, this one tests hands-on construction. The exam expects you to know how a Flow is actually assembled: the elements you use, the resources you create, how collections are managed, and the decisions that determine whether a Flow runs correctly or fails silently. Candidates who have only watched Flow demos and never built one from requirements tend to struggle here, because the questions are grounded in builder-level decisions.
β Foundations: elements and the builder
A Flow is built from elements connected by connectors, and the exam tests your knowledge of the core element types: screens, decisions, assignments, loops, record creates, record updates, record lookups, and record deletes. Each has a specific role and specific configuration requirements. Decision elements branch the flow based on conditions; assignment elements set variable values; loop elements iterate over collections. Knowing which element to use for a given step in a business process is the foundation of every construction question. The exam also tests how elements are connected and what happens when a path has no connector: an unhandled path causes a fault, and fault handling is an examinable configuration decision.
β Resources, collections, and putting it together
Resources are the data containers inside a Flow: variables, constants, formulas, text templates, record variables, and collection variables. The exam tests which resource type is appropriate for a given purpose. A collection variable holds multiple records; a record variable holds one. Using the wrong type means the loop element that processes it will not behave as expected, and the exam writes scenarios that depend on that distinction.
Collection management involves getting records into a collection via a Get Records element, iterating with a loop, and deciding what to do with each record inside the loop. The exam tests the pattern of: get, loop, assign, create or update outside the loop. Performing record operations inside a loop instead of after it is a performance anti-pattern that the exam tests explicitly. Creating a complete Flow requires understanding how all these pieces connect, in what order, and where fault paths must be added to handle errors gracefully rather than presenting users with an unhelpful error screen.
How Flow: Building from Scratch is tested
Items in this topic often describe a business requirement and ask which combination of elements and resources achieves it. The demand is that you mentally build the flow and verify each step, not just pick the element that sounds closest to the requirement.
Collection and loop questions are particularly precise: items reward knowing whether a record operation should happen inside or outside a loop, and what the consequence of placing it in the wrong location is. Resource type questions reward knowing the difference between a collection variable and a record variable at the point where a loop element references them. Fault path questions reward knowing that an unhandled fault terminates the flow with an error rather than continuing silently. Candidates who know the element names but have not thought through the consequences of misconfiguring them consistently find this topic harder than expected.
The ITExamsTopics practice test gives you exposure to the full range of Flow construction question styles, which is useful here because the item phrasing for element and resource questions varies considerably and familiarity with the style reduces time pressure on exam day.
The question below describes a flow requirement and asks you to identify the element configuration or resource type that makes it work.
Building a Flow correctly is one skill; knowing where it can break, what its limits are, and how to diagnose failures is another. This topic covers the operational side of Flow: the considerations that must inform design decisions before a Flow is deployed, the limitations that cannot be worked around, and the debugging techniques that isolate problems after deployment. With only three sub-topics, the exam goes deep on each rather than wide across many. How Flow: Considerations and Troubleshooting is...
Building a Flow correctly is one skill; knowing where it can break, what its limits are, and how to diagnose failures is another. This topic covers the operational side of Flow: the considerations that must inform design decisions before a Flow is deployed, the limitations that cannot be worked around, and the debugging techniques that isolate problems after deployment. With only three sub-topics, the exam goes deep on each rather than wide across many.
How Flow: Considerations and Troubleshooting is tested
Items in this topic tend to describe a Flow that is not behaving as expected and ask you to identify the cause or the fix. The demand is diagnostic: you must read the scenario, eliminate causes that do not fit, and land on the specific consideration or limitation that explains the behaviour.
Consideration questions reward knowing which Flow types can be called from other automations, which require user context, and which run in system mode versus user mode, because those distinctions change what the Flow can access. Limitation questions reward knowing the specific governor limits that apply to Flow, such as the limit on the number of DML operations in a transaction, rather than a general awareness that limits exist. Troubleshooting questions reward knowing how to use Flow debug mode and how to read a fault email to locate the failing element. Candidates who understand Flow construction but have not thought about what happens when it goes wrong find this topic disproportionately difficult.
Because this topic is narrow but deep, a targeted run through the ITExamsTopics items on Flow considerations and troubleshooting is more efficient than re-reading documentation: you find your specific gap faster.
The question below puts a broken or misbehaving Flow in front of you and asks you to pinpoint the consideration or limit responsible.
Approval processes sit at the intersection of automation and human decision-making, and the exam tests all three phases: defining what an approval process does, configuring it correctly, and diagnosing it when it does not work. With three sub-topics, the coverage is deep rather than broad. Candidates who have configured approval processes in practice but have not examined the edge cases in their configuration tend to underestimate this topic. How The Approval Process is tested Items on approval process definition reward...
Approval processes sit at the intersection of automation and human decision-making, and the exam tests all three phases: defining what an approval process does, configuring it correctly, and diagnosing it when it does not work. With three sub-topics, the coverage is deep rather than broad. Candidates who have configured approval processes in practice but have not examined the edge cases in their configuration tend to underestimate this topic.
How The Approval Process is tested
Items on approval process definition reward knowing the components: entry criteria, approval steps, approver assignment methods, rejection behaviour, and final approval and rejection actions. Each component has configuration options that change the outcome, and the exam tests those options specifically rather than the existence of the components.
Creation questions reward knowing the sequence of configuration decisions and which settings at the step level override settings at the process level. A common trap is assuming that a process-level setting applies uniformly when a step-level setting takes precedence for records that reach that step. Troubleshooting questions describe a record that is not routing to the expected approver, or an approval action that is not firing, and items reward tracing the configuration from entry criteria through step assignment to action. Candidates who can build an approval process but cannot read an existing one and predict its behaviour lose marks on both the creation and troubleshooting sub-topics.
The ITExamsTopics PDF is a practical way to review approval process scenarios before the exam: you can work through the items at your own pace and mark the configuration details that keep tripping you up.
The question below describes an approval process configuration and asks you to determine how a specific record will be routed or what action will fire.
After approvals, the exam turns to what happens around and beyond declarative automation: how execution order governs the full automation stack, how auditing tools let you see what ran and when, and how Salesforce extends into territory that clicks-based configuration cannot reach. This topic rewards candidates who think about automation as a system, not a collection of individual tools. How Automation Audits and Extensions is tested Order of execution items in this topic go further than the Salesforce Flow topic...
After approvals, the exam turns to what happens around and beyond declarative automation: how execution order governs the full automation stack, how auditing tools let you see what ran and when, and how Salesforce extends into territory that clicks-based configuration cannot reach. This topic rewards candidates who think about automation as a system, not a collection of individual tools.
How Automation Audits and Extensions is tested
Order of execution items in this topic go further than the Salesforce Flow topic did: they test the full save sequence including before and after triggers, which means understanding where Apex code fits relative to Flow and workflow. Items reward knowing the exact position of each automation type in the sequence, because a one-step error in that ordering changes which answer is right.
Auditing tool questions reward knowing what each tool records: the setup audit trail captures configuration changes with user and timestamp; debug logs capture runtime events; field history tracking captures field-level changes on records. Knowing which tool surfaces which type of information is the examinable skill, and the exam writes scenarios where the wrong tool would give you partial but misleading information.
Extension questions cover the boundary between declarative and programmatic Salesforce: when a Flow calls Apex, when an external service is invoked via a named credential, and what that boundary means for testing and deployment. Items reward knowing when you have reached the limit of what Flow can do natively.
Checking your weak area on this topic through the ITExamsTopics practice test is more efficient than reviewing everything: run the items, see where you drop marks, and focus your remaining study time there.
The question below tests a specific auditing or execution-order scenario where the distinction between two similar tools or two adjacent steps in the sequence determines the answer.
The final topic moves away from configuration and automation entirely and into analytics. Advanced Reporting tests your ability to build reports that go beyond standard report types: custom report types that surface data across related objects, cross filters that isolate exception records, bucketing that groups field values without a formula field, historical snapshots, and extended summaries in dashboards. The exam rewards precision about what each feature can and cannot do. β Custom report types, cross filters, and bucketing A custom...
The final topic moves away from configuration and automation entirely and into analytics. Advanced Reporting tests your ability to build reports that go beyond standard report types: custom report types that surface data across related objects, cross filters that isolate exception records, bucketing that groups field values without a formula field, historical snapshots, and extended summaries in dashboards. The exam rewards precision about what each feature can and cannot do.
β Custom report types, cross filters, and bucketing
A custom report type defines which objects and fields are available in a report, and the key exam decision is whether to include records that have related records, records that may or may not have related records, or both. That choice determines what shows up in the report, and items are written to test whether you can predict the row set for a given configuration. Cross filters add a condition based on the presence or absence of related records: show accounts that have no open cases, for example. The exam tests the difference between a cross filter and a subfilter, and rewards knowing that cross filters operate on the existence of a relationship rather than on field values of the related object. Bucketing lets you group field values into named ranges inside the report without creating a formula field, and the exam tests which field types support bucketing and what happens to null values.
β Historical reporting and extended summaries
Historical reporting in Salesforce captures field values at points in time through historical trending, which must be enabled per object and tracks a limited set of fields. The exam tests the configuration requirements and the limitations: how many months of history are retained, which field types can be tracked, and what the report shows when a field was not tracked during a particular period. Candidates who assume historical trending works like a full audit trail consistently misread historical reporting items.
Extended summaries in reports and dashboards cover custom summary formulas, which let you calculate values across groupings that standard summary fields cannot produce. The exam tests the scope of a custom summary formula: whether it applies at the grand total level, at a grouping level, or at both. Dashboard components pull from report data and the exam tests which component types support which data configurations. Knowing the boundary between what a report can display and what requires a dashboard component to visualise is a reliable source of exam items.
How Advanced Reporting is tested
Items in this topic describe a reporting requirement and ask which feature or configuration meets it. The trap is that several features sound like they address the same need: a cross filter, a standard filter, and a custom report type can all limit which records appear in a report, but they do so in different ways and with different constraints.
Custom report type questions reward knowing the object relationship configuration and the field availability rules, not just that custom report types exist. Historical trending items reward knowing the specific limits on field types and retention periods, because the exam writes scenarios where a candidate who assumes no limits would pick the wrong option. Bucketing questions reward knowing which field types are eligible and how nulls are handled, because those details change the answer. Summary formula questions reward knowing at which grouping level the formula applies. Candidates who know these features in general but have not examined their specific constraints lose marks across all five sub-topics.
Advanced Reporting has five sub-areas and the ITExamsTopics practice test covers all of them, giving you visibility into which specific feature you have not fully mapped before you sit the real exam.
The question below presents a reporting requirement and asks you to select the feature and configuration that produces the described output.
Ready to Start Practicing?
Access all questions and start your exam preparation journey
Upgrade to Full ADX-211 Exam Questions π