A health rule is configured to trigger a violation when CPU usage exceeds 80% for 10 minutes. During a test, CPU usage spiked to 90% for 8 minutes, then dropped to 70% for 2 minutes, then spiked again to 85% for 3 minutes. The health rule did not trigger. What is the most likely reason?

The health rule requires a continuous 10-minute period of CPU usage above 80%, and the interruptions reset the evaluation window.

The health rule's severity was set to warning, and the violation only triggers at critical severity.

The health rule uses a baseline condition instead of a static threshold, so the spike was not significant enough.

The health rule was not enabled for the specific tier where the CPU spike occurred.

What is the effect of deleting a policy in AppDynamics?

The associated actions will no longer be triggered by health rule violations

The health rules will be disabled

The actions will continue to run but without notifications

The associated health rules will be deleted as well

In AppDynamics, what is the purpose of assigning a severity level (warning or critical) to a health rule?

To specify the duration for which the rule must be violated before it triggers

To define the email template used for notifications

To indicate the importance of the violation and control how it is displayed and acted upon

To determine which metrics are evaluated by the rule

When testing a policy in AppDynamics, what should you verify?

That the policy is visible to all users

That the correct actions are triggered when the associated health rule is violated

That the dashboard displays the health status correctly

That the health rule thresholds are set correctly

What is the recommended way to test a health rule in AppDynamics?

Wait for a real violation to occur and observe the result

Delete the health rule and recreate it

Use the 'Test' feature in the health rule editor to simulate metric values

Disable the health rule and enable it again

CiscoAppDynamics Associate Administrator

Domain 2Objective 2

2.2 Manage Health Rules, Policies, and Actions APPDYNAMICS-ASSOCIATE-ADMINISTRATOR Practice Questions (Page 4)

Part of the Dashboards domain, which accounts for 15% of the APPDYNAMICS-ASSOCIATE-ADMINISTRATOR exam. Cisco does not publish an official question count, but from its 90-minute exam (~35–60 total, ~5–9 in this domain), expect 1–2 from this objective — we provide 27 practice questions to prepare you well beyond it. (estimate)

27questions here

6free pages

9concepts

15%of the exam

Questions 16–20

16application · medium
A health rule is configured to trigger a violation when CPU usage exceeds 80% for 10 minutes. During a test, CPU usage spiked to 90% for 8 minutes, then dropped to 70% for 2 minutes, then spiked again to 85% for 3 minutes. The health rule did not trigger. What is the most likely reason?
Select an answer first
17foundation · medium
What is the effect of deleting a policy in AppDynamics?
Select an answer first
18foundation · medium
In AppDynamics, what is the purpose of assigning a severity level (warning or critical) to a health rule?
Select an answer first
19foundation · medium
When testing a policy in AppDynamics, what should you verify?
Select an answer first
20foundation · medium
What is the recommended way to test a health rule in AppDynamics?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to APPDYNAMICS-ASSOCIATE-ADMINISTRATOR

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Cisco. “APPDYNAMICS-ASSOCIATE-ADMINISTRATOR” is a trademark of its owner, used for identification only.