BlackBerry Enterprise Server (BES) Administration Quiz

BlackBerry users are managed and can be disabled or removed using the BlackBerry Profiles database (typically named BBprofile.nsf or similar administrator-defined names) or via the BlackBerry Administration Service/Manager, not directly through standard Domino directory configuration or state databases.

BES (BlackBerry Enterprise Server) is designed to operate as a single cluster instance in a standard deployment. The architecture supports one cluster per BES environment, which handles all user connections and data routing. Multiple clusters are not supported in a single BES deployment.

BlackBerry was developed and introduced in 1999 by Research In Motion (RIM). The first BlackBerry device was the BlackBerry 850, which was released in 1999 as a two-way pager.

In the context of BlackBerry, PIM stands for Personal Information Manager. It refers to the application that manages personal information like contacts, calendar, tasks, and memos on BlackBerry devices. Protocol Independent Multicast is a networking protocol, not related to BlackBerry's PIM functionality.

BlackBerry servers work on PUSH technology. When an email arrives, it is immediately pushed to the BlackBerry device rather than the device having to poll or pull data. This push technology enables real-time email delivery, which was a key differentiator for BlackBerry devices. PULL technology would require the device to actively check for new messages.

Port 3101 (TCP) is the standard port used by the BlackBerry Enterprise Server (BES) to connect to the BlackBerry Infrastructure (routing services over the internet). The other options are incorrect.

The BlackBerry Enterprise Server configuration database (BES configuration database) is created in MS SQL (Microsoft SQL Server). This database stores critical information about users, policies, device configurations, and server settings. Oracle and SAP are not used for this purpose in standard BES deployments.

The BlackBerry PIN can be checked in the BBprofile.nsf database file. This file contains profile information for BlackBerry devices including their unique PIN numbers. The Handheld option is too vague, BB Manager is an administrative tool, and the PIN would not be found through general management interfaces.

BES (BlackBerry Enterprise Server) polls the mail server every 20 seconds to check for new emails. This polling interval ensures timely delivery of messages to BlackBerry devices while not overwhelming the mail server with excessive requests. The 20-second interval was a standard configuration for BES.

BES receives expired ACK (acknowledgment) messages from the BB relay after 7 days. This means that if a message has not been successfully delivered and acknowledged by the device within 7 days, the relay will send back an expired acknowledgment to the BES server. This timeout prevents indefinite waiting for message delivery confirmation.

SRP stands for Server Routing Protocol. It is the protocol used for communication between the BlackBerry Enterprise Server (BES) and the BlackBerry infrastructure (relay/NOCC). SRP handles the routing of data messages between BES and the BlackBerry network. It is not related to remote protocols or general system routing.

BlackBerry services must be enabled by the service provider (mobile carrier). The service provider controls the data plan and must provision the BlackBerry services on the user's account. BES itself manages connections but doesn't enable the service at the carrier level. RIM is the manufacturer and BB Manager is an administrative tool - neither enables services at the carrier level.

BBSD.nsf is the critical operations database for BlackBerry Enterprise Server. This database stores essential server configuration, state information, and operational data required for BES to function. The other options are variations of this name but BBSD.nsf (BlackBerry Server Database) is the correct filename. Note that BBprofile.nsf (from a previous question) stores user profiles, while BBSD.nsf contains server-level operational data.

BES supports common file formats like .doc, .xls, and .jpg for attachment viewing on BlackBerry devices. RTF (Rich Text Format) is typically not supported because it requires complex parsing and was not optimized for BlackBerry's efficient mobile email handling.

BlackBerry Enterprise Server was designed to run exclusively on Windows Server platforms. This architectural choice allowed tight integration with Microsoft Exchange and Windows-based email systems that dominated enterprise environments when BES was developed.

The BlackBerry State Database, which tracks device state and synchronization information, is automatically purged after 24 hours as part of BES's maintenance routine. This prevents database bloat and ensures stale data does not cause synchronization issues.

BlackBerry's default encryption method for data transmission and storage was 3DES (Triple DES). This symmetric encryption standard provided strong security for enterprise data while balancing performance on mobile devices of that era. Option B 'AED' appears to be a typo for AES.

Data deletion from BlackBerry handhelds can be performed through multiple methods beyond just the BlackBerry Manager interface on BES. These include handheld-initiated wipes, IT commands sent over the air, and local device operations, making the 'ONLY' condition in the statement incorrect.