Explore the key differences and considerations when choosing between self-hosted and cloud-hosted runners for scaling automated workflows. This quiz evaluates your knowledge on scaling strategies, cost implications, maintenance requirements, and security aspects associated with both runner types.
Which type of runner provides the highest level of control over hardware specifications and pre-installed software for specialized workflow needs?
Explanation: Self-hosted runners allow users to configure hardware components, operating systems, and install custom software, making them ideal for specialized or legacy requirements. Shared cloud-hosted runners offer generic environments without custom control. Reserved runners typically refer to specific allocations but do not guarantee full hardware or software configuration control. Temporary runners are ephemeral and not intended for customization beyond basic setups.
In a scenario where workload demand fluctuates significantly, which runner type is generally better suited for quickly scaling to handle large surges of workflow jobs?
Explanation: Cloud-hosted runners are designed to scale on demand and can automatically handle surges in workflow jobs by instantly provisioning additional capacity. Manual self-hosted runners require more effort to scale and may not respond instantly to spikes. Single-core runners refer to hardware limits, which does not address scaling needs. Offline runners are unavailable for job execution and cannot help with scaling at all.
What is a typical benefit of using self-hosted runners when scaling workflows for a large volume of jobs over time?
Explanation: Self-hosted runners may offer cost savings over time since the infrastructure is owned or managed by the organization, especially at scale. Higher direct costs per run are usually associated with usage-based cloud models, not self-hosting. Self-hosted solutions do impact organizational infrastructure, requiring oversight. Automatic software patching is not a typical feature of self-hosted setups and would need manual intervention or automation.
Who is primarily responsible for applying security updates and maintaining the operating system on machines used for self-hosted runners?
Explanation: With self-hosted runners, the hosting organization is responsible for security updates and operating system maintenance. Providers of workflow engines or automation services cannot update external infrastructure. Security vendors may offer advice but do not manage the system directly. Assuming maintenance is fully automated without setup is incorrect, as it requires explicit scheduling and management.
What is a potential security risk when using self-hosted runners that have access to your internal network?
Explanation: Self-hosted runners with network access to internal systems are vulnerable if a workflow contains malicious code, as it could compromise internal resources. Automatic failover does not directly relate to security risk; it's a resilience feature. Improved download speeds are a performance benefit but not a risk. Complete isolation from external threats is incorrect since the runner executes externally-supplied code and may increase attack surfaces.