To add a custom extension to a Machine Agent, you need at least three artifacts: a directory, a jar or script file, and a monitor.xml file12. The directory is where you place your extension files under the <machine_agent_home>/monitors directory. The jar or script file is the executable file that collects and reports the custom metrics to the Machine Agent. The monitor.xml file is the configuration file that defines the name, frequency, and parameters of your extension.You can also optionally include other files such as libraries, configuration files, or templates for your extension12.Reference:Build a Monitoring Extension Using Scripts,Extensions and Custom Metrics

The default configuration of the Mobile SDK enablescrash reportsandnetwork requests12.Crash reports capture and report any unhandled exceptions or signals that cause the app to terminate abnormally1.Network requests monitor the performance and errors of HTTP and HTTPS requests made by the app2.These features are enabled by default and do not require any additional code or configuration to work12.Reference:Crash Reports,Network Requests

According to the Cisco AppDynamics Professional Implementer (CAPI) documents, the two reasons for the missing correlated server-side snapshots are:

Server has set the HttpOnly flag on all cookies. (A) This is a valid reason because the HttpOnly flag is a security feature that prevents client-side scripts from accessing the cookies. However, the AppDynamics JavaScript Agent relies on the cookies to correlate the browser snapshots with the server-side snapshots. The JavaScript Agent injects a cookie named _appdyn_browser into the browser requests, which contains the correlation information. If the server sets the HttpOnly flag on all cookies, including the _appdyn_browser cookie, the JavaScript Agent cannot read or modify the cookie, and the correlation fails.To enable the correlation, the server should not set the HttpOnly flag on the _appdyn_browser cookie12.

Server-side application is not instrumented with server agent. (E) This is a valid reason because the server-side snapshots are collected by the AppDynamics app agents that instrument the application servers. The app agents monitor the business transactions that are executed by the server-side application, and capture the execution context, call graphs, errors, and metrics. If the server-side application is not instrumented with the app agent, the server-side snapshots are not available, and the correlation fails.To enable the correlation, the server-side application should be instrumented with the app agent that is compatible with the application server and the Controller34.

The incorrect options are:

Correlated server-side snapshots work only for .NET Applications. (B) This is not a valid reason because the correlated server-side snapshots work for any application server that is instrumented with the AppDynamics app agent, not only for .NET applications. The AppDynamics platform supports various application servers, such as Java, .NET, PHP, Node.js, Python, and C/C++.The app agents collect the server-side snapshots for the business transactions that are executed by the application server, regardless of the programming language or framework34.

Correlated snapshots are visible only if the injection mechanism is Automatic. This is not a valid reason because the correlated snapshots are visible regardless of the injection mechanism. The injection mechanism refers to the way the AppDynamics JavaScript Agent is inserted into the web pages. There are two injection mechanisms: Automatic and Manual. The Automatic injection mechanism uses the app agent to inject the JavaScript Agent into the web pages that are served by the application server. The Manual injection mechanism requires the user to manually insert the JavaScript Agent into the web pages. Both injection mechanisms support the correlation of the browser snapshots and the server-side snapshots, as long as the JavaScript Agent and the app agent are configured correctly .

Correlated snapshots are visible only if browser is Chrome. (D) This is not a valid reason because the correlated snapshots are visible regardless of the browser. The AppDynamics JavaScript Agent supports various browsers, such as Chrome, Firefox, Safari, Edge, and Internet Explorer. The JavaScript Agent collects the browser snapshots for the web pages that are loaded by the browser, and correlates them with the server-side snapshots, regardless of the browser type or version .

Correlated server-side snapshots are visible only if Java version is 1.7+. (F) This is not a valid reason because the correlated server-side snapshots are visible regardless of the Java version. The AppDynamics Java Agent supports various Java versions, such as 1.5, 1.6, 1.7, 1.8, and 11. The Java Agent collects the server-side snapshots for the business transactions that are executed by the Java application server, and correlates them with the browser snapshots, regardless of the Java version or vendor .

1: Browser Snapshots - AppDynamics

2: Troubleshoot Browser RUM - AppDynamics

3: Transaction Snapshots - AppDynamics

4: Supported Environments and Versions - AppDynamics

[5]: Browser Real User Monitoring - AppDynamics

[6]: Set Up and Configure Web EUM - AppDynamics

[7]: Browser Support - AppDynamics

[8]: Java Agent - AppDynamics

[9]: Java Supported Environments - AppDynamics

The AppDynamics REST API for retrieving metrics allows you to get values generated for metrics by specifying the path of the metric and the time frame for the data1.The following statements are true regarding this API12:

Metrics can be retrieved for a fixed time range. You can use the time-range-type parameter to specify a fixed time range such as BEFORE_NOW, AFTER_TIME, or BETWEEN_TIMES. You can also use the duration-in-mins parameter to specify the length of the time range in minutes.

Wildcards can be used in the REST API metric path. You can use the asterisk () character as a wildcard to match any metric name or part of a metric name. For example, you can use the metric path Business Transaction Performance|Business Transactions||*|Average Response Time (ms) to retrieve the average response time for all business transactions in all tiers.Reference:Retrieve Metric Data,Retrieve Metric Hierarchy

According to the Cisco AppDynamics Professional Implementer (CAPI) documents, the two reasons that would require an administrator to install the Events Service cluster manually are:

Security concerns with passwordless SSH (B): This is a valid reason because the automated installation of the Events Service cluster requires passwordless SSH access to the target hosts. Passwordless SSH allows the Enterprise Console to execute commands on the remote hosts without prompting for a password. However, some organizations may have security policies that prohibit passwordless SSH access, as it may pose a risk of unauthorized access or malicious attacks.In such cases, the administrator can install the Events Service cluster manually, by following the steps described in the Manual Installation of the Events Service Cluster document1.

Security requirements to install using a non-root user account : This is a valid reason because the automated installation of the Events Service cluster requires root privileges on the target hosts. Root privileges allow the Enterprise Console to create directories, change permissions, and install packages on the remote hosts. However, some organizations may have security policies that restrict root access, as it may pose a risk of accidental or intentional damage to the system.In such cases, the administrator can install the Events Service cluster manually, by following the steps described in the Manual Installation of the Events Service Cluster document1. The administrator can use a non-root user account that has sudo privileges to perform the manual installation.

The incorrect options are:

Installation on SUSE Linux (A): This is not a valid reason for manual installation, because the automated installation of the Events Service cluster supports SUSE Linux as one of the compatible operating systems.The Enterprise Console can install the Events Service cluster on SUSE Linux hosts using the automated installation process, as long as the hosts meet the prerequisites described in the Events Service Requirements document2.

Installation on Windows (D): This is not a valid reason for manual installation, because the Events Service cluster does not support Windows as an operating system. The Events Service cluster can only run on Linux hosts, as it is based on Apache Cassandra, which is a Linux-based distributed database.The Events Service cluster cannot be installed on Windows hosts, either manually or automatically2.

1: Manual Installation of the Events Service Cluster - AppDynamics

2: Events Service Requirements - AppDynamics