PAS-C01 Practice Exam 51 — 20 Questions

Question 1

A company runs a critical SAP ERP system on AWS. The architecture includes an SAP HANA database on an r5.24xlarge instance (with 768 GB RAM) in us-east-1a, and multiple SAP application servers in an Auto Scaling group across two Availability Zones (us-east-1a and us-east-1b). The database uses EBS volumes: two 1 TB gp3 volumes for data, one 500 GB gp3 for log, and one 100 GB gp3 for backup. The system has been running without issues for months. At 3:00 PM, the operations team receives alerts from Amazon CloudWatch that the HANA database instance's CPU utilization is at 100%, memory usage is at 95%, and the disk queue length for the log volume is consistently above 10. The SAP application is experiencing intermittent timeouts. The team checks the HANA studio and sees that there are many long-running queries and that the log volume is almost full (95% used). The database backups are scheduled to run at 2:00 AM and completed successfully. There have been no changes to the system or workload recently. The team suspects a performance degradation. What is the MOST likely cause of the issue?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

The log volume is almost full, causing HANA to stall transaction processing.. The most likely cause is that the HANA log volume is almost full (95% used). When the log area reaches capacity, SAP HANA suspends transaction processing to prevent log overflow, leading to timeouts and increased CPU/memory usage as transactions queue. Option D correctly identifies this. Option A is incorrect because HANA's memory management is dynamic and not constrained by global.ini limits. Option B is incorrect because the gp3 volumes have baseline IOPS of 3000, which is sufficient, and the symptom is log volume full, not I/O performance. Option C is incorrect because backups completed at 2:00 AM, hours before the issue.

Answer

The HANA database has reached its memory limit due to the global.ini allocation.

Answer

The gp3 volume's baseline IOPS are insufficient for the current workload.

Answer

A backup job is running and consuming CPU and I/O resources.

Question 2

A company runs its SAP ERP system on AWS using a multi-tier architecture. The SAP application servers are in an Auto Scaling group across two Availability Zones, and the SAP HANA database runs on a single large EC2 instance (r5.24xlarge) with 768 GB of memory and EBS Provisioned IOPS SSD (io1) volumes. The operations team recently noticed that the database performance degrades intermittently during peak business hours. CloudWatch metrics show that the database instance's CPU utilization remains below 40%, but the ReadLatency and WriteLatency for the EBS volumes spike above 10 ms during these periods, and the VolumeQueueLength metric increases significantly. The database instance uses a single EBS volume for /hana/data and another for /hana/log. The team has already verified that there are no network bottlenecks and that the SAP application servers are not overwhelming the database with queries. What is the MOST likely cause of the latency spikes, and what action should be taken?

Accepted Answer

Upgrade the EC2 instance to a Nitro-based instance type like r5b.24xlarge, which provides higher EBS bandwidth and lower latency.. The symptoms indicate that the EBS volumes are experiencing queueing due to insufficient I/O performance. The r5.24xlarge instance uses the Xen hypervisor, which has lower EBS bandwidth compared to Nitro-based instances like r5b.24xlarge. Upgrading to a Nitro instance provides dedicated EBS bandwidth and lower latency, addressing the latency spikes. Option A is incorrect because st1 (throughput optimized) is not suitable for low-latency database workloads; it is designed for large sequential I/O. Option B is incorrect because adding more application servers would increase the database load, exacerbating the issue. Option C is incorrect because EBS encryption does not improve I/O performance.

Answer

Change the EBS volume type from io1 to st1 for higher throughput.

Answer

Add more SAP application servers to distribute the load and reduce database contention.

Answer

Enable EBS encryption on the volumes to improve I/O performance.

Question 3

A company is running SAP on AWS and needs to monitor the health of their SAP application servers. Which TWO AWS services can be used together to achieve this?

Accepted Answer

Amazon CloudWatch. Options B (Amazon CloudWatch) and C (Amazon Route 53) are correct. CloudWatch can collect and monitor metrics from SAP application servers, and Route 53 health checks can monitor the endpoints of those servers. Option A (AWS X-Ray) is for request tracing, D (AWS CloudTrail) is for API activity logging, and E (Amazon Inspector) is for security vulnerability assessment.

Answer

AWS X-Ray

