I85PREP
⌘ K
New Relic Performance Engineer study materials
New Relic Performance Engineer study resources

New Relic Performance Engineer practice questions

One question at a time. Build your New Relic Performance Engineer understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Application Performance Monitoring (APM 360)

In New Relic APM, what does the Apdex score measure for an application?

  1. The ratio of database calls to total transaction throughput
  2. The percentage of requests that complete without any error status code
  3. The average CPU utilization of the host running the agent
  4. A normalized satisfaction score based on a configurable target response time threshold Correct answer.

Explanation

Apdex (Application Performance Index) converts response-time measurements into a satisfaction score between 0 and 1 using a target threshold T that you configure. Requests are classified as satisfied, tolerating, or frustrated relative to T. It is a user-satisfaction proxy, not an error rate or resource metric.

Question 2Application Performance Monitoring (APM 360)

Which New Relic APM concept groups the individual timed operations (such as database queries, external HTTP calls, and method invocations) that occur inside a web transaction?

  1. Synthetic monitor
  2. Segments Correct answer.
  3. Metric timeslice
  4. Deployment marker

Explanation

Segments are the timed building blocks of a transaction trace, representing each operation the agent instruments within the transaction. The transaction itself is the top-level segment, and child segments capture downstream calls. Their durations roll up into the transaction breakdown charts.

Question 3Application Performance Monitoring (APM 360)

A web transaction in a Java application is reported as a slow transaction. Which New Relic APM feature shows the detailed call sequence and per-segment timing for one specific slow transaction?

  1. A transaction trace Correct answer.
  2. The APM overview page
  3. The event loop diagram
  4. The service map

Explanation

Transaction traces capture the full call stack and timing breakdown for individual slow transactions, showing which segments consumed the most time. You can inspect traces to find the specific database call or external service responsible for latency. They are distinct from aggregated metric views.

Question 4Application Performance Monitoring (APM 360)

What is the primary purpose of a New Relic APM alert condition based on the Apdex metric?

  1. To trigger a notification when user satisfaction for a selected app drops below a defined threshold Correct answer.
  2. To automatically restart application servers when response time increases
  3. To record every individual error stack trace for later inspection
  4. To generate synthetic traffic that validates endpoint availability

Explanation

Alert conditions evaluate a chosen metric against thresholds and open incidents when breached. An Apdex-based condition fires when the satisfaction score for the selected app falls below the configured value. Alerting notifies responders; it does not remediate infrastructure or collect traces by itself.

Question 5Application Performance Monitoring (APM 360)

In New Relic APM, what does the error rate metric represent?

  1. The percentage of hosts that failed a health check
  2. The count of distinct exception classes thrown by the application
  3. The number of errors divided by the total number of transactions in the selected time window Correct answer.
  4. The average time spent handling failed requests

Explanation

Error rate expresses failed transactions as a proportion of all transactions during the time window, giving a normalized view of reliability. It differs from a raw error count, which is not normalized against traffic volume. Error rate is a common basis for alert conditions.

Question 6Application Performance Monitoring (APM 360)

Which New Relic capability lets you run a scripted browser test from multiple geographic locations on a schedule to validate an application endpoint?

  1. Distributed tracing
  2. Synthetic monitoring Correct answer.
  3. Vulnerability management
  4. Log forwarding

Explanation

Synthetic monitoring runs scripted or ping-style checks from selected locations on a schedule, producing results even when no real users are active. It validates availability and functional behavior of endpoints. It complements real-user data rather than replacing it.

Question 7Application Performance Monitoring (APM 360)

What is a New Relic APM deployment marker used for?

  1. Storing the compiled artifact for rollback
  2. Annotating the chart timeline with a release event so metric changes can be correlated with deployments Correct answer.
  3. Replacing the agent configuration for a new environment
  4. Blocking a release from reaching production until Apdex improves

Explanation

Deployment markers record a release event on the timeline, letting you visually correlate changes in throughput, response time, or error rate with a deploy. They are informational annotations, not deployment gates. This helps teams attribute performance shifts to specific releases.

Question 8Application Performance Monitoring (APM 360)

