Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Cisco Exam 500-430 Topic 1 Question 5 Discussion

Actual exam question for Cisco's 500-430 exam
Question #: 5
Topic #: 1
[All 500-430 Questions]

A Java-based web application was instrumented. The browser snapshots provide a detailed look at an individual page request, however the correlated server-side snapshots are missing for

all requests. What are two reasons for this missing correlated server-side snapshots? (Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: A, E

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

Contribute your Thoughts:

Deane
6 months ago
Hmm, I'm not so sure. What if the server has set the HttpOnly flag on all cookies? That could also prevent the correlation between the browser and server-side snapshots.
upvoted 0 times
...
Leonora
6 months ago
That's a good point. The question specifically mentions 'correlated server-side snapshots', so the server agent must be the issue here. I'm leaning towards option E as the correct answer.
upvoted 0 times
Willow
5 months ago
I think we can confidently select option E as one of the answers.
upvoted 0 times
...
Cassi
5 months ago
Looks like option E is a strong contender for one of the reasons for missing snapshots.
upvoted 0 times
...
Latrice
5 months ago
Definitely, without the server agent, the correlated snapshots can't be collected.
upvoted 0 times
...
My
5 months ago
So, the missing correlated server-side snapshots could be due to the server agent not being present on the server.
upvoted 0 times
...
Franklyn
5 months ago
That's true, if the server agent is not installed, correlated server-side snapshots won't be captured.
upvoted 0 times
...
Bo
5 months ago
Agreed, option E mentions that the server side application is not instrumented with a server agent.
upvoted 0 times
...
Izetta
5 months ago
I think the server agent not being installed is the issue.
upvoted 0 times
...
...
Katlyn
6 months ago
I agree, this is a bit of a head-scratcher. My initial thought is that the server-side application is not properly instrumented with the server agent, which would explain the missing server-side snapshots.
upvoted 0 times
...
Flo
6 months ago
This is a tricky question. It seems like the key is missing the correlated server-side snapshots, which should be available if the application is properly instrumented.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77