Adobe Campaign Classic Architect Master study plan

Diagram a multi-instance Campaign architecture (marketing, mid-sourcing, message center) from memory and label each tier's responsibility

Compare single-instance versus distributed deployment options and justify one for a stated throughput and redundancy requirement

Map which functional modules live on which instance type and explain the data flow between them

Draft a requirements-to-architecture traceability table for a hypothetical enterprise sender

Design a normalized recipient schema with at least three extension tables and define all primary/foreign key relationships

Choose appropriate data types and storage strategies for high-volume event and log tables

Explain how schemas are declared, extended, and regenerated, and identify what triggers a schema regeneration

Model a one-to-many and a many-to-many relationship and describe the query implications of each

Build a workflow that ingests an external file, applies deduplication and segmentation, and triggers a delivery

Add error handling with a test branch, a wait, and an alert activity so failures are surfaced rather than silent

Write a short script (query definition or JavaScript activity) that transforms or validates data inside a workflow

Explain the execution model of workflow activities and where custom code can be injected safely

Compare the available integration surfaces (SOAP/REST-style APIs, JSSP endpoints, file-based exchange, database access) and select one per use case

Design an idempotent inbound integration that handles retries and duplicate submissions

Sketch an authentication and authorization flow for an external system calling into Campaign

Document a two-way sync pattern between Campaign and an external CRM including conflict resolution

Identify the top five performance bottlenecks (database, workflow concurrency, delivery throughput, network, indexing) and the metric that reveals each

Propose an indexing and archiving strategy for the high-volume tables designed in week 2

Define a monitoring checklist covering workflow failures, delivery logs, disk, and queue depth

Draft a triage runbook for a stalled workflow and for a delivery that is not progressing

Design a role and permission matrix mapping job functions to operator groups and named rights

Explain how folder-based security and unit/group inheritance interact when granting access

Identify where sensitive data lives and propose encryption, masking, and retention controls

Outline the audit and governance artifacts a regulated sender must retain

Define a promotion path from development through staging to production, including what is packaged versus rebuilt per environment

List the configuration items that must never be copied blindly between environments and explain why

Write a pre- and post-deployment verification checklist

Plan a rollback strategy for a failed schema or package deployment

Re-derive the week 1 architecture diagram without notes and reconcile any gaps

Complete timed practice sets weighted toward domains 1-4 and log every miss with its root cause

Re-teach the two weakest domains aloud or in writing to confirm retention

Review all prior deliverables and patch the weakest sections