Which factors must be considered when estimating a migration plan? (Choose three)

Question

Options

• AVolume of assets to migrate
• BExisting caching configurations
• CCompatibility of user permissions
• DEstimated downtime during migration
• ECloud Manager pipeline configuration

• A
  73% (11)
• B
  20% (3)
• E
  7% (1)

Explanation

When estimating a migration plan, volume of assets (A) directly determines the time, resources, and complexity required - more assets means longer timelines and higher risk. Compatibility of user permissions (C) must be validated upfront to ensure access controls translate correctly to the new environment, preventing security gaps or broken workflows post-migration. Estimated downtime (D) is critical for communicating impact to stakeholders and scheduling the migration window to minimize business disruption.

B (caching configurations) is a performance tuning concern, not a core estimation factor - it's addressed after migration, not during planning. E (Cloud Manager pipeline configuration) is a tool-specific setup detail, not a universal migration estimation consideration; pipelines are configured as part of execution, not scoped during the planning estimate.

Memory tip: Think "VAD" - Volume, Access, Downtime - the three things you must know before you can confidently promise a migration timeline to anyone.

No community discussion yet for this question.