Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
60 results for “Real User Monitoring”
Synthetic Monitoring
Continuously executing a real user journey against production from outside it, so a broken journey is detected before a user reports it.
Field Data Versus Lab Data
The difference between what real users on real devices experience and what a synthetic run measures, and why the second is systematically optimistic.
Alert Fatigue
The desensitisation that follows from alerts that are frequent, non-actionable, or not tied to user impact — after which real alerts are missed too.
Application Performance Monitoring
Instrumentation inside the application that attributes latency and errors to specific code paths, queries and dependencies.
Platform User Research
Treating engineers as users whose actual behaviour is observed rather than assumed, which is what separates a platform from a set of shared tools.
APM Transaction Tracing
Instrumentation that attributes application latency and errors to specific code paths, database queries and external calls, usually with automatic tracing.
Backup Strategy
A plan for what is copied, how often, where to, how long it is kept, and — the part that decides whether it is real — how the restore is verified.
Burn Rate Alerting
Paging when the error budget is being consumed fast enough to matter, rather than when a component crosses a threshold.
Cardinality
The number of distinct time series produced by a metric, which is the product of the distinct values of all its labels — and the main driver of monitoring cost.
Clock Drift
Device clocks diverging from real time, which corrupts ordering, expires certificates early or late, and produces data that appears to arrive from the past.
Cognitive Load
The total amount a team must hold in its head to work effectively, and a real constraint on how many services or domains one team can own.
Content Delivery Network
A geographically distributed cache that serves content from a location near the user instead of from the origin.
Control Test Automation
Executing a control's test continuously against the whole population rather than sampling it annually, which changes both the detection latency and the strength of the evidence.
Edge Function
Code executed at a CDN point of presence close to the user, in a constrained, fast-starting runtime, typically to modify or route a request before it reaches an origin.
Fan-Out Latency Amplification
The effect by which a request that depends on many parallel sub-requests is governed by the slowest of them, so rare slowness becomes common at the user level.
Game Day
A scheduled exercise in which a failure is deliberately introduced and the team responds as though it were real, to test the system and the response together.
Geo-Blocking Accuracy
The reliability of determining a user's jurisdiction from network signals, which is imperfect in both directions and therefore needs a designed handling of errors.
Global Traffic Management
The layer that decides which region a given user reaches, using DNS, anycast or an edge network, and that performs regional failover.
Golden Path Adoption
The proportion of teams voluntarily using the supported path, which is the honest measure of whether a platform is solving real problems.
Golden Signals
The four measurements that cover most of what matters for a request-driven service: latency, traffic, errors and saturation.
Idempotency Token Store
The durable record of which idempotency keys have been seen and what each one returned, and the component that decides whether the guarantee is real.
Indirect Prompt Injection
An attack in which malicious instructions are placed in content the model will later retrieve, rather than typed by the user.
Infrastructure as Code
Defining infrastructure in version-controlled declarative files that a tool reconciles against the real environment.
Quarterly access reviews take two weeks of manager time and everyone approves everything. How do you make this a real control?
Recognise what it currently is A review where everything is approved is not producing a decision; it is producing a record of a decision shaped activity. Two we
A business sponsor asks for a real-time data platform because "the competition has one". Reporting is currently a nightly batch that lands at 06:00 and nobody has complained. How do you handle this?
Do not answer the technology question "Real time platform" is a solution, and it has arrived without a problem attached. Answering it directly leads either to a
A core mainframe system with no API supports nightly batch file exchange only. The business needs near-real-time order status. Design the integration.
Establish the real constraint "No API" usually means no API the mainframe team will build on your timeline . Find out what exists: message queue interfaces, dat
A single deploy took down your monitoring platform. What happened, and how do you prevent a recurrence?
What almost certainly happened A high cardinality label was added to a metric. Each unique combination of label values is a separate time series, and cost scale
A user in Mumbai types your URL and presses enter. Walk me through every hop until the HTML reaches their browser. Where would you look first if the page were slow?
What the interviewer is testing This is the classic architecture screening question, and it is asked because the answer's depth correlates strongly with real ex
Choose storage for four workloads: a Postgres data directory, user-uploaded images, a shared build cache, and seven years of audit records.
Postgres data directory — block storage It needs low latency random reads and writes and a filesystem, and it attaches to one instance. That is precisely block
Customers reported an outage 40 minutes before your monitoring did. How do you close that gap?
What the gap tells you Every technical signal was green while users were failing. That is not a threshold tuning problem; it means the system was monitoring com
Design a URL shortener handling 100 million new links per month and 10 billion redirects. Where is the real difficulty?
What the interviewer is testing The classic warm up. What is being assessed is not whether you can shorten a URL — it is whether you do capacity arithmetic befo
Precompute every user's timeline at write time, or assemble it at read time? Explain why the answer for a social feed is neither.
Why each pure strategy fails Fan out on read. Store each post once; on timeline load, query the posts of everyone the user follows and merge. Writes are trivial
You move a user profile service to eventual consistency and support tickets start arriving: users update their name and the old one is still shown. Fix it without abandoning the architecture.
What the interviewer is testing Whether you know that consistency is per operation rather than per system, and whether you reach for a targeted guarantee instea
Your cluster fails over spuriously under load, but a real leader failure takes 45 seconds to detect. How do you resolve the tension?
The tension Detection time is set by the heartbeat interval times the failure threshold. Shorten it and you detect real failures faster and mistake slow but ali
A deployed model performed well in validation and its business metric has declined over four months. Nothing has been deployed. What do you investigate?
The model did not change; its world did Three distinct causes, and they need different responses: Data drift. The input distribution has moved — a new customer
A partner reports your API fails from their servers with a certificate error. It works in every browser you try and from your laptop. Diagnose and prevent.
The diagnosis An incomplete certificate chain. The server presents its own certificate but not the intermediates. Browsers frequently recover — they cache inter
Real User Monitoring
Field data from real devices and networks, against the synthetic run that looked fine.
SLO Monitoring
Burn-rate alerting that fires on user impact rather than on thresholds.
Application Performance Monitoring
Attributing latency to code paths, queries and dependencies.
Continuous Controls Monitoring
Testing controls continuously instead of sampling them once a year.
Real-Time Analytical Stores
Druid, Pinot and ClickHouse — ingest-and-query engines for sub-second aggregation.
Real-Time Serving Layer
Where a low-latency read of a streaming aggregate actually lands.
Streaming & Real-Time Data
General material on continuous processing of unbounded data.
Alert Fatigue
How noise makes the real page invisible, and the structural fix.
Alerting
Symptom-based, actionable, user-impacting — and linked to a runbook.
Architecture Review Boards
Thresholds, early engagement and a real route to accept deviation.
Backfill & Reprocessing
Replaying history through changed logic without double-counting the live output.
Backup Strategies
Scope, immutability, separation, and the restore drill that makes it real.
CDC to Stream
Turning database changes into an event log, and how that differs from a domain event.
Concurrency
Operations in flight, and the limits that are the real capacity ceiling.
Data Observability
Freshness, volume, schema and distribution monitoring for pipelines that fail silently.
Dead Letter Handling
The poison message that blocks a partition, and the queue nobody reads.
Edge Computing
Moving compute towards the user, and what cannot follow it.
Edge Rendering
Running the render close to the user, and the personalisation and cache trade it implies.
Exactly-Once Semantics
What the phrase really means, where it holds, and the idempotent sink underneath it.
Feature Freshness
How stale a feature can be before the model degrades, and the pipeline that follows.
Frontend & Experience Architecture
General material on architecting the surface the user actually touches.
Kappa vs Lambda
One pipeline replayed versus two pipelines reconciled, and the maintenance each carries.