I85PREP
⌘ K
New Relic Verified Foundation study materials
New Relic Verified Foundation study resources

New Relic Verified Foundation practice questions

One question at a time. Build your New Relic Verified Foundation 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

In New Relic APM, what does a single transaction represent?

  1. A complete unit of work handled by the application, such as one web request or one background job Correct answer.
  2. A configuration snapshot of the alert policy applied to the entity
  3. A single log line emitted by the application during startup
  4. A scheduled agent update cycle that refreshes entity metadata

Explanation

New Relic APM organizes telemetry around transactions, where each transaction is one complete unit of work such as an inbound HTTP request or a background task. Response time, throughput, and error rate are all aggregated per transaction type.

Question 2Application Performance Monitoring

A team wants to see how much time a request spent in the database versus an external HTTP call. Which APM capability provides this breakdown?

  1. The entity's alert policy incident timeline
  2. The account's audit log of user logins
  3. Distributed tracing spans grouped into segments within the transaction trace Correct answer.
  4. The synthetic monitor's script step results

Explanation

Transaction traces capture the timing of instrumented calls inside a transaction, and distributed tracing exposes each call as a span so time can be attributed to database queries, external services, or application code. This breakdown is what identifies the slowest segment.

Question 3Application Performance Monitoring

What is the primary purpose of Apdex in New Relic APM?

  1. To measure CPU utilization of the host running the agent
  2. To count the total number of errors thrown by the application
  3. To summarize user satisfaction with response time using a single threshold-based score Correct answer.
  4. To rank entities by their monthly data ingestion volume

Explanation

Apdex converts response times into a satisfaction score between 0 and 1 by comparing each transaction against a configured tolerable threshold T. It gives a compact view of how response time affects perceived user experience.

Question 4Application Performance Monitoring

A web transaction shows a high error rate but normal response time. Where should an engineer look first in APM?

  1. The Errors page filtered to that transaction, including stack traces and error classes Correct answer.
  2. The synthetic monitor's device emulation settings
  3. The host's disk I/O utilization
  4. The throughput chart for the previous month

Explanation

When errors rise while latency stays flat, the error details govern the investigation: error class, message, stack trace, and attributes show what is failing. Throughput, host disk, and synthetic device settings do not explain an application-level error rate.

Question 5Application Performance Monitoring

Which statement describes how the New Relic APM agent reports data for a background job transaction?

  1. Background jobs appear only as log lines and never as transactions
  2. Background jobs are only visible if a synthetic monitor invokes them
  3. The agent instruments the job entry point and reports it as a non-web transaction with its own metrics Correct answer.
  4. Background jobs are reported as web transactions with a synthetic URL

Explanation

APM agents distinguish web transactions from non-web (background) transactions, and background jobs are instrumented at their entry point to report duration, throughput, and errors. They do not require a synthetic monitor to appear.

Question 6Application Performance Monitoring

What does the throughput metric in New Relic APM measure?

  1. Average memory allocated per transaction
  2. Requests or transactions completed per unit of time, typically requests per minute Correct answer.
  3. The number of unique users who logged in during a session
  4. The percentage of requests that returned a 5xx status

Explanation

Throughput expresses the rate at which transactions are handled, commonly reported as requests per minute (rpm). It is distinct from latency, error rate, and user counts, which are separate metrics.

Question 7Application Performance Monitoring

An engineer needs to compare response time across all transactions of a service and identify the slowest ones. Which APM view is designed for this?

  1. The alert policy's notification channel list
  2. The synthetic monitor's private location configuration
  3. The transactions table on the APM summary page, sortable by response time Correct answer.
  4. The account settings page for user roles

Explanation

The APM summary page lists transactions with sortable columns for response time, throughput, and error rate, making it straightforward to rank the slowest transaction types. Alert channels, user roles, and private locations are configuration surfaces, not performance comparisons.

Question 8Application Performance Monitoring

Which metric best indicates that users are experiencing slow page loads caused by server-side processing?

  1. Apdex of a synthetic monitor only
  2. Host network receive bytes
  3. Server-side response time for web transactions Correct answer.
  4. Number of deployed application instances

Explanation

Server-side response time measures how long the application took to process the request before responding, which directly reflects backend processing delay perceived by users. Host network bytes and instance counts are infrastructure signals, and synthetic-only Apdex is a narrow external view.

Question 9Application Performance Monitoring

