Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

IBM Exam C1000-143 Topic 2 Question 53 Discussion

Actual exam question for IBM's C1000-143 exam
Question #: 53
Topic #: 2
[All C1000-143 Questions]

When installing Al manager or Event Manager in an air-gapped environment, which registry must the OpenShift cluster be connected to in order to pull images?

Show Suggested Answer Hide Answer
Suggested Answer: C

by Dona at Sep 17, 2024, 03:58 AM

Limited Time Offer

25%

Off

Get Premium C1000-143 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Delmy
3 months ago
Obviously, the answer is C. Anyone who thinks otherwise must be living in a different universe. Or maybe they just forgot to take their 'common sense' vitamins this morning.
upvoted 0 times
Markus
1 months ago
Definitely, using the internal registry ensures everything works seamlessly in an air-gapped environment.
upvoted 0 times
...
Wenona
2 months ago
I agree, it's important to have the right registry set up for smooth installation.
upvoted 0 times
...
Malinda
2 months ago
Yeah, that's correct. The cluster needs to be connected to the internal registry for image pulling.
upvoted 0 times
...
Louis
2 months ago
I think the answer is C, the Red Hat OpenShift internal registry.
upvoted 0 times
...
...
Billi
3 months ago
I'm going with A. A Docker V2 compatible registry just makes more sense to me in an air-gapped setup. The internal registry might be too restrictive. Time to put on my best hacker hat and get creative!
upvoted 0 times
...
Chandra
3 months ago
It's gotta be C, the Red Hat OpenShift internal registry. Why would you want to connect to an external registry in an air-gapped environment? That defeats the whole purpose!
upvoted 0 times
Ashlyn
1 months ago
C) Red Hat OpenShift internal registry
upvoted 0 times
...
Malinda
2 months ago
B) quay.io
upvoted 0 times
...
Margot
2 months ago
A) Docker V2 compatible registry running behind
upvoted 0 times
...
...
Mitsue
3 months ago
Hmm, I'm torn between A and C. A Docker V2 compatible registry could work, but the Red Hat OpenShift internal registry might be the safer bet. Decisions, decisions...
upvoted 0 times
Rodolfo
2 months ago
Let's go with that then, better safe than sorry.
upvoted 0 times
...
Vincent
2 months ago
Let's go with the Red Hat OpenShift internal registry then.
upvoted 0 times
...
Jillian
2 months ago
I agree, it's probably the safer option.
upvoted 0 times
...
King
2 months ago
I agree, it seems like the safer option for an air-gapped environment.
upvoted 0 times
...
Janine
3 months ago
I think the Red Hat OpenShift internal registry is the way to go.
upvoted 0 times
...
Jordan
3 months ago
I think the Red Hat OpenShift internal registry is the way to go.
upvoted 0 times
...
...
Ivory
4 months ago
I think it's C. The Red Hat OpenShift internal registry seems like the logical choice for an air-gapped environment. Can't rely on external registries like quay.io or docker.io in that scenario.
upvoted 0 times
Odette
3 months ago
Definitely, can't risk relying on external registries like quay.io or docker.io in that situation.
upvoted 0 times
...
Carman
3 months ago
I agree, C) Red Hat OpenShift internal registry is the way to go in an air-gapped environment.
upvoted 0 times
...
...
Norah
4 months ago
I'm not sure, but I think it could also be the Red Hat OpenShift internal registry. It makes sense to use an internal registry for security reasons.
upvoted 0 times
...
Walker
4 months ago
I agree with Leota, because Al manager or Event Manager needs to pull images from a Docker V2 compatible registry in an air-gapped environment.
upvoted 0 times
...
Leota
4 months ago
I think the OpenShift cluster should be connected to a Docker V2 compatible registry.
upvoted 0 times
...

Save Cancel