A good answer is a good start.

Distribute application connections across backend servers using health checks and routing policies. Define protocol requirements, TLS handling and session persistence together with backend capacity.

The proposal specifies resource limits, software compatibility, deployment steps, operational responsibilities and recurring charges. Confirm these terms before ordering.

Map application dependencies and define recovery time and data-loss objectives. Build a replication and recovery runbook, then validate failover and return-to-primary procedures through planned exercises.

The proposal specifies resource limits, software compatibility, deployment steps, operational responsibilities and recurring charges. Confirm these terms before ordering.

Monitoring detects conditions and sends notifications. Response, automation and on-call ownership need separate definition.

Start with critical user journeys, service access and failure indicators such as full disks. Tune alerts to avoid unnecessary noise.

Share architecture, key metrics, budget range, goals and constraints. Sensitive access credentials are not needed for an initial review.

Depending on scope, outputs can include an architecture proposal, options comparison and implementation steps. Agree deliverables at the start.

Results depend on overwritten data, media condition and failure type. Recoverability cannot be guaranteed before assessment.

Stop unnecessary writes to the affected environment. Record errors, recent actions and the last working time for assessment.

Configuration review and penetration testing have different scopes. Define methods, targets and authorization at proposal stage.

Reporting and applying fixes may be separate work. Agree response, retesting and deliverables at the start.