1. |
C The default CallManager installation without MLA uses the Windows 2000 Administrator account for both CallManager Administration and server administration. A sniffed username and password could mean the demise of both the CallManager Administration interface and the underlying Windows operating system. |
2. |
B The URL to access the Cisco CallManager Administration interface remains the same. The only difference is using the HTTPS protocol rather than just HTTP. |
3. |
C There is no read-write access in Cisco MLA. This setting would be the same as full access. |
4. |
D After you enable MLA and restart the World Wide Web Service in Windows 2000, a new account "CCMAdministrator" is stored in the Windows 2000 Registry for full CallManager Administration access. |
5. |
A There is no Standard Device functional group. Rather, MLA splits the device functions into the specific devices managed, such as Standard Phone or Standard Gateway. |
6. |
B There is no FullAccess group in the MLA user group defaults. The full access role is assigned to the SuperUserGroup. |
7. |
B Self-signed certificates raise an automatic red flag in any client web browser. This is because there is no trusted authority (a Certificate Authority) authenticating the web server. |
8. |
A The MLA user accounts are stored in an LDAP directory. By default, this is the DC Directory installed with the Cisco CallManager; however, you can change this directory storage to anther directory (such as Active Directory). |
9. |
D CallManager MLA stores the CCMAdminstrator account in the Windows Registry. This allows a "back door" into the CallManager Administration interface if the LDAP directory is unavailable. |
10. |
A and C By default, MLA is disabled for a clean CallManager install; however, it will remain enabled (with a new, random CCMAdministrator password) if upgrading from previous MLA (and Cisco CallManager) version that was enabled. |