A transaction trace shows most of the duration inside a single external service call. What does this most likely indicate?

  1. The application's garbage collection is pausing all threads
  2. The APM agent is misconfigured and should be reinstalled
  3. The downstream dependency is the latency bottleneck and should be investigated or optimized Correct answer.
  4. The database connection pool is exhausted

Explanation

When a trace attributes the majority of time to one external segment, that dependency is the dominant contributor to latency. The next step is to examine that service's own performance, timeouts, or network path rather than assuming an agent fault.

Question 10Application Performance Monitoring

What is the role of a distributed trace in New Relic APM?

  1. It links spans across services so a request's path through a distributed system can be followed end to end Correct answer.
  2. It stores the full source code of each instrumented service
  3. It replaces the need for any alert policies
  4. It automatically rewrites slow database queries

Explanation

Distributed tracing propagates context between services so spans from different entities are stitched into one trace, revealing cross-service latency and errors. It is an observability mechanism, not a code store or automated optimizer.

Question 11Application Performance Monitoring

An application's Apdex drops from 0.95 to 0.70 after a deployment, while throughput is unchanged. What is the most reasonable interpretation?

  1. Error rate has fallen to zero
  2. The application is receiving far more requests than before
  3. Response times have shifted beyond the tolerable threshold for many users without a change in traffic volume Correct answer.
  4. The agent has stopped reporting data entirely

Explanation

Apdex reflects the distribution of response times relative to the threshold T, so a sharp drop with stable throughput points to slower responses rather than traffic growth. A stopped agent would remove data, and error rate is a separate signal.

Question 12Application Performance Monitoring

How should an engineer configure the Apdex T value for a transaction?

  1. Set it to the response time threshold at which users begin to perceive the interaction as slow Correct answer.
  2. Set it to the maximum observed response time in the last 24 hours
  3. Set it to the number of transactions per minute
  4. Set it to the percentage of errors allowed before alerting

Explanation

The T value is the target response time that defines satisfaction: responses at or below T are satisfied, and multiples of T define tolerating versus frustrating. It should reflect user expectations for that transaction, not observed maxima or traffic rates.

Question 13Application Performance Monitoring

A key transaction has been flagged in APM. What effect does this designation have?

  1. It moves the transaction to a different New Relic account
  2. It disables error reporting for that transaction
  3. It converts the transaction into a synthetic monitor
  4. It raises the trace and metric detail retained for that transaction so it is easier to monitor closely Correct answer.

Explanation

Marking a transaction as a key transaction increases the sampling and retention of traces for it, giving deeper visibility into an important business flow. It does not change error collection, create monitors, or relocate data.

Question 14Application Performance Monitoring

What information does the New Relic APM Errors page provide for a specific error?

  1. The list of synthetic monitor locations
  2. The host's kernel version and uptime
  3. The billing tier of the account
  4. Error class, message, stack trace, and the transaction where it occurred Correct answer.

Explanation

Error analytics surfaces the error class, message, stack trace, and associated transaction attributes, which together support root-cause analysis. Host kernel details, billing tier, and monitor locations are unrelated to a specific application error.

Question 15Application Performance Monitoring

An engineer wants to correlate slow transactions with a specific customer tier attribute. What should be done?

  1. Add the customer tier as a custom attribute on transactions and filter or facet by it in queries Correct answer.
  2. Increase the Apdex T value for all transactions
  3. Convert all transactions to background jobs
  4. Disable distributed tracing to reduce overhead

Explanation

Custom attributes attach business context to transactions so queries can filter, facet, and compare behavior by that dimension. Changing thresholds, disabling tracing, or reclassifying transactions does not provide the needed correlation.

Question 16Application Performance Monitoring

What is the relationship between an APM entity and the services it calls in New Relic?

  1. All services collapse into a single entity regardless of deployment
  2. Only the first service in a call chain is an entity
  3. Each instrumented service is its own entity, and distributed traces connect calls between entities Correct answer.
  4. Entities exist only for synthetic monitors

Explanation

New Relic models each monitored application or service as an entity, and distributed traces link spans across entities to show dependencies. Services are not merged into one entity, and synthetic monitors are a different entity type.

Question 17Application Performance Monitoring

A team sees high throughput and low response time but a rising error rate on a checkout transaction. Which combination of signals should drive the alert condition?

  1. Apdex alone, because it already incorporates errors
  2. Throughput alone, because more requests always mean more risk
  3. Error rate for the checkout transaction, since latency and volume are healthy Correct answer.
  4. Host memory alone, because errors are caused by memory

Explanation

