As a developer, you need to use GitHub Actions to deploy a microservice that requires runtime access to a secure token. This token is used by a variety of other microservices managed by different teams in different repos. To minimize management overhead and ensure the token is secure, which mechanisms should you use to store and access the token? (Choose two.)
Using a corporate secret store like HashiCorp Vault provides a secure, centralized location for sensitive information. GitHub Actions can then retrieve and store the token securely during deployment by setting it as an environment variable, ensuring the token remains secure and accessible at runtime.
Storing the token as an organizational-level encrypted secret in GitHub ensures it is accessible across multiple repositories, minimizing management overhead. GitHub Actions can then use this secret during deployment by setting it as an environment variable, allowing the microservice to access it securely at runtime.
You have exactly one Windows x64 self-hosted runner, and it is configured with custom tools. Which syntax could you use in the workflow to target that runner?
The runs-on keyword allows you to specify the operating system and other labels for the runner. By specifying self-hosted, windows, and x64, you are targeting a self-hosted Windows runner that matches these criteria, which aligns with the custom configuration of your self-hosted runner.
As a developer, how can you identify a Docker container action on GitHub?
In a Docker container action, the action.yml file includes the runs.using field, which is set to docker to specify that the action runs inside a Docker container. This is the key indicator that the action is a Docker container action.
You have exactly one Windows x64 self-hosted runner, and it is configured with custom tools. Which syntax could you use in the workflow to target that runner?
The runs-on keyword allows you to specify the operating system and other labels for the runner. By specifying self-hosted, windows, and x64, you are targeting a self-hosted Windows runner that matches these criteria, which aligns with the custom configuration of your self-hosted runner.
Which of the following scenarios would require the use of self-hosted runners instead of GitHub-hosted runners?
GitHub-hosted runners have a limit on the number of concurrent workflows (typically 20 for free-tier accounts and 5 for enterprise). If your organization needs to run more workflows simultaneously, you would need to use self-hosted runners to increase the available concurrency.
Self-hosted runners allow you to configure specialized hardware or software setups that are necessary for certain workflows. GitHub-hosted runners may not have access to custom hardware configurations like GPUs or other specialized resources, so self-hosted runners are required in such cases.
Leeann
12 days agoKip
19 days agoDetra
26 days agoTijuana
1 month agoDorsey
1 month agoAbraham
2 months agoSonia
2 months agoMartin
2 months agoPenney
2 months agoKaycee
3 months agoMarg
3 months agoJohnathon
3 months agoOlga
3 months agoJolene
4 months agoTitus
4 months agoAntonio
4 months agoJenelle
4 months agoCherrie
5 months agoElouise
5 months agoLeonard
5 months agoJulianna
5 months agoBobbye
6 months agoDesirae
6 months agoJeannine
6 months agoKatlyn
6 months agoBernadine
7 months agoLisbeth
7 months agoIra
7 months agoGilbert
7 months agoNoel
7 months agoGabriele
7 months agoGaynell
7 months ago