QUESTION: 9

Which type of Alert and Respond action is available only on an on-premises Controller?

Remediation action
Cloud auto-scaling
Diagnostic action
Custom action

Answer(s): 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

Reveal Solution Next Question

QUESTION: 10

Which implementation mode should be used when deploying an EUM Server with reverse proxy from a security and performance standpoint in a production environment?

Install the EUM Server on the same host as the Controller, behind the reverse proxy.
Install the EUM Server on a separate host from the Controller, in front of the reverse proxy.
Install the EUM Server on the same host as the Controller, in front of the reverse proxy.
Install the EUM Server on a separate host from the Controller, behind the reverse proxy.

Answer(s): 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.

Reveal Solution Next Question

QUESTION: 11

Default configuration of the Mobile SDK enables____and_____ . (Choose the two correct options to complete the sentence.)

Crash Reports
User Data
Network Requests
Custom Timers
Breadcrumbs

Answer(s): A,C

Explanation:

The default configuration of the Mobile SDK enables crash reports and network requests. Crash reports capture and report any unhandled exceptions or signals that cause the app to terminate abnormally. Network requests monitor the performance and errors of HTTP and HTTPS requests made by the app. These features are enabled by default and do not require any additional code or configuration to work.

Reference:

Crash Reports, Network Requests

Reveal Solution Next Question

QUESTION: 12

What are two valid reasons for using the REST API to retrieve health rule violations? (Choose two.)

For updating an AppDynamics dashboard
For determining which actions have been executed
When searching for historical events
For sending emails
When pushing events to the Event Management System is NOT possible

Answer(s): B,C

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 application. 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 action. 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 actions. 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 service.
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:

1: Health Rule Violations API - AppDynamics
2: Health Rule Violations - AppDynamics
3: Actions - AppDynamics

Reveal Solution Next Question

Free 500-430 Exam Braindumps (page: 4)

QUESTION: 9

Explanation:

Reference:

QUESTION: 10

Explanation:

Reference:

QUESTION: 11

Explanation:

Reference:

QUESTION: 12

Explanation:

Reference:

500-430 Discussions & Posts