nerdexam
Amazon

PAS-C01 · Question #92

A company is deploying SAP landscapes in a single AWS account. The company must use separate VPCs to host its production environment and non-production environment. The company is using an Amazon…

The correct answer is C. Set up a transit gateway or direct VPC peering to make communication possible between the. The deployment failure occurs because the production VPC and non-production VPC are isolated networks - even though they are in the same AWS account, the EFS mount target in the non-production VPC is not reachable from the production VPC. Setting up VPC peering (direct) or a…

Implementation of SAP Workloads on AWS

Question

A company is deploying SAP landscapes in a single AWS account. The company must use separate VPCs to host its production environment and non-production environment. The company is using an Amazon Elastic File System (Amazon EFS) file system to host the SAP transport file systems. An SAP engineer attempts to use AWS Launch Wizard for SAP to perform an automated SAP deployment of the production environment. A deployment failure occurs when the SAP engineer attempts to reuse the SAP transport directory share from the non-production environment. This failure did not occur in previous non-production deployments. The SAP engineer needs to complete the deployment and ensure that no additional costs are incurred for SAP transport directories. What should the SAP engineer do to meet these requirements?

Options

  • APerform a manual deployment.
  • BSet up a new SAP transport directory for the production environment. Copy all files from the non-
  • CSet up a transit gateway or direct VPC peering to make communication possible between the
  • DSkip the SAP transport directories step to complete the deployment.

How the community answered

(25 responses)
  • A
    12% (3)
  • B
    8% (2)
  • C
    76% (19)
  • D
    4% (1)

Explanation

The deployment failure occurs because the production VPC and non-production VPC are isolated networks - even though they are in the same AWS account, the EFS mount target in the non-production VPC is not reachable from the production VPC. Setting up VPC peering (direct) or a Transit Gateway between the two VPCs allows the production environment to reach the non-production EFS mount point, enabling Launch Wizard to reuse the existing SAP transport directory at no additional storage cost. Option A (manual deployment) would work but abandons the automation goal. Option B (copy files to a new EFS) would incur additional costs for duplicate storage. Option D (skip transport directory) would create an incomplete SAP landscape.

Topics

#AWS Networking#Amazon EFS#SAP Transport Management#AWS Launch Wizard

Community Discussion

No community discussion yet for this question.

Full PAS-C01 Practice