PAS-C01 Design of SAP Workloads on AWS Practice Test 21 — 15 Questions

Question 1

A company is planning to migrate its SAP HANA database to AWS. Which instance type is specifically designed for SAP HANA workloads on AWS?

Accepted Answer

x1e.32xlarge. The x1e.32xlarge instance is specifically designed and certified by SAP for production SAP HANA workloads on AWS. It offers 3.9 TB of memory and high storage throughput, meeting SAP's stringent memory-to-vCPU ratio and performance requirements for HANA databases.

Answer

r5.24xlarge

Answer

c5.18xlarge

Answer

t3.2xlarge

Question 2

A company is running SAP ERP on AWS and wants to ensure high availability for the SAP Central Services (ASCS) instance. Which AWS service should be used to achieve this?

Accepted Answer

Elastic Load Balancer (NLB). For SAP ASCS high availability, AWS recommends using a Network Load Balancer (NLB) to manage the virtual IP address (VIP) required by SAP. The NLB handles the failover of the ASCS instance between two EC2 nodes by directing traffic to the active node, ensuring seamless client connectivity without relying on a floating IP or custom scripts.

Answer

EC2 Auto Scaling

Answer

Amazon Route 53

Answer

AWS Global Accelerator

Question 3

A company is designing a multi-zone SAP system on AWS. They want to minimize network latency between SAP application servers and the SAP HANA database. What is the best practice for deploying these components?

Accepted Answer

Deploy application servers and HANA in the same AZ and same VPC.. Deploying both the SAP application servers and the SAP HANA database in the same Availability Zone (AZ) and the same VPC minimizes network latency because traffic stays within a single data center, using low-latency, high-bandwidth links. SAP HANA is latency-sensitive, and even single-digit millisecond increases can degrade performance; co-location in the same AZ ensures the lowest possible round-trip time (RTT) for SQL queries and data transfers.

Answer

Deploy in different VPCs and use VPC peering.

Answer

Deploy in different AWS Regions.

Answer

Deploy application servers in one AZ and HANA in another AZ.

Question 4

An SAP administrator needs to integrate SAP S/4HANA with Amazon S3 for archival purposes. Which AWS service should be used to enable secure and efficient data transfer from SAP to S3?

Accepted Answer

AWS DataSync. AWS DataSync is the correct choice because it is purpose-built for efficiently and securely transferring large volumes of data from on-premises or SAP systems to Amazon S3. It automates the transfer process, supports encryption in transit (TLS) and at rest, and can handle the high-throughput requirements of SAP S/4HANA archival jobs without requiring custom scripting or complex network configurations.

Answer

Amazon Kinesis

Answer

Amazon Athena

Answer

AWS Glue

Question 5

A company is running SAP HANA on AWS and needs to back up the database to Amazon S3. Which approach provides the most efficient and cost-effective backup strategy?

Accepted Answer

Use SAP HANA Backint agent to back up directly to S3.. The SAP HANA Backint agent is the native, certified integration for backing up SAP HANA directly to Amazon S3. It leverages the SAP HANA backup API to stream data directly to S3 without intermediate storage, providing the most efficient path with minimal overhead and cost, as you only pay for S3 storage and API calls.

Answer

Use AWS Storage Gateway with tapes.

Answer

Take EBS snapshots of the HANA data volumes.

Answer

Copy HANA data files to EC2 instance store.

Question 6

An SAP system on AWS is experiencing high read latency from the SAP HANA database. The system uses Provisioned IOPS EBS volumes. Which action would most likely improve read latency?

Accepted Answer

Increase the provisioned IOPS on the EBS volumes.. Increasing the provisioned IOPS on the EBS volumes directly addresses high read latency by raising the I/O performance ceiling for the SAP HANA database. Since the system already uses Provisioned IOPS (io1/io2) volumes, higher IOPS reduces queue depth and read latency under heavy workloads. Other options are incorrect: changing to gp2 reduces IOPS, disabling write caching does not improve read latency, and instance store volumes are ephemeral and not recommended for HANA data persistence.

Answer

Change the EBS volume type to gp2.

Answer

Disable write caching on the EBS volumes.

Answer

Move the HANA data to instance store volumes.

Question 7

A company wants to use AWS Systems Manager to automate patching of SAP application servers. What is a prerequisite for Systems Manager to manage these EC2 instances?

Accepted Answer

Install the SSM Agent on the EC2 instances.. AWS Systems Manager requires the SSM Agent to be installed and running on EC2 instances to enable communication with the Systems Manager service for patching and other management tasks. Without the agent, Systems Manager cannot send commands, initiate patching workflows, or gather inventory data from the instances. The SSM Agent is pre-installed on many Amazon Linux and Windows AMIs but must be manually installed on custom or imported images.

Answer

Enable SSH access to the instances.

Answer

Assign a separate IAM role to each instance.

Answer

Ensure the instances have public IP addresses.

Question 8

A company is deploying a new SAP HANA database on AWS and needs to ensure the EBS volumes are optimized for throughput. Which EBS volume type should be used for the HANA data and log volumes?

Accepted Answer

io2 Block Express. For SAP HANA data and log volumes, io2 Block Express (option B) is the correct choice because it provides the highest throughput and IOPS consistency required for SAP HANA's demanding workload. io2 Block Express supports up to 256,000 IOPS and 4,000 MB/s throughput per volume, with 99.999% durability, making it ideal for mission-critical SAP HANA databases on AWS.

