Free AZ-400 Exam Braindumps
Designing and Implementing Microsoft DevOps Solutions Questions 1–65 (page: 26)

Updated On: 16-Nov-2026

You plan to create a GitHub workflow that will use GitHub Actions. The actions will require a 256-KB secret.
You need to recommend a solution to store and encrypt the secret. The secret value must be accessible only to the workflow. The solution must minimize administrative effort.
What should you recommend?

  1. Store the secret in the organization-level GitHub secrets.
  2. Store the secret in the repository-level GitHub secrets.
  3. Encrypt the secret value and store the value in the repository. Store the decryption key in the repository-level GitHub secrets.
  4. Encrypt the secret value and store the value in the repository. Store the decryption key in the organization-level GitHub secrets.

Answer(s): C

Explanation:

Using secrets in GitHub Actions
Storing large secrets
To use secrets that are larger than 48 KB, you can use a workaround to store secrets in your repository and save the decryption passphrase as a secret on GitHub. For example, you can use gpg to encrypt a file containing your secret locally before checking the encrypted file in to your repository on GitHub.


Reference:

https://docs.github.com/en/actions/security-guides/encrypted-secrets



You have an Azure DevOps organization that contains a repo named Repo1 that contains infrastructure as code (IaC) resources.
You plan to deploy the resources by using a GitHub Actions workflow.
You need to configure an authentication method for the workflow.
What should you configure?

  1. a GitHub token
  2. an X.509 certificate
  3. a Microsoft Entra user-assigned managed identity
  4. a Microsoft Entra external identity

Answer(s): C

Explanation:

To connect a GitHub Actions workflow to an Azure DevOps repo for infrastructure as code (IaC) deployments, authentication is typically achieved using Personal Access Tokens (PATs), Service Principals with OpenID Connect (OIDC), or Managed Identities. PATs offer a straightforward approach, while Service Principals and Managed Identities provide more robust and secure authentication for automated deployments.
Note: Use GitHub Actions to connect to Azure
The Azure Login action supports different ways of authenticating with Azure:
Sign in with OpenID Connect using a Microsoft Entra application or a user-assigned managed identity Sign in with a managed identity configured on an Azure virtual machine (Only available for self-hosted GitHub runners)
Sign in with a service principal and secret (Not recommended)


Reference:

https://learn.microsoft.com/en-us/azure/developer/github/connect-from-azure



You have a GitHub Enterprise organization that contains three GitHub repositories.
You need to store a secret named Secret1. The solution must meet the following requirements:
-GitHub Actions must be able to use Secret1 in each repository.
-Administrative effort must be minimized.
As what should you store Secret1?

  1. an artifact
  2. an organization secret
  3. an environment secret
  4. a repository secret

Answer(s): B

Explanation:

Using secrets in GitHub Actions
Secrets allow you to store sensitive information in your organization, repository, or repository environments.
Organization-level secrets let you share secrets between multiple repositories, which reduces the need for creating duplicate secrets.


Reference:

https://docs.github.com/en/enterprise-cloud@latest/actions/security-for-github-actions/security-guides/using-se crets-in-github-actions



View Related Case Study

DRAG DROP (Drag and Drop is not supported)
Which package feed access levels should be assigned to the Developers and Team Leaders groups for the investment planning applications suite? To answer, drag the appropriate access levels to the correct groups. Each access level may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
Note: Each correct selection is worth one point.
Select and Place:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: Reader
Members of a group named Developers must be able to install packages.
Feeds have four levels of access: Owners, Contributors, Collaborators, and Readers. Owners can add any type of identity-individuals, teams, and groups-to any access level.
Box 2: Owner
Members of a group named Team Leaders must be able to create new packages and edit the permissions of package feeds.



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
How should you configure the release retention policy for the investment planning depletions suite? To answer, select the appropriate options in the answer area.
Note: Each correct selection is worth one point.
Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: Shared Access Authorization token
Every request made against a storage service must be authorized, unless the request is for a blob or container resource that has been made available for public or signed access. One option for authorizing a request is by using Shared Key.
Box 2: Azure Storage with HTTPS access
Scenario: The mobile applications must be able to call the share pricing service of the existing retirement fund management system. Until the system is upgraded, the service will only support basic authentication over HTTPS.
The investment planning application suite will include one multi-tier web application and two iOS mobile application. One mobile application will be used by employees; the other will be used by customers.


Reference:

https://docs.microsoft.com/en-us/rest/api/storageservices/authorize-with-shared-key



Viewing page 26 of 81
Viewing questions 126 - 130 out of 398 questions


Post your Comments and Discuss Microsoft AZ-400 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!