Learn About IBM Lotus Notes Domino 8 Building the Infrastructure
By Certification Magazine —
1 | 2 | 3 |
The first attempt to match the host name is made with the DNS whitelist. If the host name is found, then no further processing is done. However, if the host name is not found in the DNS whitelist, the DNS blacklist is used to match the host name. DNS whitelist filters can be used independently of DNS blacklist filters. Whitelist/blacklist filtering begins with private whitelist filters, continues with private blacklist filters, proceeds to DNS (public) whitelist filters and finally DNS (public) blacklist filters. So a private blacklist filter could block a connecting host before a DNS whitelist filter has a chance to process it.
Private blacklist filters are used to specify exceptions to private whitelist filters. Private blacklist filters, used for incoming SMTP mail, are used to specify hosts or domains that should be blocked from sending unwanted mail. Private blacklists are stored in the Domino Directory, which is the Names.nsf database. Private blacklist filters can be used independently of private whitelist filters. Private blacklist filtering is disabled by default.
Private whitelist filters can be used to identify exceptions for connecting host names that would otherwise be blocked by private blacklist filters. Whitelist/blacklist filtering begins with private whitelist filters. The private blacklist filters always are applied with a condition that the host name is not matched in the private whitelist. If the host name is not found in the private blacklist, then processing continues with the DNS whitelist, and if not successful, the processing is done with the DNS blacklist filters.
All the other options are incorrect because none of these options present the correct order of processing of blacklist/whitelist filters for SMTP connections.
Reference:
Objective: Manage and maintain.
Sub-objective: Understand directory services\search orders.
Multiple answer, multiple-choice
To improve performance issues in LDAP searches in Domino Directory, you create a full-text index. However, you notice the performance is still not as expected. Which three actions can you take to further improve the performance of LDAP searches? (Choose three.)
A. Delete the existing full-text index and re-create it.
B. Create a secondary directory and create a full-text index.
C. Limit the number of entries returned in the search.
D. Configure a time-out limit on the searches.
E. Specify a minimum number of characters in the search.
Answer:
C. Limit the number of entries returned in the search.
D. Configure a time-out limit on the searches.
E. Specify a minimum number of characters in the search.
Tutorial:
The following actions can be taken to increase the performance of LDAP searches:
- Limit the number of entries returned in the search.
- Configure a time-out limit on the searches.
- Specify a minimum number of characters in the search.
If there are performance issues in LDAP searches, you should first create a full-text index to increase the performance. However, if you create a full-text index and continue to notice performance issues in LDAP searches, you can modify some of the LDAP configuration fields to increase the performance of LDAP searches. These fields are: Maximum number of entries returned, Timeout and Minimum characters for wildcard search.
- The Maximum number of entries returned field defines the total number of search entries that should be returned as a result of the LDAP search. If there is no value defined, any number of search entries can be displayed as the result. To limit this, you should define the number of search entries to be displayed as the result.
- The Timeout field is used to define the amount of time, in seconds, that an LDAP search may take before timing out.
- The Minimum characters for wildcard search field defines the number of characters a user must enter before a wildcard. The default value for this field is 1. You should increase the value in this field to increase the performance of LDAP search.
You should not delete the existing full-text index and re-create it. The new full-text index may face the same performance issues as the current full-text index and therefore this option is not a valid solution in this scenario.
You should not create a secondary directory and create a full-text index because creating a secondary directory does not relate to LDAP searches. You will also have to create a full-text index for the secondary directory.
References:
Sub-objective: Certificate authority\configuring.
Single answer, multiple-choice
In the Tell ca activate <password> command, which password is being used?
A. A new password for the certifier.
B. An existing password for the certifier.
C. The Server ID password.
D. The certificate authority password.
Answer:
A. A new password for the certifier.
Tutorial:
In the Tell ca activate <password> command, you are defining a new password for the certifier. When the certifier is activated, it is activated with a new password. To activate the certifier, you need to issue the Tell ca activate <password> command and activate the certifier with a new password. All the other options are incorrect because none of these passwords are used in the Tell ca activate <password> command.
Reference:
1 | 2 | 3 |
