nerdexam
Check_Point

156-561 · Question #28

Deployment of a Security Gateway was initiated on AWS using a CloudFormation Template available through sk111013. The deployment process, after a while failed and rolled back. What could be the…

The correct answer is B. The specific software being deployed was not subscribed to in the AWS Marketplace. When deploying a product from AWS Marketplace (such as a Check Point Security Gateway) via CloudFormation, the template references a specific AMI that is tied to a Marketplace listing - if your AWS account has not explicitly subscribed to that product, the EC2 instance launch…

CloudGuard Network Security in AWS

Question

Deployment of a Security Gateway was initiated on AWS using a CloudFormation Template available through sk111013. The deployment process, after a while failed and rolled back. What could be the probable cause of this failure and roll back?

Options

  • AThe Security Management Server that will be managing the Security Gateway had a lower
  • BThe specific software being deployed was not subscribed to in the AWS Marketplace
  • CThe template used was for some cloud platform other than AWS
  • DThe web browser used to run the template was not compatible

How the community answered

(28 responses)
  • A
    4% (1)
  • B
    86% (24)
  • C
    4% (1)
  • D
    7% (2)

Explanation

When deploying a product from AWS Marketplace (such as a Check Point Security Gateway) via CloudFormation, the template references a specific AMI that is tied to a Marketplace listing - if your AWS account has not explicitly subscribed to that product, the EC2 instance launch will be rejected mid-deployment, causing the entire CloudFormation stack to fail and trigger a rollback. This is a very common "gotcha" because the template itself is valid and the process starts normally, but fails only when AWS tries to actually launch the instance.

Why the distractors are wrong:

  • A is incorrect because a version mismatch between the gateway and management server would only surface as a connectivity or policy-push issue after a successful deployment, not as a CloudFormation rollback.
  • C is incorrect because sk111013 is a Check Point solution article specifically for AWS; a wrong-platform template would typically fail template validation immediately, not "after a while."
  • D is incorrect because CloudFormation execution is entirely server-side; the browser is only used to initiate the request and has no bearing on whether the stack succeeds or fails.

Memory tip: Think "Subscribe, then Deploy" - AWS Marketplace AMIs require a one-time subscription acceptance in your account before any CloudFormation template referencing that AMI can successfully launch. If you skip that step, AWS will block the instance launch mid-stack.

Topics

#CloudFormation#AWS Marketplace#CloudGuard Gateway#Deployment Prerequisites

Community Discussion

No community discussion yet for this question.

Full 156-561 Practice