HCL-DOM-AADM-12 HCLSoftware Certified Associate Administrator Exam - Notes/Domino 12 Questions and Answers

All requests for the Administration Process are stored in the Administration Requests database (admin4.nsf) . When an administrator performs a task (like deleting a user), a "request" document is created in this database. The AdminP task on each server in the domain periodically checks this database to see if there are tasks it needs to perform, such as updating local database ACLs or deleting local replicas.

Domino Domain Monitoring (DDM) is designed to give administrators a high-level view of the health of their entire infrastructure. Its primary role is to centralize event collection and monitoring across servers within a domain. By using specialized probes, DDM gathers status information from various servers and aggregates the data into a single database (ddm.nsf), allowing administrators to identify and resolve issues from one central location.

Here is the next batch of questions (51–60) from your provided list, strictly following the requested formatting and verified for the HCL-DOM-AADM-12 exam.

Domino replication occurs in two primary directions: Push and Pull . In Pull replication, the local server asks the remote server for changes. In Push replication, the local server sends its changes to the remote server. Most standard Connection documents are configured for "Push-Pull" replication, which is a bidirectional exchange ensuring both replicas become identical during the task.

=======

A mail-only registration is used for users who will not be using the HCL Notes client and instead access their mail via internet protocols like POP3, IMAP, or HTTP. Because these users do not require Notes-specific authentication or encryption, the registration process excludes the creation of a Notes ID file . This simplifies the registration process for users who only need access to their Domino mailboxes through standard web browsers or third-party email clients.

=======

HCL Domino utilizes a hierarchical naming structure to ensure every entity (user or server) has a unique name. In this structure, OU stands for Organizational Unit . OUs are typically used to represent departments, physical locations, or branches within the broader Organization (O), allowing for granular administrative control and security delegation.

=======

The foundational security of HCL Domino is built on Public Key Infrastructure (PKI) . By default, when a Notes client connects to a Domino server, it uses the Notes ID file . This file contains the user's private key. The server uses the corresponding public key (stored in the user's Person document) to perform a complex cryptographic "handshake" to verify the user's identity without ever sending the actual password or private key over the network.

=======

For servers within a Domino domain to trust one another for replication and mail routing, they must share a common security root, which is the Organizational Certificate Authority (Certifier) . During the installation and configuration of any new server in the domain, it must be registered using a certifier that descends from the same top-level Organization (O). This shared ancestry allows servers to authenticate each other's identities securely using the Notes public-key system.

=======

The Messaging tab is the primary tool for mail administrators. It is used to monitor mail routing status, view the contents of the mail.box, and perform SMTP diagnostics . It provides a real-time view of mail flow, showing whether the Router task is active and if there are any delivery failures or bottlenecks in the messaging system.

=======

Desktop Policies are used by administrators to standardize the Notes client environment and enforce security behavior. Two key security-related settings managed through these policies include enforcing ID file locking , which automatically locks the user's ID after a specific period of inactivity to prevent unauthorized access on a shared workstation. Additionally, policies can force Smart Upgrade , ensuring that all users are running the approved, secure version of the Notes client software by automating the installation of updates.

=======

The Domino Attachment and Object Service (DAOS) stores attachments separately from NSF files. When documents are deleted, the associated attachment files (.NLO) are not immediately removed from the storage. To reclaim this physical disk space, an administrator must:

Issue the tell daosmgr prune command : This identifies and deletes attachment files that are no longer referenced by any database and have exceeded the deferral interval.

Issue the tell daosmgr resync command : This synchronizes the DAOS catalog (daoscat.nsf) with the physical files on disk to ensure the repository is accurate.

=======

In HCL Domino, the mail.box database (or databases, if multiple are configured) acts as the temporary holding area or "staging ground" for all transit mail. When mail arrives at the server—whether from a local Notes user, another Domino server, or via SMTP—it is deposited into mail.box. The Router task then monitors this database, reads the recipient information, and moves the message to its final destination (the user's mail file) or transfers it to another server.

=======

The Messaging tab in the Domino Administrator Client is the central hub for monitoring and managing the mail system. It provides administrators with a comprehensive view of mail routing status and router diagnostics , allowing them to see how many messages are pending in the mail.box, track the progress of the Router task, and troubleshoot delivery failures or bottlenecks in the mail flow.

=======

When planning where to physically place servers in a global or distributed domain, two critical factors are Time zone differences and Network bandwidth and latency . Time zones impact the scheduling of replication and maintenance tasks to avoid peak business hours. Bandwidth and latency are vital because they determine how quickly data can be replicated between servers; poor network conditions can lead to data inconsistency and slow mail delivery between locations.

To enable the Domino Attachment and Object Service (DAOS) , an administrator must first enable it in the Server document (under the DAOS tab) by specifying a base path and the minimum attachment size. Once the server-level setting is active, the administrator must then enable DAOS on individual databases and run the compact -c -daos on command. This process converts the internal database structure to move attachments into the DAOS repository.

=======

The Administration Process (AdminP) is a core server task in HCL Domino designed to automate administrative requests that would otherwise require manual intervention. When an administrator makes a change in the Domino Directory—such as renaming a user, deleting a group, or moving a mail file—the request is posted to the Administration Requests database (admin4.nsf). AdminP then processes these requests across all servers in the domain, ensuring that Access Control Lists (ACLs), person documents, and reader/author fields are updated automatically to maintain domain-wide consistency.

=======

HCL Domino uses hierarchical naming (e.g., CN=User/OU=Sales/O=HCL) to support scalability and administrative delegation . This structure allows large organizations to create unique namespaces for different departments or geographical locations. It also enables the use of different "certifiers" for different branches of the hierarchy, allowing local administrators to manage their own users and servers without affecting the entire domain.

=======

Domino Domain Monitoring (DDM) provides a centralized collection and display of server events across an entire domain. It uses "probes" to check various subsystems (like Mail, Security, or Replication). When a probe finds an issue, it generates a report in the ddm.nsf database, allowing administrators to monitor the health of multiple servers from a single interface.

=======

The Router task is the engine responsible for the delivery and transfer of all mail in the Domino system. Because it manages the mail.box and determines the delivery path for every message, it is also the task that enforces message delivery limits —such as maximum message size—and controls mail flow based on the configurations set in the Configuration Settings document.

=======