Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Cloud Digital Leader practice bank has an additional 3,070 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A financial services company is migrating its infrastructure from an on-premises data center to Google Cloud. Currently, their security operations team relies on the following traditional practices:
The company wants to modernize its security operations by adopting cloud-native operational visibility and automation.
How should the company transform its security operations in Google Cloud?
Post-production manual inspection is a traditional, reactive security practice where development teams deploy applications first and security teams manually audit the code, server configurations, and physical hardware afterward. In this model, security acts as a manual checkpoint at the very end of the software delivery lifecycle.
First, under the shared responsibility model, Google Cloud manages, secures, and patches the underlying physical data center hardware; customers never perform physical hardware inspections in the cloud. Second, halting automated pipelines to perform manual reviews after production deployment introduces severe operational bottlenecks and leaves live workloads exposed to vulnerabilities until the manual inspection finishes.
Conducting manual security assessments on a production environment would only make sense when performing a scheduled, specialized penetration test or an external regulatory validation to verify that automated runtime controls are functioning as intended.
To modernize application and deployment security, Google Cloud promotes shift-left security. By integrating automated Static Application Security Testing (SAST) into Cloud Build pipelines, scanning containers in Artifact Registry, and defining configurations with Terraform, organizations automatically block non-compliant code before it ever reaches production.
Siloed monitoring is an operational approach where individual infrastructure components, networks, or cloud services are tracked using isolated tools and separate dashboards. In this model, security analysts must manually export, review, and cross-reference logs from multiple platforms during scheduled intervals—such as quarterly compliance reviews—to identify security incidents.
Replicating fragmented, manual workflows in Google Cloud directly undermines the goal of achieving cloud-native operational visibility and automation. Cloud environments are highly dynamic; waiting for a scheduled quarterly review to correlate logs means misconfigurations, anomalous traffic spikes, or active breaches could remain undetected for months.
Manual correlation across separate dashboards is an anti-pattern in modern cloud architectures. However, a team might temporarily review separate consoles if they are in the early stages of a complex merger involving legacy systems that have not yet been integrated into a centralized Security Information and Event Management (SIEM) platform.
To avoid the pitfalls of siloed tools, Google Cloud recommends a centralized visibility model. By pairing centralized logging with analytical platforms like Security Command Center and Google Security Operations (Google SecOps), organizations can automatically correlate security events from multiple sources in real time and streamline incident response.
In a cloud-native environment, security operations transition away from fragmented hardware appliances and manual checklists toward centralized, software-defined observability. Cloud Audit Logs automatically records administrative activities, system events, and data access across Google Cloud resources, while Security Command Center (SCC) serves as a built-in security and risk management platform that continuously monitors the cloud estate.
Implementing Cloud Audit Logs and Security Command Center directly transforms each of the company's legacy on-premises practices:
Traditional on-premises security relies on periodic human intervention, which cannot keep pace with dynamic cloud resources. By combining Cloud Audit Logs with Security Command Center, the organization achieves continuous, automated visibility and proactive risk mitigation across its entire Google Cloud footprint.
Traditional perimeter security—often referred to as a castle-and-moat model—uses network boundaries such as hardware firewalls and Virtual Private Network (VPN) tunnels to separate trusted internal networks from untrusted external networks. Once a user or device connects through the VPN tunnel, the network implicitly trusts their traffic and grants broad access to internal resources.
Eliminating application-level access logging removes the granular operational visibility required for security investigations and financial regulatory audits. Furthermore, relying on implicit network trust contradicts modern cloud security paradigms, leaving workloads vulnerable if an attacker compromises a single set of credentials and breaches the VPN perimeter.
Establishing a VPN tunnel using Cloud VPN would be appropriate if the sole objective were to create an encrypted network link between an on-premises data center and a Google Cloud Virtual Private Cloud (VPC), rather than modernizing security visibility and access auditing.
Modern cloud security shifts away from physical and network perimeters toward a Zero Trust model. Instead of assuming trust based on network location or VPN connectivity, Google Cloud uses Identity-Aware Proxy (IAP), Cloud IAM, and Chrome Enterprise Premium to continuously verify user identity and device context at the application layer while logging all access events.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated