MENU
You need to execute inline testing of an Azure DevOps pipeline that uses a Docker deploymentmodel. The solution must prevent the results from being published to the pipeline.
What should you use for the inline testing?
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
31 comments · newest first
XE
Xenia
11 months ago
Not sure if multi-stage is the best choice here, honestly.
RO
Rolland
11 months ago
A Docker Compose file seems too complex for this.
AL
Aliza
12 months ago
Wait, can a single stage Dockerfile even handle inline testing?
WE
Weldon
12 months ago
Definitely agree with that! Keeps things clean.
JO
Johnna
1 year ago
I think a multi-stage Dockerfile is the way to go.
RE
Reena
1 year ago
A Docker Compose file seems like it could be useful, but I doubt it would prevent results from being published like the question asks.
EL
Elli
1 year ago
I feel like we had a practice question about using AKS pods for testing, but I can't recall if that was for inline testing specifically.
TA
Tamra
1 year ago
I think a multi-stage Dockerfile might be the right choice since it can help with isolating tests without publishing results.
LE
Leota
1 year ago
I remember we discussed inline testing, but I'm not sure if a single stage Dockerfile is enough for that.
MA
Maybelle
1 year ago
Okay, let's see here. I'm leaning towards B, since that seems to capture the importance of understanding issues from different angles when collaborating across the organization. A and C also seem plausible, but B feels like the most well-rounded and strategic approach.
DI
Dino
1 year ago
Ah, I remember learning about the differences between person and business accounts. I'll apply that knowledge here.
MO
Mose
1 year ago
This question seems to be testing our knowledge of enterprise architecture patterns. I think the key is to identify the pattern that supports long-running service activities and temporary state storage in a database.
LI
Lindsay
1 year ago
Wait, we can't publish the results? What is this, a magic trick? I'll just use a multi-stage Dockerfile and make the pipeline disappear!
SO
Socorro
1 year ago
Docker Compose file, eh? Might as well bring in the whole orchestra for a simple inline test. But hey, at least it'll keep those pesky results out of sight!
TE
Terrilyn
1 year ago
D) a Docker Compose file
VI
Viva
1 year ago
C) a multi-stage Dockerfile
TA
Tamar
1 year ago
B) an Azure Kubernetes Service (AKS) pod
JE
Jeanice
1 year ago
A) a single stage Dockerfile
DO
Dorothy
1 year ago
Ah, a multi-stage Dockerfile! Now we're talking. That's the way to go if you want to keep those pipeline results under wraps.
EM
Emeline
1 year ago
Definitely, using a multi-stage Dockerfile will help keep things secure.
KR
Kristin
1 year ago
It's a great choice to prevent the results from being published to the pipeline.
WH
Whitley
1 year ago
Yes, a multi-stage Dockerfile is the way to go for inline testing.
LO
Lorrine
1 year ago
AKS pod? Sounds like we're going to need a lot of Kubernetes magic to make this work. I'll just stick to my trusty Docker Compose file, thanks.
AR
Arlene
2 years ago
A single-stage Dockerfile? That's like trying to build a house with just a hammer. Gotta bring in the whole toolbox for this one!
KR
Krystina
1 year ago
D: Let's go with the multi-stage Dockerfile then, it's the best option for this scenario.
MO
Monte
1 year ago
C: Agreed, a multi-stage Dockerfile will give us the flexibility we need for inline testing.
HA
Harris
1 year ago
B: I think we should go with a multi-stage Dockerfile to cover all our bases.
KA
Kati
1 year ago
A: You're right, a single-stage Dockerfile might not be enough for this task.
TR
Trina
2 years ago
I'm not sure about using a multi-stage Dockerfile. Wouldn't an Azure Kubernetes Service (AKS) pod be a better option for inline testing?
PO
Pok
2 years ago
I agree with Norah. A multi-stage Dockerfile allows us to build and test the application in separate stages.
NO
Norah
2 years ago
I think we should use a multi-stage Dockerfile for inline testing.