Which New Relic feature provides a unified view of how requests flow between services and shows upstream and downstream dependencies for an APM application?

  1. The Apdex settings page
  2. The alert policy editor
  3. Distributed tracing with the service map Correct answer.
  4. The browser session replay list

Explanation

Distributed tracing links spans across services into a single trace, and the service map visualizes the resulting dependency graph. Together they reveal which downstream service contributes latency to an upstream request. This is central to diagnosing cross-service performance issues.

Question 9Application Performance Monitoring (APM 360)

An APM application shows high Apdex frustration during a specific hour. Which approach best isolates the cause using New Relic APM data?

  1. Filter the transaction breakdown by that time window and compare segment durations to a baseline period Correct answer.
  2. Delete the application and recreate it to reset metrics
  3. Disable the agent to reduce overhead during peak hours
  4. Increase the Apdex target threshold so the score improves

Explanation

Isolating the time window and comparing segment-level durations against a baseline reveals which downstream call or code path slowed down. This uses the transaction breakdown and trace data to localize latency. Changing thresholds or removing instrumentation hides the symptom rather than diagnosing it.

Question 10Application Performance Monitoring (APM 360)

A team wants alerting when the 95th percentile response time of a critical transaction exceeds 800 ms. Which New Relic configuration element should they define?

  1. A synthetic ping monitor without thresholds
  2. A metric alert condition on the response time percentile for the selected transaction Correct answer.
  3. A dashboard widget showing the average response time
  4. A deployment marker on the release timeline

Explanation

Alert conditions bind a metric, a threshold, and a scope (such as a specific transaction) to incident creation. Using the 95th percentile targets tail latency rather than the mean. Dashboards and markers display data but do not themselves trigger incidents.

Question 11Application Performance Monitoring (APM 360)

In a transaction trace, the top-level transaction segment shows 2,000 ms total, while a child database segment shows 1,400 ms. What is the most reasonable interpretation?

  1. Database time accounts for roughly 70 percent of the transaction duration and is the primary latency contributor Correct answer.
  2. The trace is invalid because child segments cannot exceed 50 percent of parent time
  3. The database is healthy because it completed successfully
  4. The remaining 600 ms must be caused by network failure

Explanation

Child segment duration divided by parent duration gives the share of transaction time attributable to that call. Here 1,400 of 2,000 ms is about 70 percent, making the database call the dominant contributor. This guides optimization toward the database path.

Question 12Application Performance Monitoring (APM 360)

What distinguishes a non-web transaction from a web transaction in New Relic APM?

  1. Non-web transactions represent background work such as queue consumers or scheduled jobs rather than inbound HTTP requests Correct answer.
  2. Non-web transactions always have zero duration
  3. Non-web transactions are only collected from browser agents
  4. Non-web transactions bypass Apdex scoring entirely and never appear in charts

Explanation

Web transactions are triggered by inbound requests such as HTTP calls, while non-web transactions cover background processes like message consumers, cron jobs, and workers. Both are instrumented by the APM agent and appear in charts. The distinction helps separate user-facing latency from asynchronous workloads.

Question 13Application Performance Monitoring (APM 360)

A Node.js application shows a high event loop utilization. What does this most directly indicate about the application?

  1. The host has run out of disk space
  2. The single-threaded event loop is busy processing work and may be delaying request handling Correct answer.
  3. The database connection pool is exhausted
  4. The garbage collector has been disabled

Explanation

Node.js runs JavaScript on a single event loop, so high event loop utilization means the loop is occupied and callbacks may be delayed. This points to CPU-bound or blocking work on the main thread. It is distinct from connection pool or disk conditions.

Question 14Application Performance Monitoring (APM 360)

How does New Relic distributed tracing help when a request crosses several microservices?

  1. It compiles all services into a single deployable unit
  2. It propagates trace context so spans from each service are stitched into one end-to-end trace Correct answer.
  3. It only records the first service in the chain
  4. It removes the need for any application instrumentation

Explanation

Distributed tracing passes a trace identifier and span context between services, allowing the backend to assemble a single trace across boundaries. This exposes which service or span dominates end-to-end latency. It requires instrumentation in each participating service.