Answer

AWS CloudTrail

Answer

Amazon Inspector

Question 4

A company runs SAP HANA on AWS using a clustered environment with two EC2 instances in an active/passive configuration. The cluster uses a shared EFS file system for the SAP HANA shared volume. The operations team recently migrated the EFS file system from the previous generation to Elastic Throughput mode to improve performance. After the migration, the HANA database becomes unresponsive intermittently. The team notices that the EFS mount target is in a different Availability Zone than the active HANA instance. What is the most likely cause of the unresponsiveness?

Accepted Answer

The EFS mount target is in a different Availability Zone than the active HANA instance, causing high latency and potential timeouts.. The most likely cause of unresponsiveness is that the EFS mount target is in a different Availability Zone than the active HANA instance. Cross-AZ access to EFS introduces higher latency and potential network timeouts, which can cause HANA database interruptions. Option A is incorrect: EFS provides adequate throughput for HANA shared volumes; IOPS is not the issue. Option B is incorrect: Elastic Throughput mode automatically scales throughput based on workload activity, so it would not throttle unless the workload exceeds burst credit balance, but that is not indicated. Option D is incorrect: EFS does not have a hard limit on concurrent connections from two EC2 instances.

Answer

The EFS file system does not provide sufficient IOPS for HANA workloads.

Answer

The EFS Elastic Throughput mode is throttling the HANA database traffic.

Answer

The EFS file system has reached its maximum number of concurrent connections.

Question 5

An administrator needs to retrieve the private IP address of an ASCS instance that was deployed via AWS CloudFormation. What is the most efficient way to get this IP address?

Accepted Answer

Modify the CloudFormation template to add the private IP as an output.. CloudFormation stack outputs are the intended mechanism for exposing resource attributes, such as private IP addresses, after stack creation. By modifying the template to include the private IP as an output, the administrator can retrieve it directly via the AWS CLI `describe-stacks` command without additional API calls or manual lookups, making it the most efficient and automated approach.

Answer

Check the CloudFormation stack events for the private IP.

Answer

Use the AWS CLI to describe the EC2 instance using the instance ID.

Answer

Use AWS Systems Manager to find the IP from the instance ID.

Question 6

A company is running SAP ERP on AWS and is experiencing high costs due to underutilized EC2 instances. The SAP system is non-production and can tolerate interruptions. Which approach would most cost-effectively reduce costs without compromising the ability to resume operations quickly?

Accepted Answer

Use EC2 Spot Instances for the application servers and configure them to be terminated gracefully. EC2 Spot Instances offer significant cost savings (up to 90% compared to On-Demand) for fault-tolerant, non-production SAP workloads. By configuring graceful termination (e.g., using lifecycle hooks or AWS Systems Manager to drain SAP application server connections before the instance is interrupted), the system can resume quickly when capacity becomes available again, meeting the requirement for cost reduction without compromising rapid recovery.

Answer

Purchase Reserved Instances for the current usage to get a discount

Answer

Increase the instance size to improve performance and reduce runtime

Answer

Use Dedicated Hosts to reduce licensing costs

Question 7

A company is migrating an SAP system to AWS. They want to use an AWS service to automate the deployment of SAP applications according to best practices. Which TWO services can be used for this purpose? (Choose TWO.)

Accepted Answer

AWS CloudFormation. AWS Launch Wizard and AWS CloudFormation can automate SAP deployments according to best practices. Option A (AWS OpsWorks) is for configuration management, not SAP-specific deployment. Option B (AWS Elastic Beanstalk) is for general web applications, not SAP. Option C (AWS CodeDeploy) is for application deployment, not infrastructure provisioning. Options D and E are correct.

Answer

AWS OpsWorks

Answer

AWS Elastic Beanstalk

Answer

AWS CodeDeploy

Question 8

A company runs a critical SAP application on an SAP HANA database in a single Availability Zone on AWS. The database is 2 TB in size. The company needs to implement a disaster recovery (DR) strategy with a Recovery Point Objective (RPO) of 15 minutes and a Recovery Time Objective (RTO) of 2 hours. The DR region must be in a different AWS Region. Which solution meets these requirements with the LEAST operational overhead?

Accepted Answer

