GH-100 practice question 3 of 15

Which events from the audit log are exposed by the GraphQL API? Each answer presents a complete solution. (Choose three.)

Full set: 65 questions
Answer options
A: changes in permissions Correct answer
B: promoting users to administrators Correct answer
C: pushes to repositories
D: changes to permissions of a GitHub App Correct answer
E: cloning of repositories
Correct Answer:
A. changes in permissions; B. promoting users to administrators; D. changes to permissions of a GitHub App
Explanation

The GitHub GraphQL API provides access to an organization's or enterprise's audit log, which records actions related to administrative settings, permissions, and security. The exposed events focus on governance and compliance. This includes tracking changes to user permissions within repositories and teams (repo.addmember, team.addrepository), promoting users to administrative roles (org.updatemember), and modifying the permissions granted to a GitHub App (integrationinstallation.permissionsupdated). These actions represent significant changes to access control and are core to the audit log's function.

Why Incorrect

C. pushes to repositories: Git push events are not included in the standard audit log by default. They are considered high-volume Git events and are only logged if explicitly enabled via Git event logging for an enterprise account.
E. cloning of repositories: Similar to pushes, git clone events are not part of the default audit log. Capturing these read-access events requires enabling the separate Git event logging feature for an enterprise.

References

1. GitHub Docs

"Audit log actions": This document provides a comprehensive list of actions recorded in the audit log. It categorizes actions

clearly showing that permission changes for users

teams

and applications are standard.

Section/Content: The page lists actions such as org.updatemember (covering promotions)

repo.addmember (permission changes)

and integrationinstallation.permissionsupdated (GitHub App permissions).

2. GitHub Docs

"About the audit log for your enterprise": This source clarifies the scope of the audit log and explicitly distinguishes standard administrative events from Git events.

Section: "Events in your audit log": It states

"The audit log lists events triggered by activities that affect your enterprise... The audit log does not show Git events." It then explains that Git events (git.clone

git.fetch

git.push) can be logged separately.

3. GitHub GraphQL API Reference

AuditEntry: The official GraphQL schema documentation confirms that the action field on an AuditEntry object returns a string corresponding to the actions listed in the "Audit log actions" documentation.

Object: AuditEntry: The documentation for this interface shows it exposes details of an audit log event

including the action performed

which can be queried via the auditLog connection on an Organization or Enterprise object.

Scroll to Top