Question 15Application Performance Monitoring (APM 360)

A team notices that error rate spikes only for requests hitting a newly added endpoint. Which New Relic APM workflow best confirms the endpoint is responsible?

  1. Review host CPU metrics only
  2. Increase the Apdex threshold for the whole application
  3. Group errors by transaction name and filter to the new endpoint to compare its error rate against others Correct answer.
  4. Disable error collection for the application

Explanation

Error analytics can group and filter by transaction name, letting you compare the new endpoint's failure rate against other transactions. This isolates whether the spike is endpoint-specific. Broad threshold changes or disabling collection would obscure the signal.

Question 16Application Performance Monitoring (APM 360)

What is the effect of setting the Apdex target threshold T to a higher value for an application?

  1. Fewer requests are classified as satisfied, lowering the Apdex score
  2. More requests are classified as satisfied, generally raising the Apdex score Correct answer.
  3. Error rate is recalculated using the new threshold
  4. Throughput is recalculated using the new threshold

Explanation

Apdex classifies a request as satisfied when its response time is at or below T, tolerating up to a multiple of T, and frustrated beyond that. Raising T therefore moves more requests into the satisfied bucket and tends to increase the score. Error rate and throughput are independent metrics.

Question 17Application Performance Monitoring (APM 360)

In New Relic APM, what does the throughput metric report for a web application?

  1. The number of active database connections
  2. The rate of requests handled per unit time, typically requests per minute Correct answer.
  3. The number of bytes transferred per request
  4. The number of deployment markers per week

Explanation

Throughput measures how many requests the application processes over a time interval, commonly expressed as requests per minute. It reflects load and capacity rather than latency or errors. It is useful for correlating traffic changes with performance shifts.

Question 18Application Performance Monitoring (APM 360)

A service map shows an APM application calling an external HTTP dependency that is slow. Which New Relic feature best quantifies how much of the transaction time that external call consumes?

  1. The alert policy notification log
  2. The browser session replay timeline
  3. External service segments within transaction traces and the transaction breakdown Correct answer.
  4. The deployment marker list

Explanation

External calls are captured as segments, and the transaction breakdown aggregates time spent in external services. This quantifies the latency contribution of the downstream dependency. Deployment markers, replays, and notification logs do not provide segment-level timing.

Question 19Application Performance Monitoring (APM 360)

What role does the New Relic APM agent play in collecting application performance data?

  1. It instruments the application runtime and reports metrics, traces, and errors to New Relic Correct answer.
  2. It hosts the application's database
  3. It replaces the application's load balancer
  4. It generates the application's production traffic

Explanation

The APM agent runs inside or alongside the application runtime, hooking into frameworks and libraries to capture transactions, segments, and errors. It then sends that telemetry to the New Relic backend for storage and analysis. It does not provide infrastructure services like databases or load balancing.

Question 20Application Performance Monitoring (APM 360)

A team wants to compare response time before and after a release without manually rebuilding charts. Which New Relic APM feature most directly supports this comparison?

  1. An alert policy with no conditions
  2. A synthetic monitor with a one-hour interval
  3. Deployment markers overlaid on the response time chart Correct answer.
  4. A dashboard with only host memory widgets

Explanation

Deployment markers place release events on the chart timeline so metric behavior before and after the deploy can be compared visually. This supports change correlation without manual chart reconstruction. Other features do not annotate releases on the metric timeline.

Question 21Application Performance Monitoring (APM 360)

In New Relic APM, what is the difference between the average response time and a percentile response time such as the 95th?

  1. The average includes only failed requests, while the 95th percentile includes only successful ones
  2. The 95th percentile is always lower than the average
  3. The average summarizes all requests, while the 95th percentile shows the value below which 95 percent of requests fall Correct answer.
  4. The average is computed only from synthetic checks

Explanation

The average is a central tendency across all requests and can hide slow outliers. A percentile describes the tail, indicating the threshold under which a given share of requests complete. Tail percentiles are often more useful for user-experience alerting.

Question 22Application Performance Monitoring (APM 360)

