Which AppDynamics capability instruments a municipal application process for DEVCOR 3.7?
Select an answer to reveal the explanation.
Short Explanation
AppDynamics instrumentation is an agent riding inside the process—like a inspector on the factory floor, not someone reading yesterday’s log binder from the parking lot.
Full Explanation
AppDynamics instrumentation for DEVCOR 3.7 loads an app-server agent into the application process—Java, .NET, Node, or another supported runtime—so the agent can observe requests inside the municipal application. In-process agents are how AppDynamics discovers business transactions and builds flow visibility; disk log tails and host SNMP alone are not that capability.
Tailing application logs without loading an agent fails because passive log reading is not AppDynamics language-agent instrumentation. Polling host SNMP CPU counters fails by substituting infrastructure metrics for in-process APM. Deploying only a Domain 4 sidecar container with no AppDynamics language agent fails when the question asks for AppDynamics process instrumentation specifically.
Exam caveat: agent type must match the runtime (a Java agent will not instrument a pure Node process); wrong agent choice looks like “AppDynamics is broken” when the process was never instrumented.
Operational check: after agent install and restart of the civic app tier, confirm the process shows in the AppDynamics application/tier inventory and that at least one business transaction begins registering before declaring instrumentation complete.