--- title: "Infrastructure Patterns: IaC, Provisioning & Orchestration" description: "Master infrastructure patterns: Infrastructure as Code, provisioning, configuration management, orchestration. Design scalable, maintainable infrastructure." author: "Mohammad Abu Mattar" canonical: https://mkabumattar.com/quizzes/post/infrastructure-patterns-quiz --- # Infrastructure Patterns: IaC, Provisioning & Orchestration Welcome to the Infrastructure Patterns Quiz! This quiz will test your knowledge of infrastructure management, including Infrastructure as Code (IaC), provisioning, configuration management, orchestration, and disaster recovery. Each question asks how to design and maintain scalable, reliable infrastructure for modern applications. It works either as a first pass over the topic or as a check on what you already run in production. Good luck! ## Questions ### 1. What is Infrastructure as Code (IaC)? - Defining and managing infrastructure using configuration files instead of manual hardware setups - A specialized programming language used to develop low-level kernel drivers for cloud servers - A proprietary cloud feature that restricts infrastructure management to a single provider console - The manual process of documenting hardware changes in a version-controlled text document **Hint:** Think about defining infrastructure in code files. ### 2. What is Terraform? - An open-source IaC tool that manages multi-cloud resources using declarative configuration - A specialized AWS service designed to manage internal security groups and IAM permissions - A public cloud provider that offers managed virtual machines and serverless compute functions - A real-time monitoring agent installed on servers to track hardware performance and logs **Hint:** Think about tool-agnostic IaC. ### 3. What is provisioning? - The process of allocating and setting up infrastructure resources like servers and networks - The continuous deployment of application source code to a running production environment - The act of updating internal software versions and security patches on existing servers - A manual-only technique for configuring local hardware devices without network connectivity **Hint:** Think about setting up infrastructure. ### 4. What is configuration management? - Using tools like Ansible or Chef to maintain consistent software states across multiple servers - The initial act of creating virtual machine instances and virtual private clouds (VPCs) - A development-only practice for tracking local environment variables in a .env file - A specialized hardware process that requires a physical restart for every minor change **Hint:** Think about maintaining consistent server state. ### 5. What is Ansible? - An agentless configuration tool that uses SSH and YAML playbooks to manage server state - A proprietary AWS dashboard used for horizontal scaling and automated instance recovery - A configuration management tool that requires a persistent agent to be installed on all servers - A low-level compiled programming language used to build high-performance web servers **Hint:** Think about agentless configuration management. ### 6. What is container orchestration? - The automated coordination of container deployment, scaling, networking, and availability - The manual process of organizing source code into modular folders for better readability - A Docker-specific feature that prevents containers from communicating across networks - A set of manual commands used to restart individual containers when they stop responding **Hint:** Think about managing many containers. ### 7. What is a load balancer? - A service that distributes incoming network traffic across a group of backend servers - A database clustering technique used to synchronize data across multiple physical disks - A tool used exclusively for high-traffic applications that have exceeded server limits - A network device that adds intentional latency to prevent servers from being overwhelmed **Hint:** Think about distributing traffic. ### 8. What is auto-scaling? - Dynamically adjusting the number of active computing resources based on real-time demand - Increasing the lines of code in an application to handle more complex business logic - A manual adjustment of server RAM and CPU performed by an administrator during peak hours - A cloud feature that only allows infrastructure to expand upward but never contract **Hint:** Think about automatically adding/removing resources. ### 9. What is high availability? - Designing a system to remain operational and accessible even during component failures - Optimizing application code to ensure the fastest possible performance for all users - A metric that measures the total storage capacity available in a primary database - A hardware-specific requirement that necessitates the use of expensive enterprise servers **Hint:** Think about minimizing downtime. ### 10. What is disaster recovery? - A documented set of procedures for restoring infrastructure after a catastrophic event - The practice of preventing any hardware or software failures from ever occurring - A simple backup strategy that only involves copying database files to a local drive - A regulatory requirement that only applies to large financial or medical corporations **Hint:** Think about recovering from catastrophic failure. ### 11. What is RTO (Recovery Time Objective)? - The maximum acceptable duration of time that a system can be down after a failure - The minimum amount of time required for an engineer to begin the recovery process - The average time it takes for a cloud provider to replace a failed physical server - The measurement of how much data was lost during a specific catastrophic failure **Hint:** Think about maximum acceptable downtime. ### 12. What is RPO (Recovery Point Objective)? - The maximum acceptable amount of data loss measured in time from a failure event - The total number of recovery points created during a single calendar month - The specific technical process used to restore a database to a previous state - The time-based goal for how long it takes to bring a server back online **Hint:** Think about maximum acceptable data loss. ### 13. What is a CDN (Content Delivery Network)? - A distributed network of proxy servers that cache content closer to end users - A centralized database system used for storing large volumes of unstructured data - A specialized security protocol used to encrypt data between two backend servers - A local area network designed to improve the speed of internal office applications **Hint:** Think about caching content geographically. ### 14. What is the difference between vertical and horizontal scaling? - Vertical adds power to one node; horizontal adds more nodes to the system - Vertical scales the database layer; horizontal scales the web application layer - Vertical scaling is always more cost-effective than horizontal scaling at scale - Vertical refers to software updates; horizontal refers to hardware replacements **Hint:** Think about adding resources to one server vs. many. ### 15. What is a reverse proxy? - A server that intercepts client requests and forwards them to one or more backends - A client-side tool used to bypass firewall restrictions and access blocked websites - A mandatory hardware device required to connect any server to the public internet - A specialized database layer that caches query results for large-scale applications **Hint:** Think about hiding backend servers. ### 16. What is Docker? - A platform that uses OS-level virtualization to deliver software in isolated packages - A hardware hypervisor used to run multiple full operating systems on one server - A specialized cloud provider that only hosts JavaScript-based microservices - A deployment script that replaces the need for configuration management tools **Hint:** Think about containerization and application isolation. ### 17. What is a Docker image? - A lightweight, standalone, executable package that includes everything to run software - A live, running instance of an application that is currently processing user data - A compressed backup of a physical server used for disaster recovery purposes - A graphical user interface used to manage and monitor containers on a local machine **Hint:** Think about blueprint for containers. ### 18. What is Kubernetes? - An open-source system for automating deployment, scaling, and management of containers - A containerization engine that serves as a direct replacement for the Docker runtime - A proprietary cloud service that only functions within the Google Cloud Platform - A configuration management tool used to install software directly on bare-metal OS **Hint:** Think about orchestrating containers at scale. ### 19. What is a pod in Kubernetes? - The smallest deployable unit in Kubernetes, consisting of one or more containers - A specialized storage volume used to persist data when a container is restarted - A physical server node that belongs to a larger managed Kubernetes cluster - A network security group that controls traffic between different microservices **Hint:** Think about smallest deployable unit. ### 20. What is immutable infrastructure? - A pattern where servers are replaced rather than modified when changes are required - A security setting that prevents any users from logging into a production server - A database configuration that prevents existing records from being updated or deleted - An infrastructure design that only supports containerized applications and services **Hint:** Think about never modifying running servers. ### 21. What is blue-green deployment? - A release model that uses two identical environments to ensure zero-downtime updates - A technique for gradually shifting traffic to a small percentage of users for testing - A coding standard that uses different environments for frontend and backend tasks - An automated testing process that only runs when the server is in a standby state **Hint:** Think about zero-downtime deployments with two environments. ### 22. What is canary deployment? - Rolling out a change to a small subset of users before deploying to the entire fleet - An instant switch between two identical production environments for fast rollbacks - A specialized security test performed by third-party auditors on live production systems - A method for deploying multiple versions of an API that are all active at once **Hint:** Think about gradual rollout to subset of users. ### 23. What is GitOps? - A practice using Git repositories as the single source of truth for infrastructure - A standardized workflow for developers to commit code to a shared repository - A cloud-based tool that automatically generates Git repositories for new projects - A deployment strategy that only works with Kubernetes and containerized applications **Hint:** Think about Git as source of truth for infrastructure. ### 24. What is a service mesh? - An infrastructure layer for handling service-to-service communication and security - A physical network topology that connects every server to every other server node - A mandatory component for any application moving from a monolith to microservices - A load balancing tool used to distribute public internet traffic to a web server **Hint:** Think about managing service-to-service communication. ### 25. What is infrastructure monitoring? - The process of collecting and analyzing metrics to ensure infrastructure health - A software licensing check performed to ensure all cloud resources are authorized - A feature that only functions when applications are deployed to public cloud providers - The act of manually reviewing server log files once per week for security threats **Hint:** Think about observing infrastructure health and performance. ### 26. What is infrastructure security? - Using firewalls, encryption, and access controls to protect the underlying system - The process of ensuring all application developers use strong personal passwords - A specialized task that is handled exclusively by the cloud provider's internal team - A security layer that prevents any external traffic from reaching the internal network **Hint:** Think about protecting infrastructure from attacks. ### 27. What is Terraform state? - A metadata file that tracks the relationship between your code and real resources - A real-time dashboard that shows the current CPU and RAM usage of all servers - A local-only file that must never be shared or stored in a remote cloud bucket - A temporary log file that is automatically deleted after every successful deployment **Hint:** Think about tracking deployed infrastructure. ### 28. What is infrastructure as environment (IaE)? - A pattern of using IaC to create consistent, reproducible application environments - A method for managing environment variables within a single application instance - A specialized testing environment used exclusively for verifying database migrations - A manual process for configuring local servers to match a production cloud setup **Hint:** Think about consistent environments via infrastructure code. ### 29. What is infrastructure cost optimization? - A set of practices to reduce cloud spending by right-sizing and removing waste - The act of always selecting the lowest-cost hardware regardless of performance - A one-time activity performed at the start of a project to set the initial budget - A strategy to reduce costs by removing essential security and monitoring features **Hint:** Think about reducing cloud spending. ### 30. What is infrastructure testing and validation? - Automatically verifying that infrastructure code meets functional and security goals - A manual walk-through of the cloud console to check for any visible error messages - A testing phase that only occurs after an application has been fully deployed - An optional process that is only required for high-risk financial applications **Hint:** Think about verifying infrastructure code before deployment.