A new APM user sees the term 'key transaction' in New Relic. What does designating a key transaction accomplish?

  1. It permanently deletes all other transactions from the account
  2. It converts the transaction into a synthetic monitor
  3. It disables error collection for that transaction
  4. It focuses Apdex scoring and alerting on a business-critical transaction rather than the whole application Correct answer.

Explanation

Key transactions let you track and alert on a specific business-critical transaction with its own Apdex score and thresholds. This provides targeted visibility separate from application-wide metrics. It does not remove other data or change monitoring type.

Question 23Application Performance Monitoring (APM 360)

An application's Apdex drops sharply while throughput stays flat and error rate stays near zero. Which explanation is most consistent with these observations?

  1. The agent stopped reporting all metrics
  2. Response times increased, moving requests into the tolerating or frustrated buckets Correct answer.
  3. The application began returning many 500 errors
  4. The application stopped receiving traffic

Explanation

With throughput and error rate stable, the Apdex decline must come from slower response times shifting requests out of the satisfied bucket. Apdex depends on response time relative to T, so latency growth alone can lower it. Traffic loss or errors would change throughput or error rate.

Question 24Application Performance Monitoring (APM 360)

A transaction trace shows a parent segment of 500 ms containing a 400 ms external call and a 300 ms database call. How should this be interpreted?

  1. The trace is corrupt because child durations exceed the parent
  2. The parent duration is the sum of all child durations by definition
  3. The external call and database call ran in parallel and each is independent of the parent
  4. The child segments overlap in time, so their durations cannot simply be summed to explain the parent Correct answer.

Explanation

Segments can nest or overlap when work happens concurrently, so child durations are not additive in a simple way. A child can also be nested inside another child. Interpreting traces requires examining the call hierarchy and timing bars rather than summing numbers.

Question 25Application Performance Monitoring (APM 360)

A team configures an alert condition on Apdex for a key transaction but receives no incidents despite observed slowdowns. Which configuration issue most plausibly explains the missing alerts?

  1. The condition is scoped to a different entity or the threshold is set below the observed values Correct answer.
  2. The deployment markers were created too recently
  3. The application has browser monitoring enabled
  4. The dashboard uses too many widgets

Explanation

Alert conditions only evaluate the entities they are scoped to and only open incidents when the threshold is breached. A mismatch in scope or a threshold that the observed values never cross would suppress incidents. Deployment markers, dashboard layout, and browser monitoring do not prevent APM alert evaluation.

Question 26Application Performance Monitoring (APM 360)

In New Relic APM, what does the Apdex score of 0.85 for an application most directly represent?

  1. The percentage of hosts reporting to the application that have a healthy agent connection
  2. The percentage of requests that completed without any application error being recorded by the agent
  3. The proportion of sampled transactions whose response time falls within the satisfied and tolerating bands, weighted so tolerating requests count half Correct answer.
  4. The ratio of successful deployments to total deployments tracked through deployment markers

Explanation

Apdex is a ratio computed as (satisfied + tolerating/2) / total requests, where the target threshold T separates satisfied from tolerating and 4T separates tolerating from frustrated. A score of 0.85 therefore reflects the weighted satisfaction of request response times, not error counts or infrastructure health.

Question 27Application Performance Monitoring (APM 360)

A Java service's APM summary shows a slow response time, and the team wants to see which specific method invocations consumed the most time inside a single sampled request. Which New Relic APM capability should they open?

  1. The events-to-metrics rule editor, showing how custom metrics are aggregated
  2. The alert policy overview, showing which conditions are currently breaching
  3. The service map, showing the calling relationships between the application and its dependencies
  4. The transaction trace for that request, showing the segment breakdown of where time was spent Correct answer.

Explanation

A transaction trace captures a single sampled transaction and breaks its total duration into segments and nested method calls, so it reveals which functions or calls consumed the most time. The service map and alerting views describe topology and condition state rather than intra-transaction timing.

Question 28Application Performance Monitoring (APM 360)

A team needs to know how often a specific backend API call inside their Python application is invoked and how long it takes, so they wrap that call with a custom instrumentation API. Which New Relic concept does the wrapped call become in the trace?

  1. A segment nested within the transaction, which can be aggregated into a metric for that call Correct answer.
  2. A synthetic monitor that runs on a schedule from polling locations
  3. A separate APM application that reports its own Apdex score and throughput
  4. A deployment marker recorded on the application's timeline

