What action should be taken if the indexing job is experiencing prolonged execution time during content migration in AEMaaCS?

Question

Options

• ABlock Cloud Acceleration Manager access in the migration service.
• BApply IP Allowlist through Cloud Manager.
• CDisable Cloud Acceleration Manager.
• DEnsure no IP Allowlist is applied through Cloud Manager.

• A
  6% (1)
• B
  6% (1)
• C
  13% (2)
• D
  75% (12)

Explanation

During content migration in AEMaaCS, an IP Allowlist applied through Cloud Manager can inadvertently block the migration service's backend from communicating with the AEM environment, causing the indexing job to stall or run indefinitely. Removing any IP Allowlist restrictions (option D) restores the open network access the Content Transfer Tool requires to complete indexing successfully.

Why the distractors are wrong:

• A - Blocking Cloud Acceleration Manager (CAM) access would cut off the very tool orchestrating your migration, making things worse.
• B - Applying an IP Allowlist tightens restrictions further, compounding the connectivity problem rather than resolving it.
• C - Disabling CAM entirely halts the migration process; it does nothing to address the root cause of restricted network access.

Memory tip: Think of it as "open the gate before the trucks arrive." An IP Allowlist is a gate - if it's closed during migration, the indexing trucks (migration service) get stuck outside. Option D = remove the gate = let traffic flow freely.

No community discussion yet for this question.