When zero downtime is requested and another BlackBerry Domain is used, what is the best method for upgrading the environment? (Choose one)

Question

Options

• AMigration using an in-place upgrade
• BMigration using a knife edge cutover
• CMigration using a phased upgrade
• DMigration using the EnterpriseTransporter.exe utility
• EMigration using the besmigrate.exe utility

• A
  3% (1)
• C
  12% (4)
• D
  82% (28)
• E
  3% (1)

Explanation

EnterpriseTransporter.exe is purpose-built for migrating BlackBerry users and data across different BlackBerry Domains while maintaining continuous service - it stages the migration so users remain active throughout, satisfying the zero-downtime requirement. The other options fail for specific reasons: an in-place upgrade (A) operates within the same environment and domain rather than moving to another one; a knife edge cutover (B) switches all traffic at once, introducing a hard stop that violates zero-downtime; a phased upgrade (C) rolls out changes gradually but is not designed for cross-domain moves and doesn't guarantee zero downtime; besmigrate.exe (E) handles BES-to-BES migrations within the same domain, not across separate BlackBerry Domains.

Memory tip: Think "EnterpriseTransporter = External Domain transfer with zero downtime." The word "Transporter" itself implies moving between separate locations (domains), and the "Enterprise" prefix signals it's the full-featured, production-safe tool for the job.

No community discussion yet for this question.