Answer

sc1

Answer

gp3

Answer

st1

Question 9

An SAP system on AWS uses a Classic Load Balancer to distribute traffic to web dispatchers. The system is experiencing intermittent timeouts. What is the most likely cause?

Accepted Answer

The load balancer idle timeout setting is too low.. The Classic Load Balancer has a default idle timeout of 60 seconds for TCP connections. If the SAP application or web dispatchers keep connections open longer than this without data transfer (e.g., during long-running reports or user think time), the load balancer will close the connection, causing intermittent timeouts. Increasing the idle timeout to match the application's keep-alive settings resolves this.

Answer

The security group for the load balancer is blocking traffic.

Answer

Sticky sessions are enabled on the load balancer.

Answer

The load balancer health check interval is too short.

Question 10

Which TWO of the following are recommended best practices for deploying SAP HANA on AWS? (Choose two.)

Accepted Answer

Use EBS-optimized instances for HANA workloads.. EBS-optimized instances provide dedicated network bandwidth for Amazon EBS I/O, which is critical for SAP HANA's high-throughput, low-latency storage requirements. Without EBS optimization, network traffic can contend with EBS traffic, causing performance degradation and potential SLA violations for HANA workloads.

Answer

Deploy HANA in a single Availability Zone to reduce costs.

Answer

Disable hyper-threading on the HANA instance.

Answer

Store HANA data on instance store volumes for better performance.

Question 11

Which THREE of the following are valid methods to secure network traffic between SAP application servers and the SAP HANA database on AWS? (Choose three.)

Accepted Answer

Use VPC peering to connect different VPCs securely.. VPC peering allows you to connect SAP application servers in one VPC to SAP HANA databases in another VPC securely using private IP addresses, with traffic staying within the AWS network and not traversing the public internet. This is a valid method for securing network traffic between these components when they are deployed in separate VPCs.

Answer

Use AWS Direct Connect to encrypt traffic.

Answer

Use AWS Shield to encrypt traffic.

Question 12

A company is designing a disaster recovery (DR) strategy for SAP HANA on AWS. Which TWO of the following are valid DR approaches? (Choose two.)

Accepted Answer

Configure HANA System Replication to a secondary Region.. HANA System Replication (HSR) is a native SAP feature that asynchronously replicates the in-memory database to a secondary Region, enabling a full DR failover with minimal data loss. This approach is fully supported on AWS by deploying HANA instances in different Availability Zones or Regions, and it meets the RPO/RTO requirements for enterprise SAP HANA workloads.

Answer

Use S3 cross-Region replication (CRR) to copy HANA backups.

Answer

Use AWS Backup with cross-Region copy.

Answer

Use Amazon RDS cross-Region read replicas for HANA.

Question 13

An SAP administrator created the IAM policy shown in the exhibit to allow an EC2 instance to back up to an S3 bucket. However, the backup fails with an access denied error. What is the most likely issue?

Accepted Answer

The policy does not grant permissions on the bucket itself.. The IAM policy shown in the exhibit grants permissions on individual objects within the S3 bucket (using the `arn:aws:s3:::bucket-name/*` resource ARN) but does not grant any permissions on the bucket itself (using `arn:aws:s3:::bucket-name`). For backup operations, the EC2 instance typically needs to list the bucket or check its existence before writing objects, which requires `s3:ListBucket` or similar actions on the bucket resource. Without these bucket-level permissions, the backup fails with an access denied error.

Answer

The actions specified are insufficient for backup operations.

Answer

The resource ARN is incorrectly formatted.

Answer

The bucket is in a different region than the EC2 instance.

Question 14

An SAP administrator runs the AWS CLI command shown in the exhibit for an EC2 instance running SAP HANA. The administrator notices that the /dev/sdf volume does not have DeleteOnTermination set to true. What is the impact of this configuration?

Accepted Answer

The volume will persist after instance termination, preserving data.. When the DeleteOnTermination attribute of an EBS volume is set to false (as indicated by the absence of 'true' in the AWS CLI output for /dev/sdf), the volume will not be automatically deleted when the EC2 instance is terminated. Instead, the volume enters a 'available' state and persists independently, preserving all data for later use or reattachment. This is critical for SAP HANA workloads where data volumes must survive instance termination for disaster recovery or migration scenarios.

Answer

The volume will be detached but not deleted.

Answer

The volume will be automatically deleted when the instance is terminated.

Answer

The volume cannot be attached to another instance.

Question 15

An administrator creates a CloudFormation stack with the template shown in the exhibit. The stack creates an Auto Scaling group with a desired capacity of 2. However, only one instance is launched. What is the most likely reason?

Accepted Answer

The Auto Scaling group is unable to launch the second instance due to capacity constraints.. The Auto Scaling group's desired capacity of 2 cannot be met if there are insufficient EC2 instance resources (e.g., vCPU, memory, or network capacity) in the selected Availability Zones. AWS Auto Scaling will launch as many instances as possible up to the desired capacity, but if the second instance launch fails due to a capacity constraint (e.g., insufficient m5.large capacity in the specified AZs), only one instance will be launched. The stack creation will still succeed, but the Auto Scaling group will remain at the lower count until capacity becomes available.

Answer

The instance type m5.large is not available in the selected AZs.

Answer

The DesiredCapacity is set incorrectly to 1.

Answer

The MinSize is set to 1, so only one instance is allowed.