2.4 Capture Snapshots APPDYNAMICS-ASSOCIATE-ADMINISTRATOR Practice Questions (Page 1)

Questions 1–5

1. 1expert · hard

   A team is diagnosing a memory leak in a Java application. They need to capture snapshots that include heap dumps for a specific transaction, but they are concerned that capturing heap dumps for every snapshot will consume excessive storage and impact performance. The team wants to capture heap dumps only when the transaction is very slow, not for normal executions. What is the best configuration approach?

   • AEnable snapshot capture for all transactions with heap dumps enabled to ensure the issue is captured
   • BManually trigger snapshots with heap dumps whenever the team suspects a memory leak
   • CConfigure snapshot capture with a very slow threshold and enable diagnostic data collection including heap dumps
   • DIncrease the snapshot retention period to keep more snapshots with heap dumps
   Reveal Solution Discussion Select an answer first
2. 2foundation · easy

   In a snapshot's call graph, what does the width of a segment typically represent?

   • AThe number of exceptions thrown by that segment
   • BThe number of child calls made by that segment
   • CThe memory allocated by that segment
   • DThe execution time of that segment
   Reveal Solution Discussion Select an answer first
4. 3foundation · easy

   Which of the following is a type of data captured in an AppDynamics transaction snapshot?

   • AServer CPU utilization
   • BDatabase schema
   • CCall graph
   • DNetwork packet capture
   Reveal Solution Discussion Select an answer first
5. 4expert · hard

   An organization has a compliance requirement to retain snapshots for 90 days, but the current controller storage is limited. The administrator has configured the retention policy to 90 days, but the controller is still running out of space because the volume of snapshots is too high. The administrator needs to reduce storage usage while still meeting the 90-day retention requirement. What is the most effective approach?

   • AReduce the retention period to 30 days to free up space
   • BReduce the snapshot capture frequency and limit data collection scope to essential transactions
   • CManually purge snapshots daily to keep storage usage low
   • DIncrease the snapshot storage limit to accommodate more snapshots
   Reveal Solution Discussion Select an answer first
6. 5application · medium

   An administrator is configuring snapshot capture for a critical payment transaction. The team needs detailed call graph data to diagnose a recurring issue, but the application is sensitive to performance overhead. The administrator wants to capture snapshots only when the transaction is slow, not for every execution. What configuration achieves this?

   • ADisable automatic capture and manually trigger snapshots whenever the team suspects an issue
   • BEnable automatic snapshot capture with a threshold-based trigger for the payment transaction
   • CEnable snapshot capture for all transactions and rely on the call graph to identify slow ones
   • DSet a high snapshot frequency to capture many snapshots and filter later
   Reveal Solution Discussion Select an answer first