Use AWS Database Migration Service (DMS) to continuously replicate data from the HANA database to a HANA database in the DR region.. AWS Database Migration Service (DMS) with continuous replication (change data capture) can achieve an RPO of 15 minutes for a 2 TB SAP HANA database across AWS Regions. The RTO of 2 hours is achievable by provisioning the target HANA instance in advance and applying changes. This solution uses a fully managed AWS service, reducing operational overhead compared to manual scripting or third-party tools. While SAP HANA System Replication (HSR) is native, cross-region synchronous replication is not feasible due to latency; asynchronous HSR could meet the RPO but is not listed as an option. DMS provides continuous replication with minimal setup and monitoring, making it the best choice among the given options.

Answer

Configure SAP HANA System Replication (HSR) in a multitier setup with a primary in the source region and a synchronous secondary in the DR region. Use HANA takeover for failover.

Answer

Deploy a second HANA node in a different Availability Zone in the same region and configure HANA System Replication. Use AWS Global Accelerator to route traffic to the standby.

Answer

Use AWS Backup to schedule daily snapshots of the HANA database and copy them to the DR region. In the event of a disaster, restore the latest snapshot to a new HANA instance.

Question 9

An SAP system running on AWS is experiencing high CPU utilization on the database server. The database is SAP HANA running on an r5.8xlarge instance. Which metric in Amazon CloudWatch would best indicate whether the CPU is being consumed by the HANA process or by other OS processes?

Accepted Answer

Custom metrics collected by the CloudWatch agent for the hdbindexserver process. The CloudWatch agent can be configured to collect custom metrics for specific processes, such as hdbindexserver (the main SAP HANA index server process). By monitoring the CPU utilization of this specific process, you can directly determine whether the HANA database process itself is consuming the CPU, as opposed to other OS-level processes like kernel threads, system daemons, or other applications. This granularity is not available from the EC2 instance-level CPUUtilization metric.

Answer

CPUUtilization metric from the EC2 instance

Answer

HANA CPU metric from SAP HANA CloudWatch integration

Answer

CPUCreditUsage metric

Question 10

An SAP Basis administrator is troubleshooting a performance issue on an SAP HANA database running on an EC2 instance. The administrator notices that the 'hdbcons' command shows high 'wait time' for 'disk I/O' operations. The instance is an r5.4xlarge with 500 GB of gp2 EBS volumes for /hana/data and /hana/log. Which of the following is the MOST effective action to improve disk I/O performance?

Accepted Answer

Change the EBS volume type from gp2 to gp3 with higher IOPS and throughput.. Changing the EBS volume type from gp2 to gp3 with higher IOPS and throughput is the most effective action because gp3 offers a baseline performance that can be increased independently of volume size, and it provides higher IOPS and throughput compared to gp2. This directly addresses the high disk I/O wait time. Upgrading the instance type (option C) may not resolve the I/O bottleneck if the volumes are the limiting factor. Increasing snapshot frequency (option A) does not improve I/O performance. Disabling delta merge (option D) is not recommended and does not address disk I/O issues.

Answer

Increase the frequency of EBS snapshots to offload I/O.

Answer

Upgrade to a larger EC2 instance type with more CPU and memory.

Answer

Disable the HANA delta merge operation to reduce I/O load.

Question 11

A company is migrating a SAP HANA database to AWS. The database is 10 TB and requires a recovery point objective (RPO) of 15 minutes and a recovery time objective (RTO) of 2 hours. Which backup strategy should be used?

Accepted Answer

Configure SAP HANA Backint agent to back up directly to Amazon S3 every 15 minutes.. The SAP HANA Backint agent can back up directly to Amazon S3, allowing frequent backups (every 15 minutes) to achieve an RPO of 15 minutes. HANA Backint backups are fast and reliable, and restoring from S3 can meet the 2-hour RTO. Option A (AWS DMS replication) is for ongoing data replication, not backup; it may not support HANA backup requirements and could exceed RTO. Option C (backups to EBS volume then copy to S3) introduces delays and manual processes, making it difficult to achieve a 15-minute RPO. Option D (AWS Backup with EBS snapshots) typically has a minimum interval of 1 hour, insufficient for a 15-minute RPO, and restoring a 10 TB database from snapshots may exceed the 2-hour RTO.

