3.6 Manage Database Credentials and Security APPDYNAMICS-ASSOCIATE-ADMINISTRATOR Practice Questions (Page 2)

Questions 6–10

1. 6foundation · easy

   What is the primary implication of AppDynamics storing database credentials in an encrypted format?

   • AThe credentials are protected from being read in plaintext, but can be updated or replaced when needed.
   • BUsers can view the plaintext password at any time to troubleshoot connection issues.
   • CThe credentials are only accessible to users with the Administrator role.
   • DThe credentials are automatically rotated by the Controller on a schedule.
   Reveal Solution Discussion Select an answer first
2. 7foundation · easy

   Which workflow correctly describes how an administrator adds a new database credential in the AppDynamics Controller?

   • AUse the Controller REST API to directly insert the password into the Controller database.
   • BSend the credentials to AppDynamics support to have them configured on your behalf.
   • CNavigate to the database collector configuration, select 'Add Credential', enter the username and password, and save.
   • DEdit the agent configuration file on the database server and restart the agent.
   Reveal Solution Discussion Select an answer first
4. 8application · medium

   A database administrator at a financial services firm is configuring a new database collector for a production Oracle instance. The DBA is concerned about the credentials being visible to other team members who have access to the Controller UI. The DBA wants to ensure the password is never exposed in plaintext to anyone, including administrators who configure the collector. What should the DBA do?

   • AStore the password in the Controller's encrypted credential vault and reference it by name in the collector configuration.
   • BUse a service account with a long, complex password and document it in a shared team password manager for transparency.
   • CEmbed the password directly in the collector configuration XML file and restrict file permissions to the DBA only.
   • DCreate a separate database user with read-only access and use those credentials in the collector, accepting that the password will be visible in the UI.
   Reveal Solution Discussion Select an answer first
5. 9application · medium

   A monitoring team is configuring a collector for a MySQL database that is also used by a production application. The team wants to follow security best practices for the credentials used by the collector. Which approach should the team take?

   • ACreate a MySQL user with all privileges on the application's database to ensure full visibility.
   • BCreate a dedicated MySQL user with only the SELECT and PROCESS privileges needed for monitoring.
   • CUse the root MySQL account to avoid permission issues with the collector.
   • DUse the production application's credentials to ensure the collector has the same access as the application.
   Reveal Solution Discussion Select an answer first
6. 10application · medium

   A new administrator is reviewing the Controller's configuration and notices that database credentials are not visible in plaintext anywhere in the UI. The administrator wants to confirm how these credentials are protected at rest. What should the administrator understand about AppDynamics' storage of database credentials?

   • ACredentials are stored as plaintext in the Controller database but are hidden from the UI by default.
   • BCredentials are stored on the collector agent machine and never persisted in the Controller database.
   • CCredentials are encrypted at rest using a key managed by the Controller.
   • DCredentials are stored in a separate database that is not encrypted but is isolated from the main Controller database.
   Reveal Solution Discussion Select an answer first