LX0-104 · Question #182
In order to migrate usernames and passwords from a NIS server, the passwd and shadow files were used with a custom script to import the data to OpenLDAP. After properly creating a test workstation to
The correct answer is A. The NIS database is not synchronized with passwd and shadow.. If getent passwd shows a different number of users after migrating from NIS to OpenLDAP using passwd and shadow files, a likely cause is that the NIS database itself was not perfectly synchronized with those local files before the migration.
Question
Options
- AThe NIS database is not synchronized with passwd and shadow.
- BThe OpenLDAP server creates some additional users that are shown in getent.
- CThe NIS clients are not receiving the correct files from the server.
- DThe NIS clients are confused since OpenLDAP and NIS use the same port to communicate.
- EThe OpenLDAP client is querying the NIS server on the wrong TCP/IP port.
How the community answered
(43 responses)- A81% (35)
- B12% (5)
- D2% (1)
- E5% (2)
Why each option
If `getent passwd` shows a different number of users after migrating from NIS to OpenLDAP using `passwd` and `shadow` files, a likely cause is that the NIS database itself was not perfectly synchronized with those local files before the migration.
The passwd and shadow files used for migration might not have been perfectly synchronized with the active NIS database at the time of export. This discrepancy would lead to a different number of users in the LDAP system compared to what NIS clients currently perceive.
OpenLDAP does not automatically create 'additional users' shown in getent; it serves only the data it has been explicitly populated with.
While NIS clients not receiving correct files could cause a discrepancy, the problem description implies the passwd and shadow files themselves were the source for LDAP migration, suggesting an issue with the source data rather than client reception.
OpenLDAP and NIS do not use the same ports to communicate; LDAP typically uses 389/636, while NIS uses 111 (RPC portmapper) and dynamic ports, so port confusion is not a factor.
The problem states a 'test workstation to authenticate against LDAP' was set up, implying the client is correctly configured to query the LDAP server, not the old NIS server on a wrong port.
Concept tested: NIS to LDAP migration data integrity
Topics
Community Discussion
No community discussion yet for this question.