Explanation

Custom instrumentation creates additional segments inside the current transaction, and the agent rolls their timings into metrics such as a call count and average duration for that named segment. These segments appear in transaction traces and can be charted like any other APM metric.

Question 29Application Performance Monitoring (APM 360)

What does the New Relic APM errors page primarily aggregate for an application?

  1. Error occurrences grouped by error class and message, with counts and affected transaction names Correct answer.
  2. The percentage of requests that exceeded the Apdex target threshold
  3. The latency contribution of each downstream service in the service map
  4. Host CPU and memory saturation across the application's reporting servers

Explanation

The errors page groups captured exceptions and error responses by class and message, showing occurrence counts and the transactions in which they appear. This lets engineers prioritize the most frequent or most damaging error types.

Question 30Application Performance Monitoring (APM 360)

An APM application reports 300 requests per minute, and the agent is configured to sample transaction traces at 10 percent. Approximately how many transaction traces should the team expect per minute, assuming sampling behaves as configured?

  1. About 30 Correct answer.
  2. About 300
  3. About 3
  4. About 10

Explanation

Trace sampling applies a fraction to the incoming request rate, so 10 percent of 300 requests per minute yields roughly 30 sampled traces per minute. Sampling reduces trace storage while preserving a representative picture of transaction behavior.

Question 31Application Performance Monitoring (APM 360)

A web transaction shows 1,000 ms of total response time, but the transaction trace reveals that 600 ms was spent waiting on an uninstrumented external call. Which conclusion is best supported?

  1. Apdex will remain high because external calls are excluded from the calculation
  2. The application is blocked waiting on a downstream dependency that may need its own instrumentation or optimization Correct answer.
  3. The application's own code consumed most of the response time and should be profiled first
  4. The agent failed to record the transaction and the trace should be discarded

Explanation

When a large share of a transaction's duration is attributed to an external call, the bottleneck lies outside the application's own code path. The team should instrument or optimize that dependency rather than profiling local methods first.

Question 32Application Performance Monitoring (APM 360)

An application's error rate rises sharply while throughput and average response time stay essentially unchanged. Which investigation path is most appropriate in New Relic APM?

  1. Raise the Apdex target threshold to reduce the number of frustrated requests
  2. Add more hosts to the application to absorb the extra load
  3. Filter the errors page by the affected transaction and time window to identify the dominant error class Correct answer.
  4. Increase the trace sampling rate to capture more transactions

Explanation

Errors can increase independently of latency and throughput, so the fastest route is to isolate which error classes and transactions account for the rise. The errors page supports filtering by transaction name and time range for exactly this triage.

Question 33Application Performance Monitoring (APM 360)

A team wants a chart of the average duration of a specific custom method they instrumented, without writing a separate query each time. Which New Relic APM capability supports this?

  1. Enabling distributed tracing headers on the application
  2. Creating a synthetic monitor that calls the method
  3. Setting the Apdex target threshold to the method's duration
  4. Creating a custom dashboard chart from the metric the custom segment generates Correct answer.

Explanation

Custom segments produce metrics that can be charted directly on dashboards, giving a reusable view of that method's duration. This avoids rebuilding ad hoc queries for the same measurement.

Question 34Application Performance Monitoring (APM 360)

An APM application shows a sharp throughput drop at the same time its host reports 100 percent CPU utilization. Which interpretation is most consistent with the data?

  1. The agent has stopped reporting and the throughput drop is a data collection artifact
  2. The application cannot process requests fast enough because the host is saturated, so requests queue or time out Correct answer.
  3. The application's error rate must be zero because throughput fell
  4. The Apdex score must have improved because fewer requests were completed

Explanation

Saturated CPU limits how quickly the application can handle work, which commonly manifests as reduced completed throughput and increased latency. Correlating the throughput drop with host saturation points to a capacity constraint rather than a reporting gap.

Question 35Application Performance Monitoring (APM 360)

