Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Cisco 500-430 Exam - Topic 10 Question 13 Discussion

Which two symptoms occur if an AppDynamics Controller is NOT scaled correctly? (Choose two.)
D) The Controller's metric reporting is 7 to 10 minutes behind the current time. and E) The Controller Ul performs slowly.
A) Snapshots are NOT available after 2 weeks.
B) Health rules violations occur more frequently.
C) The average response times of tiers are higher than normal.

Cisco 500-430 Exam - Topic 10 Question 13 Discussion

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

Which two symptoms occur if an AppDynamics Controller is NOT scaled correctly? (Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: D, E

According to the Cisco AppDynamics Professional Implementer (CAPI) documents, the two symptoms that occur if an AppDynamics Controller is not scaled correctly are:

The Controller's metric reporting is 7 to 10 minutes behind the current time. (D) This is a valid symptom because the AppDynamics Controller collects, processes, and stores metrics from the agents that monitor the applications, tiers, nodes, and other entities. If the Controller is not scaled correctly, it may not have enough resources, such as CPU, memory, disk space, or network bandwidth, to handle the incoming metrics data. This may result in a backlog of metrics data that causes the Controller to lag behind the current time.The Controller's metric reporting delay can affect the accuracy and timeliness of the performance analysis and troubleshooting12.

The Controller UI performs slowly. (E) This is a valid symptom because the AppDynamics Controller UI is a web-based application that allows users to access, visualize, and interact with the performance data and configuration settings of the AppDynamics platform. If the Controller is not scaled correctly, it may not have enough resources, such as CPU, memory, disk space, or network bandwidth, to serve the UI requests.This may result in a slow or unresponsive UI that affects the user experience and productivity12.

The incorrect options are:

Snapshots are not available after 2 weeks. (A) This is not a valid symptom because the AppDynamics Controller does not store snapshots for more than 2 weeks by default. Snapshots are detailed records of the execution context and call graphs of the business transactions that are monitored by the AppDynamics platform. Snapshots are useful for diagnosing performance issues and errors, but they also consume a lot of disk space. The AppDynamics Controller automatically purges the snapshots that are older than 2 weeks, unless the retention policy is changed by the user.The availability of snapshots is not affected by the Controller scaling, unless the disk space is exhausted34.

Health rule violations occur more frequently. (B) This is not a valid symptom because the AppDynamics Controller does not cause health rule violations to occur more frequently. Health rule violations are triggered when the performance or availability metrics of the monitored entities exceed the thresholds that are defined by the user. Health rule violations indicate the presence of performance issues or errors in the monitored applications, tiers, nodes, or other entities, not in the Controller itself.The frequency of health rule violations is not affected by the Controller scaling, unless the Controller fails to collect or process the metrics data5.

The average response times of tiers are higher than normal. This is not a valid symptom because the AppDynamics Controller does not affect the average response times of tiers. The average response time of a tier is the average time that the tier takes to process the incoming requests from the business transactions that are monitored by the AppDynamics platform. The average response time of a tier is influenced by the performance and behavior of the application code, the infrastructure, the dependencies, and the workload of the tier, not by the Controller itself. The average response time of a tier is not affected by the Controller scaling, unless the Controller fails to collect or process the metrics data .


1: Controller System Requirements - AppDynamics

2: Controller Sizing Guidelines - AppDynamics

3: Transaction Snapshots - AppDynamics

4: Configure Data Retention - AppDynamics

5: Health Rules - AppDynamics

by Cletus at Apr 28, 2024, 01:02 AM

Limited Time Offer

25%

Off

Get Premium 500-430 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Mabel
9 months ago
The Controller UI being slow is a big red flag.
upvoted 0 times
...
Alyssa
9 months ago
I thought the metric reporting delay was a myth!
upvoted 0 times
...
Peggie
10 months ago
Wait, are snapshots really gone after 2 weeks?
upvoted 0 times
...
Sage
10 months ago
Definitely, response times go up too!
upvoted 0 times
...
Reta
10 months ago
Health rules violations happen more often.
upvoted 0 times
...
Margurite
10 months ago
I vaguely recall something about metric reporting delays being a problem if the Controller isn't scaled properly. Is that option D?
upvoted 0 times
...
Rodrigo
11 months ago
I practiced a question similar to this, and I think the response times being higher might be a symptom. So, option C could be right.
upvoted 0 times
...
Dorthy
11 months ago
I'm not entirely sure, but I feel like the Controller's performance could be affected too. Could it be option E?
upvoted 0 times
...
Elinore
11 months ago
I think I remember something about health rules violations being a sign of scaling issues. Maybe option B?
upvoted 0 times
...
Laurel
11 months ago
This is a good question. I'll make sure to read through all the options thoroughly before answering.
upvoted 0 times
...
Melvin
11 months ago
I'm feeling pretty confident about this. The key is understanding how an unscaled Controller can impact monitoring and reporting.
upvoted 0 times
...
Thaddeus
11 months ago
Okay, I've got a strategy. I'll focus on the symptoms related to performance and scalability.
upvoted 0 times
...
Arminda
11 months ago
Hmm, I'm not totally sure about this. I'll have to review the AppDynamics documentation again.
upvoted 0 times
...
Cecily
11 months ago
This looks like a tricky one. I'll need to think it through carefully.
upvoted 0 times
...
Cherry
11 months ago
Alright, let me think this through. Containers are designed to support physical and virtual servers, and they also help with virtual machine capacity. I'm leaning towards options 1 and 4, but I'll double-check the details.
upvoted 0 times
...
Paris
11 months ago
Interesting, I hadn't considered using the normalizer_fn in TensorFlow's Feature Column API. That could be a clever way to handle the normalization within the model training process. I'll make sure to explore that option as well.
upvoted 0 times
...
Oneida
11 months ago
I recall something about checking the current traffic loads before starting the upgrade, but I can't remember if we should prioritize certain components over others.
upvoted 0 times
...
Colene
11 months ago
I think we discussed application visibility and host statistics in our last review session, but I'm not fully sure if system capacity is one of them.
upvoted 0 times
...
Salena
2 years ago
True, but I think C and D are the most direct symptoms. Let's go with those.
upvoted 0 times
...
Cherry
2 years ago
E could also be a good option. Slow UI performance usually indicates under-scaling.
upvoted 0 times
...
Willetta
2 years ago
Exactly, if the backend can't keep up, metric reporting would lag.
upvoted 0 times
...
Salena
2 years ago
But D also seems correct. Delayed metric reporting sounds like a scaling problem.
upvoted 0 times
...
Rex
2 years ago
Hmm, C makes sense since higher response times could be due to a scaling issue.
upvoted 0 times
...
Willetta
2 years ago
I think options C and D are likely symptoms if the AppDynamics Controller isn't scaled correctly.
upvoted 0 times
...

Save Cancel