Skip to main content

Cloud Marketplace

Exam guide§1

Cloud Marketplace deploys pre-configured, ready-to-run solutions (a full Jenkins CI environment, a LAMP stack, WordPress, and so on) with no manual VM, network, or storage setup - what would take hours or days by hand launches in minutes. Listings come from third-party vendors who ship their own declarative deployment configurations, so you deploy now and scale later when the application needs more capacity. After deployment you administer the software through its own UI and SSH into the host VM as normal.

FactsWhat Marketplace gives you
  • Production-grade solutions from third-party vendors, pre-packaged as deployment configs (Terraform today; older listings use Deployment Manager).
  • Single bill - Marketplace charges are billed together with the rest of your project's Google Cloud services.
  • Bring-your-own-license (BYOL) - if you already hold a license for a third-party product, some listings let you reuse it instead of paying again.
  • Managed images - Google patches the published images for critical issues and vulnerabilities, and notifies you when a security update is available.
  • Direct partner support for the vendor's software.

Marketplace is just a deployment config

The key exam concept: a Marketplace listing is a pre-built infrastructure-as-code configuration. When you click Deploy, Google Cloud runs that config - historically this drops you straight into Deployment Manager, where you can inspect the generated config and imported template files. The solution provisions and wires up every resource for you (VM, boot disk, firewall rules), so you never recreate them by hand.

1 · MarketplaceSearch a solution(LAMP, pick a provider)2 · ConfigureInstance type, HTTPfirewall, logging3 · DeployRuns the config viaDeployment Manager4 · RunningAddress, user,password, SSHDeployment Manager provisionsCompute Engine VMN1 instance, Linux +Apache + MySQL + PHPPersistent diskboot volumeHTTP firewall ruleallow TCP :80
Deploying a LAMP stack: a Marketplace listing runs as a Deployment Manager config that provisions the VM, disk, and firewall

The deployed VM also shows up in the normal Compute Engine instance list - it is an ordinary VM once running. The overview page hands you the site address, an admin user and generated password, and next steps you'd otherwise wire up yourself: open HTTPS traffic, change the password, or swap the default ephemeral external IP for a static one.

GotchaGoogle patches the image, not your running deployment

Marketplace keeps the published images current for critical issues and vulnerabilities, but it does not touch software you have already deployed. Once your VM is running, patching and upgrades are on you (or the vendor's support), exactly like any other Compute Engine instance.

GotchaYou still pay for the underlying resources

Marketplace removes the setup work, not the cost. Many listings are free software with no usage fee, but you are billed for the Compute Engine, disk, and network resources they provision (subject to normal sustained-use discounts) - and some listings carry their own commercial licensing fees.

0%0 of 147 pages studied