AD0-E330 Adobe Campaign Classic Developer Expert Exam Topics and Questions

System configuration is where the exam tests whether you understand Adobe Campaign Classic as a platform, before any campaign logic is built on top of it. Get this wrong in production and everything downstream breaks. The topic spans five areas: platform-wide defaults, feature selection for given use cases, troubleshooting broken configurations, custom configuration implementation, and the Campaign Control Panel. Sixteen percent of the exam lives here, so gaps are expensive.

– Platform defaults and feature selection

Adobe Campaign Classic exposes a large surface of system-wide settings: server configuration files, deployment wizard outputs, option tables, and instance-level defaults that govern everything from email routing to data retention. The exam expects you to know which setting lives where and what happens when it is wrong, not just that the setting exists.

Feature selection questions give you a business or technical use case and ask you to pick the right Campaign mechanism to satisfy it. The trap is that several features can overlap in capability. Mid-sourcing versus full on-premise routing, external accounts versus named pipelines, message centre versus standard delivery: each pair solves a surface-level similar problem but the correct choice depends on the specific constraints in the scenario. Know the decision criteria, not just the feature names.

– Troubleshooting and custom configuration

Troubleshooting questions give you a broken or misbehaving configuration and ask what is wrong and how to fix it. The exam does not reward guessing at log entries. It rewards knowing the expected behaviour of the serverConf.xml, the nlserver modules, and the deployment wizard well enough to spot what is inconsistent with a described symptom.

Custom configurations extend the platform beyond its defaults: custom server options, additional nlserver processes, modified configuration files. The exam tests whether you can implement these correctly and, critically, whether you know the side effects. A change to one area of serverConf.xml can affect an unrelated module, and the exam exploits that.

Campaign Control Panel questions focus on what that interface actually governs: subdomain delegation, GPG key management, IP allow-listing, and database capacity monitoring. Candidates who have only used the classic client interface often underestimate how much operational configuration has moved into the Control Panel.

How System configuration is tested

At 16%, this topic appears often enough that a systematic weakness will show up in your score. Items are almost always scenario-based: you are given a described environment, a symptom or requirement, and asked to select the right configuration action or feature.

The main trap is plausibility. Adobe Campaign has multiple ways to achieve similar outcomes, and the distractors are always technically valid in some context. Items reward candidates who can apply the constraint in the scenario to eliminate options, not candidates who simply recognise feature names.

Control Panel items catch candidates who have studied the classic admin console but not the Control Panel. The two do not duplicate each other, and the exam knows the boundary between them.

Troubleshooting items reward working backwards from a symptom to a root cause in the configuration layer, rather than jumping to application-layer fixes. Candidates who lose marks here usually do so by selecting an answer that addresses a symptom rather than its cause. Know what each configuration layer controls and where its scope ends.

From configuration you move into the development layer, and Customization is where this exam most resembles a developer certification rather than an administrator one. At 22% it is the single heaviest topic. The examinable territory covers data model design, API integration, JavaScript development, SQL usage, and out-of-the-box function libraries. A candidate who is strong on configuration but light on hands-on development will feel this weight.

– Data model and API design

Data model questions give you a set of requirements and ask you to choose the design that follows Campaign Classic best practices. The exam is testing judgment here, not recall. It expects you to know the difference between extending an existing schema versus creating a new one, when to use a link versus a collection, and what cardinality choices cost in query performance. Candidates who design data models by instinct rather than by the platform's documented patterns will find the distractors convincing.

API questions focus on implementation: how SOAP calls are structured in Campaign, how REST endpoints are exposed, and where the integration points are. The exam expects you to know which API mechanism fits which integration scenario. Choosing SOAP where a JavaScript API call is appropriate, or vice versa, is a common miss. Know the scope of each approach and the authentication model behind it.

– JavaScript development and libraries

JavaScript in Campaign Classic is not general-purpose JavaScript. It runs inside specific execution contexts: workflow JavaScript activities, SOAP call scripting, typology rule scripting, and personalization blocks. Each context has different available objects, different error behaviour, and different performance characteristics. The exam tests whether you know which library functions are available in which context and what the consequences of misusing them are.

