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

Cisco 350-901 Exam - Topic 14 Question 64 Discussion

An organization manages a large cloud-deployed application that employs a microservices architecture across multiple data centers. Reports have received about application slowness. The container orchestration logs show that faults have been raised in a variety of containers that caused them to fail and then spin up brand new instances.Which two actions can improve the design of the application to identify the faults? (Choose two.)
B) Implement a tagging methodology that follows the application execution from service to service.
A) Automatically pull out the container that fails the most over a time period.
C) Add logging on exception and provide immediate notification.
D) Do a write to the datastore every time there is an application failure.
E) Implement an SNMP logging system with alerts in case a network link is slow.

Cisco 350-901 Exam - Topic 14 Question 64 Discussion

Actual exam question for Cisco's 350-901 exam
Question #: 64
Topic #: 14
[All 350-901 Questions]

An organization manages a large cloud-deployed application that employs a microservices architecture across multiple data centers. Reports have received about application slowness. The container orchestration logs show that faults have been raised in a variety of containers that caused them to fail and then spin up brand new instances.

Which two actions can improve the design of the application to identify the faults? (Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: B

by Vi at Dec 27, 2023, 12:32 PM

Limited Time Offer

25%

Off

Get Premium 350-901 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Fausto
9 months ago
E seems a bit off, not sure if SNMP is the best choice here.
upvoted 0 times
...
Adria
10 months ago
A could help, but it might not address the root cause.
upvoted 0 times
...
Eliseo
10 months ago
Wait, writing to the datastore every time? That sounds excessive.
upvoted 0 times
...
Reita
10 months ago
Totally agree with B, tagging is essential for tracing issues!
upvoted 0 times
...
Winfred
10 months ago
I think option C is a must for immediate feedback.
upvoted 0 times
...
Herminia
10 months ago
Option D seems risky to me; writing to the datastore on every failure could create more issues. I wonder if option E about SNMP logging is really necessary for this scenario.
upvoted 0 times
...
Tanesha
11 months ago
I practiced a question similar to this, and I think automatically pulling out the most failing container could help identify patterns, so option A seems relevant.
upvoted 0 times
...
Roxane
11 months ago
I'm not entirely sure, but I feel like implementing a tagging methodology could help track issues across services, so maybe option B?
upvoted 0 times
...
Chery
11 months ago
I remember we discussed the importance of logging exceptions, so I think option C might be a good choice.
upvoted 0 times
...
Katy
11 months ago
I'm feeling pretty confident about this one. The tagging and logging options seem like the most effective approaches to improve the application's observability and troubleshoot the faults. The other options don't seem as directly relevant to the problem.
upvoted 0 times
...
Lonna
11 months ago
Okay, I think I've got a strategy here. The tagging option sounds like it could help trace the application execution across services, which could provide valuable context for diagnosing the issues. And the logging on exception with immediate notification seems like a good way to surface the faults quickly.
upvoted 0 times
...
Dolores
11 months ago
I'm a bit confused by the options. I'm not sure if automatically pulling the failing container or writing to the datastore on failure would actually help identify the root cause. Maybe the tagging and logging options would be better approaches.
upvoted 0 times
...
Blondell
11 months ago
This question seems straightforward. I think the key is to focus on improving the application's observability and traceability to identify the root causes of the faults.
upvoted 0 times
...
Donte
11 months ago
Wait, I'm not sure about this. Does the lack of a copy constructor in class A cause any issues here? I better double-check that.
upvoted 0 times
...
Felicitas
11 months ago
I think the answer is Snapshots. That way I can easily revert the VMs back to their original state after applying the updates.
upvoted 0 times
...
Cherry
11 months ago
Okay, let me see. The Bank Secrecy Act deals with financial institutions and reporting requirements, so I'm guessing the answer has to do with the type of business and whether it's considered a financial institution or not. I'll have to review the details.
upvoted 0 times
...
Bobbye
1 year ago
I'm just going to go with the 'write to the datastore' option. It's the most straightforward and won't require any fancy-schmancy microservices wizardry.
upvoted 0 times
Tamera
1 year ago
Definitely. It's better to be proactive in monitoring and addressing issues before they escalate.
upvoted 0 times
...
Alyce
1 year ago
I agree. It's important to have a system in place that alerts us right away when something goes wrong.
upvoted 0 times
...
Yaeko
1 year ago
Yeah, that way we can quickly identify and address any faults in the application.
upvoted 0 times
...
Mari
1 year ago
I think adding logging on exception and providing immediate notification is also a good idea.
upvoted 0 times
...
...
Alease
1 year ago
Wait, you want me to implement an SNMP logging system? Is this exam testing my IT skills or my stand-up comedy routine?
upvoted 0 times
...
Marti
1 year ago
Logging exceptions and providing notifications? Sounds like a no-brainer to me. Let's get that done!
upvoted 0 times
Vesta
1 year ago
C: Agreed. Both actions can help us identify faults and improve the design of the application.
upvoted 0 times
...
Erick
1 year ago
B: We should also consider implementing a tagging methodology to track the application execution.
upvoted 0 times
...
Mitsue
1 year ago
A: Implementing logging on exceptions and providing immediate notifications is definitely a good idea.
upvoted 0 times
...
...
Carylon
1 year ago
Ooh, I like the idea of tagging the application execution. That could really help us track down those pesky faults!
upvoted 0 times
Eladia
1 year ago
User 3: We should also add logging on exception and get immediate notifications to quickly address any issues.
upvoted 0 times
...
Stevie
1 year ago
User 2: Yeah, that sounds like a good idea. It could help us identify where the faults are coming from.
upvoted 0 times
...
Keva
1 year ago
User 1: I think we should implement a tagging methodology to track the application execution.
upvoted 0 times
...
...
Lashaunda
1 year ago
I believe options C and B are both crucial for improving fault identification in the application.
upvoted 0 times
...
Timothy
1 year ago
I agree with Vivan. Option B can also help track faults across services.
upvoted 0 times
...
Vivan
1 year ago
I think option C is important for immediate notification of exceptions.
upvoted 0 times
...
Herman
1 year ago
I believe implementing both options C and B would greatly improve fault identification in the application.
upvoted 0 times
...
Valentine
1 year ago
Hmm, I'm not sure about that 'pull out the container' option. Sounds like a recipe for more problems to me.
upvoted 0 times
Lizbeth
1 year ago
B) Implement a tagging methodology that follows the application execution from service to service.
upvoted 0 times
...
Denny
1 year ago
Hmm, I'm not sure about that 'pull out the container' option. Sounds like a recipe for more problems to me.
upvoted 0 times
...
Erick
1 year ago
C) Add logging on exception and provide immediate notification.
upvoted 0 times
...
Truman
1 year ago
A) Automatically pull out the container that fails the most over a time period.
upvoted 0 times
...
...
Una
1 year ago
Whoa, this question is a real brain-teaser! I'm definitely going to need to think this through carefully.
upvoted 0 times
...
Una
1 year ago
I agree with you, Tayna. Option B can also help in tracking faults across services.
upvoted 0 times
...
Tayna
1 year ago
I think option C is important for identifying faults quickly.
upvoted 0 times
...

Save Cancel