IBM C1000-143 Exam - Topic 2 Question 53 Discussion

Actual exam question for IBM's C1000-143 exam

Question #: 53
Topic #: 2

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?

ADocker V2 compatible registry running behind

Bquay.io

CRed Hat OpenShift internal registry

Ddocker.io

Show Suggested 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

Blair

3 months ago

I’m surprised there’s so much flexibility with registries!

upvoted 0 times

...

Ammie

3 months ago

Wait, can you really use docker.io in an air-gapped setup?

upvoted 0 times

...

Alexia

3 months ago

I disagree, the internal registry is usually the best option.

upvoted 0 times

...

Josefa

4 months ago

I think quay.io is a solid choice too.

upvoted 0 times

...

Zita

4 months ago

Definitely need a Docker V2 compatible registry!

upvoted 0 times

...

Shawn

4 months ago

I thought docker.io was the answer, but now I’m questioning if it’s really suitable for air-gapped setups.

upvoted 0 times

...

Jade

4 months ago

I’m leaning towards quay.io, but I recall there being some confusion about which registry is actually needed.

upvoted 0 times

...

Yoko

4 months ago

I remember practicing a question about air-gapped environments, and I feel like it was related to a Docker V2 compatible registry.

upvoted 0 times

...

Sylvie

5 months ago

I think it might be the Red Hat OpenShift internal registry, but I'm not entirely sure.

upvoted 0 times

...

Based on my experience, the answer is definitely A. In an air-gapped setup, you need a local registry that the OpenShift cluster can access to pull the required images. The other options like quay.io and docker.io won't work since they're on the public internet.

upvoted 0 times

...

Nobuko

5 months ago

I'm a bit confused by the options here. Is the Red Hat OpenShift internal registry not a valid option in an air-gapped environment? I'll need to double-check the documentation on that.

upvoted 0 times

...

Blair

5 months ago

Okay, let me think this through. Since it's an air-gapped environment, the OpenShift cluster can't access the public internet, so it needs to be connected to a local registry. I'm guessing the answer is A, a Docker V2 compatible registry running behind the firewall.

upvoted 0 times

...

Ressie

5 months ago

This question seems straightforward, but I want to make sure I understand the context correctly. Is this about installing specific Red Hat products in an air-gapped environment?

upvoted 0 times

...

Delmy

9 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

8 months ago

Definitely, using the internal registry ensures everything works seamlessly in an air-gapped environment.

upvoted 0 times

...

Wenona

8 months ago

I agree, it's important to have the right registry set up for smooth installation.

upvoted 0 times

...

Malinda

8 months ago

Yeah, that's correct. The cluster needs to be connected to the internal registry for image pulling.

upvoted 0 times

...

Louis

9 months ago

I think the answer is C, the Red Hat OpenShift internal registry.

upvoted 0 times

...

Billi

10 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

10 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

8 months ago

C) Red Hat OpenShift internal registry

upvoted 0 times

...

Malinda

8 months ago

B) quay.io

upvoted 0 times

...

Margot

9 months ago

A) Docker V2 compatible registry running behind

upvoted 0 times

...

Mitsue

10 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

9 months ago

Let's go with that then, better safe than sorry.

upvoted 0 times

...

Vincent

9 months ago

Let's go with the Red Hat OpenShift internal registry then.

upvoted 0 times

...

Jillian

9 months ago

I agree, it's probably the safer option.

upvoted 0 times

...

King

9 months ago

I agree, it seems like the safer option for an air-gapped environment.

upvoted 0 times

...

Janine

9 months ago

I think the Red Hat OpenShift internal registry is the way to go.

upvoted 0 times

...

Jordan

10 months ago

I think the Red Hat OpenShift internal registry is the way to go.

upvoted 0 times

...

Ivory

10 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

10 months ago

Definitely, can't risk relying on external registries like quay.io or docker.io in that situation.

upvoted 0 times

...

Carman

10 months ago

I agree, C) Red Hat OpenShift internal registry is the way to go in an air-gapped environment.

upvoted 0 times

...

Norah

11 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

11 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

11 months ago

I think the OpenShift cluster should be connected to a Docker V2 compatible registry.

upvoted 0 times

...