Front End Development Professional Standards & Competencies 5 — Questions and Answers
Question 1: What is the professional implication of shipping front-end code without addressing known performance issues?
- It is acceptable if the feature works correctly
- It accumulates technical debt that degrades user experience and increases future maintenance cost (Correct answer)
- It only matters for e-commerce sites
- It can always be fixed in a future sprint with no consequence
Correct answer: It accumulates technical debt that degrades user experience and increases future maintenance cost
Deferred performance work compounds over time, making future improvements more expensive and harming user retention.
Question 2: Which of the following best describes 'semantic HTML' and why it matters professionally?
- HTML with inline styles applied for visual meaning
- Using HTML elements according to their intended meaning to improve accessibility and SEO (Correct answer)
- Minified HTML for production performance
- HTML that uses custom data attributes exclusively
Correct answer: Using HTML elements according to their intended meaning to improve accessibility and SEO
Semantic HTML communicates structure to browsers, search engines, and assistive technologies, making it a professional baseline.
Question 3: When a product manager requests a feature that requires significant front-end refactoring, the professional response is to:
- Refuse to build it until the codebase is perfect
- Estimate and communicate the refactoring cost transparently so it can be included in sprint planning (Correct answer)
- Hide the refactoring work in the estimate
- Build the feature on top of bad code to meet the deadline
Correct answer: Estimate and communicate the refactoring cost transparently so it can be included in sprint planning
Transparent communication of technical costs allows informed business decisions and prevents hidden debt accumulation.
Question 4: What professional standard governs the use of open-source libraries in commercial front-end projects?
- Any public repository can be used freely without restriction
- Developers must review license terms (MIT, GPL, Apache, etc.) to ensure commercial compatibility (Correct answer)
- Only libraries with over 10,000 GitHub stars are acceptable
- Open-source licenses are irrelevant once code is bundled
Correct answer: Developers must review license terms (MIT, GPL, Apache, etc.) to ensure commercial compatibility
License compliance is a legal and professional obligation; copyleft licenses like GPL can impose significant constraints on commercial products.
Question 5: Which habit best demonstrates professional ownership of front-end work in production?
- Monitoring error dashboards and performance metrics after deployments (Correct answer)
- Marking tasks done in the tracker immediately after pushing code
- Logging off immediately after a release
- Letting QA own all post-release monitoring
Correct answer: Monitoring error dashboards and performance metrics after deployments
Actively monitoring production after a deploy catches regressions early when rollback is cheapest and impact is smallest.
Question 6: A client insists on a dark-pattern UI technique (e.g., hidden unsubscribe) to increase conversions. The ethical professional should:
- Implement it since conversion optimization is the goal
- Implement it but add a comment in the code
- Decline and explain that dark patterns violate user trust and may breach consumer protection regulations (Correct answer)
- Implement a watered-down version without telling the client
Correct answer: Decline and explain that dark patterns violate user trust and may breach consumer protection regulations
Front-end developers have an ethical duty to advocate against manipulative design that harms users and may carry legal liability.
Question 7: What is the purpose of defining a 'Definition of Done' (DoD) on a front-end team?
- To track individual developer velocity
- To establish a shared checklist of quality gates every feature must pass before being considered complete (Correct answer)
- To document which features the team decided not to build
- To set the maximum number of lines a file can contain
Correct answer: To establish a shared checklist of quality gates every feature must pass before being considered complete
A DoD aligns the team on quality expectations—covering tests, accessibility, performance, and review—preventing inconsistent standards.
Front End Development Professional Standards & Competencies 5
What is the professional implication of shipping front-end code without addressing known performance issues?