Best-practice questions are particularly sharp here. The exam will describe a working implementation and ask whether it follows best practices, or present two approaches and ask which is preferable. The answer often turns on memory management, execution order, or the risk of blocking the workflow engine. Candidates who have only written JavaScript that works, without considering how Campaign executes it, will lose marks.

– SQL usage and OOTB functions

SQL in Adobe Campaign Classic is used in query conditions, data management activities, and direct script execution. The exam distinguishes between using SQL expressions inside Campaign's query editor, writing SQL scripts in workflow activities, and understanding when each is appropriate. Best-practice questions here often turn on performance: a query that works on a small dataset can lock a production table.

Out-of-the-box functions are the built-in Campaign expression library available in formulas, conditions, and personalisation. The exam expects familiarity with the commonly used categories: string manipulation, date arithmetic, aggregate functions, and conditional expressions. The trap is assuming that a SQL function and its Campaign-expression equivalent behave identically. They do not always, and the exam uses that gap.

How Customization is tested

The heaviest topic on the exam demands the most from your practical experience. Items are almost never definition questions. They present a scenario, often with a partial implementation already described, and ask you to complete it correctly, fix it, or choose between two valid-looking approaches.

JavaScript items reward candidates who understand execution context. Knowing that a function exists is not enough; you need to know where it can be called and what it returns in that context. The distractors are written to catch candidates who know the API surface but not the runtime behaviour.

Data model items reward constraint-driven reasoning. The scenario will include a requirement that eliminates some designs, and the strongest option satisfies all stated constraints without introducing unstated ones.

SQL and OOTB function items reward knowing the performance and behavioural differences between approaches. Candidates who lose marks here tend to select the option that produces the right result without considering what it costs the system. At 22%, getting this topic right or wrong shifts your overall score significantly.

Access management carries the smallest weight on this exam, but the concepts it tests appear as constraints inside scenarios across other topics too. At 8%, a clean sweep here is worth having, and the topic is compact enough to achieve one. The four sub-topics form a single coherent area: operator security settings, access configuration from a solution design, Control Panel access management, and the boundary between data partitioning and sysfilter.

How Access management is tested

Items here are scenario-driven. You will be given an operator's role or a described deployment and asked to select the correct security configuration. The exam expects you to distinguish between named rights, operator group membership, and folder-level permissions, because each controls a different kind of access and the wrong choice in a scenario produces a different failure mode.

Control Panel access management items test whether you know what the Control Panel governs versus what the classic console governs. IP allow-listing and GPG key assignment live in the Control Panel; schema-level permissions do not. Candidates who conflate the two interfaces lose marks on otherwise straightforward items.

The data partitioning and sysfilter distinction is the sharpest concept in this topic. The exam rewards knowing when partitioning alone is insufficient and a sysfilter is required to enforce row-level isolation. Candidates who treat sysfilter as simply another partitioning mechanism will select the wrong option in any scenario where the distinction matters. At 8%, this topic is small enough that thorough preparation should make it a reliable source of marks rather than a source of loss.

Data integration sits at the boundary between Adobe Campaign Classic and the systems around it, and that boundary is where implementations break. At 16%, this topic matches System configuration in weight and demands a different kind of knowledge: not what Campaign can do internally, but how it connects outward, and at what cost. The five sub-topics cover integration approach selection, workflow data-processing practices, in-workflow integration techniques, security and network settings, and external CRUD operations on Campaign schemas.

– Choosing an integration approach and securing the connection

The exam gives you a scenario describing an external system and asks you to select the right integration mechanism. The options typically span file-based exchange, direct database federation (FDA), API-based integration, and pipeline connectors. Each has a different latency profile, a different failure mode, and different infrastructure requirements. The exam tests whether you can read the scenario constraints and eliminate approaches that technically work but are wrong for the stated conditions.

Security and network settings questions cover what must be in place before any external system can reach Campaign: IP allow-listing, firewall rules, account permissions, and encrypted transport. These items reward candidates who understand that integration security is configured in layers, and that a gap in any layer can be the right answer to a troubleshooting scenario. Candidates who treat this as background knowledge rather than examinable content lose marks.

