AD0-E327 Adobe Campaign Classic Business Practitioner - Certified Expert Exam Topics and Questions

Campaign management is where the Adobe Campaign Classic platform first shows its complexity. The exam expects you to move between strategic decisions, like which template fits a given brief, and configuration-level knowledge of typologies, target mappings, and web forms. Getting these right depends on understanding how each setting shapes what downstream activities can and cannot do. Gaps here cascade into workflow and delivery errors, so this is one of the first places candidates lose points.

– Templates, typologies and best practices

Campaign templates are not just shortcuts. The exam tests whether you can read a scenario and identify which template structure is appropriate given the campaign type, channel, and approval chain required. A wrong template choice can make later configuration impossible without starting over, so the distinction between template types carries real weight in scenario questions.

Typologies sit on top of templates as a rule-enforcement layer. They control pressure rules, exclusions, and control groups. The examinable point is not that typologies exist but what happens when rules within them conflict or when a typology is missing entirely. Candidates who treat typologies as a checkbox miss the questions that ask what a misconfigured typology would do to a live send.

Best practices around campaign structure, naming conventions, and folder organisation come up in scenario form. The exam rewards knowing which practice prevents a specific operational problem, not a general knowledge of best practice as a concept.

– Target mappings and web channel configuration

Target mappings define which database schema a delivery reads recipients from. The exam tests this in scenarios where a non-standard recipient table is in play, such as a custom subscriber or loyalty schema. Picking the wrong mapping means the delivery either fails or reads the wrong population, so you need to know when the default mapping is insufficient and what selecting an alternative actually changes at the data level.

Web apps and web forms extend Campaign Classic into the browser, but the exam is interested in how they connect back to the campaign data model. Configuration questions focus on which settings control data capture, how form submissions feed into recipient records or custom tables, and what the approval and publishing steps look like. Candidates who have only used email channels often underestimate this sub-topic. The questions are practical rather than conceptual, so your preparation should include knowing the setup steps, not just what the features are for.

How Campaign management is tested

At 20% of the exam, campaign management generates a meaningful share of your score. Items are almost entirely scenario-based: you are given a business requirement or a partially built campaign and asked to identify the right next step, the right template, or the root cause of a configuration problem.

The trap in this topic is treating each sub-area as independent. The exam frequently builds a scenario where a typology rule, a target mapping choice, and a web form setting all interact. Candidates who have memorised individual features but have not thought about how they connect tend to eliminate the wrong options first.

Items reward precision over familiarity. Knowing that typologies enforce pressure rules is not enough; you need to know what happens when a recipient matches multiple rules, and which rule wins. Similarly, target mapping questions reward knowing the downstream consequence of a mapping choice, not just the fact that mappings can be changed. Broad familiarity with the interface will not protect you here.

Workflow management carries the highest weight of any topic on this exam. Where campaign management sets the strategic frame, workflows are the operational engine, and the exam reflects that by testing both design decisions and fault diagnosis. Expect to read workflow configurations and spot what will break under specific data conditions, as well as to match a set of campaign requirements to a workflow structure that actually satisfies them. This is the topic that separates candidates with hands-on experience from those who have only read about the platform.

– Designing workflows to meet campaign requirements

Workflow design questions give you a set of campaign requirements and ask you to identify the correct sequence of activities, branching logic, or data enrichment steps. The exam is not testing whether you know every activity in the palette; it is testing whether you can read a business requirement and translate it into a workflow structure that delivers the right population to the right delivery at the right time.

The recommended practices sub-topic sits alongside design and is examinable in the same scenario format. Practices around transition management, activity naming, scheduler configuration, and error notification are tested because violating them causes specific, identifiable problems. The exam gives you one of those problems and asks which practice, if applied, would have prevented it. Knowing a practice in the abstract is less useful than knowing what breaks when you ignore it.

– Analysing and resolving workflow errors

Error analysis questions are among the most practical in the exam. You are shown a workflow state, an error log excerpt, or a description of unexpected behaviour, and you must identify the cause and the appropriate corrective action. Common failure points include targeting activities that return zero records, enrichment joins that produce duplicate rows, and scheduler configurations that fire at unintended intervals.

