Microsoft AZ-400 Value Pack (Frequently Bought Together)

Correct Answer: A  🗳️

Explanation: Only visible for PracticeTorrent members. You can sign-up / login (it's free).

Correct Answer: B  🗳️

Explanation: Only visible for PracticeTorrent members. You can sign-up / login (it's free).

Correct Answer:

See the solution below in explanation.
Explanation:
To store signed images in an Azure Container Registry (ACR) instance and support your planned images while minimizing costs, you need to modify the SKU of your ACR instance to one that supports content trust and image signing. Here's how you can do it:
Determine the Appropriate SKU:
Content trust and image signing are features of thePremiumservice tier of Azure ContainerRegistry1.
If cost minimization is a priority, ensure that the Premium tier is necessary for your use case. If you require content trust, the Premium tier is the appropriate choice.
Modify the SKU of the ACR Instance:
Navigate to the Azure Portal.
Go to your ACR instanceaz40038443478act1.
SelectUpdatefrom the overview pane.
Choose thePremiumSKU from the SKU drop-down menu2.
Review the changes and pricing, then save the configuration.
By upgrading to the Premium SKU, you'll be able to store signed images in your ACR instance. Remember to monitor your usage and costs to ensure they align with your budget and requirements.

Correct Answer:

See explanation below
Explanation:
Step 1: Access Azure DevOps
Open your browser and navigate to https://aex.dev.azure.com.
You will be prompted to sign in. Enter the following credentials:
Username: [email protected]
Password: aFpJ2j-6M!
Click Next or Sign in to proceed.
Note: If you see any Microsoft security challenge (like phone or email verification), follow the instructions to complete it.
Step 2: Sign Up for Azure DevOps
After signing in, you'll see a prompt to sign up for Azure DevOps.
Use the default settings provided by Azure DevOps for the sign-up process (region, default name, etc.).
Click Continue or Start free with Azure DevOps.
An Azure DevOps Organization is a container for your projects and resources. Default settings are usually fine for new organizations.
Step 3: Create the Organization
Enter a name for your organization. Azure DevOps will suggest a default name (like yourname or org-name), but you can change it if you prefer.
Verify the region is correct.
Click Continue to create the organization.
Your Azure DevOps organization is now created. It's the top-level container for all your projects.
Step 4: Create a Private Project Named Project1
In your Azure DevOps portal, find the " New Project " button and click it.
Enter the following details:
Project Name: Project1
Description: (optional)
Visibility: Private
Click Create.
A private project means that only users you add can see or access it. This is important for security and privacy.
Step 5: Enforce Maximum File Size for Repositories
By default, Azure DevOps allows files up to 100 MB to be pushed. To ensure the maximum file size for repositories in Project1 is 2 MB, you can enforce this using a pipeline validation.
Azure DevOps does not provide a direct setting for file size limits. However, you can create a pipeline to validate file size on pull requests and block changes if a file exceeds 2 MB.
Here's how to do it:
Option 1: Enforce with a pipeline validation for pull requests
In your Project1, create a new pipeline.
Use the following YAML for the pipeline:
yaml
Copy
trigger: none
pr:
branches:
include:
- " * "
jobs:
- job: CheckFileSize
pool:
vmImage: ' ubuntu-latest '
steps:
- script: |
echo " Checking file sizes in the PR... "
git fetch origin +refs/pull/*/merge:refs/remotes/origin/pr/*
large_files=$(git diff --cached --name-only | xargs -I{} du -b {} | awk ' $1 > 2097152 {print $2} ' ) if [ -n " $large_files " ]; then echo " Error: The following files exceed 2 MB: " echo " $large_files " exit 1 fi displayName: ' Check file sizes in PR ' This pipeline will:
Run on pull requests only.
Check the size of all files in the pull request.
If any file is larger than 2 MB (2,097,152 bytes), it will fail the pipeline and block the PR.
Option 2: Local Git configuration (for each developer)
On each developer's machine, run this command in their local repository:
bash
Copy
git config --local core.bigFileThreshold 2M
This limits the file threshold for checkout, but does not prevent large files from being pushed. Using the pipeline validation (Option 1) is more secure for team environments.

Correct Answer:

Explanation: