GCP Professional Cloud Architect Practice Question

A financial-services firm is in the discovery phase of migrating 500 on-premises virtual machines to Google Cloud. Executives want a dependency map before grouping workloads into migration waves. The data center uses dynamic service routing, and application traffic patterns vary during month-end processing. Using Google Cloud Migration Center, which pre-migration action best ensures that application dependencies are captured accurately while keeping operational risk low?

Install the Migration Center discovery client on all relevant VMs and enable network profiling for a full business cycle to record live traffic between services.
Deploy Google Application Migration Service mobility agents only and combine agent metrics with current firewall rules to infer dependencies.
Import the existing configuration-management database (CMDB) into Migration Center and generate the dependency map without collecting live network data.
Perform a one-time SNMP and port scan from a Migration Center appliance to catalog open ports on each host.

Report Issue

Answer Description

Migration Center's discovery client (also called the MigrateOps Agent) can be installed on each VM to collect hardware, software, and process information. When network profiling is enabled, the agent records inbound and outbound connections over time, producing a traffic graph that identifies service dependencies. Running the profiling for at least one representative business cycle (often one to two weeks) is recommended to capture periodic spikes such as month-end jobs. Importing a static CMDB, relying only on firewall logs, performing one-time port sweeps, or using the Application Migration Service agent alone will not reliably reveal transient or east-west dependencies, risking missed links and poorly sequenced migration waves.

Ask Bash

Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.