nerdexam
BlackBerry

BCP-620 · Question #81

Nextair Corporation has configured push application access to be above the failover threshold but below the promotion threshold. Which situation will cause a failover? (Choose one)

The correct answer is D. BlackBerry MDS Connection Service fails on the primary BlackBerry Enterprise Server instance. Option D is correct because failover is triggered when the primary BlackBerry Enterprise Server (BES) experiences a service degradation - specifically, when the BlackBerry MDS Connection Service fails on the primary instance, push application access drops below the configured…

High Availability and Disaster Recovery

Question

Nextair Corporation has configured push application access to be above the failover threshold but below the promotion threshold. Which situation will cause a failover? (Choose one)

Options

  • ABlackBerry MDS Connection Service is healthy on the secondary BlackBerry Enterprise Server
  • BBlackBerry MDS Connection Service is healthy on the primary BlackBerry Enterprise Server instance
  • CBlackBerry MDS Connection Service fails on the secondary BlackBerry Enterprise Server instance
  • DBlackBerry MDS Connection Service fails on the primary BlackBerry Enterprise Server instance

How the community answered

(25 responses)
  • A
    16% (4)
  • B
    8% (2)
  • C
    4% (1)
  • D
    72% (18)

Explanation

Option D is correct because failover is triggered when the primary BlackBerry Enterprise Server (BES) experiences a service degradation - specifically, when the BlackBerry MDS Connection Service fails on the primary instance, push application access drops below the configured failover threshold, prompting the system to switch traffic to the secondary server. Option A is wrong because a healthy MDS on the secondary server is simply a normal, expected state - not a trigger for anything. Option B is wrong because a healthy MDS on the primary server means everything is functioning correctly, so no failover is needed. Option C is a trap: MDS failing on the secondary server does not trigger a failover, because the secondary is the failover destination, not the source of failover decisions - its health only matters after a failover has already occurred.

Memory tip: Failover is always about the primary going down - remember "Primary Fails → Failover." If the secondary has a problem, that's a concern for after you've failed over, not a trigger for the process itself.

Topics

#failover threshold#promotion threshold#MDS Connection Service#push application access

Community Discussion

No community discussion yet for this question.

Full BCP-620 Practice