The symptom is elevated errors while latency and volume are normal, so an alert condition on the transaction's error rate targets the actual problem. Throughput and Apdex do not capture error percentage directly, and host memory is not implicated by the evidence.

Question 18Application Performance Monitoring

What does the response time chart's breakdown into web and non-web transactions help an engineer determine?

  1. Which synthetic monitor location is fastest
  2. Whether latency originates in user-facing requests or in background processing Correct answer.
  3. The account's data retention policy
  4. The exact source code line responsible for every slow request

Explanation

Separating web and non-web transactions shows whether slowness affects interactive requests or asynchronous jobs, guiding where to investigate. It does not pinpoint source lines, describe retention, or rank synthetic locations.

Question 19Application Performance Monitoring

How does New Relic APM handle a transaction that exceeds the trace threshold?

  1. It is automatically deleted from all metrics
  2. It is more likely to be captured as a transaction trace for detailed inspection Correct answer.
  3. It is reclassified as a synthetic monitor
  4. It stops being reported until the next agent restart

Explanation

Slow transactions crossing the configured threshold are prioritized for trace capture so engineers can inspect segment-level timing. They are not deleted, reclassified, or suppressed from reporting.

Question 20Application Performance Monitoring

An engineer must determine why a specific user's request was slow, using only a single trace. Which trace element is most useful?

  1. The account's user role assignments
  2. Span durations and their parent-child relationships, showing where time accumulated Correct answer.
  3. The entity's alert policy severity levels
  4. The synthetic monitor's schedule frequency

Explanation

Span durations with parent-child structure reveal which operation consumed the most time and how nested calls contributed. Alert severity, user roles, and monitor schedules do not explain an individual request's timing.

Question 21Application Performance Monitoring

A service reports stable Apdex but its p99 response time has doubled. What is the best explanation?

  1. A small fraction of requests became much slower, which barely moves the threshold-based Apdex score Correct answer.
  2. Apdex and response time always move together in lockstep
  3. The agent has stopped collecting trace data
  4. Throughput must have fallen to zero

Explanation

Apdex is driven by the proportion of requests within threshold bands, so a tail-latency regression affecting few requests can leave the score nearly unchanged while p99 doubles. This is why percentile metrics complement Apdex.

Question 22Application Performance Monitoring

Two services show increased latency simultaneously, and traces reveal the upstream service waiting on the downstream one. How should the investigation proceed?

  1. Investigate the upstream service's CPU first, since it reported the symptom
  2. Assume both services are independently faulty
  3. Focus on the downstream service's own spans and dependencies, since upstream latency is inherited Correct answer.
  4. Ignore the trace and rely on Apdex alone

Explanation

When a trace shows the upstream span blocked on a downstream call, the upstream latency is inherited, so root cause lies in the downstream service or its dependencies. Investigating the upstream first would chase a symptom rather than the source.

Question 23Application Performance Monitoring

An engineer needs to distinguish time spent in application code from time spent waiting on I/O within one transaction. Which trace detail supports this?

  1. The entity's tags and ownership metadata
  2. The alert policy's incident count
  3. The account's data ingestion quota
  4. Segment or span categories such as database, external, and application code, with their durations Correct answer.

Explanation

Trace segments and spans are categorized by type, so durations can be attributed to databases, external calls, or application code. Ingestion quotas, entity tags, and incident counts do not separate code time from I/O time.

Question 24Application Performance Monitoring

A background job's throughput is steady but its average duration is climbing, and traces show growing time in a database segment. Which conclusion is best supported?

  1. The APM agent is sampling too few traces to be reliable
  2. The job is receiving fewer executions per minute
  3. Database query performance is degrading and is the primary contributor to the job's rising duration Correct answer.
  4. The application code outside the database is the bottleneck

Explanation

Steady throughput with rising duration and traces dominated by database segment time points to query performance as the main contributor. Throughput is explicitly steady, and the trace evidence contradicts an application-code bottleneck.

Question 25Application Performance Monitoring

An engineer wants alerts to fire only when a transaction's error rate is high and its throughput is meaningful, avoiding noise from low-traffic periods. What approach fits New Relic APM alerting?

  1. Rely solely on synthetic monitors for error detection
  2. Use only an Apdex condition with the default threshold
  3. Combine an error-rate condition with a throughput or baseline condition so low-traffic periods do not trigger Correct answer.
  4. Disable the alert policy during business hours

Explanation

Combining conditions such as error rate with a throughput threshold or baseline prevents low-volume noise from generating incidents. Apdex alone does not capture error rate, disabling policies removes coverage, and synthetic monitors do not replace production error detection.

