Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Cisco Exam 500-430 Topic 1 Question 6 Discussion

Actual exam question for Cisco's 500-430 exam
Question #: 6
Topic #: 1
[All 500-430 Questions]

Which two user accounts are created by the AppDynamies Controller during installation? (Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: B, C

The AppDynamics Controller is a Java web application that runs on a GlassFish application server and uses a MySQL database. During the installation of the Controller, two user accounts are created by default:

The GlassFish asadmin user is the administrative user for the GlassFish server. This user has the authority to start, stop, and configure the GlassFish server and its domains. The default username for this user isadminand the default password isappdynamics.You can change the password for this user after the installation by using theasadmincommand-line tool1.

The customer-specified Controller administrator account is the user account that you provide during the installation wizard. This is the account that you use to access the AppDynamics User Interface (UI) for the first time and perform various tasks such as creating applications, configuring agents, managing users and groups, and so on. You can choose any username and password for this account, but AppDynamics recommends using only ASCII characters.You can also create additional user accounts in the Controller UI after the installation2.

The other options are not user accounts that are created by the Controller installation. The Elastic search root user, the REST API user, and the MySQL appd admin user are user accounts that are used internally by the Controller components and are not exposed to the end user.The OS user that will run the controller is a user account that you need to create on the host machine before the installation, and it is not created by the Controller installation3.Reference:Controller Installation,Manage Users and Groups, andUpdate the Root User and Glassfish Admin Passwordsin the AppDynamics documentation.


Contribute your Thoughts:

Zachary
6 months ago
You guys are probably right, but I'm still a bit unsure about the REST API user. Maybe we should double-check the documentation to be sure. Either way, this is a pretty straightforward question, nothing too tricky.
upvoted 0 times
Pete
5 months ago
Sorry, but I don't think GlassFish asadmin user and MySQL appd admin user are created by the Controller.
upvoted 0 times
...
Jolanda
5 months ago
You're right, the REST API user is also created during installation according to the documentation.
upvoted 0 times
...
Justine
5 months ago
E) REST API user
upvoted 0 times
...
Louvenia
5 months ago
C) Customer-specified Controller administrator account
upvoted 0 times
...
Suzan
5 months ago
Yeah, those two are definitely created by the AppDynamics Controller during installation.
upvoted 0 times
...
Golda
5 months ago
D) OS user that will run the controller
upvoted 0 times
...
Queenie
5 months ago
A) Elastic search root user
upvoted 0 times
...
...
Lashandra
6 months ago
Yeah, I'm leaning towards C and D as well. Although, the REST API user (E) could also be a possibility, as the controller usually provides a REST API for integration purposes.
upvoted 0 times
...
Jennie
6 months ago
I agree with you on C and D. The rest of the options seem to be related to other components like Elasticsearch, GlassFish, and MySQL, which are not directly part of the AppDynamics Controller installation.
upvoted 0 times
...
Levi
6 months ago
Hmm, this is a good question. I'm pretty sure the correct answers are C and D, the customer-specified Controller administrator account and the OS user that will run the controller. The other options don't seem to be related to the AppDynamics Controller.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77