500-430 Sample Questions & Answers

The 'Application Viewer' role is the most appropriate choice. It grants permissions to view most application data, including flow maps, dashboards, and the metric browser, but explicitly denies access to sensitive data like snapshots and prevents any configuration changes. 'Dashboard Viewer' is too restrictive as it only allows viewing dashboards. 'Read-Only User' is a legacy term, and 'Custom Role' would be the next step if 'Application Viewer' wasn't a sufficient match.

For a Machine Agent to run a custom script extension on a Linux system, the script file itself must have execute permissions. A common oversight is to copy the script to the monitors directory without setting the appropriate permissions (chmod +x script_name.sh). The agent will fail to execute the script, and no metrics will be reported. While ownership and output format are important, the lack of execute permissions is the most frequent and fundamental cause of this specific problem.

When dealing with unsupported protocols or frameworks for transaction correlation, the correct approach is to use custom correlation. This involves defining a custom exit point on the calling application to identify the outbound call and a corresponding custom transaction demarcation (entry point) on the receiving application. The developer must also ensure the AppDynamics correlation header is propagated within the message payload across the proprietary TCP queue. This allows AppDynamics to stitch the two business transactions together.

This plan correctly addresses all key requirements. It establishes an on-premises HA Controller pair across the two data centers, which is necessary for disaster recovery. It correctly identifies the need to import the custom SSL certificate into the Controller's keystore to secure communications. It also specifies the correct agent types for each part of the environment (Java Agent for JBoss, Cluster Agent for OpenShift, DB Agent for Oracle) and points them to a virtual IP, which is best practice for an HA setup.

The reportEvent method is specifically designed for this purpose. It allows developers to send custom-named events (like 'Item Added to Cart') along with a dictionary or map of key-value properties ('Item ID', 'Price'). This data flows into the Events Service and can be queried using ADQL. reportMetric is for numerical metrics, leaveBreadcrumb is for tracking user flow before a crash, and timers are for measuring custom time intervals.

The Controller's server.log file, located in /logs/, is the primary source for troubleshooting core Controller functionality, including agent registration and communication. This log will contain entries related to agent connection attempts, SSL handshake issues, license validation problems, and other errors that could cause agents to disconnect. The Events Service handles analytics data, and the database log would show database-specific issues, not typically agent connectivity problems.

When an alerting extension is triggered, the AppDynamics Controller executes the specified script (e.g., a shell script or batch file) and passes the event details as command-line arguments. The script must be written to parse these arguments to get information like application name, affected entity, health rule name, summary message, etc. This allows the script to be flexible and use the event context to formulate the custom notification.

AppDynamics provides specific helper scripts for certain application servers to simplify instrumentation. For WebSphere, the install-s-appagent-websphere.sh script is designed to automatically modify the necessary server configuration files to add the required -javaagent JVM argument. This is the preferred method over manual configuration in a WebSphere environment.

The AppDynamics Controller database is extremely write-intensive, as it constantly receives and persists metric data from all connected agents. Therefore, the most critical performance characteristic for the disk hosting the MySQL data directory is low-latency, high IOPS (Input/Output Operations Per Second) for random writes. Using high-performance storage like SSDs or a SAN configured for write performance is crucial for Controller stability and scalability.

The three core properties that define an agent's identity in the AppDynamics model are the application name, tier name, and node name. These are configured via the appdynamics.agent.application.name, appdynamics.agent.tier.name, and appdynamics.agent.node.name system properties, respectively. unique.host.id is used for machine agent identification, and sim.enabled is for Serverless Infrastructure Monitoring.