Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
21 results for “Core Web Vitals”
Cumulative Layout Shift
The extent to which visible content moves unexpectedly during load, which correlates with mis-taps and is almost entirely preventable by reserving space.
JSON Web Token
A signed, self-contained token carrying claims, which a service can validate locally without calling the issuer.
Web Application Firewall
A filter in front of an application that inspects HTTP requests and blocks those matching known attack patterns — useful as a layer, dangerous as a substitute.
JWKS
A published endpoint listing an issuer's current public keys, allowing resource servers to validate token signatures without a shared secret and to survive key rotation.
Mainframe Offload
Moving read traffic and selected processing off a mainframe onto modern platforms, reducing cost and unblocking new development without replacing the core.
OWASP Top Ten
A periodically updated consensus list of the most critical web application security risks, useful as a design-review checklist.
Performance Budget Enforcement
A stated limit on bundle size or a timing metric that fails a build when exceeded, which is what turns performance from a periodic project into a constraint.
Pilot Light
A disaster recovery posture where core data is continuously replicated and minimal infrastructure runs, with the rest provisioned only on failover.
Stripe's API Versioning
Stripe pins each account to the API version current when it integrated and transforms requests and responses between versions internally, so integrations never break and the core …
eBay's Architectural Generations
eBay rewrote its core platform several times across its first decade, each time because the previous generation had hit a limit that could not be tuned away.
Mobile conversion is 40% below desktop. Product blames the design; analytics shows users leaving before the page is usable. How do you investigate?
Get field data before touching anything A laboratory run on a developer machine measures one configuration, usually the fastest one anyone uses. Real traffic in
A 15-year-old monolith runs the core of the business. Leadership wants microservices. How do you approach it, and what would make you refuse?
What the interviewer is testing Whether you start from the business problem or from the target architecture, and whether you are willing to say no. First, estab
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 twenty-year-old core system supports most of the business. It is on unsupported technology, three people understand it, and the last replacement attempt was abandoned after two years. Design the programme.
Learn from the abandoned attempt first The most important input is why the last one failed, and the reasons are usually structural rather than technical: a big
TSB's 2018 core banking migration moved 1.9 million customers in a single weekend and failed publicly. What would you have required before approving that cutover?
The case, as publicly reported In April 2018 TSB migrated from a platform rented from Lloyds Banking Group to Proteo4UK, built by its parent Banco Sabadell. The
You are designing APIs for a platform with a web app, a mobile app, internal service-to-service traffic and third-party partners. What do you expose, and where?
What the interviewer is testing Whether you choose per constraint or adopt one technology as an identity. The wrong answers here are all defensible sounding and
Core Web Vitals
LCP, INP and CLS — what they measure, and the architecture that moves them.
Web Performance Budgets
A number a build can fail against, rather than a performance sprint once a year.
Licence & Vendor Costs
Per-core, per-seat and per-environment terms that shape designs.
Mainframe Modernization
Batch windows, COBOL, and the risk profile of core banking systems.
OWASP Risks
The recurring web and API risk classes, several of which are design flaws.