The exam rewards a systematic reading of error states rather than pattern-matching to a memorised list of error codes. Candidates who have worked through real workflow failures tend to do well here because they approach errors as a chain of causes rather than isolated events. If your preparation has been theoretical, spend time tracing how a single misconfigured query activity can produce failures several steps downstream. That causal reasoning is what the strongest answer options reflect, and it is what distinguishes a confident selection from an educated guess.

How Workflow management is tested

At 22%, workflow management is the single largest section of the exam. The volume of items means your overall score is highly sensitive to how well you perform here. A weak result in this topic is difficult to offset elsewhere.

Items are scenario-heavy and often multi-step. You may be shown a workflow diagram or a written description of one, then asked to evaluate whether it meets a stated requirement, or to identify which modification would fix a described problem. The exam does not ask you to recall the name of an activity; it asks what that activity does in a specific configuration.

The most common way candidates lose marks is by selecting an option that solves the visible symptom without addressing the underlying cause. Error analysis items in particular are designed so that one option fixes the immediate error while another prevents it from recurring. Items reward identifying the root cause. A second trap is workflow design questions where two options look structurally similar but differ in one activity parameter that changes the output population significantly. Slow down on those and trace the data flow before committing.

Data management is the heaviest topic on the exam at 24%, and it earns that weight because almost every other topic depends on it. Workflow logic, delivery targeting, and reporting accuracy all rest on how data is structured, accessed, and maintained. The sub-topics here span relational database concepts, data sources, export methods, investigation techniques, list creation, predefined filters, and input forms. That breadth means you need fluency across the data layer, not just familiarity with one or two corners of it.

– Relational database foundations and data sources

The relational database concepts sub-topic is not an invitation to explain normalisation theory. The exam tests the concepts that change how you build queries and workflows: primary keys, joins, cardinality, and how schema relationships surface in targeting activities. A candidate who understands why a one-to-many join can inflate a recipient count will make a different, better selection than one who cannot trace the data through the model.

Data sources are tested in the context of workflow activities. The question is not what sources exist in principle but which source a specific workflow activity can reach, and what configuration is needed to access a non-standard source. External files, FDA-linked external databases, and internal Campaign tables each have different access patterns, and the exam tests whether you can match the source to the correct activity and configuration path.

– Exporting data and investigating data quality

Export method questions are scenario-driven: given a volume, a format requirement, or a scheduling constraint, which export approach is appropriate? The exam distinguishes between direct export from a list, workflow-based file extraction, and scheduled recurring exports. The wrong choice in a scenario is usually one that works in simple cases but fails under the stated constraint.

Data investigation sits alongside export and covers the tools Campaign Classic provides for auditing record counts, checking for duplicates, and diagnosing unexpected query results. The exam rewards knowing which investigation tool is appropriate for a described symptom. Candidates who have only used the query editor tend to be unfamiliar with the audit and deduplication tooling, which is exactly where the harder items in this sub-topic tend to concentrate.

– Lists, filters and input forms

List creation best practices are tested in the same scenario format as the rest of the topic: you are given a business requirement and asked to identify the correct approach or to spot the flaw in a described one. The exam is interested in the difference between a static list and a workflow-populated list, and in the update behaviours that make one appropriate over the other in a given situation.

Predefined filters reduce the risk of targeting errors by enforcing consistent query conditions across users. The exam tests the configuration steps and, importantly, the scope of a predefined filter: which users see it, which activities it applies to, and what happens when a user bypasses it. Input forms are the final sub-topic here and connect directly to the data model. Questions focus on which form type is appropriate for a given schema and what the configuration steps look like, rather than on form design aesthetics.

How Data management is tested

At 24%, data management generates more exam items than any other topic. You cannot afford to treat any of its seven sub-topics as optional reading.

Items in this topic frequently embed a data condition inside a workflow or delivery scenario. You are not asked a pure theory question about relational databases; you are shown a workflow that produces an unexpected record count and asked to identify the data-layer cause. That framing means you need to apply database concepts in context, not recall them in isolation.

