Cisco Exam 300-910 Topic 13 Question 94 Discussion

Actual exam question for Cisco's 300-910 exam

Question #: 94
Topic #: 13

[All 300-910 Questions]

What is a capability of node-level logging in Kubernetes?

AUsing the Kubernetes JSON logging driver enables log persistence

BOutput that is written to stdin is retrieved by using kubectl

COutput that is written to stderr is not logged or retrievable by using kubectl

DUsing the local logging driver of Docker enables log persistence

Show Suggested Answer

Suggested Answer: B

by Virgina at Mar 05, 2025, 10:20 PM

Limited Time Offer

25%

Off

Get Premium 300-910 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Lea

1 months ago

Option A sounds like a feature, but Option C is just a bug. Maybe the correct answer is 'All of the above, plus a dash of duct tape and hope.'

upvoted 0 times

...

Venita

1 months ago

Wait, so Kubernetes has its own logging driver? I thought it just relied on the Force to keep track of everything.

upvoted 0 times

...

Levi

1 months ago

Option D doesn't seem quite right. Isn't the whole point of node-level logging in Kubernetes to have a standardized logging solution, rather than relying on the local Docker driver?

upvoted 0 times

Carline

12 hours ago

C) Output that is written to stderr is not logged or retrievable by using kubectl

upvoted 0 times

...

Cherri

13 days ago

B) Output that is written to stdin is retrieved by using kubectl

upvoted 0 times

...

Nelida

17 days ago

A) Using the Kubernetes JSON logging driver enables log persistence

upvoted 0 times

...

Marica

1 months ago

Option C is a bit concerning. If stderr output isn't logged or retrievable, that could be a real problem in troubleshooting Kubernetes issues.

upvoted 0 times

...

Alesia

2 months ago

I'm leaning towards Option B, as being able to retrieve logs using kubectl seems like a key feature of node-level logging in Kubernetes.

upvoted 0 times

Wilda

7 days ago

Using kubectl to retrieve logs definitely simplifies the process of node-level logging.

upvoted 0 times

...

Howard

9 days ago

User1: I see your point, but I still think Option A is the best choice for node-level logging in Kubernetes.

upvoted 0 times

...

Alison

13 days ago

User3: I'm not sure, but I think Option C is incorrect, output written to stderr should still be retrievable.

upvoted 0 times

...

Hubert

15 days ago

I agree, kubectl is a powerful tool for managing logs in Kubernetes.

upvoted 0 times

...

Hyman

1 months ago

I think Option B is correct, kubectl is essential for retrieving logs.

upvoted 0 times

...

Ruthann

1 months ago

User2: I agree with User1, that does sound like a key capability of node-level logging.

upvoted 0 times

...

Catherin

2 months ago

User1: I think Option A is correct, using the Kubernetes JSON logging driver enables log persistence.

upvoted 0 times

...

Twila

2 months ago

Option A sounds promising, but I'm not sure if it's the whole story. I'd like to know more about how the Kubernetes JSON logging driver works and what other capabilities it might have.

upvoted 0 times

...