An organization manages a large cloud-deployed application that employs a microservices architecture. No notable issues occur with downtime because the services of this application are redundantly deployed over three or more data center regions. However, several times a week reports are received about application slowness. The container orchestration logs show faults in a variety of containers that cause them to fail and then spin up brand new.
Which action must be taken to improve the resiliency design of the application while maintaining current scale?

Users report that they are no longer able to process transactions with the online ordering application, and the logging dashboard is displaying these messages:
Fri Jan 10 19:37:31.123 ESI 2020 [FRONTEND] [NFO: Incoming request to add item to cart from user
45834534858
Fri Jan 10 19:37:31.247 EST 2020 [BACKEND] INFO: Attempting to add item to cart Fri Jan 10 19:37:31.250 EST 2020 [BACKEND] ERROR: Failed to add item: MYSQLDB ERROR:
Connection refused
What is causing the problem seen in these log messages?

Which command is used 10 enable application hosting on a Cisco IOS XE device?

Which two statements about a stateless application are true? (Choose two.)

What is an effective logging strategy according 10 the 12-factor app tenets?