A company has 50 Java agents on Tomcat and 30 .NET agents on IIS. They need to upgrade all agents from 21.8 to 22.4. The team has limited time and wants to minimize downtime. They also need to ensure the upgrade is reversible. What is the best approach?

Use the Controller's Agent Management feature to upgrade all agents automatically.

Upgrade all agents simultaneously during a single maintenance window.

Upgrade the Java agents first using a rolling restart, then upgrade the .NET agents during a maintenance window.

Upgrade the .NET agents first, then the Java agents.

A company runs 100 Java agents on Tomcat servers. They want to upgrade from 21.10 to 22.4. The team has a CI/CD pipeline that builds and deploys the applications. What is the most sustainable approach for future agent upgrades?

Use the Controller's Agent Management feature to push the new agent to all Tomcat servers.

Create a shared network drive with the agent and configure all Tomcat servers to load it from there.

Manually upgrade each Tomcat server by replacing the agent files.

Incorporate the agent download and installation into the CI/CD pipeline so each deployment uses the target agent version.

An administrator is upgrading the Java agent on a Linux server running a Spring Boot application. They have downloaded the new agent zip and extracted it to a temporary directory. The application is started with the -javaagent flag pointing to /opt/appdynamics/javaagent.jar. What is the correct next step?

Update the -javaagent flag to point to the new extracted directory and restart the application.

Copy the new agent files over the old ones while the application is running.

Run the agent installer script from the extracted directory.

Replace /opt/appdynamics/javaagent.jar with the new agent jar and restart the application.

After upgrading the Java agent on a Tomcat server, the agent appears in the Controller, but the administrator notices that the agent version shown is still the old version. The application was restarted after the upgrade. What is the most likely cause?

The Controller caches the old agent version and will update later.

The Tomcat server was not fully restarted.

The -javaagent flag still points to the old agent jar file.

The agent configuration file specifies an older version.

Which of the following describes an automated method for upgrading AppDynamics agents?

Downloading the agent installer and running it interactively on each server.

Manually replacing the agent files on each application server.

Using the AppDynamics Controller UI to push the agent update to all application servers.

Using a configuration management tool such as Ansible or Chef to deploy the new agent version.

CiscoAppDynamics Associate Administrator

Domain 1Objective 2

1.2 Upgrade Agents APPDYNAMICS-ASSOCIATE-ADMINISTRATOR Practice Questions (Page 4)

Part of the Agents domain, which accounts for 15% of the APPDYNAMICS-ASSOCIATE-ADMINISTRATOR exam. Cisco does not publish an official question count, but from its 90-minute exam (~35–60 total, ~5–9 in this domain), expect 1–2 from this objective — we provide 23 practice questions to prepare you well beyond it. (estimate)

23questions here

5free pages

4concepts

15%of the exam

Questions 16–20

16expert · hard
A company has 50 Java agents on Tomcat and 30 .NET agents on IIS. They need to upgrade all agents from 21.8 to 22.4. The team has limited time and wants to minimize downtime. They also need to ensure the upgrade is reversible. What is the best approach?
Select an answer first
17application · medium
A company runs 100 Java agents on Tomcat servers. They want to upgrade from 21.10 to 22.4. The team has a CI/CD pipeline that builds and deploys the applications. What is the most sustainable approach for future agent upgrades?
Select an answer first
18application · medium
An administrator is upgrading the Java agent on a Linux server running a Spring Boot application. They have downloaded the new agent zip and extracted it to a temporary directory. The application is started with the -javaagent flag pointing to /opt/appdynamics/javaagent.jar. What is the correct next step?
Select an answer first
19expert · hard
After upgrading the Java agent on a Tomcat server, the agent appears in the Controller, but the administrator notices that the agent version shown is still the old version. The application was restarted after the upgrade. What is the most likely cause?
Select an answer first
20foundation · easy
Which of the following describes an automated method for upgrading AppDynamics agents?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to APPDYNAMICS-ASSOCIATE-ADMINISTRATOR

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Cisco. “APPDYNAMICS-ASSOCIATE-ADMINISTRATOR” is a trademark of its owner, used for identification only.