Risk Assessment & Management Flashcards
7 cards from real Front End Development practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Risk Assessment & Management flashcards as text
Which front-end testing type provides the MOST direct risk coverage for a complete user checkout flow spanning multiple components?
Answer: End-to-end (E2E) tests simulating the full browser interaction
E2E tests exercise the entire user journey in a real or headless browser, catching integration gaps that unit or snapshot tests miss.
A Content Security Policy (CSP) header is primarily used to mitigate which class of front-end attack?
Answer: Cross-site scripting (XSS)
CSP restricts which scripts, styles, and resources the browser may execute, blocking many XSS payloads even if injection occurs.
Technical debt in a front-end codebase is best classified as which type of risk?
Answer: Internal operational risk
Technical debt is an internally generated risk that increases the probability of defects, slower delivery, and system failure over time.
A team ships a breaking change to a shared component library used by five product teams simultaneously. Which risk management practice would have best prevented the outage?
Answer: Semantic versioning with a deprecation period and consumer communication before removal
Semantic versioning communicates breaking changes via major version bumps and a migration window, allowing consumers to upgrade on their own schedule.
An application renders user-supplied HTML directly using `innerHTML`. The MOST appropriate risk control is:
Answer: Sanitize HTML using a trusted library (e.g., DOMPurify) before insertion
DOMPurify and similar libraries strip dangerous tags and attributes from HTML before it touches the DOM, preventing XSS.
Which action would be categorized as 'risk acceptance' in a front-end project?
Answer: Documenting a known IE11 rendering issue as out of scope because IE11 usage is <0.1%
Risk acceptance means formally acknowledging a risk and deciding not to mitigate it, usually because the cost of mitigation exceeds the expected impact.
During a sprint retrospective, the team identifies that unclear API contracts between front-end and back-end teams caused two production bugs. Which risk management action addresses the ROOT CAUSE?
Answer: Establish a shared API contract using OpenAPI/Swagger with automated contract testing
Contract testing with a shared specification prevents front-end/back-end mismatches from reaching production by validating both sides against the same source of truth.
How this page was made: written with AI tools and published by Nathan Beja, founder of Practice Test Geeks, who is responsible for its content. We have not yet matched this exam's facts to an official source, so confirm fees, dates and rules with the exam body. Not reviewed by a subject-matter expert. Editorial policy