Question 26Application Performance Monitoring

In New Relic APM, what does the Apdex score represent?

  1. A normalized satisfaction score based on response time thresholds Correct answer.
  2. The average response time of all transactions in milliseconds
  3. The percentage of requests that completed without an error
  4. The ratio of throughput to error rate for a service

Explanation

Apdex is a user satisfaction metric derived from response times relative to a target threshold T. It classifies requests as satisfied, tolerating, or frustrated, then computes a score between 0 and 1. It does not measure errors directly, nor is it an average response time or a throughput ratio.

Question 27Application Performance Monitoring

An engineer notices that a web transaction's response time has increased significantly, and the transaction trace shows a large portion of time spent in a single external service call. What is the most appropriate next step to diagnose the issue?

  1. Disable the external call to see if response time improves
  2. Add more instances to the application to handle the load
  3. Increase the Apdex T threshold to reduce alert noise
  4. Review the external service's own APM data or distributed trace for latency Correct answer.

Explanation

When a transaction trace points to an external service call as the dominant time consumer, the next step is to investigate that external service's performance. New Relic can correlate the call with the downstream service's APM data or a distributed trace. Adjusting Apdex or scaling the application does not address the root cause.

Question 28Application Performance Monitoring

A service's Apdex score remains stable at 0.92, but its p99 response time has increased from 800 ms to 1600 ms over the same period. What is the best explanation for this observation?

  1. The Apdex T threshold is set too high, causing the score to ignore slow requests
  2. Apdex is calculated only from error-free transactions, so errors are masking the latency increase
  3. The p99 metric is calculated from a different time window than Apdex, making them incomparable
  4. Apdex is dominated by the majority of fast requests, while p99 reflects the slowest 1% of requests Correct answer.

Explanation

Apdex aggregates satisfaction across all requests, so a large volume of fast requests can keep the score high even when a small fraction of requests become much slower. The p99 specifically measures the tail latency experienced by the slowest 1% of requests. Therefore, a stable Apdex can coexist with a rising p99 if only tail latency degrades.

Question 29Application Performance Monitoring

An engineer wants to identify which database query is contributing most to the duration of a specific slow transaction. Which New Relic APM feature should they use?

  1. The error rate chart for the application
  2. The Apdex score for the transaction
  3. The throughput chart for the application
  4. The transaction trace's segment breakdown Correct answer.

Explanation

A transaction trace captures the detailed timing of segments within a single transaction, including database calls. By examining the segment breakdown, the engineer can see which query consumed the most time. Apdex, throughput, and error rate are aggregate metrics and do not provide per-query timing.

Question 30Digital Experience Monitoring

In New Relic Browser monitoring, what does the page load timing breakdown primarily help you understand?

  1. Which infrastructure hosts consume the most network bandwidth
  2. How much time users spend in each phase from network request to DOM processing and rendering Correct answer.
  3. How often synthetic monitors fail across multiple global locations
  4. Which server-side database queries are slowest during an application transaction

Explanation

Browser page load timing splits the load into phases such as network, backend, DOM processing, and page rendering so you can see where user-perceived latency originates. Server-side query timing and host bandwidth belong to APM and infrastructure data, not the browser timing breakdown.

Question 31Digital Experience Monitoring

A team wants to measure how long it takes for a specific button click to update the visible UI in a single-page application. Which New Relic Browser capability is designed for this?

  1. Synthetic scripted browsers
  2. Infrastructure agents on the web servers
  3. APM transaction traces
  4. Custom events recorded with the Browser API Correct answer.

Explanation

The Browser API lets you record custom events and interactions, so you can time a user action and its resulting UI update and then query that data. Synthetic browsers simulate traffic rather than measure real user interactions, and APM traces cover server-side work.

Question 32Digital Experience Monitoring

What is the primary purpose of New Relic Synthetic monitoring?

  1. To trace distributed requests across microservices
  2. To proactively test availability and performance of URLs and scripted flows from chosen locations Correct answer.
  3. To capture JavaScript errors thrown by real users in production browsers
  4. To aggregate log lines from application hosts

Explanation

Synthetic monitoring runs scripted checks, such as ping, simple browser, and scripted browser, from selected locations to detect availability and performance problems proactively. JavaScript error capture for real users is Browser monitoring, and distributed tracing is APM.

Question 33Digital Experience Monitoring

