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
A single-page application stores the user's JWT in localStorage. What is the PRIMARY security risk?
Answer: Any XSS attack can read and exfiltrate the token
localStorage is accessible via JavaScript, so a successful XSS attack can steal the token and hijack the user's session.
A risk is rated HIGH probability but LOW impact. What is typically the recommended response?
Answer: Monitor it regularly but avoid spending major resources on mitigation
High-probability, low-impact risks warrant monitoring and lightweight controls rather than costly mitigation efforts.
Subresource Integrity (SRI) checks on third-party script tags help mitigate which front-end risk?
Answer: Serving of a tampered or hijacked third-party file
SRI hashes verify that the fetched file exactly matches the expected content, blocking execution if the CDN-hosted file has been compromised.
Which practice is most effective for identifying accessibility risks before a front-end release?
Answer: Running automated accessibility audits (e.g., axe) plus manual screen-reader testing
Automated tools catch roughly 30–40% of issues, and manual testing with assistive technology covers the remainder of real-world accessibility risks.
Your team is about to migrate from a legacy CSS framework to a new one across 200 components. The HIGHEST risk you should plan for is:
Answer: Visual regressions across components that break the UI for end users
Wide-scope CSS migrations frequently introduce subtle visual regressions that are hard to catch without screenshot-based regression testing.
In risk management, 'residual risk' refers to:
Answer: The remaining risk after mitigation controls have been applied
No mitigation is perfect; residual risk is whatever exposure remains after controls are in place and must be accepted or further reduced.
A dependency audit using `npm audit` reports a HIGH-severity vulnerability in a package used only in devDependencies for local linting. What is the appropriate risk response?
Answer: Assess that production users are not exposed, document it, and schedule a routine fix
devDependencies are not shipped to users, so the production risk is negligible—document the finding and fix it in a non-emergency window.
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