Cisco®
CompTIA
Checkpoint
ISC
EC-Council
EXIN
Fortinet
ITIL®
Juniper
Microsoft
VMware
Avaya
SAP
Google
Salesforce
Amazon
Palo Alto Networks
ISC2
All Vendors
  2. Home
  3. Exams
  4. GitHub
  5. GitHub-Advanced-Security

Free GitHub GitHub-Advanced-Security Exam Questions (page: 3)

Page 3 of 20
PDF with 75 Questions

­ [Configure GitHub Advanced Security Tools in GitHub Enterprise]

As a repository owner, you want to receive specific notifications, including security alerts, for an individual repository.
Which repository notification setting should you use?

  1. Ignore
  2. Participating and @mentions
  3. All Activity
  4. Custom

Answer(s): D

Explanation:

Using the Custom setting allows you to subscribe to specific event types, such as Dependabot alerts or vulnerability notifications, without being overwhelmed by all repository activity. This is essential for repository maintainers who need fine-grained control over what kinds of events trigger notifications.

This setting is configurable per repository and allows users to stay aware of critical issues while minimizing notification noise.


Reference:

GitHub Docs ­ Configuring notifications; Managing security alerts



­ [Configure GitHub Advanced Security Tools in GitHub Enterprise]

Which of the following Watch settings could you use to get Dependabot alert notifications? (Each answer presents part of the solution. Choose two.)

  1. The Custom setting
  2. The Participating and @mentions setting
  3. The All Activity setting
  4. The Ignore setting

Answer(s): A,C

Explanation:

Comprehensive and Detailed Explanation;
To receive Dependabot alert notifications for a repository, you can utilize the following Watch settings:

Custom setting: Allows you to tailor your notifications, enabling you to subscribe specifically to security alerts, including those from Dependabot.

All Activity setting: Subscribes you to all notifications for the repository, encompassing issues, pull requests, and security alerts like those from Dependabot.

The Participating and @mentions setting limits notifications to conversations you're directly involved in or mentioned, which may not include security alerts. The Ignore setting unsubscribes you from all notifications, including critical security alerts.

GitHub Docs

+1

GitHub Docs

+1


Reference:

GitHub Docs ­ Configuring notifications; Managing security alerts



­ [Configure and Use Dependency Management]

Which Dependabot configuration fields are required? (Each answer presents part of the solution.
Choose three.)

  1. directory
  2. package-ecosystem
  3. milestone
  4. schedule.interval
  5. allow

Answer(s): A,B,D

Explanation:

Comprehensive and Detailed Explanation;
When configuring Dependabot via the dependabot.yml file, the following fields are mandatory for each update configuration:

directory: Specifies the location of the package manifest within the repository. This tells Dependabot where to look for dependency files.

package-ecosystem: Indicates the type of package manager (e.g., npm, pip, maven) used in the specified directory.

schedule.interval: Defines how frequently Dependabot checks for updates (e.g., daily, weekly). This ensures regular scanning for outdated or vulnerable dependencies.

The milestone field is optional and used for associating pull requests with milestones. The allow field is also optional and used to specify which dependencies to update.

GitLab


Reference:

GitHub Docs ­ Configuration options for dependency updates



­ [Configure and Use Code Scanning]

What is required to trigger code scanning on a specified branch?

  1. The repository must be private.
  2. Secret scanning must be enabled on the repository.
  3. Developers must actively maintain the repository.
  4. The workflow file must exist in that branch.

Answer(s): D

Explanation:

Comprehensive and Detailed Explanation;
For code scanning to be triggered on a specific branch, the branch must contain the appropriate workflow file, typically located in the .github/workflows directory. This YAML file defines the code scanning configuration and specifies the events that trigger the scan (e.g., push, pull_request).

Without the workflow file in the branch, GitHub Actions will not execute the code scanning process for that branch. The repository's visibility (private or public), the status of secret scanning, or the activity level of developers do not directly influence the triggering of code scanning.


Reference:

GitHub Docs ­ About workflows; About code scanning alerts



Viewing page 3 of 20
Viewing questions 9 - 12 out of 75 questions



Post your Comments and Discuss GitHub GitHub-Advanced-Security exam prep with other Community members:

GitHub-Advanced-Security Exam Discussions & Posts