Which New Relic Browser metric best indicates the proportion of page views that loaded within an acceptable time threshold?

  1. Ajax request throughput
  2. JavaScript error rate
  3. Page views with satisfactory load time Correct answer.
  4. Session trace count

Explanation

Browser monitoring classifies page views by whether their load time met a threshold, giving a satisfactory-versus-unsatisfactory view of user experience. Error rate, Ajax throughput, and session trace counts measure different things.

Question 34Digital Experience Monitoring

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

  1. The time zone used to display dashboards
  2. The alert policy that evaluates the monitor
  3. The retention period for monitor results
  4. The geographic data center from which the check is executed Correct answer.

Explanation

Locations determine which New Relic data centers run the synthetic check, letting you observe performance from different regions. Time zone, retention, and alert policy are separate configuration concerns.

Question 35Digital Experience Monitoring

Which New Relic feature lets you view a detailed, step-by-step replay of an individual real user's browser session?

  1. Session replay Correct answer.
  2. Synthetic scripted browser
  3. Distributed tracing
  4. Service map

Explanation

Session replay records and plays back individual browser sessions so you can inspect what a real user experienced, including interactions and errors. Synthetic browsers are simulated, and distributed tracing and service maps describe backend service relationships.

Question 36Digital Experience Monitoring

What does the New Relic Browser 'Ajax' section primarily report?

  1. The DNS resolution time of the initial document
  2. The CPU usage of the user's device
  3. Timing and outcomes of asynchronous requests made by the page Correct answer.
  4. The number of DOM nodes rendered on the page

Explanation

The Ajax section captures asynchronous requests initiated by browser code, including their duration and success or failure. DOM node counts, device CPU, and initial DNS timing are not what the Ajax section reports.

Question 37Digital Experience Monitoring

Which statement describes how New Relic applies alert conditions to synthetic monitors?

  1. Alert conditions only apply to Browser page load metrics
  2. Alert conditions require a separate APM agent on the target server
  3. Synthetic monitors automatically create incidents without any alert policy
  4. Alert conditions evaluate monitor results and open incidents when thresholds are breached Correct answer.

Explanation

Synthetic monitor results feed alert conditions within alert policies, which trigger incidents when thresholds such as failures or response time are exceeded. Monitors do not create incidents on their own, and no APM agent is required on the monitored endpoint.

Question 38Digital Experience Monitoring

A simple browser monitor reports failures only from one location while all other locations succeed. What is the most useful first interpretation?

  1. The monitor has no alert policy attached
  2. The target application is completely down for all users
  3. A location-specific network or routing issue may be affecting that data center Correct answer.
  4. Browser monitoring agents are not installed on the target

Explanation

When a single location fails while others succeed, the target is reachable globally, so a location-specific network or routing problem is a likely cause. A full outage would fail across locations, and synthetic checks do not depend on Browser agents.

Question 39Digital Experience Monitoring

Which New Relic Browser setting determines whether data is collected for a percentage of page loads rather than every one?

  1. The alert policy threshold
  2. The synthetic monitor interval
  3. The APM transaction threshold
  4. The sampling or capture rate configured for the browser agent Correct answer.

Explanation

Browser agents can be configured to capture data for a portion of page loads, which controls data volume and cost. Alert thresholds, monitor intervals, and APM transaction thresholds do not set browser data sampling.

Question 40Digital Experience Monitoring

You need to verify that a login flow works end to end, including form entry and a post-login dashboard element. Which synthetic monitor type fits best?

  1. A simple browser monitor
  2. A scripted browser monitor Correct answer.
  3. A ping monitor
  4. A certificate check monitor

Explanation

A scripted browser monitor runs a Selenium-style script that can enter credentials, submit forms, and assert on elements after login. Ping and simple browser monitors cannot perform multi-step interactions, and certificate checks only validate TLS certificates.

Question 41Digital Experience Monitoring

A Browser app shows a high JavaScript error rate concentrated in one browser version. What is the most appropriate next step?

  1. Disable Browser monitoring for all users
  2. Add an infrastructure agent to the user's device
  3. Increase the synthetic monitor frequency
  4. Filter the error data by browser version and inspect the affected error groups Correct answer.

Explanation

Filtering by browser version isolates the affected error groups so you can identify the failing code path and reproduce the issue. Disabling monitoring removes visibility, synthetic frequency does not fix client errors, and infrastructure agents do not run on end-user devices.

Question 42Digital Experience Monitoring