A team wants alerts when the error rate of a specific key transaction exceeds a fixed percentage. Which New Relic alerting building block should they configure?

  1. A synthetic monitor that pings the transaction's endpoint every five minutes
  2. A deployment marker recorded when the next release ships
  3. An alert condition scoped to that key transaction, attached to a policy that defines the notification workflow Correct answer.
  4. A dashboard widget showing the transaction's error rate over time

Explanation

Alert conditions define the signal and threshold, and attaching the condition to a policy determines who is notified and how. Scoping the condition to the key transaction limits the alert to the traffic the team cares about.

Question 36Application Performance Monitoring (APM 360)

A service's Apdex falls from 0.95 to 0.70 after a release, while throughput and error rate are stable. Which explanation best fits this pattern?

  1. The number of reporting hosts dropped, reducing the data available
  2. The application began returning many more error responses to clients
  3. The agent stopped sampling transaction traces entirely
  4. Response times for a subset of requests shifted into the tolerating or frustrated bands Correct answer.

Explanation

With throughput and errors unchanged, the Apdex decline must come from a shift in the response-time distribution, moving more requests out of the satisfied band. This often follows a change that slows a specific code path or dependency.

Question 37Application Performance Monitoring (APM 360)

An engineer needs to compare the response time distribution of two transactions within the same APM application over the past week. Which New Relic APM approach is most direct?

  1. Review the deployment markers recorded during the week
  2. Chart both transactions' response time metrics on a single dashboard with a shared time range Correct answer.
  3. Read the application's error profile for the week
  4. Open the service map and compare the two nodes visually

Explanation

Charting both transactions' response-time metrics on one dashboard with a common time picker aligns the series for direct comparison. This is the standard way to compare distributions across transactions in APM.

Question 38Application Performance Monitoring (APM 360)

A transaction trace shows a parent segment of 800 ms that contains a 500 ms database segment and a 200 ms external HTTP segment. What does the remaining 100 ms most likely represent?

  1. The time the agent spent sampling the transaction
  2. Time spent in the application's own code and framework overhead not attributed to a child segment Correct answer.
  3. The network latency of the external HTTP call only
  4. A second database call that the agent failed to record

Explanation

In a trace, child segment durations nest inside the parent, and the residual time not covered by children corresponds to the application's own execution and framework overhead. This residual is where local code optimization would matter.

Question 39Application Performance Monitoring (APM 360)

A team wants to correlate a latency regression with the exact code release that introduced it, using APM data alone. Which combination of New Relic capabilities best supports this?

  1. The service map combined with host CPU charts
  2. Apdex scoring combined with alert policy summaries
  3. Deployment markers overlaid on response time charts for the affected transaction Correct answer.
  4. Synthetic monitors combined with the errors page

Explanation

Deployment markers annotate the timeline with release events, so overlaying them on response-time charts shows whether latency shifted at the moment of a specific deployment. This directly links a regression to the release that preceded it.

Question 40Application Performance Monitoring (APM 360)

An application reports high throughput and low average response time, yet users complain about intermittent slow requests. Which New Relic APM analysis best explains the discrepancy?

  1. Examine the deployment markers, since releases always cause intermittent slowness
  2. Examine the host memory charts, since averages are unaffected by memory pressure
  3. Examine the higher percentile response time series, since averages can hide a slow tail of requests Correct answer.
  4. Examine the errors page, since slow requests are always recorded as errors

Explanation

Averages are dominated by the bulk of fast requests and can mask a small population of very slow ones, which is exactly what users perceive as intermittent. Percentile metrics such as the 95th or 99th expose that tail behavior.

Question 41Digital Experience Monitoring

In New Relic Browser monitoring, which metric directly measures how long it takes for the DOMContentLoaded event to fire after the initial HTML document begins loading?

  1. Page load time
  2. DOM processing time Correct answer.
  3. Time to first byte
  4. First contentful paint

Explanation

DOM processing time captures the interval from navigation start until the DOMContentLoaded event fires, measuring parsing and synchronous script execution. It excludes network latency before the document arrives, so it is distinct from page load time and TTFB.

Question 42Digital Experience Monitoring

