What is the most important factor in determining sizing for AppDynamics Controller?
A
Explanation:
The most important factor in determining sizing for AppDynamics Controller is the projected metric
load per minute on the Controller. This is because the metric load represents the actual workload on
the Controller, which depends on the nature of the application, the AppDynamics configuration, and
the usage patterns. The number of agents, the type of agents, the number of administrators/end
users, and the number of AppDynamics applications are only rough estimates that can vary greatly
depending on the specific scenario. Therefore, it is recommended to test the performance of the
system in a staging environment and verify the Controller sizing using the metric upload rate before
deploying to production. Reference:
Controller System Requirements
,
Performance and Controller
sizing guidelines
,
How to Run AppDynamics in Microsoft Azure
,
Platform Requirements
Which two choices are available when specifying an application in a URL string for the Health Rule
REST API? (Choose two.)
BD
Explanation:
The Health Rule REST API allows you to create, configure, update, and delete health rules for
multiple applications simultaneously. To use this API, you need to specify the application in the URL
string. You can use either the application ID or the application name for this purpose. The application
ID is a unique numeric identifier for each application in the Controller. The application name is the
display name of the application in the AppDynamics UI. You cannot use the application alias, GUID,
or REGEX for the Health Rule REST API. Reference:
Health Rule API
and
Retrieve All Business
Applications
in the AppDynamics documentation.
What are three requirements to set up AppDynamics Controllers as a high availability pair? (Choose
three.)
ADF
Explanation:
To set up AppDynamics Controllers as a high availability pair, you need to meet the following
requirements1
:
Passwordless SSH must be configured between the two Controller servers. This allows the Enterprise
Console to automate the configuration and administration tasks associated with a highly available
deployment on Linux systems.
Both servers must have the Controller software installed prior to setting up high availability. The
Controllers in an HA pair must be equivalent versions, and be in the same data center.
Both servers must have identical directory structures for the Controller installation. The individual
machines in the Controller HA pair need to have an equivalent amount of disk
space. Reference:
Prerequisites for High Availability
Which two statements are true when updating the Database Agent? (Choose two.)
AD
Explanation:
According to the Cisco AppDynamics Professional Implementer (CAPI) documents, when updating
the Database Agent, you need to follow these steps12
:
Stop the agent as described for your specific installation in Start and Stop the Database Agent.
Make a copy of the existing agent directory, <db_agent_home>. Backing up allows you to revert to
the previous agent installation if you need to. You can also copy over the controller-info.xml
configuration file to the new installation to ensure the agent configuration is maintained.
Install the Database Agent as described for your specific installation in Administer the Database
Agent.
Copy the <backup_db_agent_home>\conf\controller-info.xml file to the new installation directory,
<db_agent_home>\conf. To ensure the agent configuration is maintained, copy the
<backup_db_agent_home>\conf\controller-info.xml file to the new installation directory,
<db_agent_home>\conf.
Start the new agent. See Start and Stop the Database Agent.
Verify the Database Agent Installation. See Verify the Database Agent Installation.
Therefore, the correct statements are:
The Database Agent must be stopped and restarted during the upgrade. (A)
Controller-info.xml is the only file that needs to be migrated from the previous agent to the new
agent. (D)
The incorrect statements are:
If the agent is moved to a new location during the upgrade, the AppDynamics Controller must be
reconfigured to reference the new location of the agent. (B) This is not true because the controller-
info.xml file contains the information about the Controller host, port, account name, access key, and
SSL settings. As long as this file is copied to the new agent location, the Controller does not need to
be reconfigured.
All data collectors created from the previous agent must be migrated to the new agent. © This is not
true because the data collectors are configured on the Controller UI, not on the agent. The agent
collects the metrics from the databases and sends them to the Controller. The data collectors do not
need to be migrated to the new agent.
After the Database Agent is upgraded, the AppDynamics Controller must be restarted. (E) This is not
true because the Controller does not depend on the agent version. The agent and the Controller are
compatible as long as they meet the Agent and Controller Compatibility requirements.
Reference:
: Upgrade the Database Agent - AppDynamics
: Release Upgrade Checklist for Database Agents - AppDynamics
What are two settings that an administrator can configure from the AppDynamics Controller Admin
Console? (Choose two.)
DE
Explanation:
The AppDynamics Controller Admin Console lets you configure certain global settings for the
Controller, such as metric retention periods, UI notification triggers, tenancy mode, and accounts in
multi-tenancy mode1
. Two of the settings that an administrator can configure from the AppDynamics
Controller Admin Console are:
License allocation: This setting allows you to view and manage the license usage and availability for
your Controller. You can see the total number of licenses, the number of licenses in use, the number
of licenses available, and the license expiration date for each agent type.
You can also allocate
licenses to specific applications or accounts, and set license limits and alerts2
.
Retention periods: This setting allows you to specify how long the Controller retains the metric data
and the event data for your monitored applications. You can configure the retention periods for
different types of data, such as minute-level metrics, hour-level metrics, day-level metrics,
transaction snapshots, and events.
You can also configure the data purge schedule and the data
backup schedule3
.
Reference:
Access the Administration Console
,
License Rules
,
Data Retention
If using SSL for agent communication with an AppDynamics Controller, it is recommended that agent
SSL traffic
C
Explanation:
AppDynamics recommends that you terminate SSL connections from agents at a reverse proxy or a
load balancer in front of the Controller, rather than at the Controller itself. This improves the
performance and scalability of the Controller by offloading the SSL processing to the proxy or load
balancer. It also simplifies the configuration and management of SSL certificates and truststores. To
enable this option, you need to configure the proxy or load balancer to accept SSL connections from
agents and forward them to the Controller using HTTP. You also need to configure the agents to use
SSL and point to the proxy or load balancer host and port. See
Enable SSL for the Java Agent
for an
example. Reference:
Agent-to-Controller Connections
and
Enable SSL and SSH for Database Agent
Communications
in the AppDynamics documentation.
Which artifacts are needed, at minimum, to add a custom extension to a Machine Agent?
A
Explanation:
To add a custom extension to a Machine Agent, you need at least three artifacts: a directory, a jar or
script file, and a monitor.xml file12
. The directory is where you place your extension files under the
<machine_agent_home>/monitors directory. The jar or script file is the executable file that collects
and reports the custom metrics to the Machine Agent. The monitor.xml file is the configuration file
that defines the name, frequency, and parameters of your extension.
You can also optionally include
other files such as libraries, configuration files, or templates for your extension12
. Reference:
Build a
Monitoring Extension Using Scripts
,
Extensions and Custom Metrics
An administrator is asked to improve the capacity of an Events Service cluster. What is the
recommended way to add capacity to the cluster?
B
Explanation:
According to the Cisco AppDynamics Professional Implementer (CAPI) documents, the
recommended way to add capacity to the Events Service cluster is to add nodes running on machines
with identical hardware matching the existing nodes12
. This will increase the data storage,
replication, and redundancy of the cluster, as well as the processing power for queries.
The Events
Service cluster is horizontally scalable, so nodes can be added as your data storage requirements
grow32
.
The Events Service must run on dedicated machines with identical directory structures, user
account profiles, and hardware profiles1
.
For heap space allocation, AppDynamics recommends
allocating half of the available RAM to the Events Service process, with a minimum of 7 GB up to 31
GB1
.
Solid-state drives (SSD) can significantly outperform hard disk drives (HDD), and are therefore
recommended for production deployments1
.
The incorrect options are:
Add a new Events Service cluster to share the load. (A) This is not recommended because it will
create additional complexity and overhead for managing multiple clusters and routing data and
queries to the appropriate cluster. It will also require more license units to enable analytics on
multiple clusters.
Add more storage to the master nodes of the cluster. © This is not recommended because it will not
increase the data replication and redundancy of the cluster, nor the processing power for queries. It
will also create an imbalance in the cluster, as the master nodes will have more storage than the
worker nodes, which may affect the performance and stability of the cluster.
Add more storage to as many of the existing nodes as possible. (D) This is not recommended because
it will not increase the data replication and redundancy of the cluster, nor the processing power for
queries. It will also create an imbalance in the cluster, as some nodes will have more storage than
others, which may affect the performance and stability of the cluster.
Reference:
: Cisco AppDynamics Professional Implementer (500-430)
: Events Service Requirements - AppDynamics
: Events Service Deployment - AppDynamics
: Events Service Deployment - AppDynamics
Which type of Alert and Respond action is available only on an on-premises Controller?
D
Explanation:
A custom action is a type of Alert and Respond action that allows you to integrate AppDynamics
notifications with your own alerting or ticketing system. You can create a custom action by writing an
executable script and an XML file that describe how to pass information from AppDynamics to your
system. A custom action can be triggered by a policy based on a health rule violation or an event. A
custom action is available only on an on-premises Controller, because it requires access to the
Controller file system and the ability to execute scripts on the Controller host machine.
For a SaaS
Controller, you can use HTTP request templates instead of custom actions to integrate with external
systems
. Reference:
Build a Custom Action
,
Alert and Respond
,
Actions
,
Custom Actions
Which implementation mode should be used when deploying an EUM Server with reverse proxy
from a security and performance standpoint in a production environment?
D
Explanation:
The EUM Server is the on-premises version of the EUM Cloud that receives, processes, and stores
data from EUM agents. For production installation, AppDynamics recommends that the EUM Server
and the Controller sit on different hosts, and the EUM Server hosts its own MySQL instance. This
improves the scalability and performance of both components. Moreover, AppDynamics strongly
recommends that SSL traffic from agents to the EUM Server is terminated at a reverse proxy that sits
in front of the EUM Server in the network path, and forwards connections to the EUM Server using
HTTP. This relieves the SSL processing load from the EUM Server, simplifies the certificate
management, and enhances the security by isolating the EUM Server from the external Internet.
Therefore, the best implementation mode for deploying an EUM Server with reverse proxy in a
production environment is option D. Reference:
EUM Server Deployment
,
Install a Production EUM
Server
,
Reverse Proxy configuration for EUM
, and
Browser EUM installation
in the AppDynamics
documentation and community.
Default configuration of the Mobile SDK enables____and_____ . (Choose the two correct options to
complete the sentence.)
AC
Explanation:
The default configuration of the Mobile SDK enables crash reports and network requests12
.
Crash
reports capture and report any unhandled exceptions or signals that cause the app to terminate
abnormally1
.
Network requests monitor the performance and errors of HTTP and HTTPS requests
made by the app2
.
These features are enabled by default and do not require any additional code or
configuration to work12
. Reference:
Crash Reports
,
Network Requests
What are two valid reasons for using the REST API to retrieve health rule violations? (Choose two.)
BC
Explanation:
According to the Cisco AppDynamics Professional Implementer (CAPI) documents, the REST API for
health rule violations allows you to retrieve information about the health rule violations that
occurred in a specified time range for a given application1
. You can use the REST API for health rule
violations for the following valid reasons:
For determining which actions have been executed (B): The REST API response includes the details of
the actions that were triggered by the health rule violation, such as email, SMS, HTTP request, or
custom action1
. You can use this information to verify if the actions were executed successfully, or to
troubleshoot any issues with the action execution.
When searching for historical events ©: The REST API allows you to specify a custom time range for
retrieving the health rule violations, such as BEFORE_TIME, AFTER_TIME, BETWEEN_TIMES, or
BEFORE_NOW1
. You can use this feature to search for historical events that occurred in the past, or
to analyze the trends and patterns of the health rule violations over time.
The incorrect options are:
For updating an AppDynamics dashboard (A): This is not a valid reason for using the REST API for
health rule violations, because the AppDynamics dashboards already display the health rule
violations that occurred in the selected time frame, along with the severity, status, affected entities,
and actions2
. You do not need to use the REST API to update the dashboard, as the dashboard is
automatically refreshed with the latest data from the Controller.
For sending emails (D): This is not a valid reason for using the REST API for health rule violations,
because the REST API does not send emails directly. The REST API only returns the information about
the health rule violations, and the actions that were triggered by them.
If you want to send emails
based on the health rule violations, you need to configure an email action in the health rule
configuration, or use a custom action that invokes an external email service3
.
When pushing events to the Event Management System is NOT possible (E): This is not a valid reason
for using the REST API for health rule violations, because the REST API does not push events to the
Event Management System. The REST API only returns the information about the health rule
violations, and the actions that were triggered by them.
If you want to push events to the Event
Management System, you need to configure an HTTP request action in the health rule configuration,
or use a custom action that invokes an external API3
.
Reference:
: Health Rule Violations API - AppDynamics
: Health Rule Violations - AppDynamics
: Actions - AppDynamics
Which AppDynamics Controller port(s) does the EUM Server require access to in a configuration
where the EUM Server and Controller are on separate hosts (split-host configuration)?
D
Explanation:
In a split-host configuration, where the EUM Server and Controller are on separate hosts, the EUM
Server requires access to the Controller primary HTTP(s) port. This is because the EUM Server needs
to communicate with the Controller API server to send data and receive configuration
information.
The default primary HTTP port for the Controller is 8090 and the default primary HTTPS
port is 81811
.
The dedicated EUM HTTP(s) ports are used by the EUM agents to send data to the
EUM Server, not by the EUM Server to access the Controller2
.
The GlassFish administration port is
used to access the Controller Admin Console, not by the EUM Server3
.
The Controller database port
is used by the Controller to connect to the MySQL database, not by the EUM
Server4
. Reference:
Controller Port Settings
,
Configure the Port for the EUM Agent
,
Access the
Administration Console
,
Controller System Requirements
Which two preparatory tasks are required prior to installing an AppDynamics Controller on Linux?
(Choose two.)
DE
Explanation:
Before installing an AppDynamics Controller on Linux, you need to perform some preparatory tasks
to ensure the system meets the requirements and the installation runs smoothly. Two of these tasks
are:
Install libaio on the host machine if it does not already have it installed. This library facilitates
asynchronous I/O operations on the system, which are required by the Controller. You can use the
package manager of your Linux distribution to install libaio, such as yum or apt-get.
For example, on
CentOS, you can run yum install libaio1
.
Verify that you have enough temporary (tmp) space available on the system, at least 1 GB. The
Controller installation uses the tmp space to extract and install the software components.
You can
check the tmp space by running df -h /tmp2
.
If the tmp space is insufficient, you can either free up
some space by deleting unnecessary files, or specify a different temporary directory for the
installation by passing the -Djava.io.tmpdir parameter to the installer3
.
Other preparatory tasks include verifying the user account permissions, configuring the virus
scanners, installing the netstat network utility, and setting the file descriptor
limit2
. Reference:
Prepare Linux for the Controller
,
Install the Controller on Linux
, and [Controller
System Requirements] in the AppDynamics documentation.
The AppDynamics Controller is instrumented by an internal, out-of-the-box, AppDynamics Java
agent. Which account and user name are used to connect to the Controller to view the information
provided by the internal AppDynamics agent?
C
Explanation:
The AppDynamics Controller is instrumented by an internal, out-of-the-box, AppDynamics Java agent
that monitors the performance and health of the Controller itself1
.
To access the information
provided by the internal agent, you need to log in to the Controller UI with the following
credentials2
:
Account = system
Username = root
Password = <root_user_password>
The system account is a special account that is used only for internal monitoring and troubleshooting
purposes.
It is not visible in the normal Controller UI and requires a special URL to access it2
.
The
root user is the default administrator user for the system account and has the same password as the
admin user for the customer1 account3
. Reference:
Controller Self-Monitoring
,
Monitoring a
Controller Using the Internal Monitoring Agent
,
Controller Accounts