Core Concepts in Technology
Five multiple-choice questions that build from fundamentals to deeper reasoning about technology mindsets, frameworks, and consequences.
Try this quiz
Play through the questions and see your score instantly
Ready to test your knowledge?
5 questions · Quick play · Instant results
Make your own quiz videos
Turn any topic into a polished video quiz — with AI-powered questions, voiceover, and animations. No video editing skills needed.
Unlimited quizzes, free to start
Create as many quizzes as you want. Describe your topic and AI builds the questions, answers, and explanations for you.
Customise everything
Pick from stunning templates, tweak colours and fonts, add your branding, and choose between vertical or landscape formats.
Export-ready videos
Download HD videos optimised for TikTok, YouTube Shorts, Instagram Reels, or full-length YouTube — one click, no editing.
No credit card required
Quiz Questions & Answers
Review every prompt, the correct responses, and helpful context to prep for your own run-through.
Question 1: What best describes the core idea of 'scalability' in software systems?
Software that never needs updates
Ability to handle growing load by adding resources
Code written in a single programming language
Question 2: Which practice most directly reduces risk when releasing new features to users?
Releasing all features at once to all users
Relying solely on manual QA before launch
Gradual rollout with monitoring and rollback capability
Question 3: Which mindset most helps teams prioritize long-term reliability over short-term speed?
Engineering for observability and maintainability
Maximizing feature count each sprint
Avoiding documentation to move faster
Question 4: If a machine-learning model performs well in tests but fails in production, what is the likeliest root cause to investigate first?
That the model weights are precisely the same file format
Data drift or mismatch between training and production data
That users are using a different web browser
Question 5: Which statement about technical debt best informs long-term product strategy?
Ignoring debt has no impact on developer productivity
All technical debt is bad and must be eliminated immediately
Intentional, tracked debt can speed delivery but must be repaid to avoid rising maintenance cost