|
26 | 26 | - content: "Team maintainer"
|
27 | 27 | isCorrect: true
|
28 | 28 | explanation: "Correct! As a team maintainer, the user can add and remove organization members to and from a team."
|
| 29 | + |
29 | 30 | - content: "As an organization owner, you want to ensure that everyone who is signed in to your corporate network can access the GitHub website without requiring a second sign-in. Which technology would you enable to accomplish this?"
|
30 | 31 | choices:
|
31 | 32 | - content: "Single sign-on"
|
|
40 | 41 | - content: "SSH keys"
|
41 | 42 | isCorrect: false
|
42 | 43 | explanation: "Incorrect. SSH keys provide access for the git client through a username and password. You don't use them to access the GitHub website."
|
| 44 | + |
43 | 45 | - content: "What's the appropriate repository permission level for contributors who need to actively push changes to your repository?"
|
44 | 46 | choices:
|
45 | 47 | - content: "Admin"
|
|
54 | 56 | - content: "Maintain"
|
55 | 57 | isCorrect: false
|
56 | 58 | explanation: "Incorrect. The maintain permission is for contributors who need to manage the repository without access to sensitive or destructive actions. It provides too much access for other users."
|
| 59 | + |
| 60 | + - content: "What is a benefit of integrating Active Directory (AD) for team synchronization?" |
| 61 | + choices: |
| 62 | + - content: "Centralized Identity Management" |
| 63 | + isCorrect: true |
| 64 | + explanation: "Correct. Integrating AD leverages existing infrastructure for consistent user identities." |
| 65 | + - content: "Increased administrative overhead" |
| 66 | + isCorrect: false |
| 67 | + explanation: "Incorrect. AD integration aims to reduce administrative overhead." |
| 68 | + - content: "Decentralized administration" |
| 69 | + isCorrect: false |
| 70 | + explanation: "Incorrect. AD integration centralizes identity management." |
| 71 | + - content: "Enhanced isolation" |
| 72 | + isCorrect: false |
| 73 | + explanation: "Incorrect. Enhanced isolation is not a direct benefit of AD integration." |
| 74 | + |
| 75 | + - content: "Which of the following actions is exclusive to Organization Owners in GitHub?" |
| 76 | + choices: |
| 77 | + - content: "Collaborate on repositories based on assigned roles or team memberships" |
| 78 | + isCorrect: false |
| 79 | + explanation: "Incorrect. Organization Members can collaborate on repositories if granted the appropriate roles or added to teams." |
| 80 | + - content: "Contribute code and participate in discussions" |
| 81 | + isCorrect: false |
| 82 | + explanation: "Incorrect. Any Organization Member with sufficient permissions can contribute code and join discussions." |
| 83 | + - content: "Manage organization settings, including security and billing" |
| 84 | + isCorrect: true |
| 85 | + explanation: "Correct. Only Organization Owners have the authority to manage organization-wide settings, including security policies and billing configurations." |
| 86 | + - content: "Access resources as defined by team or repository-specific permissions" |
| 87 | + isCorrect: false |
| 88 | + explanation: "Incorrect. Organization Members can access resources if permissions are granted through team or repository-level settings." |
| 89 | + |
| 90 | + - content: "What is a key difference between an organization member and an outside collaborator?" |
| 91 | + choices: |
| 92 | + - content: "Organization members are included in the organization’s internal directory." |
| 93 | + isCorrect: true |
| 94 | + explanation: "Correct. Organization members are included in the internal directory and can be assigned to teams, while outside collaborators are not." |
| 95 | + - content: "Outside collaborators have access to all repositories." |
| 96 | + isCorrect: false |
| 97 | + explanation: "Incorrect. Outside collaborators have explicit access to specific repositories only." |
| 98 | + - content: "Organization members do not appear in the organization’s internal member list." |
| 99 | + isCorrect: false |
| 100 | + explanation: "Incorrect. Organization members do appear in the internal member list." |
| 101 | + - content: "Outside collaborators inherit organization-wide settings." |
| 102 | + isCorrect: false |
| 103 | + explanation: "Incorrect. Outside collaborators do not inherit organization-wide settings." |
| 104 | + |
| 105 | + - content: "Which permission level allows users to manage repository settings but not delete or transfer the repository?" |
| 106 | + choices: |
| 107 | + - content: "Maintain" |
| 108 | + isCorrect: true |
| 109 | + explanation: "Correct. The Maintain permission level allows users to manage repository settings but not delete or transfer the repository." |
| 110 | + - content: "Write" |
| 111 | + isCorrect: false |
| 112 | + explanation: "Incorrect. The Write permission level allows users to push code and manage issues and pull requests but not manage repository settings." |
| 113 | + - content: "Admin" |
| 114 | + isCorrect: false |
| 115 | + explanation: "Incorrect. The Admin permission level grants full control over the repository, including deleting or transferring it." |
| 116 | + - content: "Triage" |
| 117 | + isCorrect: false |
| 118 | + explanation: "Incorrect. The Triage permission level allows users to manage issues and pull requests but not manage repository settings." |
0 commit comments