IBM Exam C1000-143 Topic 3 Question 63 Discussion

Actual exam question for IBM's C1000-143 exam

Question #: 63
Topic #: 3

What action should be done when the IBM Automation foundation Operator pods crashes with OOMKilled and CrashLoopBackOf f errors in the openshift-operators project during installation of Al Manager?

AUse the spec.config section of the subscription to modify the default CPU and memory allocation.

BDelete the ibm-aiops-orchestrator pods.

CVerify the image registry is accessible from the cluster.

DUse the openshift-operators deployment.yaml to update the resource CPU limit.

Show Suggested Answer

Suggested Answer: A

by Elli at Apr 30, 2025, 04:42 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Aja

2 months ago

This question is a real brain-teaser, huh? I'm tempted to just go with option B and see what happens. Nothing like a little chaos to spice up an exam!

upvoted 0 times

...

Melinda

2 months ago

Deleting the ibm-aiops-orchestrator pods might also help resolve the problem.

upvoted 0 times

...

Frederic

2 months ago

I believe we should also consider updating the resource CPU limit.

upvoted 0 times

...

Zana

2 months ago

D sounds like a lot of work. Why bother with the deployment.yaml when you can just tweak the operator's configuration directly? A is the way to go, in my opinion.

upvoted 0 times

Ilene

15 days ago

C) If that's not the issue, then we can consider updating the resource CPU limit in the deployment.yaml.

upvoted 0 times

...

Cassie

16 days ago

A) True, but first we should check if the image registry is accessible from the cluster.

upvoted 0 times

...

Annamaria

17 days ago

B) But what if that doesn't solve the issue? Deleting the pods might be necessary.

upvoted 0 times

...

Ricki

19 days ago

A) Use the spec.config section of the subscription to modify the default CPU and memory allocation.

upvoted 0 times

...

Bobbie

30 days ago

C) Verify the image registry is accessible from the cluster.

upvoted 0 times

...

Onita

1 months ago

B) I think deleting the ibm-aiops-orchestrator pods might solve the issue.

upvoted 0 times

...

Cordelia

2 months ago

A) Use the spec.config section of the subscription to modify the default CPU and memory allocation.

upvoted 0 times

...

Carlton

2 months ago

Haha, deleting the pods? That's like trying to fix a flat tire by removing the wheel! Option B is definitely not the way to go here.

upvoted 0 times

Shad

1 months ago

C) Verify the image registry is accessible from the cluster.

upvoted 0 times

...

Hubert

1 months ago

A) Use the spec.config section of the subscription to modify the default CPU and memory allocation.

upvoted 0 times

...

Stefania

2 months ago

Option C is interesting, but I doubt that's the solution. Verifying the image registry access is probably a good troubleshooting step, but it doesn't directly address the pod crashes.

upvoted 0 times

Nelida

1 months ago

C) Verify the image registry is accessible from the cluster.

upvoted 0 times

...

Wilda

1 months ago

B) Delete the ibm-aiops-orchestrator pods.

upvoted 0 times

...

Felicia

2 months ago

A) Use the spec.config section of the subscription to modify the default CPU and memory allocation.

upvoted 0 times

...

Daniela

2 months ago

I agree with Glory, that could be causing the issue.

upvoted 0 times

...

Amalia

3 months ago

I think the correct answer is A. Modifying the CPU and memory allocation in the spec.config section seems like the best way to address the OOMKilled and CrashLoopBackOff errors.

upvoted 0 times