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 C1000-143 Exam - Topic 8 Question 69 Discussion

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?
A) Use the spec.config section of the subscription to modify the default CPU and memory allocation.
B) Delete the ibm-aiops-orchestrator pods.
C) Verify the image registry is accessible from the cluster.
D) Use the openshift-operators deployment.yaml to update the resource CPU limit.

IBM C1000-143 Exam - Topic 8 Question 69 Discussion

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

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?

Show Suggested Answer Hide Answer
Suggested Answer: A

by Kenda at Nov 25, 2025, 10:01 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Luis
3 months ago
True, but if they crash, we need to change something. A or D seems safer.
upvoted 0 times
...
Tamar
3 months ago
I’m not sure about A. What if the default settings are actually fine?
upvoted 0 times
...
Isaiah
3 months ago
Deleting pods (option B) feels like a temporary fix. Better to adjust resources first.
upvoted 0 times
...
Junita
3 months ago
I’m leaning towards C. If the image registry isn’t accessible, nothing will work.
upvoted 0 times
...
Luis
4 months ago
I agree, but option D also seems valid. Updating resource limits might help too.
upvoted 0 times
...
Magdalene
4 months ago
I think option A is the best choice. Adjusting CPU and memory can prevent OOMKilled errors.
upvoted 0 times
...
Gilbert
4 months ago
Wait, can OOMKilled really be fixed just by changing resources?
upvoted 0 times
...
Charlie
4 months ago
C) is crucial too, can't install if the registry is down.
upvoted 0 times
...
Mitsue
5 months ago
B) seems risky, might lose important data.
upvoted 0 times
...
Art
5 months ago
Totally agree, adjusting CPU/memory should help!
upvoted 0 times
...
Nathan
5 months ago
Option A is the clear winner here. Adjusting the resource limits is the most logical step to take.
upvoted 0 times
...
Jaime
5 months ago
Option D seems promising, but I'm not sure if that's the best approach for this specific issue. I'd go with Option A.
upvoted 0 times
...
Albert
5 months ago
Haha, deleting the pods? That's like trying to fix a flat tire by removing the whole wheel! Option A is the way to go.
upvoted 0 times
...
Kiera
6 months ago
I'm going with Option C. Checking the image registry accessibility is crucial before troubleshooting further.
upvoted 0 times
...
Arlyne
6 months ago
Option A looks like the right choice to me. Modifying the CPU and memory allocation should help resolve the OOMKilled and CrashLoopBackOff errors.
upvoted 0 times
...
Izetta
6 months ago
I think updating the deployment.yaml for resource limits could be a good move, but I’m not completely confident if that’s the best first step.
upvoted 0 times
...
Laticia
6 months ago
I feel like we practiced a question similar to this, and it was about checking the image registry accessibility. That could be a factor too.
upvoted 0 times
...
Domonique
6 months ago
I’m not entirely sure, but I think deleting the pods might just restart the issue unless we fix the resource limits first.
upvoted 0 times
...
Jamal
6 months ago
I remember something about OOMKilled errors indicating resource limits might be too low, so maybe we should adjust the CPU and memory allocation.
upvoted 0 times
...
Lisbeth
7 months ago
This seems straightforward enough. The pods are crashing due to resource issues, so I'm going with option A. Modifying the CPU and memory allocation in the subscription should do the trick.
upvoted 0 times
...
Apolonia
7 months ago
A) is the way to go for resource issues.
upvoted 0 times
...
Millie
7 months ago
Alright, I've got a strategy here. I'll start by verifying the image registry accessibility, as per option C. That could be a potential root cause. Then, if that checks out, I'll try adjusting the resource limits using the subscription or the deployment.yaml file.
upvoted 0 times
...
Jerry
8 months ago
I'm a bit confused by this question. Are we supposed to modify the resource limits directly, or use the subscription to do it? I'll need to double-check the documentation to make sure I understand the right approach.
upvoted 0 times
...
Jenise
8 months ago
Okay, let's see here. The pods are crashing with OOMKilled and CrashLoopBackOff errors, so it seems like a resource issue. I'm thinking option A or D might be the way to go.
upvoted 0 times
...
Meghan
8 months ago
Hmm, this looks like a tricky one. I'll need to carefully read through the options and think about the potential causes of the pod crashes.
upvoted 0 times
Jacinta
2 months ago
We should definitely consider all options before acting.
upvoted 0 times
...
Hubert
3 months ago
Updating the resource limits in the deployment.yaml sounds smart.
upvoted 0 times
...
Lamar
3 months ago
Checking the image registry is crucial too.
upvoted 0 times
...
Charlene
7 months ago
Deleting the pods might just be a temporary fix.
upvoted 0 times
...
Kris
7 months ago
I think modifying the CPU and memory allocation could help.
upvoted 0 times
...
...

Save Cancel