Answer

Use AWS DMS to replicate the HANA database to a standby instance.

Answer

Schedule SAP HANA backups to an EBS volume and copy to S3.

Answer

Use AWS Backup with EBS snapshots every hour.

Question 12

A company is designing an SAP HANA disaster recovery solution across AWS Regions. The primary site is in us-east-1 and the DR site is in us-west-2. The database size is 5 TB. The RTO is 1 hour and RPO is 15 minutes. Which method should be used for SAP HANA replication?

Accepted Answer

Configure SAP HANA System Replication in asynchronous mode to the DR region.. SAP HANA System Replication with asynchronous mode can replicate across regions with RPO of seconds to minutes. Option A is wrong because AWS DMS does not support SAP HANA as a target database. Option B is wrong because synchronous mode over long distances introduces high latency and is not feasible for cross-region replication. Option C is wrong because EBS snapshots alone cannot achieve a 15-minute RPO due to snapshot frequency limits and longer recovery time.

Answer

Use AWS Database Migration Service (DMS) to continuously replicate changes.

Answer

Configure SAP HANA System Replication in synchronous mode between the two regions.

Answer

Use AWS Backup to copy EBS snapshots to the DR region every 15 minutes.

Question 13

A company is deploying a new SAP S/4HANA system on AWS and needs to ensure that the application servers can communicate with the database servers securely and with low latency. The application servers and database servers are in different VPCs. Which AWS service should be used to connect these VPCs?

Accepted Answer

VPC Peering. VPC Peering is the correct choice because it establishes a direct network connection between two VPCs using AWS's internal infrastructure, enabling private IPv4 or IPv6 traffic with low latency and high throughput. For SAP S/4HANA, where application-to-database communication requires consistent sub-millisecond latency and avoids internet transit, VPC Peering provides the necessary Layer-3 connectivity without bandwidth bottlenecks or single points of failure. Unlike VPN or Direct Connect, VPC Peering does not introduce additional hop latency or third-party hardware, making it ideal for this intra-region, cross-VPC scenario.

Answer

AWS VPN

Answer

Amazon API Gateway

Answer

AWS Direct Connect

Question 14

A company runs SAP S/4HANA on AWS in a multi-AZ deployment. The SAP HANA database is 2 TB and uses EBS gp3 volumes. During a monthly patching cycle, the primary database fails over to the secondary, but the secondary takes over 30 minutes to come online. Which TWO changes would most likely reduce the failover time? (Choose two.)

Accepted Answer

Increase the provisioned IOPS and throughput on the EBS log volumes.. Increasing the provisioned IOPS and throughput on the EBS log volumes accelerates the replay of redo logs during the takeover process. SAP HANA relies on log replay to bring the secondary database to a consistent state; higher IOPS/throughput reduces the time required to apply pending log entries, directly shortening failover duration.

Answer

Use different EC2 instance types for primary and secondary to balance cost.

Answer

Deploy all HANA nodes in the same Availability Zone to reduce network latency.

Answer

Enable EBS optimization on the secondary instance's EBS volumes.

Question 15

A company plans to migrate its SAP systems to AWS and needs to set up a secure connection to the corporate data center. The company requires consistent network performance and low latency. Which AWS service should be used?

Accepted Answer

AWS Direct Connect. (AWS Direct Connect) is correct because it provides a dedicated private network connection from the corporate data center to AWS, ensuring consistent network performance and low latency. Option A (AWS Transit Gateway) is a network transit hub but does not itself provide a direct connection; it can be used with Direct Connect or VPN attachments. Option B (AWS Site-to-Site VPN) uses the public internet, which can lead to variable performance and latency. Option D (AWS Client VPN) is designed for individual remote clients, not for site-to-site connectivity.

Answer

AWS Transit Gateway

Answer

AWS Site-to-Site VPN

Answer

AWS Client VPN

Question 16

A company is migrating a legacy application to AWS. The application uses a custom TCP protocol and requires session persistence. The application runs on a fleet of EC2 instances behind a Network Load Balancer (NLB). The current configuration uses a TCP listener with 'source IP' stickiness. However, some clients are being routed to different instances mid-session, causing application errors. What is the most likely cause and solution?

Accepted Answer