– Workflow data processing and external CRUD

Workflow data-processing best practices are about how data moves through a workflow without degrading performance or corrupting results. The exam tests whether you know the cost of retaining large working populations in memory across activities, when to use intermediate storage, and how enrichment and reconciliation activities should be sequenced. Getting the sequence wrong is a common implementation mistake, and the exam reflects that.

In-workflow integration techniques include FDA queries, file transfer activities, HTTP requests, and JavaScript-based calls. The exam expects you to know which technique is appropriate for a given data volume and latency requirement, not just that the technique exists.

External CRUD on a Campaign schema tests whether you understand how an outside system reads and writes Campaign data correctly: the API endpoints involved, the schema extension requirements, and the constraints on what can be modified externally without breaking internal consistency. This is a narrow but precise area and the exam items on it tend to be specific.

How Data integration is tested

At 16%, Data integration items appear regularly throughout the exam. They almost always present a scenario with a named external system type and a set of constraints, then ask you to choose an approach or identify a problem.

The integration-approach items reward elimination. Candidates who try to identify the single best answer from first principles often stall. The stronger technique is to read the constraints and discard options that violate them, leaving one or two candidates that differ on a specific dimension, which the scenario will have addressed.

Workflow data-processing items reward knowing the order of operations and the memory implications of each activity. Items in this area often describe a workflow that produces an unexpected result or runs slowly, and the strongest option identifies the activity or sequencing choice that caused it.

Security items reward completeness: knowing all the layers that must be configured, not just the most obvious one. Candidates who miss marks here typically select an answer that addresses one layer while ignoring another that the scenario implies is absent.

After integration, the exam shifts to keeping a running instance healthy. Instance maintenance is the operational layer: not building features, but ensuring the platform continues to perform correctly over time. At 12%, it rewards candidates who have spent time in production environments rather than purely in development. The five sub-topics span the Workflow Heatmap, custom monitoring workflows and reports, system indicator interpretation, service and process impact, and baseline audit metrics.

– Monitoring tools and indicators

The Workflow Heatmap is the starting point for understanding concurrent workflow load on an instance. The exam expects you to read a described heatmap state and draw the right operational conclusion: which workflows are competing for resources, where peak load falls, and what action is appropriate. Candidates who know the heatmap exists but have not used it to make a decision will find these items harder than expected.

System indicators and audit metrics items give you a described set of monitoring outputs and ask you to identify what the numbers mean for instance health. This is not about memorising threshold values; it is about knowing which indicator points to which subsystem and what a deviation signals. The exam also tests whether you know how to build a custom workflow or report to surface monitoring data that the default console does not expose, which requires knowing both the monitoring data model and the reporting framework.

– Services, processes, and their impact

Adobe Campaign Classic runs as a set of named server modules: mta, wfserver, syslogd, trackinglogd, and others. Each module has a defined responsibility, and when one behaves unexpectedly the impact on the rest of the instance is predictable if you know the architecture. The exam tests this: given a described module failure or degradation, identify the downstream effect.

This is one area where theoretical knowledge and operational experience diverge sharply. A candidate who has read the architecture documentation knows which module handles what. A candidate who has worked in production knows which module failures are silent and which ones produce immediate visible symptoms. The exam items are written to reward the second kind of knowledge, which means you need to think through the failure chain, not just recall the module's function. Know what each process owns and what stops working when it does not.

How Instance maintenance is tested

At 12%, this topic is mid-weight, and its items are among the most operationally specific on the exam. They describe a system state: a heatmap reading, a set of indicator values, a module status, or a monitoring report output, and ask you to draw a conclusion or recommend an action.

The Heatmap items reward the ability to connect a visual load pattern to a specific operational decision. Candidates who lose marks here typically select a valid operational action that does not address the pattern described.

Service and process items reward knowing the dependency chain between modules. The exam will describe a symptom and include a distractor that addresses a plausible but incorrect module. Knowing which module owns which function is the only way to eliminate it confidently.

Custom monitoring items reward knowing what Campaign's native reporting and workflow frameworks can surface, and how to build against them. The exam does not test deep reporting development, but it does test whether you know where to start. Candidates who treat monitoring as a read-only activity rather than a configurable one tend to miss these items.

