Which condition requires the use of Cisco ThousandEyes transaction tests for monitoring?

Question

Options

• Amonitoring the availability of an HTTP server for an application, using a specific port
• Bmonitoring a thick-client on-premises application making calls to MongoDB database transactions
• Cmonitoring the complete process of M365 users from logging in to the web portal to opening a specific SharePoint page
• Dmonitoring voice and video traffic for a unified communication application

• A
  4% (2)
• B
  15% (7)
• C
  77% (37)
• D
  4% (2)

Explanation

Option C is correct because ThousandEyes transaction tests use a scripted synthetic browser to replay multi-step, sequential user workflows through web applications - exactly what's needed to simulate a user logging into M365, navigating a portal, and arriving at a specific SharePoint page. No other ThousandEyes test type can execute and validate this kind of chained, stateful web interaction.

Why the distractors are wrong:

• A is handled by a standard HTTP Server test, which checks availability, response codes, and response times on a given port - no scripted browser needed.
• B is outside ThousandEyes' scope for this use case; transaction tests are browser-based and cannot directly instrument a thick-client app or monitor MongoDB database calls at the transaction level.
• D is covered by ThousandEyes RTP Stream or Voice tests, which measure MOS scores, jitter, and packet loss for UC traffic - not transaction tests.

Memory tip: Think of "transaction" the way you think of an e-commerce checkout - multiple ordered steps (browse → cart → pay → confirm). Whenever a monitoring scenario describes a sequence of user actions in a web browser, that's your signal to choose a transaction test.

No community discussion yet for this question.