Adobe Campaign Classic Developer Professional Free Sample Questions
Description
Covers administration node configuration and schema management, campaign schema customization, user groups and security zones, import/export and data transformation workflows, and approvals.
12 free sample questions135 in the full practice test
A marketing technology architect is designing a new custom table in Adobe Campaign Classic to store external loyalty data. The table will contain over 50 million records and will be frequently joined with the OOTB nms:recipient schema. Which approach is the OPTIMAL way to define the primary key for this new schema to ensure high performance during workflow queries?
Answer and explanation
Correct answer: B
In Adobe Campaign Classic, using an auto-generated numeric primary key (autopk="true") is the standard and most performant best practice for large tables. Numeric joins are significantly faster than string-based joins (like Email Address or alphanumeric Loyalty IDs). Creating a dedicated link (foreign key) to the recipient table allows the query engine to optimize joins efficiently.
Q2Question 2
Beginner
System Configuration · Administration Node Configuration
A developer is tasked with updating the default server URL used for tracking links across the entire Adobe Campaign Classic instance. Where should this configuration change be made to ensure it applies system-wide?
Answer and explanation
Correct answer: A
Q3Question 3
Advanced
System Configuration · Typology Rules
Case Study: Global Retailer Fatigue Management
A global retail company with over 10 million active subscribers relies heavily on email and SMS marketing. Over the last quarter, their unsubscribe rates have spiked by 18%. The marketing team wants to implement a strict fatigue management strategy.
Requirements:
No recipient should receive more than 3 emails and 1 SMS per week.
Highly valuable VIP customers should bypass this rule for urgent product recall notices.
The system must automatically rank communications so that promotional newsletters are dropped before targeted lifecycle messages if the limit is reached.
The solution must integrate seamlessly with existing campaign workflows without requiring manual query exclusions in every campaign.
Which combination of configurations is the MOST robust way to satisfy all these requirements?
flowchart TD
A[Campaign Delivery] --> B{Typology Application}
B --> C[Filtering Rules]
B --> D[Pressure Rules]
B --> E[Control Rules]
D --> F{Weight Calculation}
F --> G[Deliver]
F --> H[Exclude]
Answer and explanation
Correct answer: B
Pressure rules are specifically designed for fatigue management (controlling contact frequency). Setting thresholds per channel and assigning weights allows the system to prioritize important lifecycle messages over standard promos when limits are reached. A complementary Filtering rule can be used to exempt specific high-priority targets (VIPs for product recalls) from standard fatigue caps.
Q4Question 4
Intermediate
System Configuration · Target Maps
A developer needs to send a targeted delivery to a custom table cus:investor instead of the standard nms:recipient table. After creating the custom target mapping, the developer notices that tracking logs are not being correctly attributed to the investors.
What is the MOST likely cause of this issue regarding the custom target map configuration?
Answer and explanation
Correct answer: C
When creating a custom target mapping in Adobe Campaign Classic, the standard nms:trackingLogRcp table only logs interactions for the standard recipient table. For a custom target dimension (like cus:investor), the developer MUST create corresponding custom tracking log and broadlog schemas, and explicitly link them in the Target Mapping configuration settings.
Q5Question 5
Beginner
System Configuration · Adobe Experience Cloud Integration
True or False: When integrating Adobe Campaign Classic with Adobe Audience Manager (AAM) using the People Core Service, audiences shared from AAM to Campaign are physically imported into the Campaign database as static list records.
Answer and explanation
Correct answer: A
True. In Adobe Campaign Classic, audiences shared from Adobe Audience Manager (or the Experience Cloud) via the People Core Service are physically imported via a technical workflow (Import shared audience) and stored as static lists in the Campaign database, linked to the recipient table via the Visitor ID or Declared ID.
Q6Question 6
Intermediate
System Configuration · Form Renderings
An administrator needs to create a custom user interface in the Campaign client console to allow operators to easily input and update metadata for a custom cus:storeLocation schema.
Which type of Form Rendering should the developer configure to bind directly to the schema and provide this capability?
Answer and explanation
Correct answer: B
An Input Form (xtk:form) is specifically used in Adobe Campaign Classic to create custom user interfaces within the rich client console. It binds directly to a data schema, allowing operators to view, insert, and update database records natively without needing to write complex database queries.
Register free for 6 more questions
Or unlock all 135 AD0-E331 questions with explanations, timed mode and flashcards.
