AZ-400 Implement an instrumentation strategy Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Step 1: Create a new feed, Step 2: Configure upstream sources, Step 3: Set feed permissions, Step 4: Publish NuGet packages, Step 5: Consume packages from feed

  Why this is correct

  This is the correct order because you must first create the feed, then add upstream sources to pull packages from external sources, set permissions to control who can access and contribute, then publish your own packages, and finally consume them.

• ✗

  Step 1: Create a new feed, Step 2: Set feed permissions, Step 3: Configure upstream sources, Step 4: Publish NuGet packages, Step 5: Consume packages from feed

  Why it's wrong here

  Configuring upstream sources after feed permissions is incorrect because upstream sources are a core feed-level setting that affects how all packages are resolved and cached. If you lock down permissions first, you may inadvertently block the account or build service principal from adding or modifying upstream sources, since that action requires feed management rights. Upstream sources should be set immediately after feed creation so that any subsequent publish or restore operations can automatically save dependencies from external sources.

• ✗

  Step 1: Create a new feed, Step 2: Publish NuGet packages, Step 3: Configure upstream sources, Step 4: Set feed permissions, Step 5: Consume packages from feed

  Why it's wrong here

  Publishing NuGet packages before configuring upstream sources defeats the purpose of upstream caching, because during the publish operation the feed cannot yet see nuget.org or other upstream feeds to save missing dependencies. Additionally, setting feed permissions after publishing means you have no access control over who pushed packages beforehand — the feed is still using its default permissions, which may allow any project contributor to publish. Permissions must be established prior to any publishing to enforce a trusted contributor set.

• ✗

  Step 1: Create a new feed, Step 2: Configure upstream sources, Step 3: Publish NuGet packages, Step 4: Set feed permissions, Step 5: Consume packages from feed

  Why it's wrong here

  Setting feed permissions after packages have already been published exposes your feed to unauthorized or accidental pushes, because Azure Artifacts' default permissions grant contribute rights to every project contributor. By the time you restrict permissions, malicious or incorrect packages may already be present, and you cannot retroactively prevent them from having been published. The correct order places permissions before publishing but after upstream sources are configured, ensuring the feed’s access model is enforced from the first push.

Go deeper

Related to this question