Since the sales application is mission-critical, what can be done to ensure its content is always delivered to the BlackBerry device users? (Choose one)

Question

Options

• AConfigure a secondary pool of BlackBerry MDS Connection Services
• BConfigure one primary pool of BlackBerry MDS Connection Services
• CPut the MDS Integration Service Database in a separate server
• DCreate a pool of BlackBerry MDS Integration Services

• A
  8% (3)
• B
  72% (26)
• C
  3% (1)
• D
  17% (6)

Explanation

Configuring a primary pool of BlackBerry MDS Connection Services (B) provides high availability by clustering multiple Connection Service instances together - if one node fails, others continue delivering content to devices without interruption, which is exactly what a mission-critical application requires.

Why the distractors are wrong:

• (A) A "secondary" pool implies a backup-only configuration without a functioning primary - you need the primary pool itself to be the HA solution.
• (C) Isolating the MDS Integration Service database improves database performance or separation of concerns, but does nothing to ensure continuous content delivery to devices.
• (D) The MDS Integration Service handles web service workflows and push APIs - it is not responsible for delivering content to BlackBerry devices; that is the Connection Service's job.

Memory tip: Think "Connection = Content to device." The MDS Connection Service is the component that connects BlackBerry devices to content, so pooling it is how you guarantee that connection is always available for mission-critical apps.

No community discussion yet for this question.