The most reliable way to lose marks here is to select an answer that would work in a simple case but fails under the specific constraint the scenario states. Export questions are a good example: one option is technically valid but ignores a volume or scheduling requirement buried in the scenario text. Read the constraints before evaluating the options.

Input form and predefined filter questions reward knowing the exact configuration steps. The exam does not accept a general understanding of what these features do; it tests whether you know which setting controls which behaviour. Candidates who have worked through the setup in the platform tend to perform better on these items than those who have only read about them.

After the data-heavy section above, delivery management brings the focus back to execution. At 14%, it is a mid-weight topic, but the three sub-topics are tightly practical: creating and configuring deliveries, setting up proof audiences for approval, and reading delivery audits. The exam expects operational precision here. Knowing that a delivery has configuration options is not enough; you need to know which option does what and what the audit output tells you about a send that did not perform as expected.

How Delivery management is tested

Delivery management items are among the most scenario-specific on the exam. Delivery creation and configuration questions give you a channel, a target population, and a set of constraints, then ask which configuration steps are required or which setting is incorrect. The trap is selecting a step that is generally correct for deliveries but does not satisfy the specific constraint in the scenario.

Proof audience questions test whether you understand the distinction between a proof, a seed address, and a control group, and when each is appropriate in an approval workflow. Candidates who conflate these tend to select options that get the right concept but the wrong tool.

Delivery audit questions reward the ability to read audit data and draw a specific conclusion. Items present a described audit state and ask what it indicates about the send. The strongest options identify a precise cause rather than a general category of problem. Candidates lose marks by selecting an option that is plausible but broader than what the audit data supports. Train yourself to match audit indicators to specific delivery states rather than treating the audit as a pass or fail signal.

Reporting is the second-lightest topic on this exam, but the three sub-topics it covers are more interconnected than they appear. Selecting the right report, reading it correctly, and understanding how data retention decisions affect what the report can show are all part of the same operational question. Candidates who treat reporting as a memorisation exercise, learning which report shows which metric, tend to be caught out by the logs cleanup sub-topic, which requires understanding what happens to report data when purge settings are configured aggressively.

How Reporting is tested

At 12%, reporting generates fewer items than the heavier topics, but those items tend to be precise. Report selection questions give you a business requirement or an operational question and ask which built-in report addresses it. The exam tests the distinction between reports that look similar but cover different scopes or time windows. Selecting a report that shows the right metric but the wrong scope is a common way to lose a mark.

Built-in report interpretation questions present a described report state and ask what conclusion it supports. Items reward a specific reading of the data rather than a general one. If the report shows a particular delivery throughput pattern, the strongest option identifies what that pattern indicates, not just that something is wrong.

The logs cleanup sub-topic is where many candidates are underprepared. The exam tests the causal link between purge configuration and report accuracy: if logs are purged on a schedule that is shorter than a report's lookback window, specific metrics become unavailable or inaccurate. Items reward knowing which metrics are affected and why, not just that purging affects reporting in general.

Administration is the lightest topic on the exam at 8%, and its three sub-topics are tightly scoped: the impact of logs purge on reporting (which connects directly to what you covered in the previous topic), access control and authorisation, and SFTP configuration via the control panel. Do not underestimate it because of the weight. Items in this topic are precise, and a candidate who has focused only on the heavier topics can drop marks here on questions that require knowing a specific configuration step rather than a general principle.

How Administration is tested

Administration items are configuration-precise. The logs purge sub-topic overlaps with reporting, but the angle here is different: questions focus on the administrator's decision about purge settings and what that decision costs in terms of reporting capability. Items reward knowing the specific relationship between a purge interval and the reports it affects, and the strongest options identify a precise trade-off rather than a general caution.

Authorisation and access questions are scenario-based: you are given a business requirement describing what a user or group needs to do, and you must identify the correct permission or access configuration. The exam tests the difference between operator groups, named rights, and folder-level permissions. Selecting a permission that is broader than the requirement states is the most common error here, because it solves the access problem but violates the principle of least privilege that the exam rewards.

SFTP configuration via the control panel is the most procedural sub-topic in this section. Items test the sequence of steps and the settings involved. Candidates who have not worked through this configuration path in the platform should review it step by step, because the exam does not accept a general awareness that SFTP can be enabled.