Cyber Monday 2024! 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 4 Question 28 Discussion

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

What are three valid reasons to use the AppDynamics REST API to retrieve metrics? (Choose three.)

Show Suggested Answer Hide Answer
Suggested Answer: A, C, E

The AppDynamics REST API to retrieve metrics allows you to get values generated for metrics by specifying the path of the metric and the time frame for the data1.Some of the valid reasons to use this API are12:

To archive 1-minute granularity data. The AppDynamics Controller stores metric data at different levels of granularity depending on the retention period. For example, it stores 1-minute granularity data for 8 days, 10-minute granularity data for 32 days, and 1-hour granularity data for 365 days. If you want to archive the 1-minute granularity data for longer than 8 days, you can use the API to retrieve and store the data in an external database or file system.

To calculate a new metric based on two existing metrics. The AppDynamics Controller provides some built-in metrics such as average response time, calls per minute, errors per minute, etc. However, you may want to calculate a new metric that is not available in the Controller, such as the ratio of errors to calls, or the percentage of slow transactions. You can use the API to retrieve the values of the existing metrics and perform the calculation using your own logic or formula.

To retrieve health rule violations. Health rules are the rules that define the performance and availability thresholds for your application components. When a health rule is violated, the AppDynamics Controller generates an event and optionally triggers a policy action. You can use the API to retrieve the list of health rule violations for a given application, time range, and severity level. This can help you monitor and troubleshoot the health of your application and take corrective actions if needed.Reference:Retrieve Metric Data,Health Rule API


Contribute your Thoughts:

Alva
1 months ago
Haha, gotta love these API questions. I'm going with C, E, and F - can't go wrong with custom metrics, health rule violations, and internal alerts!
upvoted 0 times
Krissy
1 days ago
Definitely, those are all valid reasons to use the AppDynamics REST API.
upvoted 0 times
...
In
19 days ago
Creating alerts for internal ticketing systems is a must.
upvoted 0 times
...
Queenie
21 days ago
I agree, health rule violations are important to monitor.
upvoted 0 times
...
Margart
1 months ago
Samesies! Custom metrics are always useful.
upvoted 0 times
...
...
Marge
2 months ago
This is a tricky one, but I think D, E, and F are the way to go. The API is great for getting a deeper look at your application's health and performance.
upvoted 0 times
...
Georgiana
2 months ago
I believe option F is important too, creating alerts for internal ticketing system.
upvoted 0 times
...
Isadora
2 months ago
Hmm, I'm not sure about B. Isn't that more of a use case for the standard AppDynamics dashboard? I'd go with A, C, and F.
upvoted 0 times
Felicitas
9 days ago
Yes, evaluating health rules could definitely be another valid reason to use the API.
upvoted 0 times
...
Latricia
14 days ago
But what about evaluating health rules? Wouldn't that be important too?
upvoted 0 times
...
Deeanna
15 days ago
I agree with you, A, C, and F seem like more common reasons to use the API.
upvoted 0 times
...
Elise
1 months ago
I think B could still be valid for creating a custom report.
upvoted 0 times
...
...
Herschel
2 months ago
I agree with you, Loren. Option B also seems useful for creating custom reports.
upvoted 0 times
...
Viki
2 months ago
A, C, and E are definitely the right choices here. Retrieving metrics with the AppDynamics REST API is super useful for all sorts of custom reporting and analysis needs.
upvoted 0 times
Fidelia
1 months ago
User 3: It's great that you can calculate new metrics based on existing ones.
upvoted 0 times
...
Julio
1 months ago
User 2: I agree, using the API for custom reporting is very helpful.
upvoted 0 times
...
Goldie
1 months ago
A, C, and E are definitely the right choices.
upvoted 0 times
...
...
Loren
2 months ago
I think option A is valid because archiving data is important.
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