PAS-C01 Operations and Maintenance Practice Test 17 — 15 Questions

Question 1

A company runs SAP S/4HANA on AWS using an ASCS and PAS cluster with SUSE Linux Enterprise Server. The cluster fails over unexpectedly several times a day. What is the most likely cause and solution?

Accepted Answer

Cluster quorum loss due to insufficient votes; add a third node or configure a witness. The most likely cause of frequent failovers in an SAP S/4HANA cluster on AWS is cluster quorum loss due to insufficient votes. In a two-node cluster, if one node fails or there is a network partition, the remaining node may not have quorum to keep the cluster running, leading to failover. Adding a third node or configuring a witness (such as a quorum device) resolves this by providing additional votes.

Answer

High network latency between nodes; use placement groups

Answer

Insufficient memory on the cluster nodes; increase memory

Answer

Incorrect ASCS instance configuration; verify SAP profiles

Question 2

A company runs SAP Business Suite on AWS. The SAP system frequently crashes with a 'JAVA out of memory' error. The application server is an EC2 instance with 32 GB RAM. Which solution should be implemented to prevent this issue?

Accepted Answer

Configure Amazon CloudWatch alarms to trigger EC2 Auto Scaling based on memory utilization. By configuring Amazon CloudWatch alarms to trigger EC2 Auto Scaling based on memory utilization, the system can automatically add more application server instances when memory usage is high. This distributes the load and prevents any single instance from running out of Java heap space. Option A is incorrect because manually increasing the EC2 instance memory is a temporary workaround that does not scale automatically. Option B is incorrect as reducing the Java heap size would increase the likelihood of out-of-memory errors. Option C is incorrect because increasing swap space can cause severe performance degradation and does not resolve the underlying memory shortage.

Answer

Increase the EC2 instance memory to 64 GB

Answer

Reduce the Java heap size in the SAP system

Answer

Increase the swap space on the EC2 instance

Question 3

An SAP system is running on EC2 instances with EBS volumes. The administrator wants to automate the creation of point-in-time snapshots of the EBS volumes for disaster recovery. Which AWS service is best suited for this?

Accepted Answer

Amazon Data Lifecycle Manager (DLM). Amazon Data Lifecycle Manager (DLM) is the AWS service specifically designed to automate the creation, retention, and deletion of EBS snapshots. It allows you to define lifecycle policies that schedule snapshots at regular intervals, specify retention rules, and apply them to volumes tagged with specific keys. This directly meets the requirement for automated point-in-time snapshots for disaster recovery.

Answer

AWS Backup

Answer

Amazon S3 Lifecycle policies

Answer

AWS CloudFormation

Question 4

A company recently migrated SAP ERP to AWS. The SAP application logs indicate repeated 'ORA-1555 snapshot too old' errors in the Oracle database. Which AWS-specific parameter could be causing this?

Accepted Answer

EBS volume queue depth is too low causing I/O throttling. The 'ORA-1555 snapshot too old' error occurs when Oracle's undo data is overwritten before a long-running query finishes, typically because the undo tablespace is undersized or the undo retention period is too short. On AWS, this is frequently triggered by EBS I/O latency: when the EBS volume's queue depth is too low, I/O operations queue up, making queries run much longer than expected. Those extended runtimes exceed the undo retention window, causing the snapshot to become too old. Thus, an AWS-specific parameter—EBS volume queue depth—can indirectly cause the error by throttling I/O and prolonging query execution.

Answer

Enhanced Networking is disabled

Answer

Incorrect Oracle DB parameter settings

Answer

EBS snapshot schedule is too frequent

Question 5

Which TWO AWS services can be used to perform automated backups of an SAP HANA database running on EC2? (Choose 2.)

Accepted Answer

AWS Backup. AWS Backup (D) is correct because it is a fully managed backup service that supports SAP HANA databases on EC2 through its application-consistent backup capabilities, allowing you to define backup plans with schedules and retention policies that automate the backup process. Amazon Data Lifecycle Manager (E) is correct because it automates the creation, retention, and deletion of EBS snapshots, which can be used to back up the EBS volumes hosting the SAP HANA database on EC2. Amazon CloudWatch Events (A) is only an event-routing service and does not itself perform backups, Amazon S3 (B) is a storage service rather than a backup orchestration tool, and AWS CloudTrail (C) is an API activity logging service, not a backup mechanism.

Answer

Amazon CloudWatch Events

Answer

Amazon S3

Answer

AWS CloudTrail

Question 6

Which TWO AWS services can be used to automate the restart of an SAP application server when it becomes unresponsive? (Choose 2.)

Accepted Answer