Clients are behind a NAT gateway, so the source IP changes between requests, breaking stickiness. Use a 'stitched' cookie or switch to an Application Load Balancer.. Clients behind a NAT gateway will have their source IP address translated to the NAT gateway's public IP, which remains consistent for all requests from that gateway. However, if multiple clients share the same NAT gateway, the source IP is the same, but the NLB's source IP stickiness is based on the client's source IP as seen by the NLB. If the NAT gateway uses multiple public IPs or if clients are behind different NAT gateways, the source IP can change between requests, breaking stickiness. The solution is to use a 'stitched' cookie or switch to an Application Load Balancer, which supports cookie-based session persistence independent of source IP.

Answer

The NLB does not support source IP stickiness; use a Classic Load Balancer instead.

Answer

The NLB has cross-zone load balancing enabled, which distributes traffic across instances in different Availability Zones.

Answer

The idle timeout of the NLB is too low, causing the NLB to close connections prematurely.

Question 17

A company runs SAP on AWS and uses a multi-AZ deployment for SAP HANA. The operations team notices that the secondary HANA node in the standby replica is not automatically taking over during a planned failover test. What is the most likely cause?

Accepted Answer

HANA system replication is not configured with 'PRIMARY' and 'SECONDARY' roles.. For automatic failover in SAP HANA system replication, the secondary node must be configured with the 'SECONDARY' role and the primary with 'PRIMARY' role. If these roles are not set, the secondary will not automatically take over during a planned failover test. Option B is incorrect because security groups can block replication traffic, but that would prevent replication altogether, not just automatic failover during a planned test. Option C is incorrect because instance families do not affect automatic failover; HANA can run on different families but that is not a typical cause. Option D is incorrect because EBS replication is not a factor in HANA system replication; HANA uses its own replication mechanism.

Answer

Security Groups are blocking replication traffic.

Answer

The secondary instance is launched in a different instance family.

Answer

The EBS volumes are not configured for replication across AZs.

Question 18

The exhibit shows a CloudFormation template snippet for deploying SAP ASCS and ERS instances. Both instances are launched in the same subnet. What is the main architectural issue with this deployment?

Accepted Answer

Both instances are in the same Availability Zone, which defeats the purpose of high availability. For high availability, ASCS and ERS should be in different Availability Zones to avoid a single point of failure. Option B is wrong because the instance type is acceptable for a test environment. Option C is wrong because the AMI is not specified, but that is not the main issue. Option D is wrong because there is no security group defined, but that is a security issue, not an architectural HA issue.

Answer

The AMI ID is not specified correctly

Answer

The instance type m5.large is too small for SAP

Answer

No security group is defined, exposing the instances to the internet

Question 19

An SAP system is running on AWS and needs to be migrated from a current generation instance (r3) to a newer generation (r5). What is the recommended process to minimize downtime?

Accepted Answer

Stop the instance, change the instance type, and start the instance.. Stopping the instance is required to change the instance type for EC2 instances that are not configured for 'Stop/Start' hibernation or Nitro-based instance compatibility. For SAP systems running on current-generation instances (r3), which are Xen-based, a stop is necessary to modify the instance type to r5 (Nitro-based). This process minimizes downtime by allowing the instance to be stopped, changed, and started in a controlled manner, typically taking only a few minutes.

Answer

Modify the instance type while the instance is running.

Answer

Create an AMI of the r3 instance and launch an r5 instance from it.

Answer

Launch a new r5 instance and migrate the SAP system.

Question 20

A company is migrating a large SAP HANA workload to AWS. They need to ensure the fastest network throughput for data transfer between on-premises and AWS. Which AWS service or feature should they use?

Accepted Answer

AWS Direct Connect. AWS Direct Connect provides a dedicated, private network connection from on-premises to AWS, ensuring consistent high throughput and low latency—ideal for large SAP HANA migrations. Option A (Snowball Edge) is a physical device for offline data transfer, not suitable for real-time network throughput. Option B (Site-to-Site VPN) uses the public internet and may have variable performance, making it less optimal than Direct Connect. Option D (Client VPN) is designed for individual user remote access, not for high-volume data transfer.

Answer

AWS Snowball Edge

Answer

AWS Site-to-Site VPN

Answer

AWS Client VPN