You have an Azure subscription that contains the resources shown in the following table.

Project1 produces npm packages that are published to Feed 1. Feed1 is consumed by multiple projects.
You need to ensure that only tested packages are available for consumption. The solution must minimize development effort.
What should you do?
Suggested Answer: C
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
SH
Sherill
11 months ago
Surprised there's no mention of versioning in these options!
ET
Ettie
11 months ago
I think D could work too, but it feels a bit risky.
OM
Omega
12 months ago
Wait, why not just use C? Tagging sounds simpler!
KI
Kimbery
12 months ago
I disagree, B looks more efficient for setting defaults.
JA
Janella
1 year ago
Option A seems like the best choice for managing views.
AL
Alaine
1 year ago
I recall that setting a default view is important, but I can't remember if it should be @default or @release for this case.
LU
Lucy
1 year ago
I'm a bit confused about whether tagging the packages or promoting them to a view is more effective. I need to think this through.
EL
Elena
1 year ago
I think we practiced a similar question where we had to promote packages after testing. I feel like option A might be the right approach.
YU
Yuette
1 year ago
I remember something about feed views, but I'm not sure if @default or @release is the better choice for this scenario.
LE
Lettie
1 year ago
I'm pretty sure the answer is 1.1, since that's a common starting point for new APIs to avoid conflicts.
NA
Nan
1 year ago
I've got this! The question is asking about setting the override date field, and the correct answers are A and B - setting it to be more restrictive at the legal entity or shared level.
BE
Beula
1 year ago
This seems like a pretty straightforward question about BIG-IP device synchronization. I'm confident I can figure this out.