Amazon CloudWatch alarm with an EC2 action to recover the instance. Option B is correct because a CloudWatch alarm can monitor an SAP application server (e.g., via a custom metric or status check) and trigger an EC2 action to recover or reboot the instance, which restarts the SAP application server when it becomes unresponsive. Option C is correct because an AWS Systems Manager Automation document can run predefined or custom runbooks that execute commands on the instance (such as restarting the SAP application server process) or reboot the instance, providing automated remediation. Option A is incorrect because Amazon ECS service auto-recovery applies to containerized tasks in ECS, not to SAP application servers running on EC2. Option D is incorrect because an EC2 Auto Scaling group with a health check replaces unhealthy instances, which would terminate and recreate the instance rather than simply restart the SAP application server. Option E is incorrect because EventBridge with a Lambda function is a generic event-driven automation pattern and is not a specific AWS service designed for restarting an SAP application server; while it could be used, it is not one of the two intended services for this scenario.

Answer

Amazon ECS service auto-recovery

Answer

EC2 Auto Scaling group with a health check

Answer

Amazon EventBridge with a Lambda function

Question 7

A company runs SAP S/4HANA on AWS with a High Availability (HA) cluster spanning two Availability Zones (us-east-1a and us-east-1b). The cluster uses an Amazon FSx for NetApp ONTAP file system for the global transport directory. Recently, the cluster experienced a split-brain situation, leading to data corruption. The administrator wants to prevent this from recurring. The current setup uses a single FSx file system mounted on both cluster nodes. What should the administrator do to prevent split-brain?

Accepted Answer

Configure a STONITH (Shoot The Other Node In The Head) mechanism using AWS Lambda. A STONITH mechanism ensures that in a split-brain scenario, one node is forcibly fenced off (powered off or isolated) to prevent both nodes from accessing shared storage simultaneously. Using AWS Lambda to trigger the fencing action (e.g., stopping the EC2 instance) provides a reliable way to prevent data corruption. This is a standard practice in HA clusters to maintain quorum and data integrity.

Answer

Add a third cluster node in a third Availability Zone

Answer

Increase the memory on both EC2 instances

Answer

Set up cross-region replication for the FSx file system

Question 8

A company runs a critical SAP HANA database on an m5.24xlarge EC2 instance. The operations team notices that the database performance degrades during peak hours. Which AWS service should be used to identify whether the instance is experiencing CPU throttling due to CPU credit exhaustion?

Accepted Answer

Use CloudWatch to monitor the CPUUtilization metric.. CPU credit exhaustion on a burstable instance is diagnosed by monitoring the CPUCreditBalance CloudWatch metric. When the balance hits zero, the instance is throttled to baseline performance, which explains the peak-hour degradation. CloudWatch is the correct service to observe this metric.

Answer

Use CloudTrail to review the EC2 instance launch configuration.

Answer

Use AWS Trusted Advisor to check for instance performance issues.

Answer

Use CloudWatch to monitor the CPUCreditBalance metric.

Question 9

An SAP administrator is troubleshooting an issue where SAP application servers are unable to connect to the SAP HANA database. The database is running on an EC2 instance in a private subnet. The application servers are in a different VPC connected via VPC peering. The security group for the database instance allows TCP port 3$15$13 from the application server security group. Which additional configuration is MOST likely required?

Accepted Answer

Enable DNS resolution for the VPC peering connection.. VPC peering does not automatically enable DNS resolution for hostnames across peered VPCs. The application servers need to resolve the database's private DNS hostname to its private IP. By default, DNS resolution for peered VPCs is disabled. Enabling DNS resolution on the VPC peering connection allows the application servers to resolve the database's hostname, which is essential for connectivity. Option A is incorrect as the security group already allows the port; Option B is incorrect because the route tables already handle traffic via the peering connection; Option C is incorrect because network ACLs are not the core issue—the problem is DNS resolution, not NACL rules.

Answer

Modify the security group to allow traffic from the application server subnet CIDR.

Answer

Update the route tables to add a route to the database subnet.

Answer

Add a rule to the network ACL to allow inbound traffic on port 3$15$13.

Question 10

An SAP system running on AWS uses a Multi-AZ RDS for SAP ASE database. The operations team notices that the database failover took longer than expected during a recent outage. What should the team investigate to reduce failover time?

Accepted Answer

Check for long-running transactions that delay the failover.. Multi-AZ failover time is primarily affected by the time required to complete in-flight transactions and apply redo logs to the standby. Long-running transactions can delay failover because they must be completed or rolled back before the standby can become the primary. Option A is incorrect because increasing storage may improve I/O performance but does not directly reduce failover time. Option B is incorrect because the standby must be in a different Availability Zone for Multi-AZ. Option D is incorrect because Multi-AZ RDS uses synchronous replication, not asynchronous.

Answer

Increase the allocated storage for the database to improve I/O performance.

