Microsoft GH-100 Practice Test 37
Question 360
GitHub Enterprise administration scenario — Distinguish OAuth app consent from a GitHub App installation. In an enterprise development environment: A security reviewer treats third-party OAuth application authorization as identical to a scoped GitHub App installation request. A controlled enterprise configuration review requires a coherent rationale, approved change and confirmed outcome. Select EXACTLY THREE: the governing GitHub administration principle, the proportionate authorized intervention AND the independently observable outcome for this scenario.
- OAuth apps and GitHub Apps have different authorization models, token scopes and installation permission boundaries.
- The integration accesses only approved resources and its permission grant can be independently reviewed and revoked.
- Unauthorized reference rewrites are rejected while approved releases continue to reference reviewed commits.
- Dependency vulnerability alerts depend on supported dependency identification and security configurations at the correct repository scope.
- Require validated triage categories with documented revocation and exception decisions for exposed tokens.
- Evaluate the product's supported integration model and approve only the least-privilege application type and rights.
Explanation
Correct Answers
A:OAuth apps and GitHub Apps have different authorization models, token scopes and installation permission boundaries. Evaluate the product's supported integration model and approve only the least-privilege application type and rights. The integration accesses only approved resources and its permission grant can be independently reviewed and revoked.
B:The integration accesses only approved resources and its permission grant can be independently reviewed and revoked. Evaluate the product's supported integration model and approve only the least-privilege application type and rights. OAuth apps and GitHub Apps have different authorization models, token scopes and installation permission boundaries.
F:Evaluate the product's supported integration model and approve only the least-privilege application type and rights. OAuth apps and GitHub Apps have different authorization models, token scopes and installation permission boundaries. The integration accesses only approved resources and its permission grant can be independently reviewed and revoked.
Incorrect Answers
C:Unauthorized reference rewrites are rejected while approved releases continue to reference reviewed commits. It would not independently demonstrate that the control works: A security reviewer treats third-party OAuth application authorization as identical to a scoped GitHub App installation request. The integration accesses only approved resources and its permission grant can be independently reviewed and revoked. Evaluate the product's supported integration model and approve only the least-privilege application type and rights.
D:Dependency vulnerability alerts depend on supported dependency identification and security configurations at the correct repository scope. It is not the rule that supports the proposed change and acceptance test: A security reviewer treats third-party OAuth application authorization as identical to a scoped GitHub App installation request. OAuth apps and GitHub Apps have different authorization models, token scopes and installation permission boundaries. Evaluate the product's supported integration model and approve only the least-privilege application type and rights.
E:Require validated triage categories with documented revocation and exception decisions for exposed tokens. It does not implement the governing rule for this approval: A security reviewer treats third-party OAuth application authorization as identical to a scoped GitHub App installation request. Evaluate the product's supported integration model and approve only the least-privilege application type and rights. The integration accesses only approved resources and its permission grant can be independently reviewed and revoked.
Question 361
GitHub Enterprise administration scenario — Constrain a GitHub App to selected repositories. In an enterprise development environment: A bot needs to comment on pull requests for one platform repository but the installation is granted access to all enterprise repositories. The administrator must identify the controlling access, governance or platform principle rather than an unrelated configuration fix. Which principle BEST addresses this condition? Choose ONE best answer.
- Dismissing security findings requires a recorded technical rationale and approval appropriate to organizational risk appetite.
- GitHub App installation repository selection and granular permissions should match the integration's legitimate service boundary.
- Visibility and repository creation settings must reflect effective organization or enterprise policy rather than verbal guidance.
- Compliance evidence should establish effective control coverage across the actual governed scope, not only the intended policy.
Explanation
Correct Answer
B:GitHub App installation repository selection and granular permissions should match the integration's legitimate service boundary. Review the app manifest permissions, selected repositories and the organization policy controlling installations. Limit the installation to the required repository with only the necessary issues or pull request permissions.
Incorrect Answers
A:Dismissing security findings requires a recorded technical rationale and approval appropriate to organizational risk appetite. It does not govern the condition described: A bot needs to comment on pull requests for one platform repository but the installation is granted access to all enterprise repositories. GitHub App installation repository selection and granular permissions should match the integration's legitimate service boundary.
C:Visibility and repository creation settings must reflect effective organization or enterprise policy rather than verbal guidance. It does not govern the condition described: A bot needs to comment on pull requests for one platform repository but the installation is granted access to all enterprise repositories. GitHub App installation repository selection and granular permissions should match the integration's legitimate service boundary.
D:Compliance evidence should establish effective control coverage across the actual governed scope, not only the intended policy. It does not govern the condition described: A bot needs to comment on pull requests for one platform repository but the installation is granted access to all enterprise repositories. GitHub App installation repository selection and granular permissions should match the integration's legitimate service boundary.
Question 362
GitHub Enterprise administration scenario — Constrain a GitHub App to selected repositories. In an enterprise development environment: A bot needs to comment on pull requests for one platform repository but the installation is granted access to all enterprise repositories. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Inspect alert evidence, affected execution path, dismissal reason and the repository's triage policy.
- Determine affected file content, publication duration, forks, caches and any included credentials or personal data.
- Review the app manifest permissions, selected repositories and the organization policy controlling installations.
- Inspect sanitized sample key structure, false-positive likelihood and existing scanner pattern capabilities.
Explanation
Correct Answer
C:Review the app manifest permissions, selected repositories and the organization policy controlling installations. GitHub App installation repository selection and granular permissions should match the integration's legitimate service boundary. Limit the installation to the required repository with only the necessary issues or pull request permissions.
Incorrect Answers
A:Inspect alert evidence, affected execution path, dismissal reason and the repository's triage policy. That check would not establish the decisive facts for this condition: A bot needs to comment on pull requests for one platform repository but the installation is granted access to all enterprise repositories. Review the app manifest permissions, selected repositories and the organization policy controlling installations.
B:Determine affected file content, publication duration, forks, caches and any included credentials or personal data. That check would not establish the decisive facts for this condition: A bot needs to comment on pull requests for one platform repository but the installation is granted access to all enterprise repositories. Review the app manifest permissions, selected repositories and the organization policy controlling installations.
D:Inspect sanitized sample key structure, false-positive likelihood and existing scanner pattern capabilities. That check would not establish the decisive facts for this condition: A bot needs to comment on pull requests for one platform repository but the installation is granted access to all enterprise repositories. Review the app manifest permissions, selected repositories and the organization policy controlling installations.
Question 363
GitHub Enterprise administration scenario — Constrain a GitHub App to selected repositories. In an enterprise development environment: A bot needs to comment on pull requests for one platform repository but the installation is granted access to all enterprise repositories. The enterprise administrator needs a least-privilege corrective change with accountable approval and rollback. Which action BEST resolves the reported GitHub configuration or governance problem? Choose ONE best answer.
- Limit the installation to the required repository with only the necessary issues or pull request permissions.
- Open an appropriately scoped private security advisory and coordinate a tested fix before authorized public disclosure.
- Revoke and replace the token promptly, contain abuse, and plan any history remediation with authorized owners.
- Create or choose an authorized GitHub App with least-privilege permissions and documented credential rotation.
Explanation
Correct Answer
A:Limit the installation to the required repository with only the necessary issues or pull request permissions. Review the app manifest permissions, selected repositories and the organization policy controlling installations. The bot comments in its assigned repository and access checks fail for unrelated private repositories.
Incorrect Answers
B:Open an appropriately scoped private security advisory and coordinate a tested fix before authorized public disclosure. That change would leave the reported problem unresolved: A bot needs to comment on pull requests for one platform repository but the installation is granted access to all enterprise repositories. Limit the installation to the required repository with only the necessary issues or pull request permissions.
C:Revoke and replace the token promptly, contain abuse, and plan any history remediation with authorized owners. That change would leave the reported problem unresolved: A bot needs to comment on pull requests for one platform repository but the installation is granted access to all enterprise repositories. Limit the installation to the required repository with only the necessary issues or pull request permissions.
D:Create or choose an authorized GitHub App with least-privilege permissions and documented credential rotation. That change would leave the reported problem unresolved: A bot needs to comment on pull requests for one platform repository but the installation is granted access to all enterprise repositories. Limit the installation to the required repository with only the necessary issues or pull request permissions.
Question 364
GitHub Enterprise administration scenario — Constrain a GitHub App to selected repositories. In an enterprise development environment: A bot needs to comment on pull requests for one platform repository but the installation is granted access to all enterprise repositories. The change reviewer separates a justified investigation from a merely plausible fix. Select EXACTLY TWO: the decisive diagnostic evidence required BEFORE change and the independent successful result that must be verified AFTER change.
- The bot comments in its assigned repository and access checks fail for unrelated private repositories.
- Inventory organizations, active rulesets, security configuration exceptions and audit evidence locations.
- Inspect the vulnerable dependency manifest, available patched version, Dependabot configuration and test coverage.
- Every sampled alert has a defensible resolved status and still-active compromised credentials are revoked.
- Review the app manifest permissions, selected repositories and the organization policy controlling installations.
Explanation
Correct Answers
A:The bot comments in its assigned repository and access checks fail for unrelated private repositories. Review the app manifest permissions, selected repositories and the organization policy controlling installations. GitHub App installation repository selection and granular permissions should match the integration's legitimate service boundary.
E:Review the app manifest permissions, selected repositories and the organization policy controlling installations. The bot comments in its assigned repository and access checks fail for unrelated private repositories. Limit the installation to the required repository with only the necessary issues or pull request permissions.
Incorrect Answers
B:Inventory organizations, active rulesets, security configuration exceptions and audit evidence locations. It would not provide the evidence needed for the paired diagnosis and follow-up: A bot needs to comment on pull requests for one platform repository but the installation is granted access to all enterprise repositories. Review the app manifest permissions, selected repositories and the organization policy controlling installations. The bot comments in its assigned repository and access checks fail for unrelated private repositories.
C:Inspect the vulnerable dependency manifest, available patched version, Dependabot configuration and test coverage. It would not provide the evidence needed for the paired diagnosis and follow-up: A bot needs to comment on pull requests for one platform repository but the installation is granted access to all enterprise repositories. Review the app manifest permissions, selected repositories and the organization policy controlling installations. The bot comments in its assigned repository and access checks fail for unrelated private repositories.
D:Every sampled alert has a defensible resolved status and still-active compromised credentials are revoked. It would not verify whether the proposed change works: A bot needs to comment on pull requests for one platform repository but the installation is granted access to all enterprise repositories. The bot comments in its assigned repository and access checks fail for unrelated private repositories. Limit the installation to the required repository with only the necessary issues or pull request permissions.
Question 365
GitHub Enterprise administration scenario — Constrain a GitHub App to selected repositories. In an enterprise development environment: A bot needs to comment on pull requests for one platform repository but the installation is granted access to all enterprise repositories. A controlled enterprise configuration review requires a coherent rationale, approved change and confirmed outcome. Select EXACTLY THREE: the governing GitHub administration principle, the proportionate authorized intervention AND the independently observable outcome for this scenario.
- Configure supported audit log streaming into a controlled security repository with health monitoring and access boundaries.
- Successful scheduling is not evidence that compiled-language analysis completed successfully.
- The bot comments in its assigned repository and access checks fail for unrelated private repositories.
- Limit the installation to the required repository with only the necessary issues or pull request permissions.
- Every sampled alert has a defensible resolved status and still-active compromised credentials are revoked.
- GitHub App installation repository selection and granular permissions should match the integration's legitimate service boundary.
Explanation
Correct Answers
C:The bot comments in its assigned repository and access checks fail for unrelated private repositories. Limit the installation to the required repository with only the necessary issues or pull request permissions. GitHub App installation repository selection and granular permissions should match the integration's legitimate service boundary.
D:Limit the installation to the required repository with only the necessary issues or pull request permissions. GitHub App installation repository selection and granular permissions should match the integration's legitimate service boundary. The bot comments in its assigned repository and access checks fail for unrelated private repositories.
F:GitHub App installation repository selection and granular permissions should match the integration's legitimate service boundary. Limit the installation to the required repository with only the necessary issues or pull request permissions. The bot comments in its assigned repository and access checks fail for unrelated private repositories.
Incorrect Answers
A:Configure supported audit log streaming into a controlled security repository with health monitoring and access boundaries. It does not implement the governing rule for this approval: A bot needs to comment on pull requests for one platform repository but the installation is granted access to all enterprise repositories. Limit the installation to the required repository with only the necessary issues or pull request permissions. The bot comments in its assigned repository and access checks fail for unrelated private repositories.
B:Successful scheduling is not evidence that compiled-language analysis completed successfully. It is not the rule that supports the proposed change and acceptance test: A bot needs to comment on pull requests for one platform repository but the installation is granted access to all enterprise repositories. GitHub App installation repository selection and granular permissions should match the integration's legitimate service boundary. Limit the installation to the required repository with only the necessary issues or pull request permissions.
E:Every sampled alert has a defensible resolved status and still-active compromised credentials are revoked. It would not independently demonstrate that the control works: A bot needs to comment on pull requests for one platform repository but the installation is granted access to all enterprise repositories. The bot comments in its assigned repository and access checks fail for unrelated private repositories. Limit the installation to the required repository with only the necessary issues or pull request permissions.
Question 366
GitHub Enterprise administration scenario — Rotate compromised GitHub App credentials. In an enterprise development environment: An application administrator finds a leaked private key used to mint GitHub App installation tokens and proposes waiting for existing tokens to expire. The administrator must identify the controlling access, governance or platform principle rather than an unrelated configuration fix. Which principle BEST addresses this condition? Choose ONE best answer.
- Push protection reduces exposure by blocking supported detected secrets before a push completes, subject to available controls and approved bypasses.
- Ruleset bypass is a deliberate exception capability and needs tightly limited authorization and auditability.
- Effective security compliance should be demonstrated through current repository policy and audit data rather than self-attestation alone.
- Compromise of an app credential calls for immediate containment and rotation of the underlying signing material.
Explanation
Correct Answer
D:Compromise of an app credential calls for immediate containment and rotation of the underlying signing material. Assess the key identity, installed app permissions, issued token activity and supported key rotation window. Rotate or revoke the exposed app private key, investigate token activity and update the application secret store.
Incorrect Answers
A:Push protection reduces exposure by blocking supported detected secrets before a push completes, subject to available controls and approved bypasses. It does not govern the condition described: An application administrator finds a leaked private key used to mint GitHub App installation tokens and proposes waiting for existing tokens to expire. Compromise of an app credential calls for immediate containment and rotation of the underlying signing material.
B:Ruleset bypass is a deliberate exception capability and needs tightly limited authorization and auditability. It does not govern the condition described: An application administrator finds a leaked private key used to mint GitHub App installation tokens and proposes waiting for existing tokens to expire. Compromise of an app credential calls for immediate containment and rotation of the underlying signing material.
C:Effective security compliance should be demonstrated through current repository policy and audit data rather than self-attestation alone. It does not govern the condition described: An application administrator finds a leaked private key used to mint GitHub App installation tokens and proposes waiting for existing tokens to expire. Compromise of an app credential calls for immediate containment and rotation of the underlying signing material.
Question 367
GitHub Enterprise administration scenario — Rotate compromised GitHub App credentials. In an enterprise development environment: An application administrator finds a leaked private key used to mint GitHub App installation tokens and proposes waiting for existing tokens to expire. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Inventory organizations, active rulesets, security configuration exceptions and audit evidence locations.
- Examine requested scopes, app publisher trust, data handling and the workflow's legitimate API needs.
- Assess the key identity, installed app permissions, issued token activity and supported key rotation window.
- Inspect the vulnerable dependency manifest, available patched version, Dependabot configuration and test coverage.
Explanation
Correct Answer
C:Assess the key identity, installed app permissions, issued token activity and supported key rotation window. Compromise of an app credential calls for immediate containment and rotation of the underlying signing material. Rotate or revoke the exposed app private key, investigate token activity and update the application secret store.
Incorrect Answers
A:Inventory organizations, active rulesets, security configuration exceptions and audit evidence locations. That check would not establish the decisive facts for this condition: An application administrator finds a leaked private key used to mint GitHub App installation tokens and proposes waiting for existing tokens to expire. Assess the key identity, installed app permissions, issued token activity and supported key rotation window.
B:Examine requested scopes, app publisher trust, data handling and the workflow's legitimate API needs. That check would not establish the decisive facts for this condition: An application administrator finds a leaked private key used to mint GitHub App installation tokens and proposes waiting for existing tokens to expire. Assess the key identity, installed app permissions, issued token activity and supported key rotation window.
D:Inspect the vulnerable dependency manifest, available patched version, Dependabot configuration and test coverage. That check would not establish the decisive facts for this condition: An application administrator finds a leaked private key used to mint GitHub App installation tokens and proposes waiting for existing tokens to expire. Assess the key identity, installed app permissions, issued token activity and supported key rotation window.
Question 368
GitHub Enterprise administration scenario — Rotate compromised GitHub App credentials. In an enterprise development environment: An application administrator finds a leaked private key used to mint GitHub App installation tokens and proposes waiting for existing tokens to expire. The enterprise administrator needs a least-privilege corrective change with accountable approval and rollback. Which action BEST resolves the reported GitHub configuration or governance problem? Choose ONE best answer.
- Rotate or revoke the exposed app private key, investigate token activity and update the application secret store.
- Build a reproducible evidence collection workflow with reviewed exceptions and restricted access to exported results.
- Evaluate the product's supported integration model and approve only the least-privilege application type and rights.
- Limit the installation to the required repository with only the necessary issues or pull request permissions.
Explanation
Correct Answer
A:Rotate or revoke the exposed app private key, investigate token activity and update the application secret store. Assess the key identity, installed app permissions, issued token activity and supported key rotation window. A test installation token signed through the new approved key works and the compromised key is unusable.
Incorrect Answers
B:Build a reproducible evidence collection workflow with reviewed exceptions and restricted access to exported results. That change would leave the reported problem unresolved: An application administrator finds a leaked private key used to mint GitHub App installation tokens and proposes waiting for existing tokens to expire. Rotate or revoke the exposed app private key, investigate token activity and update the application secret store.
C:Evaluate the product's supported integration model and approve only the least-privilege application type and rights. That change would leave the reported problem unresolved: An application administrator finds a leaked private key used to mint GitHub App installation tokens and proposes waiting for existing tokens to expire. Rotate or revoke the exposed app private key, investigate token activity and update the application secret store.
D:Limit the installation to the required repository with only the necessary issues or pull request permissions. That change would leave the reported problem unresolved: An application administrator finds a leaked private key used to mint GitHub App installation tokens and proposes waiting for existing tokens to expire. Rotate or revoke the exposed app private key, investigate token activity and update the application secret store.
Question 369
GitHub Enterprise administration scenario — Rotate compromised GitHub App credentials. In an enterprise development environment: An application administrator finds a leaked private key used to mint GitHub App installation tokens and proposes waiting for existing tokens to expire. The change reviewer separates a justified investigation from a merely plausible fix. Select EXACTLY TWO: the decisive diagnostic evidence required BEFORE change and the independent successful result that must be verified AFTER change.
- Review the documents' classification, enterprise audience permitted by internal visibility and alternative private access roles.
- A test installation token signed through the new approved key works and the compromised key is unusable.
- Sample existing and new repositories have the required supported scanning controls or documented exceptions.
- Assess the key identity, installed app permissions, issued token activity and supported key rotation window.
- Check dependency graph visibility, package manifest coverage, alert settings and relevant organization security policies.
Explanation
Correct Answers
B:A test installation token signed through the new approved key works and the compromised key is unusable. Assess the key identity, installed app permissions, issued token activity and supported key rotation window. Compromise of an app credential calls for immediate containment and rotation of the underlying signing material.
D:Assess the key identity, installed app permissions, issued token activity and supported key rotation window. A test installation token signed through the new approved key works and the compromised key is unusable. Rotate or revoke the exposed app private key, investigate token activity and update the application secret store.
Incorrect Answers
A:Review the documents' classification, enterprise audience permitted by internal visibility and alternative private access roles. It would not provide the evidence needed for the paired diagnosis and follow-up: An application administrator finds a leaked private key used to mint GitHub App installation tokens and proposes waiting for existing tokens to expire. Assess the key identity, installed app permissions, issued token activity and supported key rotation window. A test installation token signed through the new approved key works and the compromised key is unusable.
C:Sample existing and new repositories have the required supported scanning controls or documented exceptions. It would not verify whether the proposed change works: An application administrator finds a leaked private key used to mint GitHub App installation tokens and proposes waiting for existing tokens to expire. A test installation token signed through the new approved key works and the compromised key is unusable. Rotate or revoke the exposed app private key, investigate token activity and update the application secret store.
E:Check dependency graph visibility, package manifest coverage, alert settings and relevant organization security policies. It would not provide the evidence needed for the paired diagnosis and follow-up: An application administrator finds a leaked private key used to mint GitHub App installation tokens and proposes waiting for existing tokens to expire. Assess the key identity, installed app permissions, issued token activity and supported key rotation window. A test installation token signed through the new approved key works and the compromised key is unusable.
Question 370
GitHub Enterprise administration scenario — Rotate compromised GitHub App credentials. In an enterprise development environment: An application administrator finds a leaked private key used to mint GitHub App installation tokens and proposes waiting for existing tokens to expire. A controlled enterprise configuration review requires a coherent rationale, approved change and confirmed outcome. Select EXACTLY THREE: the governing GitHub administration principle, the proportionate authorized intervention AND the independently observable outcome for this scenario.
- Rotate or revoke the exposed app private key, investigate token activity and update the application secret store.
- Dependency graph completeness depends on supported manifests and any required submission or extraction configuration.
- Apply a centrally approved policy baseline and allow only formally approved supported exceptions.
- A test installation token signed through the new approved key works and the compromised key is unusable.
- The integration accesses only approved resources and its permission grant can be independently reviewed and revoked.
- Compromise of an app credential calls for immediate containment and rotation of the underlying signing material.
Explanation
Correct Answers
A:Rotate or revoke the exposed app private key, investigate token activity and update the application secret store. Compromise of an app credential calls for immediate containment and rotation of the underlying signing material. A test installation token signed through the new approved key works and the compromised key is unusable.
D:A test installation token signed through the new approved key works and the compromised key is unusable. Rotate or revoke the exposed app private key, investigate token activity and update the application secret store. Compromise of an app credential calls for immediate containment and rotation of the underlying signing material.
F:Compromise of an app credential calls for immediate containment and rotation of the underlying signing material. Rotate or revoke the exposed app private key, investigate token activity and update the application secret store. A test installation token signed through the new approved key works and the compromised key is unusable.
Incorrect Answers
B:Dependency graph completeness depends on supported manifests and any required submission or extraction configuration. It is not the rule that supports the proposed change and acceptance test: An application administrator finds a leaked private key used to mint GitHub App installation tokens and proposes waiting for existing tokens to expire. Compromise of an app credential calls for immediate containment and rotation of the underlying signing material. Rotate or revoke the exposed app private key, investigate token activity and update the application secret store.
C:Apply a centrally approved policy baseline and allow only formally approved supported exceptions. It does not implement the governing rule for this approval: An application administrator finds a leaked private key used to mint GitHub App installation tokens and proposes waiting for existing tokens to expire. Rotate or revoke the exposed app private key, investigate token activity and update the application secret store. A test installation token signed through the new approved key works and the compromised key is unusable.
E:The integration accesses only approved resources and its permission grant can be independently reviewed and revoked. It would not independently demonstrate that the control works: An application administrator finds a leaked private key used to mint GitHub App installation tokens and proposes waiting for existing tokens to expire. A test installation token signed through the new approved key works and the compromised key is unusable. Rotate or revoke the exposed app private key, investigate token activity and update the application secret store.