Campaign configuration is the heaviest topic on the exam at 26%, and it sits last because it draws on everything before it. Personalisation, target mappings, JavaScript in workflows, temp table manipulation, workflow debugging, delivery settings, performance anti-patterns, and complex targeting design: this is where the exam tests whether you can put the platform to work at an advanced level, not just describe it. Candidates who have coasted through earlier topics on recall alone will feel the difference here.

– Personalisation and target mappings

Advanced personalisation in Campaign Classic goes well past merge fields. The exam tests conditional content blocks, dynamic content conditions, personalisation scripts, and the interaction between personalisation and delivery rendering. Items in this area often describe a personalisation requirement and ask you to select the implementation that will produce the correct output without breaking rendering or causing a script error at send time.

Custom target mappings change what a delivery addresses: not the default recipient table but a custom schema. The exam expects you to know how to configure a target mapping, what it affects downstream in the delivery, and what breaks if the mapping is misconfigured. Candidates who have only worked with the default recipient mapping will find these items unfamiliar. The configuration steps are specific and the exam tests them precisely.

– JavaScript in workflows and temp table manipulation

JavaScript in Campaign workflows appears in multiple activity types, and the exam tests whether you can choose the right usage for a given requirement. Using a JavaScript activity where a query activity would be more appropriate, or writing to a persistent table where a temp table is correct, are the kinds of judgment calls the exam rewards getting right.

Temp table and workflow context manipulation is one of the more technically specific areas in this topic. The exam tests whether you understand how Campaign creates and scopes temp tables during workflow execution, how to read and write to them from a JavaScript activity, and how workflow context variables are passed between activities. Candidates who have never needed to manipulate workflow context directly will find these items require more than documentation recall: they require understanding the execution model.

– Workflow validation, debugging, and performance

Validating and debugging workflow logic is a practical skill the exam tests through described failure scenarios. You are given a workflow that produces wrong results or fails at a specific activity, and asked to identify the cause. The exam rewards systematic diagnosis: knowing which log, which activity output, and which transition carries the evidence of the failure. Candidates who guess at causes rather than trace them will find the distractors convincing.

Workflow performance anti-patterns are a distinct examinable area. The exam describes workflow designs and asks you to identify which practices degrade performance: unbounded queries, excessive enrichment on large populations, synchronous JavaScript calls in high-volume contexts, and similar patterns. The exam does not ask you to optimise in the abstract; it asks you to recognise a specific anti-pattern in a described design.

– Advanced delivery settings and complex targeting

Advanced delivery settings cover the configuration options that go beyond the standard delivery wizard: typology rules, pressure rules, capacity rules, routing, and mid-sourcing configuration at the delivery level. The exam tests whether you know which setting controls which behaviour and what the consequences of a misconfiguration are at send time, not at configuration time.

Complex targeting workflow design items give you a use case and ask you to recommend a workflow structure. The exam tests whether you can choose the right combination of targeting activities, set operations, and enrichment steps to satisfy the requirement efficiently. The trap is that multiple workflow designs can produce the correct population; the exam rewards the design that does so without the performance or logic problems that the distractors introduce. At 26%, getting this sub-area right or wrong has more impact on your final score than any other single area.

How Campaign configuration is tested

A quarter of the exam lives in this topic, and the items are the most complex on the paper. Scenario length is longer, the described environments are more detailed, and the distractors are more carefully constructed than in earlier topics.

Personalisation and delivery items reward knowing what happens at render time, not just at configuration time. A setting that looks correct in the wizard can produce a different outcome when the delivery engine processes it against a real population.

Workflow items reward tracing logic rather than pattern-matching to a remembered design. The exam will describe a workflow you have not seen before and expect you to reason through it. Candidates who rely on recognising familiar patterns will encounter scenarios designed to look familiar but behave differently.

Performance items reward knowing why an anti-pattern is harmful, not just that it is listed as one. The strongest option in these items identifies both the problematic element and the mechanism by which it degrades performance.

At 26%, this topic can make or break an otherwise borderline score. Spend the most preparation time here.