Answer

Ensure that the standby instance is in the same Availability Zone as the primary.

Answer

Verify that the database is using asynchronous replication.

Question 11

A company runs SAP on AWS and uses a shared file system via Amazon EFS for transport files. Recently, the SAP system experienced slowness when importing transports. The CloudWatch metrics show high BurstCreditBalance for the EFS file system. What action should be taken to improve performance?

Accepted Answer

Enable Max I/O performance mode on the EFS file system.. When BurstCreditBalance is high, it indicates that the file system is not using its burst credits, meaning it is operating at baseline throughput. To improve performance, enable Max I/O performance mode on the EFS file system, which provides higher throughput and IOPS. Option B is incorrect because changing to General Purpose mode does not increase throughput; it may even reduce performance. Option C is incorrect because encryption does not affect throughput. Option D is incorrect because BurstCreditBalance cannot be purchased; it is automatically accrued and consumed.

Answer

Change the performance mode to General Purpose.

Answer

Enable encryption at rest to improve data transfer speed.

Answer

Increase the BurstCreditBalance by purchasing additional credits.

Question 12

A company runs SAP HANA on AWS and needs to perform a backup of the HANA database to Amazon S3. Which AWS service should be used to orchestrate the backup and ensure consistency?

Accepted Answer

AWS Backup with pre- and post-backup scripts for application-consistent backups.. AWS Backup supports SAP HANA backups with application-consistent snapshots by using pre- and post-backup scripts to quiesce the database and ensure data integrity. It orchestrates the backup process and integrates with Amazon S3 for storage. This approach ensures that the HANA database is in a consistent state before the backup is taken, which is critical for SAP HANA.

Answer

Amazon S3 Lifecycle policies to transition backups to Glacier.

Answer

Amazon Data Lifecycle Manager (DLM) to schedule EBS snapshots.

Answer

AWS Storage Gateway file gateway to back up to S3.

Question 13

During a disaster recovery test, an SAP administrator finds that the SAP application cannot connect to the replicated HANA database in the DR region. The replication is done using SAP HANA System Replication. What is the MOST likely cause?

Accepted Answer

The application connection string still points to the primary database endpoint.. In SAP HANA System Replication, the database is replicated to the DR region, but the SAP application's connection string must be updated to point to the DR database endpoint. Without this update, the application will still try to connect to the primary database endpoint, which is not accessible during the DR test. Option A is incorrect because the replication link being down does not cause the application connection failure; the issue is the connection string. Option C is incorrect because even if the DR database is not fully synchronized (which is typical for async replication), the application could still connect to the DR database if the connection string were correct. Option D is incorrect because simply restarting the application server does not update the connection string; the endpoint configuration needs to be changed.

Answer

The replication link is down because the source database is not accessible.

Answer

The HANA database in the DR region is not synchronized due to network latency.

Answer

The application server needs to be restarted to recognize the new database.

Question 14

An SAP administrator is troubleshooting a performance issue where the SAP application is slow. The administrator suspects that the EBS volumes are not meeting performance requirements. Which THREE metrics should be examined in Amazon CloudWatch to confirm this? (Choose THREE.)

Accepted Answer

VolumeQueueLength. VolumeQueueLength (A) is correct because it measures the number of read/write requests waiting to be serviced on the EBS volume; a consistently elevated queue length indicates the volume cannot keep up with the I/O demand, directly confirming a performance bottleneck. VolumeReadBytes (B) is correct because it reports the total bytes read from the volume, letting the administrator quantify read throughput and compare it against the volume's provisioned IOPS/throughput limits. VolumeWriteBytes (C) is correct because it reports the total bytes written, allowing the same throughput analysis for write-heavy SAP workloads (e.g., database redo/transaction logs). CPUCreditBalance (D) is not relevant because it applies to burstable EC2 instance types (T-family), not EBS volume performance. BurstBalance (E) is not relevant because it applies to burst-capable EBS volume types (gp2/st1/sc1) tracking burst bucket depletion, not the general throughput/queue metrics needed here.

Answer

CPUCreditBalance

Answer

BurstBalance

Question 15

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 r5.24xlarge instance type has a maximum EBS bandwidth of 9.5 Gbps and supports up to 80,000 IOPS, but the observed VolumeQueueLength spikes and high latencies with low CPU utilization indicate that the instance's EBS I/O capacity is saturated. The r5b.24xlarge is a Nitro-based instance that provides 60% higher EBS bandwidth (up to 19 Gbps) and 2.5x more IOPS (up to 120,000) than the r5.24xlarge, directly addressing the bottleneck. Since the database is already using io1 volumes, the volume type is not the limiting factor; the instance's EBS attachment limits are. Therefore, upgrading to r5b.24xlarge is the most effective action.

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.