GitHub Actions Intermediate Practice Exam: Medium Difficulty 2025

Your team is developing a workflow that needs to deploy to Azure App Service only when changes are made to the /src directory, and only on the main branch. The workflow should skip deployment if only documentation files are changed. Which workflow trigger configuration should you implement?

You need to create a reusable workflow that can be called from multiple repositories in your organization. The reusable workflow should accept environment-specific parameters and return output values to the caller. Which approach correctly implements this requirement?

Your CI/CD pipeline uses a matrix strategy to test across multiple Node.js versions (14, 16, 18) and operating systems (ubuntu-latest, windows-latest). The build is failing only for Node.js 14 on Windows. You want to continue testing other combinations while investigating this issue. What is the best solution?

You are implementing a workflow that uses an action from the GitHub Marketplace. Your security team requires that all external actions be pinned to specific versions and verified. Which approach best meets these security requirements?

Your workflow needs to access secrets from Azure Key Vault during the build process. The workflow runs in a GitHub-hosted runner and should follow the principle of least privilege. What is the most secure approach to implement this?

A workflow run is stuck in a queued state for over an hour. You need to diagnose the issue. The repository has multiple workflows configured, and you're using GitHub-hosted runners. What are the most likely causes you should investigate first?

You need to implement a workflow that automatically retries failed jobs due to transient network issues, but should not retry jobs that fail due to test failures. The workflow deploys to Azure resources that occasionally have connectivity issues. How should you configure this?

Your team is implementing a CI/CD pipeline where pull requests should trigger build and test jobs, while merges to the main branch should additionally trigger deployment to a staging environment. Both scenarios should use the same build artifacts. What workflow structure best implements this requirement?

You're implementing a deployment workflow to Azure App Service that should only deploy if all of the following conditions are met: the branch is 'main', all tests pass, and code coverage is above 80%. The coverage check is performed by a third-party tool. How should you structure this workflow?

Your organization requires that production deployments be traceable and include approval records. You're using GitHub Actions to deploy to Azure. The deployment workflow should automatically create a release record and require approval from two team leads before proceeding. Which combination of features should you implement?