A Performance Engineer wants New Relic Browser to report Core Web Vitals such as Largest Contentful Paint. Which agent capability must be enabled in the browser snippet?

  1. Session replay
  2. Synthetic monitor scripting
  3. Core Web Vitals and PageView timing via the browser agent Correct answer.
  4. Distributed tracing

Explanation

The Browser agent collects web vitals like LCP, CLS, and INP as part of its page view timing instrumentation when the appropriate configuration is active. Session replay and distributed tracing are separate features that do not generate web vitals metrics.

Question 43Digital Experience Monitoring

Which New Relic Browser feature lets you correlate a slow page view with the backend transaction that served it?

  1. Browser distributed tracing Correct answer.
  2. JavaScript error grouping
  3. Session replay
  4. Ajax timing

Explanation

Browser distributed tracing injects trace headers so the browser page load links to the originating APM transaction, enabling end-to-end latency analysis. Ajax timing only covers XHR calls and does not link to the server transaction as a trace.

Question 44Digital Experience Monitoring

A synthetic monitor script must verify that a login flow works from three geographic locations every five minutes. Which New Relic capability is designed for this?

  1. Synthetic monitoring with scripted API and browser monitors Correct answer.
  2. Applied intelligence alerting
  3. Browser Pro+SPA agent
  4. Infrastructure agent

Explanation

Synthetic monitors run scripted checks from selected locations on a schedule, validating availability and performance from outside the data center. They are the correct tool for multi-location scheduled flow verification.

Question 45Digital Experience Monitoring

In New Relic, what does a synthetic monitor's 'location' setting control?

  1. The region of the APM account
  2. The timezone used for chart display
  3. The data center where results are stored
  4. The geographic point of presence from which the check executes Correct answer.

Explanation

The location setting selects the public or private minion point of presence that runs the synthetic check, so results reflect latency from that geography. It does not affect storage location or display timezone.

Question 46Digital Experience Monitoring

Which Browser metric best indicates that users are seeing a blank screen for too long before any content renders?

  1. Interaction to next paint
  2. First contentful paint Correct answer.
  3. Cumulative layout shift
  4. First paint

Explanation

First contentful paint records when the browser first renders text or an image, so a poor FCP value signals a prolonged blank screen. First paint can occur with only a background color and does not guarantee visible content.

Question 47Digital Experience Monitoring

A team wants to capture the actual JavaScript stack trace when an uncaught exception occurs in the browser. Which New Relic Browser feature provides this?

  1. SPA route change tracking
  2. Page view timing
  3. Session trace
  4. JavaScript error tracking with stack traces Correct answer.

Explanation

Browser JavaScript error tracking captures uncaught exceptions with stack traces, source file, and line information to speed diagnosis. Page view timing and session traces describe performance rather than exception detail.

Question 48Digital Experience Monitoring

Which statement about New Relic Browser session replay is accurate?

  1. It replaces the need for JavaScript error tracking
  2. It reconstructs a DOM-based replay of user interactions with configurable privacy masking Correct answer.
  3. It only works for synthetic monitors
  4. It stores raw video recordings of the user's screen

Explanation

Session replay reconstructs the page DOM and user interactions rather than storing video, and supports masking of sensitive content. It complements error tracking and applies to real user sessions, not synthetic checks.

Question 49Digital Experience Monitoring

A synthetic scripted browser monitor intermittently fails with a timeout when waiting for a button to appear. Which change is most appropriate to reduce false failures?

  1. Disable the monitor's location
  2. Add an explicit wait or assertion for the element with a longer timeout Correct answer.
  3. Increase the monitor frequency
  4. Switch the monitor to an API monitor

Explanation

Explicit waits with generous timeouts handle variable render timing and reduce flaky failures caused by elements appearing late. Changing frequency or removing locations does not address the underlying race condition.

Question 50Digital Experience Monitoring

In New Relic Browser, the 'Page load time' metric is composed of which broad phases?

  1. Session duration
  2. Server response only
  3. Network, DOM processing, and page rendering Correct answer.
  4. Ajax calls only

Explanation

Page load time aggregates network time, DOM processing, and rendering phases from navigation start to load event. Isolating these phases helps identify whether latency is network, parsing, or render bound.