An AEM Architect is moving existing content from an on-premise AEM to an AEM Cloud Service instance using the Content Transfer Tool. As part of the initial source preparation, the Architect is going…

Question

Options

• AValidate that all replication agents are disabled
• BVerify that wipe mode is enabled
• CStop all bundles using the AEM Web Console
• DVerify that free disk space is at least 1.5x the JCR size
• ERun datastore consistency check via oak-run

• A
  4% (1)
• B
  82% (23)
• C
  11% (3)
• E
  4% (1)

Explanation

Before extracting content, the on-premise AEM must have at least 1.5x the segment store (JCR) size available as free disk space (D) because the extraction process writes a local copy of the migration set before uploading it to cloud storage - without that headroom, the extraction will fail mid-run. Wipe mode (B) must also be verified as enabled so the target AEMaaCS repository is cleared before ingestion, preventing stale or conflicting content from corrupting the migrated dataset.

Why the distractors are wrong:

• A - Disabling replication agents is a target-side concern, not a source preparation step; the source keeps running normally during extraction.
• C - You must not stop bundles; AEM needs to stay running to serve the CTT extraction process.
• E - A datastore consistency check via oak-run is a best-practice health check but is optional, not a required pre-extraction action in the CTT workflow.

Memory tip: Think "D-W" = Disk + Wipe - check your Disk has room to dump the content, and confirm Wipe mode so the target starts clean. If you remember those two source-prep commitments, you can eliminate the distractors (agent config, bundle stops, and optional health checks) as out-of-scope or optional steps.

No community discussion yet for this question.