5.5 Create and Maintain Error and Exception Configurations APPDYNAMICS-ASSOCIATE-ADMINISTRATOR Practice Questions (Page 3)

Questions 11–15

1. 11application · medium

   You have created a new error detection rule to mark `DatabaseConnectionException` as an error for the `Inventory` business transaction. Before relying on this rule in production, you want to verify that it correctly captures the error. What is the most efficient way to validate the rule?

   • AReview the rule configuration in the UI to ensure it matches the exception class name.
   • BEnable the rule in production and monitor for the error to appear.
   • CTrigger the exception in a test environment and check the error dashboard for the business transaction.
   • DCompare the rule with a similar rule from another application.
   Reveal Solution Discussion Select an answer first
2. 12foundation · easy

   Which action can an administrator perform to keep error and exception configurations current?

   • AChange the application's logging level to suppress errors.
   • BRename the business transaction to match the rule.
   • CDisable a rule that no longer applies to the application.
   • DIncrease the application server's memory to avoid errors.
   Reveal Solution Discussion Select an answer first
4. 13foundation · easy

   How can an error detection rule be applied to a specific business transaction in AppDynamics?

   • ABy configuring the transaction to inherit all rules globally.
   • BBy setting the rule's scope to that business transaction.
   • CBy creating a separate application for each transaction.
   • DBy adding a comment to the rule mentioning the transaction name.
   Reveal Solution Discussion Select an answer first
5. 14foundation · easy

   What is a common method to test an exception detection rule?

   • AVerify the rule is enabled in the configuration.
   • BInvoke a code path that throws the exception and observe if it is captured as an error event.
   • CCompare the rule with other rules in the same application.
   • DCheck the exception class in the application's source code.
   Reveal Solution Discussion Select an answer first
6. 15foundation · easy

   What is the primary purpose of error and exception configurations in AppDynamics?

   • ATo define the severity levels (INFO, WARN, ERROR) for application log messages.
   • BTo automatically fix application errors and exceptions without requiring code changes.
   • CTo define which application errors and exceptions are captured and displayed as error events in the flow map and transaction snapshots.
   • DTo configure the logging framework used by the application to write error messages.
   Reveal Solution Discussion Select an answer first