You need to deploy an application to Google Cloud. The application receives traffic via TCP and reads and writes data to the filesystem. The application does not support horizontal scaling. The application process requires full control over the data on the file system because concurrent access causes corruption. The business is willing to accept a downtime when an incident occurs, but the application must be available 24/7 to support their business operations. You need to design the architecture of this application on Google Cloud. What should you do?

The correct option addresses the application's unique constraints. An unmanaged instance group with an active/standby setup across different zones is necessary because the application doesn't support horizontal scaling and concurrent filesystem access causes corruption; this ensures only one instance is active at a time while providing disaster recovery. A regional persistent disk provides block storage that can be attached to either the active or standby instance, enabling failover without data loss and meeting the full control requirement. A network load balancer is chosen because the application receives traffic via TCP, not HTTP, and it can direct traffic to the currently active instance. Incorrect options: Managed instance groups are unsuitable because the application doesn't support horizontal scaling. Cloud Filestore is a shared file system, which would violate the "full control" and "concurrent access causes corruption" requirements. HTTP load balancers are for HTTP/S traffic, not generic TCP. This option still uses a managed instance group and Cloud Filestore, which are inappropriate for the reasons stated above. This option correctly uses an unmanaged instance group with active/standby and a regional persistent disk, but an HTTP load balancer is incorrect for TCP traffic.