What is the role of the browser agent's 'beacon' or data transmission endpoint?

  1. It routes server-side APM traces between services
  2. It executes synthetic scripts in the cloud
  3. It receives the collected browser data sent from the user's page Correct answer.
  4. It stores the application's source code for debugging

Explanation

The browser agent collects data in the page and transmits it to a New Relic endpoint, often called the beacon, which ingests it. It does not store source code, run synthetic scripts, or route APM traces.

Question 43Digital Experience Monitoring

Which New Relic capability correlates a slow backend API call with the browser interaction that triggered it?

  1. An infrastructure dashboard for CPU
  2. A ping monitor on the API host
  3. Distributed tracing linking the browser Ajax call to the backend transaction Correct answer.
  4. A log parsing rule on the web server

Explanation

Distributed tracing propagates trace context from the browser Ajax request into the backend transaction, letting you follow one request across tiers. Ping monitors, CPU dashboards, and log rules do not directly link a specific browser call to its backend span.

Question 44Digital Experience Monitoring

A synthetic monitor's alert condition uses a response time threshold. What happens when several consecutive checks exceed the threshold?

  1. An incident opens according to the condition's threshold duration settings Correct answer.
  2. The target server is restarted by New Relic
  3. The monitor is automatically deleted
  4. Browser agents are redeployed to the target

Explanation

Alert conditions use threshold durations so that sustained breaches, not single blips, open incidents. New Relic does not delete monitors or perform remediation such as restarting servers or redeploying agents.

Question 45Digital Experience Monitoring

Which metric in New Relic Browser most directly reflects the time until the main content of a page becomes visible to the user?

  1. Ajax error count
  2. JavaScript error rate
  3. Session count
  4. First contentful paint or largest contentful paint timing Correct answer.

Explanation

Paint timing metrics such as first contentful paint and largest contentful paint measure when meaningful content appears on screen. Error counts and session counts describe failures and traffic volume, not visual rendering timing.

Question 46Digital Experience Monitoring

A team wants to track Core Web Vitals for real users. Which New Relic Browser data supports this?

  1. Real user monitoring metrics such as LCP, CLS, and INP captured by the browser agent Correct answer.
  2. Synthetic ping results from a single location
  3. Infrastructure network throughput
  4. APM database call counts

Explanation

The browser agent captures real user performance metrics that map to Core Web Vitals, including loading, layout stability, and responsiveness measures. Synthetic pings, APM database counts, and infrastructure throughput do not measure real-user web vitals.

Question 47Digital Experience Monitoring

What does a New Relic synthetic monitor's 'script' contain in a scripted browser monitor?

  1. An alert policy definition in JSON
  2. A SQL query executed against the application database
  3. A log parsing expression
  4. Steps written with browser automation commands to navigate and assert on the page Correct answer.

Explanation

Scripted browser monitors contain automation steps that navigate pages, interact with elements, and assert expected outcomes. They are not SQL queries, alert policy definitions, or log parsing expressions.

Question 48Digital Experience Monitoring

A dashboard needs to show the percentage of synthetic checks that failed over the last day. Which approach is appropriate?

  1. Use the browser JavaScript error rate
  2. Inspect infrastructure disk usage
  3. Query synthetic monitor result events and compute the failed percentage with NRQL Correct answer.
  4. Read APM error rate from the application

Explanation

Synthetic monitor results are stored as event data that can be queried with NRQL to calculate failure percentages over a time window. APM error rate, browser error rate, and disk usage describe different signals.

Question 49Digital Experience Monitoring

Which consideration is most important when choosing how frequently a synthetic monitor should run?

  1. Balancing detection speed against the data volume and cost the check frequency generates Correct answer.
  2. Running the monitor from a single location to reduce noise
  3. Ensuring the monitor runs only during business hours
  4. Setting the interval equal to the alert threshold duration

Explanation

Check frequency trades off how quickly problems are detected against the volume of results and associated cost. Restricting to business hours or one location reduces coverage, and interval and threshold duration serve different purposes.

Question 50Digital Experience Monitoring

A Browser app reports many 'unsatisfactory' page loads but low server response times in APM. Which explanation is most plausible?

  1. Client-side rendering or third-party resources are adding latency after the server responds Correct answer.
  2. The database is the bottleneck for every request
  3. The APM agent is misconfigured and missing transactions
  4. The synthetic monitors are running too often

Explanation

If server response is fast but users see slow loads, the delay likely occurs in the browser, such as heavy rendering or slow third-party assets. Misconfigured APM would affect server data, a database bottleneck would raise server time, and synthetic frequency does not change real-user load times.