Microsoft GH-100 Practice Test 38
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.
Question 371
GitHub Enterprise administration scenario — Handle API rate limiting safely in integrations. In an enterprise development environment: An inventory integration gets HTTP rate-limit responses and engineers propose parallel retries with more personal tokens to force completion. 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.
- API rate-limit protections require respectful backoff and efficient requests, not credential multiplication to evade governance.
- Third-party OAuth app access should be evaluated against actual capabilities, ownership and enterprise application policy.
- Dependency graph completeness depends on supported manifests and any required submission or extraction configuration.
- Enterprise security governance needs risk-tiered alert owners and observable remediation accountability.
Explanation
Correct Answer
A:API rate-limit protections require respectful backoff and efficient requests, not credential multiplication to evade governance. Compare response status and headers, request volume, retry behavior and relevant authenticated caller limits. Implement supported conditional polling, caching and retry-after or backoff handling with monitored budgets.
Incorrect Answers
B:Third-party OAuth app access should be evaluated against actual capabilities, ownership and enterprise application policy. It does not govern the condition described: An inventory integration gets HTTP rate-limit responses and engineers propose parallel retries with more personal tokens to force completion. API rate-limit protections require respectful backoff and efficient requests, not credential multiplication to evade governance.
C:Dependency graph completeness depends on supported manifests and any required submission or extraction configuration. It does not govern the condition described: An inventory integration gets HTTP rate-limit responses and engineers propose parallel retries with more personal tokens to force completion. API rate-limit protections require respectful backoff and efficient requests, not credential multiplication to evade governance.
D:Enterprise security governance needs risk-tiered alert owners and observable remediation accountability. It does not govern the condition described: An inventory integration gets HTTP rate-limit responses and engineers propose parallel retries with more personal tokens to force completion. API rate-limit protections require respectful backoff and efficient requests, not credential multiplication to evade governance.
Question 372
GitHub Enterprise administration scenario — Handle API rate limiting safely in integrations. In an enterprise development environment: An inventory integration gets HTTP rate-limit responses and engineers propose parallel retries with more personal tokens to force completion. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Compare response status and headers, request volume, retry behavior and relevant authenticated caller limits.
- Determine affected file content, publication duration, forks, caches and any included credentials or personal data.
- Inspect existing branch and tag rulesets, active bypass actors and the release process's published refs.
- Inspect enterprise repository creation rules, organization-level permissions and a nonprivileged test member's options.
Explanation
Correct Answer
A:Compare response status and headers, request volume, retry behavior and relevant authenticated caller limits. API rate-limit protections require respectful backoff and efficient requests, not credential multiplication to evade governance. Implement supported conditional polling, caching and retry-after or backoff handling with monitored budgets.
Incorrect Answers
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: An inventory integration gets HTTP rate-limit responses and engineers propose parallel retries with more personal tokens to force completion. Compare response status and headers, request volume, retry behavior and relevant authenticated caller limits.
C:Inspect existing branch and tag rulesets, active bypass actors and the release process's published refs. That check would not establish the decisive facts for this condition: An inventory integration gets HTTP rate-limit responses and engineers propose parallel retries with more personal tokens to force completion. Compare response status and headers, request volume, retry behavior and relevant authenticated caller limits.
D:Inspect enterprise repository creation rules, organization-level permissions and a nonprivileged test member's options. That check would not establish the decisive facts for this condition: An inventory integration gets HTTP rate-limit responses and engineers propose parallel retries with more personal tokens to force completion. Compare response status and headers, request volume, retry behavior and relevant authenticated caller limits.
Question 373
GitHub Enterprise administration scenario — Handle API rate limiting safely in integrations. In an enterprise development environment: An inventory integration gets HTTP rate-limit responses and engineers propose parallel retries with more personal tokens to force completion. 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.
- Enable appropriate external collection before incidents and document search sources by event type.
- Implement supported conditional polling, caching and retry-after or backoff handling with monitored budgets.
- Enable a supported default code-scanning setup for the repository and confirm its language coverage with security owners.
- Require validated triage categories with documented revocation and exception decisions for exposed tokens.
Explanation
Correct Answer
B:Implement supported conditional polling, caching and retry-after or backoff handling with monitored budgets. Compare response status and headers, request volume, retry behavior and relevant authenticated caller limits. The job eventually completes within allowed API budgets without aggressive retry storms.
Incorrect Answers
A:Enable appropriate external collection before incidents and document search sources by event type. That change would leave the reported problem unresolved: An inventory integration gets HTTP rate-limit responses and engineers propose parallel retries with more personal tokens to force completion. Implement supported conditional polling, caching and retry-after or backoff handling with monitored budgets.
C:Enable a supported default code-scanning setup for the repository and confirm its language coverage with security owners. That change would leave the reported problem unresolved: An inventory integration gets HTTP rate-limit responses and engineers propose parallel retries with more personal tokens to force completion. Implement supported conditional polling, caching and retry-after or backoff handling with monitored budgets.
D:Require validated triage categories with documented revocation and exception decisions for exposed tokens. That change would leave the reported problem unresolved: An inventory integration gets HTTP rate-limit responses and engineers propose parallel retries with more personal tokens to force completion. Implement supported conditional polling, caching and retry-after or backoff handling with monitored budgets.
Question 374
GitHub Enterprise administration scenario — Handle API rate limiting safely in integrations. In an enterprise development environment: An inventory integration gets HTTP rate-limit responses and engineers propose parallel retries with more personal tokens to force completion. 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.
- A fork PR can run safe checks but cannot access production deployment credentials.
- Compare response status and headers, request volume, retry behavior and relevant authenticated caller limits.
- Trace workflow build logs, language-specific extraction, required toolchains and generated-source steps.
- The job eventually completes within allowed API budgets without aggressive retry storms.
- Review available enterprise audit streaming options, required API events, source IP visibility and SIEM retention.
Explanation
Correct Answers
B:Compare response status and headers, request volume, retry behavior and relevant authenticated caller limits. The job eventually completes within allowed API budgets without aggressive retry storms. Implement supported conditional polling, caching and retry-after or backoff handling with monitored budgets.
D:The job eventually completes within allowed API budgets without aggressive retry storms. Compare response status and headers, request volume, retry behavior and relevant authenticated caller limits. API rate-limit protections require respectful backoff and efficient requests, not credential multiplication to evade governance.
Incorrect Answers
A:A fork PR can run safe checks but cannot access production deployment credentials. It would not verify whether the proposed change works: An inventory integration gets HTTP rate-limit responses and engineers propose parallel retries with more personal tokens to force completion. The job eventually completes within allowed API budgets without aggressive retry storms. Implement supported conditional polling, caching and retry-after or backoff handling with monitored budgets.
C:Trace workflow build logs, language-specific extraction, required toolchains and generated-source steps. It would not provide the evidence needed for the paired diagnosis and follow-up: An inventory integration gets HTTP rate-limit responses and engineers propose parallel retries with more personal tokens to force completion. Compare response status and headers, request volume, retry behavior and relevant authenticated caller limits. The job eventually completes within allowed API budgets without aggressive retry storms.
E:Review available enterprise audit streaming options, required API events, source IP visibility and SIEM retention. It would not provide the evidence needed for the paired diagnosis and follow-up: An inventory integration gets HTTP rate-limit responses and engineers propose parallel retries with more personal tokens to force completion. Compare response status and headers, request volume, retry behavior and relevant authenticated caller limits. The job eventually completes within allowed API budgets without aggressive retry storms.
Question 375
GitHub Enterprise administration scenario — Handle API rate limiting safely in integrations. In an enterprise development environment: An inventory integration gets HTTP rate-limit responses and engineers propose parallel retries with more personal tokens to force completion. 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.
- Implement supported conditional polling, caching and retry-after or backoff handling with monitored budgets.
- API rate-limit protections require respectful backoff and efficient requests, not credential multiplication to evade governance.
- Contain repository exposure, rotate embedded secrets and follow the legal and security incident response process.
- Sample existing and new repositories have the required supported scanning controls or documented exceptions.
- Ruleset bypass is a deliberate exception capability and needs tightly limited authorization and auditability.
- The job eventually completes within allowed API budgets without aggressive retry storms.
Explanation
Correct Answers
A:Implement supported conditional polling, caching and retry-after or backoff handling with monitored budgets. API rate-limit protections require respectful backoff and efficient requests, not credential multiplication to evade governance. The job eventually completes within allowed API budgets without aggressive retry storms.
B:API rate-limit protections require respectful backoff and efficient requests, not credential multiplication to evade governance. Implement supported conditional polling, caching and retry-after or backoff handling with monitored budgets. The job eventually completes within allowed API budgets without aggressive retry storms.
F:The job eventually completes within allowed API budgets without aggressive retry storms. Implement supported conditional polling, caching and retry-after or backoff handling with monitored budgets. API rate-limit protections require respectful backoff and efficient requests, not credential multiplication to evade governance.
Incorrect Answers
C:Contain repository exposure, rotate embedded secrets and follow the legal and security incident response process. It does not implement the governing rule for this approval: An inventory integration gets HTTP rate-limit responses and engineers propose parallel retries with more personal tokens to force completion. Implement supported conditional polling, caching and retry-after or backoff handling with monitored budgets. The job eventually completes within allowed API budgets without aggressive retry storms.
D:Sample existing and new repositories have the required supported scanning controls or documented exceptions. It would not independently demonstrate that the control works: An inventory integration gets HTTP rate-limit responses and engineers propose parallel retries with more personal tokens to force completion. The job eventually completes within allowed API budgets without aggressive retry storms. Implement supported conditional polling, caching and retry-after or backoff handling with monitored budgets.
E:Ruleset bypass is a deliberate exception capability and needs tightly limited authorization and auditability. It is not the rule that supports the proposed change and acceptance test: An inventory integration gets HTTP rate-limit responses and engineers propose parallel retries with more personal tokens to force completion. API rate-limit protections require respectful backoff and efficient requests, not credential multiplication to evade governance. Implement supported conditional polling, caching and retry-after or backoff handling with monitored budgets.
Question 376
GitHub Enterprise administration scenario — Deny an OAuth integration that requests excessive account scope. In an enterprise development environment: A browser extension requests broad profile, organization and repository access to provide a simple issue-labeling shortcut. 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.
- Third-party OAuth app access should be evaluated against actual capabilities, ownership and enterprise application policy.
- App-based installation identity separates automated service authorization from individual employee lifecycle while supporting scoped permissions.
- Successful scheduling is not evidence that compiled-language analysis completed successfully.
- Security response should contain the exposed collaborator identity while preserving incident evidence and reviewing actual repository access.
Explanation
Correct Answer
A:Third-party OAuth app access should be evaluated against actual capabilities, ownership and enterprise application policy. Examine requested scopes, app publisher trust, data handling and the workflow's legitimate API needs. Deny the excessive authorization and suggest a reviewed narrower integration or native repository automation.
Incorrect Answers
B:App-based installation identity separates automated service authorization from individual employee lifecycle while supporting scoped permissions. It does not govern the condition described: A browser extension requests broad profile, organization and repository access to provide a simple issue-labeling shortcut. Third-party OAuth app access should be evaluated against actual capabilities, ownership and enterprise application policy.
C:Successful scheduling is not evidence that compiled-language analysis completed successfully. It does not govern the condition described: A browser extension requests broad profile, organization and repository access to provide a simple issue-labeling shortcut. Third-party OAuth app access should be evaluated against actual capabilities, ownership and enterprise application policy.
D:Security response should contain the exposed collaborator identity while preserving incident evidence and reviewing actual repository access. It does not govern the condition described: A browser extension requests broad profile, organization and repository access to provide a simple issue-labeling shortcut. Third-party OAuth app access should be evaluated against actual capabilities, ownership and enterprise application policy.
Question 377
GitHub Enterprise administration scenario — Deny an OAuth integration that requests excessive account scope. In an enterprise development environment: A browser extension requests broad profile, organization and repository access to provide a simple issue-labeling shortcut. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Determine affected file content, publication duration, forks, caches and any included credentials or personal data.
- Examine requested scopes, app publisher trust, data handling and the workflow's legitimate API needs.
- Inspect enabled private reporting settings, maintainer contact procedures and the repository's security policy.
- Determine token validity, permission scope, committed history, exposure window and affected cloud-resource access logs.
Explanation
Correct Answer
B:Examine requested scopes, app publisher trust, data handling and the workflow's legitimate API needs. Third-party OAuth app access should be evaluated against actual capabilities, ownership and enterprise application policy. Deny the excessive authorization and suggest a reviewed narrower integration or native repository automation.
Incorrect Answers
A: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 browser extension requests broad profile, organization and repository access to provide a simple issue-labeling shortcut. Examine requested scopes, app publisher trust, data handling and the workflow's legitimate API needs.
C:Inspect enabled private reporting settings, maintainer contact procedures and the repository's security policy. That check would not establish the decisive facts for this condition: A browser extension requests broad profile, organization and repository access to provide a simple issue-labeling shortcut. Examine requested scopes, app publisher trust, data handling and the workflow's legitimate API needs.
D:Determine token validity, permission scope, committed history, exposure window and affected cloud-resource access logs. That check would not establish the decisive facts for this condition: A browser extension requests broad profile, organization and repository access to provide a simple issue-labeling shortcut. Examine requested scopes, app publisher trust, data handling and the workflow's legitimate API needs.
Question 378
GitHub Enterprise administration scenario — Deny an OAuth integration that requests excessive account scope. In an enterprise development environment: A browser extension requests broad profile, organization and repository access to provide a simple issue-labeling shortcut. 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.
- Enable supported push protection and establish a documented response for verified false positives and genuine exposures.
- Contain repository exposure, rotate embedded secrets and follow the legal and security incident response process.
- Require validated triage categories with documented revocation and exception decisions for exposed tokens.
- Deny the excessive authorization and suggest a reviewed narrower integration or native repository automation.
Explanation
Correct Answer
D:Deny the excessive authorization and suggest a reviewed narrower integration or native repository automation. Examine requested scopes, app publisher trust, data handling and the workflow's legitimate API needs. The user can complete required labeling without giving an untrusted extension access to confidential source.
Incorrect Answers
A:Enable supported push protection and establish a documented response for verified false positives and genuine exposures. That change would leave the reported problem unresolved: A browser extension requests broad profile, organization and repository access to provide a simple issue-labeling shortcut. Deny the excessive authorization and suggest a reviewed narrower integration or native repository automation.
B:Contain repository exposure, rotate embedded secrets and follow the legal and security incident response process. That change would leave the reported problem unresolved: A browser extension requests broad profile, organization and repository access to provide a simple issue-labeling shortcut. Deny the excessive authorization and suggest a reviewed narrower integration or native repository automation.
C:Require validated triage categories with documented revocation and exception decisions for exposed tokens. That change would leave the reported problem unresolved: A browser extension requests broad profile, organization and repository access to provide a simple issue-labeling shortcut. Deny the excessive authorization and suggest a reviewed narrower integration or native repository automation.
Question 379
GitHub Enterprise administration scenario — Deny an OAuth integration that requests excessive account scope. In an enterprise development environment: A browser extension requests broad profile, organization and repository access to provide a simple issue-labeling shortcut. 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 user can complete required labeling without giving an untrusted extension access to confidential source.
- Trace the failing API request through organization SSO policy, token settings, permissions and authentication logs.
- CodeQL successfully analyzes the intended modules and results appear under the correct repository security context.
- Inspect existing branch and tag rulesets, active bypass actors and the release process's published refs.
- Examine requested scopes, app publisher trust, data handling and the workflow's legitimate API needs.
Explanation
Correct Answers
A:The user can complete required labeling without giving an untrusted extension access to confidential source. Examine requested scopes, app publisher trust, data handling and the workflow's legitimate API needs. Third-party OAuth app access should be evaluated against actual capabilities, ownership and enterprise application policy.
E:Examine requested scopes, app publisher trust, data handling and the workflow's legitimate API needs. The user can complete required labeling without giving an untrusted extension access to confidential source. Deny the excessive authorization and suggest a reviewed narrower integration or native repository automation.
Incorrect Answers
B:Trace the failing API request through organization SSO policy, token settings, permissions and authentication logs. It would not provide the evidence needed for the paired diagnosis and follow-up: A browser extension requests broad profile, organization and repository access to provide a simple issue-labeling shortcut. Examine requested scopes, app publisher trust, data handling and the workflow's legitimate API needs. The user can complete required labeling without giving an untrusted extension access to confidential source.
C:CodeQL successfully analyzes the intended modules and results appear under the correct repository security context. It would not verify whether the proposed change works: A browser extension requests broad profile, organization and repository access to provide a simple issue-labeling shortcut. The user can complete required labeling without giving an untrusted extension access to confidential source. Deny the excessive authorization and suggest a reviewed narrower integration or native repository automation.
D:Inspect existing branch and tag rulesets, active bypass actors and the release process's published refs. It would not provide the evidence needed for the paired diagnosis and follow-up: A browser extension requests broad profile, organization and repository access to provide a simple issue-labeling shortcut. Examine requested scopes, app publisher trust, data handling and the workflow's legitimate API needs. The user can complete required labeling without giving an untrusted extension access to confidential source.
Question 380
GitHub Enterprise administration scenario — Deny an OAuth integration that requests excessive account scope. In an enterprise development environment: A browser extension requests broad profile, organization and repository access to provide a simple issue-labeling shortcut. 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.
- The user can complete required labeling without giving an untrusted extension access to confidential source.
- Fix dependency graph inputs or supported submission process and retest the nested component.
- Third-party OAuth app access should be evaluated against actual capabilities, ownership and enterprise application policy.
- Enterprise security governance needs risk-tiered alert owners and observable remediation accountability.
- Sample existing and new repositories have the required supported scanning controls or documented exceptions.
- Deny the excessive authorization and suggest a reviewed narrower integration or native repository automation.
Explanation
Correct Answers
A:The user can complete required labeling without giving an untrusted extension access to confidential source. Deny the excessive authorization and suggest a reviewed narrower integration or native repository automation. Third-party OAuth app access should be evaluated against actual capabilities, ownership and enterprise application policy.
C:Third-party OAuth app access should be evaluated against actual capabilities, ownership and enterprise application policy. Deny the excessive authorization and suggest a reviewed narrower integration or native repository automation. The user can complete required labeling without giving an untrusted extension access to confidential source.
F:Deny the excessive authorization and suggest a reviewed narrower integration or native repository automation. Third-party OAuth app access should be evaluated against actual capabilities, ownership and enterprise application policy. The user can complete required labeling without giving an untrusted extension access to confidential source.
Incorrect Answers
B:Fix dependency graph inputs or supported submission process and retest the nested component. It does not implement the governing rule for this approval: A browser extension requests broad profile, organization and repository access to provide a simple issue-labeling shortcut. Deny the excessive authorization and suggest a reviewed narrower integration or native repository automation. The user can complete required labeling without giving an untrusted extension access to confidential source.
D:Enterprise security governance needs risk-tiered alert owners and observable remediation accountability. It is not the rule that supports the proposed change and acceptance test: A browser extension requests broad profile, organization and repository access to provide a simple issue-labeling shortcut. Third-party OAuth app access should be evaluated against actual capabilities, ownership and enterprise application policy. Deny the excessive authorization and suggest a reviewed narrower integration or native repository automation.
E:Sample existing and new repositories have the required supported scanning controls or documented exceptions. It would not independently demonstrate that the control works: A browser extension requests broad profile, organization and repository access to provide a simple issue-labeling shortcut. The user can complete required labeling without giving an untrusted extension access to confidential source. Deny the excessive authorization and suggest a reviewed narrower integration or native repository automation.