The IBM Security Access Manager (ISAM) V9.0 deployment professional tries to login to the LMI and discovers user "admin" no longer works, even though the correct password is also provided. The iSAM deployment professional must use "admin@local".
What ISAM application configuration change has occured to cause this behavior?
The behavior described in the question indicates that the login process for the LMI (Local Management Interface) has changed, specifically requiring the format 'admin@local'. This suggests that authentication requirements have been configured or modified, which is directly related to 'Management Authentication.' When management authentication is configured, it can change how usernames are structured and validated during the login process.
I guess the right answer is the letter D.