NEW
Font size
WorksheetsModule 4: GitHub Ribbon Features: Projects, Actions, Deployment
Total questions: 26
Worksheet time: 9mins
What is the primary purpose of the GitHub ribbon?
To manage billing and subscriptions
To provide quick access to repository and collaboration features
To display repository statistics only
To manage local Git configuration
Which of the following best describes the GitHub ribbon interface?
Different layout for every repository
Hidden navigation that appears only on demand
Consistent interface across repositories for easier collaboration
Focused only on code browsing
What does the GitHub ribbon centrally provide access to?
Only code and releases
Code, issues, pull requests, and actions
External project management tools
Local development environments
How does the GitHub ribbon support the software development lifecycle?
By separating planning from development tools
By aligning features with lifecycle phases
By limiting automation to production only
By replacing CI/CD systems
Which GitHub ribbon feature supports planning and task tracking?
Actions
Environments
Projects
Settings
What is the main purpose of GitHub Projects?
To store deployment logs
To plan, track, and manage work within GitHub
To automate CI pipelines
To manage repository permissions
Which capability is a key feature of GitHub Projects?
External issue tracking only
Centralized tracking of work items across repositories
Manual progress reporting
Code execution
How do GitHub Projects integrate with development work?
Through external APIs only
By linking only commits
By directly integrating issues and pull requests
By replacing pull requests
What distinguishes classic GitHub project boards from the new Projects experience?
Classic boards support advanced filtering
New Projects only support Kanban views
New Projects offer multiple views and advanced tracking
Classic boards scale better for agile workflows
Which feature makes new GitHub Projects more suitable for agile and cross-team planning?
Static columns
Advanced filtering and sorting
Limited views
Repository-only scope
What is the first step in creating a GitHub Project?
Write a workflow file
Navigate to repository Settings
Open a repository and go to the Projects section
Create issues first
What is the primary purpose of the table view in GitHub Projects?
To execute workflows
To organize tasks using custom fields
To replace pull requests
To manage secrets
In the new GitHub Projects experience, what does the Status field represent?
Repository visibility
Workflow stages like To do, In progress, and Done
Deployment targets
Branch protection rules
How do GitHub Projects support agile execution?
By isolating issues from pull requests
By tracking issues and PRs across workflow stages
By requiring external tools
By limiting real-time updates
What do issues represent in GitHub Projects?
Deployment environments
Units of work that move through workflow stages
Workflow files
Automation logs
Why is GitHub Actions central to automation?
It replaces version control
It automates build, test, and deployment tasks
It only manages permissions
It is used only for production releases
Which event can trigger a GitHub Actions workflow?
Opening GitHub settings
Repository events such as pushes or pull requests
Local file changes
Manual server restarts
How are GitHub Actions workflows defined?
Using JSON files
Through the GitHub UI only
Using YAML files stored in the repository
Via command-line scripts
What information do workflow run logs provide?
Only success or failure status
Repository access permissions
Detailed execution output for jobs and steps
Billing usage
Which is a typical stage in a web application deployment workflow?
Code review
Issue triage
Run automated tests
Repository cloning
What is a key benefit of automating web application deployments with GitHub Actions?
Slower but safer releases
Reduced visibility into releases
Faster, repeatable deployments
Manual approval for every step
Where can deployment settings be configured?
Only at repository level
Only at organisation level
At both repository and organisation levels
Only in workflow files
What do repository-level GitHub Actions permissions control?
UI customization
Which workflows can run and what access automation has
Issue assignment rules
Project layouts
Why are approval requirements for forked pull requests important?
To speed up deployments
To allow all third-party actions
To prevent untrusted code from executing workflows
To disable automation
What is the purpose of GitHub Environments?
To replace repositories
To represent deployment targets like staging and production
To store workflow logs
To manage user accounts
How do environments improve deployment security?
By eliminating automation
By applying protection rules to sensitive stages
By allowing unrestricted deployments
By merging all environments into one
