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

Question

Options

• ASnapshots are NOT available after 2 weeks.
• BHealth rules violations occur more frequently.
• CThe average response times of tiers are higher than normal.
• DThe Controller's metric reporting is 7 to 10 minutes behind the current time.
• EThe Controller Ul performs slowly.

• A
  7% (2)
• B
  4% (1)
• C
  11% (3)
• D
  79% (22)

Explanation

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 troubleshooting. 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 productivity.

No community discussion yet for this question.