Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Cisco Exam 500-430 Topic 2 Question 16 Discussion

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

What are two reasons that would require an administrator to install the Events Service cluster manually? (Choose two.)

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:

Malcolm
1 months ago
Wait, so we can't just use our trusty 'admin1234' password and call it a day? Darn, there goes my weekend plans.
upvoted 0 times
...
Noel
1 months ago
You know, I heard that the Events Service cluster is so secure, it makes Fort Knox look like a lemonade stand. B and C are definitely the way to go here.
upvoted 0 times
...
Jaime
1 months ago
I'm leaning towards B and C as well. Gotta love those security requirements, am I right? It's like the IT gods are testing our skills.
upvoted 0 times
Merri
6 days ago
C) Security requirements to install using a non-root user account
upvoted 0 times
...
Dominga
9 days ago
B) Security concerns with passwordless SSH
upvoted 0 times
...
Crissy
15 days ago
Definitely, security is always a top priority in IT.
upvoted 0 times
...
Luisa
18 days ago
C) Security requirements to install using a non-root user account
upvoted 0 times
...
Sharee
19 days ago
A) Installation on SUSE Linux
upvoted 0 times
...
Avery
29 days ago
B) Security concerns with passwordless SSH
upvoted 0 times
...
...
Toshia
2 months ago
Hmm, I don't think A and D are correct. SUSE Linux and Windows aren't exactly the most common platforms for this kind of service, are they?
upvoted 0 times
Lonny
1 months ago
C) Security requirements to install using a non-root user account
upvoted 0 times
...
Artie
2 months ago
B) Security concerns with passwordless SSH
upvoted 0 times
...
...
Veronika
2 months ago
I believe installation on Windows could be another reason. Not all systems are compatible with automated installation processes.
upvoted 0 times
...
Flo
2 months ago
I agree with Dorothy. Security requirements to install using a non-root user account could also be a reason for manual installation.
upvoted 0 times
...
Loise
2 months ago
I'm pretty sure the correct answers are B and C. Having to install using a non-root account and security concerns with passwordless SSH seem like valid reasons to install the Events Service cluster manually.
upvoted 0 times
Corinne
1 months ago
It's important to consider security and user account permissions when installing the Events Service cluster.
upvoted 0 times
...
Freeman
1 months ago
Definitely, those are the two main reasons for manual installation.
upvoted 0 times
...
Shannon
2 months ago
I agree, security concerns and non-root user account are important reasons.
upvoted 0 times
...
Shaquana
2 months ago
I think you're right, B and C make sense for manual installation.
upvoted 0 times
...
...
Dorothy
2 months ago
I think the administrator might need to install manually if there are security concerns with passwordless SSH.
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