HCL-DOM-AADM-12 Exam Dumps - HCLSoftware Certified Associate Administrator Exam - Notes/Domino 12

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.

=======

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 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.

=======

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.

=======

While a Security Policy manages passwords and ID Vault settings, the Desktop Policy is used to manage the workstation environment itself. This includes workstation-level security settings like Execution Control Lists (ECLs) , which prevent unauthorized code from running on the user's machine, and ID file locking preferences. It ensures that security standards are enforced directly at the user's desktop interface.

=======