Your company has an Azure DevOps project that produces Node Package Manager (npm) packages. Multiple projects consume the packages.
You need to minimize the amount of disk space used by older packages in Azure Artifacts.
What should you modify?
Suggested Answer: B
Get Premium AZ-400 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
12 comments · newest first
GI
Giuseppe
11 months ago
I agree with A, but I’m surprised it’s that simple!
MA
Marcelle
11 months ago
Wait, can we really manage space with just retention settings?
HO
Howard
12 months ago
C seems irrelevant, tests don’t affect disk space much.
PA
Pansy
12 months ago
I think B makes more sense for releases.
ER
Ernest
1 year ago
Definitely A, the pipeline retention settings are key.
MA
Matthew
1 year ago
I’m a bit confused about the company pipeline versus the project pipeline. Does the company-wide setting impact the disk space for individual projects?
BO
Bong
1 year ago
I feel like the release settings could also play a role, but I can't recall if they specifically affect npm packages.
DE
Deangelo
1 year ago
I remember practicing a question about retention policies, and I think it was related to the project's pipeline. That might be option A.
IS
Isaiah
1 year ago
I think we need to look at the retention settings, but I'm not sure if it's the pipeline or the release settings that matter more for npm packages.
KI
Kimberlie
1 year ago
This question is asking about managing Azure subscriptions and role assignments. I think the key is to use the principle of least privilege, so I'll need to carefully consider the options.
OD
Odelia
1 year ago
I've got a good feeling about B. Dynamic Updates-Review Policies. That seems like the most straightforward way to preview the security policy rules for new application signatures.
RO
Rory
1 year ago
I feel like the pWWN configuration is crucial too. I saw something similar in the materials, but I'm torn between B and D.