Which two tow actions must be taken when an observable microservice application is developed? (Choose two.)

Knowing the state of a single instance is a desired outcome of observability, but not a specific development action for making the application observable.

Placing "try/except" statements is a fundamental practice for error handling and robust code, but it is not directly an observability technique, although the errors handled should be logged.

Placing log statements in the code is essential for an observable application, providing detailed chronological records of events, errors, and state changes that are critical for debugging and monitoring.

Utilizing distributed tracing techniques allows developers to follow the end-to-end path of requests as they traverse multiple microservices, which is vital for understanding performance bottlenecks and debugging issues in a distributed system.

Deploying microservices to multiple datacenters is a strategy for high availability and disaster recovery, not an action directly related to making the application itself observable from a development perspective.