Courseiva

AWS Certified SAP on AWS Specialty PAS-C01 (PAS-C01) — Questions 1126–1200

1616 questions total · 22pages · All types, answers revealed

Take a mock examExam hub
Page 15

Page 16 of 22

Page 17
1126
MCQmedium

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?

A.The volume will be detached but not deleted.
B.The volume will be automatically deleted when the instance is terminated.
C.The volume cannot be attached to another instance.
D.The volume will persist after instance termination, preserving data.
AnswerD

The volume will be retained and can be reattached.

Why this answer

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.

Exam trap

The trap here is that candidates confuse the default behavior (DeleteOnTermination=true for root volumes, false for non-root volumes) with the explicit setting shown in the CLI output, leading them to incorrectly assume the volume will be deleted or cannot be reused.

How to eliminate wrong answers

Option A is wrong because the volume is not automatically detached; it is detached by AWS as part of the termination process, but the key point is that it remains in the account as an available volume. Option B is wrong because it describes the default behavior when DeleteOnTermination is set to true, but the question states the attribute is not set to true, so the volume will not be automatically deleted. Option C is wrong because a volume with DeleteOnTermination set to false can be attached to another instance after it is detached, as long as it is in the 'available' state and within the same Availability Zone.

Full explanation →
1127
MCQmedium

A company is migrating an on-premises Oracle database to Amazon RDS for Oracle. The database is 2 TB in size and has a 24-hour migration window. The company has a 1 Gbps dedicated connection to AWS. Which migration approach minimizes downtime?

A.Use AWS Schema Conversion Tool (AWS SCT) to convert the schema and AWS DMS for full load only.
B.Use native Oracle Data Pump export and import to transfer the database over the dedicated connection.
C.Use AWS Database Migration Service (AWS DMS) with ongoing replication from the on-premises database to Amazon RDS.
D.Use AWS DataSync to copy the database files to Amazon S3, then restore to Amazon RDS.
AnswerC

Ongoing replication minimizes downtime by keeping the target in sync until cutover.

Why this answer

AWS DMS with ongoing replication allows continuous data synchronization, minimizing downtime by enabling a cutover with minimal data loss. Option A is wrong because AWS SCT is for schema conversion, not data migration. Option B is wrong because a native Oracle export/import requires downtime for the export and import operations.

Option D is wrong because AWS DataSync is for file-based data, not databases.

Full explanation →
1128
MCQmedium

A company is running an SAP HANA database on a single EC2 instance. The operations team notices that the instance is running low on memory, which is causing performance degradation. The team needs to increase memory without downtime. Which solution should they use?

A.Increase the swap space on the existing instance.
B.Launch a new EC2 instance with more memory and migrate the database.
C.Add additional EBS volumes to increase swap space.
D.Modify the EC2 instance type to a larger type with more memory.
AnswerA

Correct. Increasing swap can be done online (without stopping the instance) and provides temporary virtual memory.

Why this answer

Increasing swap space on the existing instance can be done without downtime by adding a swap file or enlarging an existing swap partition. This provides additional virtual memory, which can help alleviate memory pressure without stopping the database. While swap does not increase physical memory, it is a quick, no-downtime solution to mitigate performance degradation until a more permanent solution (e.g., migrating to a larger instance) can be scheduled.

Option D is incorrect because modifying the EC2 instance type requires stopping the instance, which causes downtime, contradicting the requirement.

Exam trap

Although adding swap space does not increase physical RAM, it can provide immediate relief without downtime, making it the only option that meets the no-downtime requirement in this scenario.

Full explanation →
1129
MCQeasy

A company is migrating its SAP environment to AWS and needs to ensure that the SAP systems can communicate with each other using their hostnames without relying on a DNS service. Which AWS feature should be used?

A.Network Load Balancer (NLB)
B.Security Group rules
C.VPC Peering
D.Amazon Route 53 private hosted zone
AnswerD

Private hosted zones enable DNS resolution within VPCs.

Why this answer

Amazon Route 53 private hosted zones allow DNS resolution for custom domain names (such as hostnames) within Amazon VPCs without requiring an external DNS service. Option A (Network Load Balancer) is incorrect because an NLB distributes incoming traffic across targets, it does not provide DNS resolution. Option B (Security Group rules) is incorrect because security groups act as virtual firewalls to control traffic, not DNS.

Option C (VPC Peering) is incorrect because VPC peering connects networks at the IP level but does not offer hostname resolution. Option D is correct because a Route 53 private hosted zone is specifically designed for DNS resolution within VPCs, enabling hostname-based communication between SAP systems.

Full explanation →
1130
MCQmedium

A company is migrating its SAP system to AWS and wants to use AWS Backup to manage backups of SAP HANA databases running on EC2 instances. What is the prerequisite for this integration?

A.The HANA database must be configured to use in-memory backups.
B.The HANA database must not use EBS snapshots for backup.
C.The EC2 instance must be running on a Dedicated Host.
D.The HANA database must be registered as a resource in AWS Backup using the Backint agent.
AnswerD

AWS Backup for SAP HANA requires the Backint agent to be installed and configured.

Why this answer

AWS Backup supports HANA databases via the SAP HANA Backint integration. The HANA database must be registered as a resource in AWS Backup, which requires the Backint agent. Options A (SAP HANA in-memory backup) is not a thing.

Option B (Dedicated Host) is not required. Option C (not using EBS snapshots) is unnecessary.

Full explanation →
1131
MCQhard

A company has an SAP HANA database on an r5.8xlarge EC2 instance. The database is experiencing high CPU utilization during peak hours. The company wants to improve performance without changing the instance family. Which action should be taken?

A.Change the instance type to x1e.32xlarge for more CPU.
B.Scale up to a larger instance size within the r5 family, such as r5.12xlarge.
C.Use a burstable performance instance like t3.2xlarge.
D.Enable CPU hyper-threading on the instance.
AnswerB

Increasing instance size provides more vCPUs and memory, staying in the same family.

Why this answer

The r5.8xlarge instance is experiencing high CPU utilization, and the requirement is to improve performance without changing the instance family. Scaling up to a larger instance size within the same r5 family, such as r5.12xlarge, provides more vCPUs and memory while maintaining compatibility with the existing SAP HANA workload and AWS architecture. This approach avoids the complexity of migrating to a different instance family and ensures that the SAP HANA database can leverage additional compute resources directly.

Exam trap

The trap here is that candidates may assume any larger instance type will work, but the question explicitly restricts staying within the same instance family, making Option A a distractor that offers more CPU but violates the constraint.

How to eliminate wrong answers

Option A is wrong because the x1e.32xlarge is a different instance family (X1e) optimized for large in-memory databases, not for general CPU scaling, and changing the instance family violates the requirement to stay within the same family. Option C is wrong because burstable performance instances like t3.2xlarge are designed for workloads with variable CPU usage and can throttle under sustained high CPU, making them unsuitable for a consistently high-CPU SAP HANA database. Option D is wrong because CPU hyper-threading is already enabled by default on all current-generation EC2 instances, including r5, so enabling it again is not possible and would not resolve high CPU utilization.

Full explanation →
1132
MCQmedium

An SAP administrator runs the AWS CLI command shown in the exhibit to check the configuration of an SAP HANA EC2 instance. The instance is running in us-east-1a. They need to deploy a second SAP HANA instance for high availability in a different Availability Zone. Which Availability Zone should be used?

A.us-west-2a
B.us-east-1b
C.Any Availability Zone
D.us-east-1a
AnswerB

Different AZ in same region provides HA.

Why this answer

For SAP HANA high availability, the secondary instance must be deployed in a different Availability Zone within the same AWS Region to achieve multi-AZ resilience. Since the primary instance is in us-east-1a, the correct choice is us-east-1b, which is a distinct Availability Zone in the same region (us-east-1). This ensures low-latency replication and compliance with SAP's requirement for synchronous replication within a single region.

Exam trap

The trap here is that candidates may confuse 'different Availability Zone' with 'different region' (option A) or assume any zone works (option C), but SAP HANA high availability specifically requires a different AZ within the same region to maintain synchronous replication and low latency.

How to eliminate wrong answers

Option A is wrong because us-west-2a is in a different AWS Region (US West Oregon), which would introduce high latency and is not supported for SAP HANA synchronous replication; SAP HANA system replication requires both instances to be in the same region. Option C is wrong because 'Any Availability Zone' is too broad and could include zones in different regions or the same zone as the primary, both of which violate SAP HANA high availability best practices. Option D is wrong because us-east-1a is the same Availability Zone as the primary instance, which would not provide fault isolation against an AZ failure and defeats the purpose of high availability.

Full explanation →
1133
MCQhard

A company is migrating an SAP ERP system to AWS. The system requires low-latency access to a shared file system for SAP transport directories. The file system must be accessible from multiple EC2 instances in different Availability Zones. Which storage solution meets these requirements?

A.Amazon EBS volumes snapshotted and shared across instances.
B.Instance store volumes on each EC2 instance.
C.Amazon S3 with Transfer Acceleration.
D.Amazon EFS file system.
AnswerD

Provides shared, low-latency file system across AZs.

Why this answer

Amazon EFS provides a fully managed, NFS-based shared file system that can be mounted concurrently by multiple EC2 instances across different Availability Zones, offering the low-latency access required for SAP transport directories. It automatically scales storage capacity and throughput, ensuring consistent performance for SAP workloads without manual provisioning.

Exam trap

The trap here is that candidates may confuse EBS snapshots or S3 with a shared file system, overlooking that EFS is the only option that provides a POSIX-compliant, multi-AZ shared file system with low-latency access required for SAP transport directories.

How to eliminate wrong answers

Option A is wrong because Amazon EBS volumes are block-level storage that can only be attached to a single EC2 instance at a time; while snapshots can be shared, they cannot provide concurrent, low-latency access from multiple instances across AZs. Option B is wrong because instance store volumes are ephemeral and tied to the specific EC2 instance's lifecycle, so they cannot be shared across instances or persist independently. Option C is wrong because Amazon S3 is object storage accessed via HTTP/S, not a POSIX-compliant file system, and Transfer Acceleration only improves upload speed over long distances, not low-latency shared file access for SAP transport directories.

Full explanation →
1134
MCQeasy

An SAP application must be highly available across two Availability Zones in a single Region. The SAP Central Services (ASCS) and ERS are to be deployed on EC2 instances. Which AWS service should be used to manage the floating IP address for the ASCS instance?

A.Network Load Balancer
B.AWS Global Accelerator
C.Amazon Route 53 with failover routing
D.Elastic IP address
AnswerC

Route 53 failover routing can automatically redirect traffic to a healthy IP.

Why this answer

In an SAP on AWS deployment, the ASCS instance requires a floating IP address for clients to connect to the active instance. Amazon Route 53 with failover routing can manage this by using health checks to automatically update DNS records to point to the secondary ASCS instance in case of failure. This provides a DNS-based failover mechanism for the floating IP.

Option A (Network Load Balancer) is incorrect because while an NLB can front-end the ASCS service, it does not manage a floating IP; it provides a static IP but requires a load balancer configuration. Option B (AWS Global Accelerator) is designed for global traffic and not for intra-region floating IP management for SAP ASCS. Option D (Elastic IP address) can be remapped manually but does not provide automatic failover without additional scripting.

Full explanation →
1135
Multi-Selecteasy

Which TWO Amazon EBS volume types are recommended for SAP HANA database workloads? (Choose two.)

Select 2 answers
A.sc1 (Cold HDD)
B.st1 (Throughput Optimized HDD)
C.io1 (Provisioned IOPS SSD)
D.io2 Block Express
E.gp3 (General Purpose SSD)
AnswersD, E

High performance for SAP HANA.

Why this answer

Options D and E are correct. io2 Block Express provides high performance for SAP HANA, and gp3 provides balanced performance. Option A is wrong because sc1 is cold storage, not suitable for databases. Option B is wrong because st1 is throughput-optimized, not suitable for databases.

Option C is wrong because io1 is an older SSD type; io2 Block Express is recommended for SAP HANA.

Full explanation →
1136
MCQhard

An SAP system is deployed on AWS using a shared account structure. The security team requires that all changes to SAP security groups be logged and alerted. Which combination of AWS services should be used?

A.AWS Config with an SNS topic
B.AWS CloudTrail with Amazon CloudWatch Events
C.Amazon Inspector with Amazon SNS
D.Amazon GuardDuty with Amazon SNS
AnswerB

CloudTrail logs API calls and CloudWatch Events can trigger alerts in real-time.

Why this answer

AWS CloudTrail logs all API calls, including changes to security groups (e.g., AuthorizeSecurityGroupIngress, RevokeSecurityGroupEgress). Amazon CloudWatch Events can be configured to filter these specific API calls and trigger alerts via SNS or other targets, enabling real-time logging and alerting. Option A (AWS Config + SNS) can detect configuration changes but is not real-time and does not capture API-level details.

Option C (Amazon Inspector) is for vulnerability assessment, not change logging. Option D (Amazon GuardDuty) is for threat detection, not security group change monitoring.

Full explanation →
1137
MCQmedium

A company is running an SAP HANA database on an Amazon EC2 instance. The instance type is r5.4xlarge with 16 vCPUs and 128 GiB of memory. The storage is configured with a single 400 GB gp2 EBS volume for /hana/data and a separate 100 GB gp2 volume for /hana/log. The database experiences high latency during peak loads. Which change will most likely improve performance?

A.Change the EBS volumes to io2 Block Express volumes with provisioned IOPS.
B.Increase the instance size to r5.8xlarge.
C.Disable the EBS volume caching.
D.Create a RAID 0 stripe of multiple gp2 volumes.
AnswerA

io2 Block Express provides consistent low latency and high IOPS, critical for SAP HANA.

Why this answer

SAP HANA on EC2 requires consistently low latency for /hana/data and /hana/log volumes, especially under peak loads. The gp2 volume's burst model can deplete credits, causing throughput throttling and high latency. io2 Block Express volumes provide consistent, provisioned IOPS performance without reliance on burst credits, directly addressing the latency issue.

Exam trap

The trap here is that candidates often assume increasing instance size (Option B) will resolve all performance issues, overlooking that SAP HANA's high-latency problem under peak load is typically storage-bound, not compute-bound, and that gp2's burst model is the root cause.

How to eliminate wrong answers

Option B is wrong because increasing the instance size to r5.8xlarge adds more CPU and memory but does not fix the underlying storage I/O bottleneck; the gp2 volumes will still suffer from credit exhaustion and latency spikes. Option C is wrong because disabling EBS volume caching would actually increase latency by forcing all I/O to go directly to the disk, worsening performance. Option D is wrong because RAID 0 striping of multiple gp2 volumes can improve throughput but does not eliminate the burst credit model; each gp2 volume still depletes credits independently, and under sustained peak load, all volumes can throttle simultaneously, failing to resolve the high-latency issue.

Full explanation →
1138
MCQeasy

A company is planning to migrate its SAP HANA database to AWS. They need to ensure high availability with automatic failover. Which AWS service should they use to achieve this?

A.AWS Launch Wizard for SAP
B.AWS OpsWorks
C.AWS CloudFormation
D.Amazon Elastic File System (EFS)
AnswerA

AWS Launch Wizard for SAP automates the deployment of SAP HANA with high availability and failover.

Why this answer

AWS Launch Wizard for SAP is the correct service because it automates the deployment of SAP HANA on AWS with built-in high availability and automatic failover configurations. It orchestrates the setup of a multi-AZ cluster, including the installation of SAP HANA system replication, the configuration of a Pacemaker cluster, and the integration with AWS resources such as Elastic IPs and Amazon Route 53 health checks to ensure seamless failover.

Exam trap

The trap here is that candidates often confuse AWS CloudFormation or OpsWorks as capable of handling SAP-specific high-availability configurations, but they lack the SAP-aware automation and integration with HANA system replication and Pacemaker that Launch Wizard provides.

How to eliminate wrong answers

Option B is wrong because AWS OpsWorks is a configuration management service based on Chef and Puppet, designed for managing application stacks and infrastructure as code, not for deploying SAP HANA with automatic failover. Option C is wrong because AWS CloudFormation is an infrastructure-as-code service that can provision resources but does not natively handle the complex SAP-specific high-availability setup, such as configuring HANA system replication or Pacemaker clustering. Option D is wrong because Amazon Elastic File System (EFS) is a scalable file storage service for Linux-based workloads and does not provide database-level high availability or automatic failover for SAP HANA.

Full explanation →
1139
MCQhard

An SAP system on AWS is experiencing slow performance. The operations team suspects a memory bottleneck on the SAP HANA database. Which CloudWatch metric should be monitored to confirm memory pressure?

A.CPUUtilization
B.SwapUsage (custom metric from HANA)
C.DiskReadOps
D.NetworkIn
AnswerB

High swap usage indicates insufficient physical memory.

Why this answer

(SwapUsage). SAP HANA uses swap space extensively when memory is under pressure; high swap usage directly indicates memory bottlenecks. Option A (CPUUtilization) measures processor load, not memory.

Option C (DiskReadOps) measures storage I/O operations, which may be a symptom but not a direct memory metric. Option D (NetworkIn) measures network throughput, unrelated to memory.

Full explanation →
1140
MCQhard

An SAP system on AWS is experiencing performance issues during peak hours. The operations team notices that the EBS volumes are consistently showing high queue depth. What should they do to improve performance?

A.Change the EC2 instance type to a larger one.
B.Provision more IOPS on the EBS volumes.
C.Change the EBS volume type to Throughput Optimized HDD (st1).
D.Increase the size of the EBS volumes.
AnswerB

Provisioned IOPS can directly reduce queue depth.

Why this answer

High EBS queue depth indicates that the volumes are not keeping up with IO demand, and provisioning more IOPS directly addresses this. Option A is incorrect: changing the EC2 instance type may improve available EBS bandwidth (throughput), but it does not provision additional IOPS; queue depth is primarily an IOPS issue. Option C is incorrect: switching to Throughput Optimized HDD (st1) is optimized for sequential throughput, not for high IOPS or low latency, so it would likely worsen queue depth for typical SAP workloads.

Option D is incorrect: increasing EBS volume size can increase baseline IOPS for gp2/gp3 volumes, but that increase is indirect and often insufficient; the direct remedy for high queue depth is to provision more IOPS.

Full explanation →
1141
MCQhard

A company is migrating its SAP landscape to AWS. The SAP systems consist of multiple instances (development, quality, production) running on different EC2 instances. The company wants to automate the provisioning of these instances using infrastructure as code. Which AWS service should be used to define and provision the SAP infrastructure in a repeatable manner?

A.AWS Elastic Beanstalk
B.AWS CloudFormation
C.AWS Service Catalog
D.AWS OpsWorks
AnswerB

CloudFormation enables you to model and provision AWS resources using templates.

Why this answer

AWS CloudFormation is the correct service because it allows you to define your entire SAP infrastructure—including EC2 instances, VPCs, security groups, and storage—as code using a JSON or YAML template. This enables repeatable, version-controlled provisioning of development, quality, and production environments, which is essential for an SAP migration requiring consistent and automated deployments.

Exam trap

The trap here is that candidates often confuse AWS OpsWorks or Elastic Beanstalk as infrastructure-as-code solutions, but they are designed for application management and configuration, not for declarative provisioning of raw infrastructure resources like EC2 instances for SAP.

How to eliminate wrong answers

Option A is wrong because AWS Elastic Beanstalk is a Platform-as-a-Service (PaaS) solution designed for web applications and does not provide the granular control over EC2 instances, operating systems, and SAP-specific configurations required for an SAP landscape. Option C is wrong because AWS Service Catalog is a governance tool that allows you to create and manage a catalog of approved IT services, but it does not directly define and provision infrastructure; it relies on CloudFormation templates underneath for provisioning. Option D is wrong because AWS OpsWorks is a configuration management service based on Chef and Puppet, which is more suited for application configuration and lifecycle management, not for defining and provisioning the underlying infrastructure in a repeatable, declarative manner like CloudFormation.

Full explanation →
1142
MCQhard

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?

A.The instance type m5.large is not available in the selected AZs.
B.The DesiredCapacity is set incorrectly to 1.
C.The Auto Scaling group is unable to launch the second instance due to capacity constraints.
D.The MinSize is set to 1, so only one instance is allowed.
AnswerC

Capacity constraints in the AZs could prevent launching additional instances.

Why this answer

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.

Exam trap

The trap here is that candidates often confuse capacity constraints with instance type availability (Option A) or misinterpret MinSize as a hard limit on the number of instances (Option D), when in fact Auto Scaling groups can launch more instances than MinSize as long as they do not exceed MaxSize.

How to eliminate wrong answers

Option A is wrong because if the instance type m5.large were not available in the selected AZs, the first instance would also fail to launch, not just the second. Option B is wrong because the exhibit explicitly states the desired capacity is 2, and the question confirms the administrator set it to 2; the DesiredCapacity parameter is not set to 1. Option D is wrong because MinSize set to 1 only defines the minimum number of instances that must be running; it does not prevent the Auto Scaling group from launching more instances up to the desired capacity of 2.

Full explanation →
1143
MCQhard

A company runs its SAP HANA database on an EC2 instance with multiple EBS volumes striped using LVM. The operations team notices increased latency and wants to ensure consistent I/O performance. What is the MOST effective way to monitor the average queue length of the EBS volumes?

A.Monitor the `VolumeQueueLength` CloudWatch metric for each EBS volume.
B.Enable detailed monitoring on the EC2 instance to get per-minute metrics.
C.Create a custom CloudWatch metric using the `QueueDepth` performance counter from the OS.
D.Use the `iostat` command on the EC2 instance to monitor device queue length.
AnswerA

This metric directly reports the number of pending I/O requests, which is the queue length.

Why this answer

CloudWatch provides the `VolumeQueueLength` metric for EBS volumes, which is the best indicator of I/O queue depth.

Full explanation →
1144
MCQeasy

A company plans to migrate 50 TB of archived data from on-premises tape storage to Amazon S3 Glacier Deep Archive. The data is rarely accessed. Which migration method is most cost-effective and suitable for the data volume?

A.AWS DataSync
B.AWS CLI with multipart upload
C.AWS Snowball Edge
D.AWS Database Migration Service (DMS)
AnswerC

Snowball Edge is designed for large offline data transfers.

Why this answer

AWS Snowball Edge is a physical device that can transfer large amounts of data offline, avoiding high network costs. For 50 TB, Snowball Edge is cost-effective and efficient. Option C is correct.

Option A (AWS DataSync) is for network-based transfers, which may be slow and costly for 50 TB. Option B (AWS CLI with multipart upload) would require significant network bandwidth and time. Option D (AWS Database Migration Service) is for database migration.

Full explanation →
1145
MCQmedium

An organization runs SAP S/4HANA on AWS with a single-host HANA database on an EC2 instance. The company wants to implement high availability (HA) for the HANA database within the same AWS Region. The HA solution must ensure automatic failover with minimal data loss. The SAP application servers are already distributed across multiple Availability Zones (AZs). The database administrator proposes using SAP HANA System Replication (HSR) with synchronous replication. However, the network latency between the primary and secondary HANA instances is consistently between 2 ms and 4 ms. What should the administrator do to ensure that the HA solution meets the requirements?

A.Increase the HANA replication timeout value to accommodate the latency.
B.Use asynchronous replication instead and accept the risk of data loss.
C.Continue with synchronous replication; the latency is acceptable for HA.
D.Deploy both HANA instances in the same Availability Zone to reduce network latency.
AnswerD

Same AZ reduces latency, making synchronous replication feasible.

Why this answer

SAP HANA System Replication (HSR) with synchronous mode requires network latency typically below 1 ms to avoid transaction commit delays and replication timeouts. With consistent 2–4 ms latency, synchronous replication would cause unacceptable performance degradation and potential replication failures. Deploying both HANA instances in the same Availability Zone (AZ) reduces latency to sub-millisecond levels, enabling synchronous replication to meet the automatic failover and minimal data loss requirements.

Exam trap

The trap here is that candidates assume synchronous replication is always the best choice for HA, ignoring the strict latency threshold required for HANA synchronous replication to function without performance impact.

How to eliminate wrong answers

Option A is wrong because increasing the HANA replication timeout does not solve the underlying latency issue; it only delays the timeout, allowing transactions to stall longer, which degrades performance and can still lead to replication failures. Option B is wrong because asynchronous replication accepts the risk of data loss (RPO > 0), which contradicts the requirement for minimal data loss. Option C is wrong because 2–4 ms latency is not acceptable for synchronous HSR; the recommended maximum latency is 1 ms to ensure transaction commits are not delayed beyond acceptable thresholds.

Full explanation →
1146
Multi-Selectmedium

A company is migrating SAP to AWS and needs to set up connectivity between on-premises and AWS VPC with high bandwidth and low latency. Which TWO AWS services should be used? (Choose TWO.)

Select 2 answers
A.AWS Transit Gateway
B.AWS Client VPN
C.AWS VPN CloudHub
D.AWS Site-to-Site VPN
E.AWS Direct Connect
AnswersA, E

AWS Transit Gateway is correct because it provides a central hub to connect multiple VPCs and on-premises networks, enabling high-bandwidth, low-latency connectivity.

Why this answer

AWS Direct Connect provides a dedicated network connection with high bandwidth and low latency, ideal for SAP migration. AWS Transit Gateway allows central management of connectivity between multiple VPCs and on-premises networks, simplifying network architecture. Options B, C, and D are incorrect: AWS Client VPN is for remote user access, not site-to-site; AWS VPN CloudHub connects multiple VPN connections but lacks dedicated bandwidth; AWS Site-to-Site VPN uses the public internet, which cannot guarantee the low latency and high bandwidth required for SAP workloads.

Full explanation →
1147
MCQeasy

A company is migrating its SAP systems to AWS and needs to ensure high availability for the SAP Central Services (ASCS) instance. Which AWS service can be used to implement a failover cluster for ASCS?

A.Amazon S3
B.Application Load Balancer (ALB)
C.AWS using shared file system and DNS-based failover
D.Amazon RDS Multi-AZ
AnswerC

Shared file system (e.g., EFS) with DNS-based routing provides ASCS failover.

Why this answer

For SAP ASCS failover, AWS recommends using a shared file system (e.g., Amazon EFS) combined with DNS-based failover via Route53. This provides high availability without requiring additional clustering software. Option C correctly describes this approach.

Option A (Amazon S3) is object storage, not suitable for ASCS. Option B (Application Load Balancer) handles inbound traffic, not ASCS clustering. Option D (Amazon RDS Multi-AZ) is for database high availability, not ASCS.

Full explanation →
1148
MCQeasy

An SAP administrator needs to review API calls made by a user who accidentally deleted an S3 bucket used for SAP backups. Which AWS service provides a record of these API calls?

A.Amazon S3 server access logs
B.Amazon CloudWatch Logs
C.AWS Config
D.AWS CloudTrail
AnswerD

CloudTrail provides a record of API calls for governance and auditing.

Why this answer

AWS CloudTrail is the correct service because it records all API calls made to the AWS environment, including S3 bucket deletion events. When a user accidentally deletes an S3 bucket, CloudTrail captures the event details such as the user identity, source IP, and timestamp, enabling the SAP administrator to audit the action. This is essential for security analysis and operational troubleshooting in the context of SAP backups.

Exam trap

The trap here is that candidates often confuse Amazon S3 server access logs (which log object-level requests) with AWS CloudTrail (which logs management-plane API calls), leading them to select Option A when the question specifically asks about API calls that deleted the bucket itself.

How to eliminate wrong answers

Option A is wrong because Amazon S3 server access logs provide detailed records of requests made to an S3 bucket (e.g., GET, PUT, DELETE objects), but they do not capture management-plane API calls like bucket deletion itself; they log object-level operations, not bucket-level administrative actions. Option B is wrong because Amazon CloudWatch Logs is used for monitoring, storing, and accessing log files from AWS resources (e.g., EC2, Lambda), but it does not natively record API calls; it can ingest logs from other services like CloudTrail, but it is not the source of API call records. Option C is wrong because AWS Config is a service for evaluating resource configurations against desired policies and tracking configuration changes over time, but it does not record API calls; it focuses on resource state and compliance, not the audit trail of who performed an action.

Full explanation →
1149
MCQhard

A company runs a critical web application on a fleet of EC2 instances behind an Application Load Balancer (ALB) in an Auto Scaling group. The application stores session state in an ElastiCache Redis cluster (Cluster Mode disabled). The operations team receives alerts that the application is experiencing intermittent timeouts and high error rates. Upon investigation, they find that the Redis cluster's CPU utilization is consistently above 90%, and there are frequent 'MAXMEMORY' evictions. The application team confirms that they recently increased the number of concurrent users and added more session data per user. The current Redis cluster is a single cache.r5.large node with 13.37 GB of memory. Which of the following should the operations team do FIRST to address the performance issues?

A.Upgrade the instance type to cache.r5.2xlarge to double the memory and compute capacity.
B.Create a read replica in a different Availability Zone and redirect read traffic to it.
C.Change the eviction policy to 'allkeys-lru' to maximize memory utilization.
D.Enable Cluster Mode and add multiple shards to distribute the data across nodes.
AnswerD

Enabling Cluster Mode and adding shards allows horizontal scaling, distributing CPU and memory load.

Why this answer

The correct first step is to enable Cluster Mode and add multiple shards because the performance issue stems from CPU saturation and memory pressure on a single Redis node. Cluster Mode distributes data across multiple shards, reducing per-node CPU load and memory usage, which directly addresses the high CPU utilization and 'MAXMEMORY' evictions caused by increased concurrent users and session data.

Exam trap

The trap here is that candidates often choose vertical scaling (Option A) or eviction policy changes (Option C) as quick fixes, failing to recognize that the scenario's high CPU and memory evictions indicate a need for horizontal scaling via sharding, which is the only option that directly reduces per-node load and memory pressure.

How to eliminate wrong answers

Option A is wrong because upgrading to cache.r5.2xlarge only doubles memory and compute capacity, which is a vertical scaling approach that does not address the root cause of CPU saturation and may still lead to bottlenecks as load increases; it also ignores the horizontal scaling benefit of sharding. Option B is wrong because creating a read replica in a different AZ and redirecting read traffic does not reduce CPU utilization on the primary node for write-heavy session data, and ElastiCache Redis (Cluster Mode disabled) does not support read replicas in the same way as RDS; replicas are for read scaling, not for solving memory eviction or CPU issues on the primary. Option C is wrong because changing the eviction policy to 'allkeys-lru' only changes which keys are evicted when memory is full, but does not reduce the underlying memory pressure or CPU utilization; it may even worsen performance by evicting important session data, leading to application errors.

Full explanation →
1150
MCQmedium

A company is running a production SAP HANA database on an r5.4xlarge EC2 instance with EBS-backed storage. The operations team notices that the database checkpoint writes are frequently slow, causing application performance degradation. The team has already increased the EBS IOPS and throughput. What should the team do next to improve checkpoint write performance?

A.Modify the Linux I/O scheduler to 'noop' and ensure the EBS-optimized instance attribute is enabled.
B.Change the EBS volume type from io1 to gp2 for higher throughput.
C.Disable SAP HANA checkpoint compression to reduce CPU overhead.
D.Increase the EBS volume size to gain additional baseline IOPS.
AnswerA

Using noop scheduler reduces latency and improves sequential I/O performance for SAP HANA checkpoints.

Why this answer

Modifying the Linux I/O scheduler to 'noop' reduces CPU overhead and prevents fragmentation of sequential writes, which is beneficial for SAP HANA checkpoint writes. Additionally, ensuring the EBS-optimized instance attribute is enabled guarantees dedicated bandwidth between the instance and EBS. Option B is incorrect because changing from io1 to gp2 would reduce performance, as gp2 has lower sustained IOPS and throughput compared to provisioned IOPS volumes.

Option C is incorrect because disabling checkpoint compression would increase the volume of data written during checkpoints, worsening the performance issue. Option D is incorrect because simply increasing volume size does not directly improve checkpoint write performance; the team has already increased IOPS and throughput, so the bottleneck is likely I/O scheduling, not volume size.

Full explanation →
1151
MCQeasy

A customer is running SAP NetWeaver on AWS and wants to use Amazon EFS for shared file storage for the SAP transport directory. Which access option should be used to secure the file system?

A.Network ACLs
B.IAM role
C.Security group
D.S3 bucket policy
AnswerC

EFS uses security groups to allow inbound NFS traffic.

Why this answer

Amazon EFS uses security groups as a stateful firewall to control NFS traffic (port 2049) at the network level. For SAP transport directories, security groups allow you to restrict access to specific EC2 instances or other AWS resources that need to mount the EFS file system, providing granular network-layer security without managing individual IP addresses.

Exam trap

The trap here is that candidates confuse network-level access controls (security groups) with identity-based controls (IAM roles) or assume that EFS, being a shared file system, can be secured with policies similar to S3 bucket policies.

How to eliminate wrong answers

Option A is wrong because Network ACLs are stateless and operate at the subnet level, not at the resource level; they cannot be directly attached to an EFS file system and would require managing inbound/outbound rules for ephemeral NFS ports, making them less precise and more complex. Option B is wrong because IAM roles are used for authentication and authorization to AWS API actions (e.g., creating or deleting EFS), not for controlling network-level access to NFS traffic on port 2049; EFS does not support IAM-based access control for mounting the file system. Option D is wrong because S3 bucket policies are specific to Amazon S3 and have no relevance to EFS; EFS is a file storage service accessed via NFSv4.1, not an object storage service, and cannot be secured with S3 bucket policies.

Full explanation →
1152
Multi-Selecteasy

Which TWO AWS services can be used to migrate on-premises SAP systems to AWS? (Choose 2.)

Select 2 answers
A.AWS Schema Conversion Tool (SCT)
B.AWS Direct Connect
C.AWS Server Migration Service (SMS)
D.AWS Database Migration Service (DMS)
E.Amazon CloudFront
AnswersC, D

SMS is used for server-level migration.

Why this answer

AWS Server Migration Service (SMS) is correct because it automates the replication of live on-premises servers, including SAP application servers, to AWS as Amazon Machine Images (AMIs). This allows you to migrate the entire SAP server stack (OS, SAP binaries, configurations) without needing to reinstall or reconfigure the SAP software, making it ideal for lift-and-shift migrations.

Exam trap

The trap here is that candidates often confuse AWS DMS as only a database migration tool and overlook that it can also migrate SAP databases (e.g., SAP HANA, SAP ASE) to AWS, while simultaneously thinking that AWS SCT (a schema conversion tool) is needed for SAP migrations, when in fact SCT is irrelevant for SAP systems that are not changing database engines.

Full explanation →
1153
MCQeasy

A company is running SAP NetWeaver on AWS and wants to implement high availability for the ASCS instance. Which AWS service can be used to monitor and automatically restart the ASCS instance if it fails?

A.EC2 Auto Scaling group
B.AWS Lambda with a scheduled function
C.Elastic Load Balancing (ELB)
D.Amazon CloudWatch with EC2 Auto Recovery
AnswerD

CloudWatch can detect instance failure and automatically recover the instance.

Why this answer

Amazon CloudWatch with EC2 Auto Recovery is the correct choice because it monitors the health of an EC2 instance at the hypervisor level and can automatically recover a failed instance by restarting it on a new host. For SAP NetWeaver ASCS instances, which require persistent state and are typically tied to a single instance, Auto Recovery ensures the instance is restored with the same private IP, Elastic IP, and instance metadata, maintaining the SAP cluster quorum without manual intervention.

Exam trap

The trap here is that candidates often confuse EC2 Auto Recovery with EC2 Auto Scaling, assuming both can restart a failed instance, but Auto Scaling replaces instances rather than recovering them in-place, which breaks the persistent IP and state required for SAP ASCS high availability.

How to eliminate wrong answers

Option A is wrong because EC2 Auto Scaling groups are designed for horizontal scaling by launching new instances based on scaling policies, not for monitoring and restarting a single critical instance like ASCS; they would replace the instance with a new one, potentially losing the persistent state and IP required for SAP high availability. Option B is wrong because AWS Lambda with a scheduled function can run custom scripts to check instance status and trigger a restart, but it operates at the application layer and cannot perform a hypervisor-level recovery that preserves the instance's private IP and metadata, which is essential for ASCS cluster communication. Option C is wrong because Elastic Load Balancing (ELB) distributes incoming traffic across multiple targets and does not monitor or restart individual instances; it is used for load balancing, not instance recovery.

Full explanation →
1154
MCQmedium

A company runs SAP ERP on AWS with a DR strategy using cross-region replication for SAP HANA. During a DR drill, the team discovers that the HANA database is not starting on the DR instance. Which configuration is most likely missing?

A.IAM roles for the DR instance to access S3.
B.EBS encryption on the DR volumes.
C.HANA system replication configuration with the correct 'PRIMARY' and 'SECONDARY' roles.
D.CloudWatch agent for logging.
AnswerC

HSR configuration is required for DR.

Why this answer

HANA system replication requires proper configuration of primary and secondary roles. Without the correct HSR configuration, the HANA database will not start on the DR instance. Option A is incorrect because IAM roles for S3 access are not necessary for HANA startup.

Option B is incorrect because EBS encryption does not affect HANA startup. Option D is incorrect because CloudWatch agent is for monitoring, not for HANA startup.

Full explanation →
1155
MCQhard

A company is running SAP S/4HANA on AWS and needs to ensure that the system can survive a single Availability Zone failure. The SAP HANA database is 1.5 TB in size. What is the most cost-effective high availability solution that meets SAP's support requirements?

A.Implement SAP HANA System Replication (HSR) with two EC2 instances in different Availability Zones.
B.Deploy SAP HANA on Amazon RDS for SAP HANA in Multi-AZ.
C.Use Amazon RDS Multi-AZ for the SAP HANA database.
D.Use a single EC2 instance with EBS snapshots taken every 5 minutes.
AnswerA

HSR is SAP's recommended HA solution and supports automatic failover across AZs.

Why this answer

SAP HANA System Replication (HSR) with two EC2 instances in different Availability Zones provides synchronous replication to meet SAP's support requirements for high availability (HA) while surviving a single AZ failure. This is the most cost-effective solution as it uses standard EC2 instances and does not require additional licensing or managed services, and it supports the 1.5 TB database size without the limitations of RDS for SAP HANA.

Exam trap

The trap here is that candidates may confuse Amazon RDS Multi-AZ with a valid option for SAP HANA, but RDS Multi-AZ is not supported for SAP HANA, and AWS does not offer a managed RDS service for SAP HANA, leading to the misconception that a managed database service can be used.

How to eliminate wrong answers

Option B is wrong because Amazon RDS for SAP HANA does not exist as a service; AWS does not offer a managed RDS service for SAP HANA, and SAP HANA must be self-managed on EC2. Option C is wrong because Amazon RDS Multi-AZ is not supported for SAP HANA databases; RDS Multi-AZ is designed for relational databases like MySQL, PostgreSQL, and Oracle, not for SAP HANA. Option D is wrong because using a single EC2 instance with EBS snapshots every 5 minutes does not meet SAP's support requirements for high availability, as it cannot provide automatic failover within the required recovery time objective (RTO) and can result in data loss (RPO) of up to 5 minutes, failing to survive an AZ failure.

Full explanation →
1156
MCQmedium

A company is migrating their SAP ERP system running on an on-premises IBM Db2 database to Amazon RDS for Db2. The migration must have minimal downtime. The current database size is 2 TB. The network link between on-premises and AWS is 1 Gbps. The migration team plans to use AWS DMS with a full load followed by ongoing replication. During a test migration, they notice that the full load takes longer than expected, causing the change data capture (CDC) lag to grow. They need to adjust the migration approach to meet the downtime window. What should they do?

A.Use multiple DMS tasks in parallel for the full load
B.Increase the compute capacity of the DMS replication instance
C.Create an RDS read replica to offload the initial load
D.Use AWS Snowball to transfer the initial load and then resume CDC
AnswerB

Increasing the compute capacity of the DMS replication instance provides more processing power to handle the full load faster, reducing the time taken and preventing CDC lag from growing.

Why this answer

Increasing the compute capacity of the DMS replication instance provides more processing power to handle the full load faster, reducing the time taken and preventing CDC lag from growing. Option A is incorrect because using multiple DMS tasks in parallel can cause conflicts and may not improve performance due to constraints on the source database. Option C is incorrect because an RDS read replica cannot offload the initial load from an on-premises source.

Option D is incorrect because using Snowball for offline transfer would interrupt ongoing replication and is not suitable for minimal downtime.

Full explanation →
1157
MCQhard

A company is migrating its SAP ERP system to AWS and needs to ensure high availability for the SAP Central Services (ASCS) and Enqueue Replication Server (ERS). They plan to use two EC2 instances in different Availability Zones with a shared file system. Which AWS service should they use to manage the failover of the virtual IP address?

A.Use an Elastic IP address and reassign it during failover using a script.
B.Configure Amazon Route 53 with failover routing and health checks for the virtual IP.
C.Deploy an Application Load Balancer to route traffic to the active instance.
D.Set up a Classic Load Balancer with cross-zone load balancing enabled.
AnswerA

Correct. Elastic IP can be reassigned between instances in different Availability Zones via automated scripts, providing a manageable virtual IP for SAP ASCS/ERS failover.

Why this answer

An Elastic IP address can be used as a virtual IP for SAP ASCS/ERS failover. By associating the Elastic IP with the active EC2 instance in one Availability Zone, and having a script (e.g., a watchdog process) automatically reassociate the Elastic IP to the standby instance upon failure, you can achieve virtual IP failover. This is a common pattern on AWS for SAP high availability when using shared file systems.

Option B is incorrect because Amazon Route 53 provides DNS failover, not virtual IP management; DNS time-to-live (TTL) delays make it unsuitable for fast failover in SAP environments. Option C is incorrect because an Application Load Balancer operates at Layer 7 and does not provide a static IP for SAP protocols. Option D is incorrect because Classic Load Balancer is deprecated and lacks the required static IP failover capability.

Exam trap

Candidates may think Route 53 is the solution for virtual IP failover, but DNS failover is not equivalent to IP address failover. The correct approach uses a floating IP address, typically via an Elastic IP or Network Load Balancer.

Full explanation →
1158
Multi-Selectmedium

A company is migrating an SAP system to AWS and wants to ensure that the migration process is compliant with SAP's requirements. Which TWO of the following are recommended practices? (Choose 2)

Select 2 answers
A.Use a database engine that is not supported by SAP to reduce licensing costs.
B.Skip the testing phase to accelerate the migration timeline.
C.Reduce the memory allocation of the SAP application to save costs.
D.Follow SAP migration notes and best practices.
E.Use EC2 instance types that are certified by SAP for the specific SAP workload.
AnswersD, E

SAP provides detailed notes for migration.

Why this answer

Using certified EC2 instance types and following SAP notes are mandatory. Reducing memory is not recommended. Using unsupported DB engines violates compliance.

Skipping testing is risky.

Full explanation →
1159
Multi-Selectmedium

A company is running SAP HANA on AWS and uses multiple EBS volumes for data and log storage. The company wants to encrypt all data at rest. Which three steps are required to ensure encryption of all EBS volumes? (Choose THREE.)

Select 3 answers
A.Use a custom AWS Key Management Service (KMS) key for encryption.
B.Enable encryption on the EBS snapshots after creation.
C.Launch EC2 instances with the EBS-optimized attribute set.
D.Enable EBS encryption by default in the AWS account for the region.
E.For existing unencrypted volumes, create an encrypted snapshot and restore from it.
AnswersA, D, E

Using a custom KMS key is not strictly required but is a valid step to control encryption keys, so it is correct.

Why this answer

Using a custom AWS KMS key allows granular control over encryption of EBS volumes. Option D is correct because enabling EBS encryption by default ensures all new volumes are encrypted automatically. Option E is correct because for existing unencrypted volumes, you must create an encrypted snapshot and restore from it to encrypt the volume.

Option B is incorrect because you cannot enable encryption on a snapshot after creation; encryption must be set when creating the snapshot copy. Option C is incorrect because the EBS-optimized attribute relates to network performance, not encryption.

Exam trap

A common trap is thinking that you can directly enable encryption on an existing unencrypted EBS volume or that you can encrypt snapshots after creation. The correct process is to create an encrypted snapshot copy and restore from it.

Full explanation →
1160
Matchingmedium

Match the SAP sizing parameter to its AWS EC2 equivalent.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Benchmark unit for CPU capacity

Instance RAM size

EBS bandwidth or instance storage performance

Placement group or instance type network performance

Why these pairings

SAP sizing parameters (SAPS, Memory, Disk I/O, Network throughput) map directly to AWS EC2 equivalents (vCPU, RAM, IOPS, bandwidth). Common confusions involve swapping compute metrics with network or memory metrics.

Full explanation →
1161
MCQmedium

A company is running SAP on AWS and needs to patch the operating system of multiple SAP application servers. The servers are in an Auto Scaling group behind an Application Load Balancer. What strategy minimizes downtime?

A.Create a new Auto Scaling group with patched instances and shift traffic using Route 53.
B.Use AWS Systems Manager Patch Manager to patch all instances at once.
C.Perform a rolling update by updating the Auto Scaling group's launch configuration with a new AMI.
D.Stop all instances, apply patches, then start them.
AnswerC

A rolling update replaces instances gradually, maintaining availability.

Why this answer

A rolling update with a launch template allows replacing instances one at a time, maintaining capacity. Option A is wrong because creating a new Auto Scaling group and shifting traffic using Route 53 is more complex and may cause downtime during the traffic shift. Option B is wrong because patching all instances at once via SSM may cause simultaneous reboots, leading to downtime.

Option D is wrong because stopping all instances, applying patches, then starting them causes downtime.

Full explanation →
1162
MCQmedium

An organization is migrating a large SAP HANA workload to AWS. The current on-premises environment uses IBM Spectrum Scale (GPFS) for shared storage. Which AWS storage solution should they use to provide a similar shared file system for SAP HANA?

A.Amazon S3
B.Amazon Elastic Block Store (EBS)
C.Amazon FSx for NetApp ONTAP
D.Amazon Elastic File System (EFS)
AnswerC

FSx for ONTAP provides a high-performance shared file system compatible with SAP HANA.

Why this answer

Amazon FSx for NetApp ONTAP provides a fully managed shared file system that supports NFS, SMB, and iSCSI protocols, and can replace GPFS for SAP HANA. EBS is block storage not shared. S3 is object storage.

EFS is NFS but lacks some enterprise features needed for HANA.

Full explanation →
1163
MCQmedium

An SAP system administrator is configuring an SAP HANA database on an EC2 instance with multiple EBS volumes. The administrator wants to ensure that the data volumes are mirrored to protect against volume failure. Which RAID configuration should the administrator use for the HANA data volumes?

A.RAID 5
B.RAID 0
C.RAID 10
D.RAID 6
AnswerC

RAID 10 combines mirroring and striping for performance and redundancy.

Why this answer

RAID 10 (striping + mirroring) is recommended for SAP HANA data volumes on AWS because it provides both high performance through striping and redundancy through mirroring, protecting against EBS volume failure. RAID 0 offers no fault tolerance. RAID 5 and RAID 6 introduce significant write penalties due to parity calculations, which can degrade HANA performance.

Full explanation →
1164
MCQmedium

A company is migrating an SAP HANA database to AWS. The database is 2 TB in size and runs on a single server. The company needs to minimize downtime during the migration. Which AWS service should be used for the initial data transfer?

A.AWS Snowball Edge
B.AWS Database Migration Service (DMS) with ongoing replication
C.AWS Direct Connect
D.Amazon S3 Transfer Acceleration
AnswerA

Snowball Edge provides a physical device for large data transfer, minimizing network usage and downtime.

Why this answer

AWS Snowball Edge is a physical device designed for large-scale data transfer, allowing the 2 TB SAP HANA database to be shipped to AWS, bypassing network limitations and minimizing downtime. Option B is incorrect because AWS DMS with ongoing replication is intended for continuous synchronization after initial load, not for the initial bulk transfer, and still relies on network speed. Option C is incorrect because AWS Direct Connect provides a dedicated network connection but does not eliminate transfer time for large datasets like 2 TB.

Option D is incorrect because Amazon S3 Transfer Acceleration speeds up uploads over the public internet, but for 2 TB, network transfer would still be slower and less predictable than a physical device.

Full explanation →
1165
MCQmedium

You are an SAP Basis consultant for a company running SAP ECC on Oracle on AWS. The system is hosted on a single EC2 instance (r5.8xlarge) with a separate EC2 instance for the database (Oracle on RDS). Recently, users have reported that the system becomes unresponsive for a few minutes every day at 10:00 AM. You check CloudWatch metrics and see a spike in CPU utilization on the application server at that time, but the database metrics are normal. The application server is running SAP instance and also a custom batch job that runs daily at 10:00 AM. The batch job is using a significant amount of CPU. You need to resolve the issue without losing the functionality of the batch job. Which action should you take?

A.Reschedule the batch job to run at a different time, such as 2:00 AM.
B.Move the custom batch job to a separate EC2 instance dedicated to running batch processes.
C.Upgrade the application server instance to a larger size, such as r5.16xlarge.
D.Create an RDS read replica and offload the batch job's database queries to it.
AnswerB

Isolating the batch job prevents it from competing for CPU with the SAP application.

Why this answer

The correct answer. Moving the custom batch job to a separate EC2 instance isolates the CPU-intensive process from the main SAP application server, preventing it from impacting user sessions. This resolves the issue without losing batch job functionality.

Option A (rescheduling) might avoid peak hours but does not address resource contention if the batch job overlaps with other activities. Option C (upgrading instance) is costly and may not be necessary. Option D (RDS read replica) only offloads database queries and does not address application server CPU spikes.

Full explanation →
1166
Multi-Selectmedium

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

Select 2 answers
A.Use a burstable instance type (e.g., t3) for non-production HANA systems.
B.Use EBS-optimized instances or instances with dedicated EBS bandwidth.
C.Use a dedicated EC2 instance for the HANA database, separate from application servers.
D.Configure a large swap space on the HANA instance to handle memory pressure.
E.Mount the HANA data volume using Amazon EFS for high throughput.
AnswersB, C

EBS optimization provides consistent performance for storage.

Why this answer

SAP HANA requires consistent, high-throughput I/O for its data and log volumes. EBS-optimized instances provide dedicated network bandwidth to Amazon EBS, eliminating contention with other traffic and ensuring the low-latency, high-IOPS performance that HANA demands. Without this dedicated bandwidth, EBS performance can degrade under load, risking database stability.

Exam trap

The trap here is that candidates often confuse general best practices (like using swap for memory pressure) with SAP HANA's specific requirements, where swap is harmful, or they assume that any storage service (like EFS) can substitute for block storage, ignoring HANA's need for low-latency, direct-attached block devices.

Full explanation →
1167
Multi-Selectmedium

A company is running SAP HANA on an EC2 instance. The storage is provided by multiple EBS volumes. Which THREE considerations are important when configuring EBS volumes for SAP HANA? (Choose THREE.)

Select 3 answers
A.Use RAID 0 striping across multiple EBS volumes to increase throughput.
B.Use gp2 volumes with burst credits to handle peak IOPS.
C.Separate data and log volumes to avoid I/O contention.
D.Enable EBS bursting for all volumes to ensure high throughput.
E.Provision EBS volumes with sufficient IOPS to meet SAP HANA performance requirements.
AnswersA, C, E

RAID 0 improves performance by combining multiple volumes.

Why this answer

Options A, C, and E are correct. Option A is correct because using RAID 0 striping across multiple EBS volumes increases aggregated throughput and IOPS, which benefits SAP HANA workloads. Option C is correct because separating data and log volumes prevents I/O contention and aligns with SAP best practices.

Option E is correct because SAP HANA requires consistent, sufficient IOPS; provisioning volumes with adequate provisioned IOPS meets performance requirements. Option B is incorrect because gp2 burst credits are not reliable for production HANA; provisioned IOPS volumes (e.g., io1/io2) or gp3 are recommended. Option D is incorrect because EBS bursting introduces variability and is not suitable for production HANA; volumes should be sized for baseline performance.

Full explanation →
1168
MCQhard

An SAP HANA database on EC2 is experiencing high swap usage. The system administrator suspects that the memory configuration is insufficient. Which CloudWatch metric should be monitored to confirm this?

A.NetworkOut
B.DiskWriteOps
C.SwapUsage
D.MemoryUtilization
AnswerC

SwapUsage is a custom metric reported by the CloudWatch agent. Monitoring this metric directly confirms high swap usage, indicating insufficient memory.

Why this answer

High swap usage indicates memory pressure, and SwapUsage is a custom metric that can be monitored via the CloudWatch agent. It is not a default EC2 metric. Option A (NetworkOut) measures network traffic, not memory.

Option B (DiskWriteOps) measures disk I/O, not memory. Option D (MemoryUtilization) is also a custom metric that measures memory usage, but swap usage directly indicates insufficient memory.

Exam trap

The trap is assuming SwapUsage is a standard EC2 metric. In reality, both SwapUsage and MemoryUtilization require the CloudWatch agent.

Full explanation →
1169
MCQhard

A company runs its SAP system on AWS and uses an Application Load Balancer (ALB) to distribute traffic to SAP Web Dispatchers. The operations team reports that some users experience intermittent connectivity issues. The ALB health checks are configured to check the /sap/public/bc/icf/logon endpoint. Which configuration change would best improve the reliability of health checks?

A.Increase the unhealthy threshold count to reduce false positives.
B.Enable HTTP/2 support on the ALB.
C.Replace the ALB with a Network Load Balancer.
D.Change the health check endpoint to a static HTML page that does not require authentication.
AnswerD

A static endpoint avoids session overhead and is more reliable.

Why this answer

Health checks should target a simple, static resource that is always available and does not require authentication. The /sap/public/bc/icf/logon endpoint requires a session and may fail due to transient authentication issues, causing false health check failures. Using a static HTML page eliminates this dependency and improves reliability.

Option A is incorrect because increasing the unhealthy threshold would actually delay detection of real failures, potentially allowing unhealthy instances to receive traffic longer. Option B is incorrect because HTTP/2 is a protocol enhancement for performance, not health check reliability. Option C is incorrect because replacing the ALB with a Network Load Balancer would not address the root cause; the issue is the health check endpoint itself.

Full explanation →
1170
MCQhard

An SAP system running on AWS experiences a significant performance degradation after a patching activity. The SAP application (PAS) and database (HANA) run on separate EC2 instances. The network throughput between the two instances has dropped. What is the MOST likely cause?

A.The EBS-optimization feature was disabled on the database instance.
B.The instances were moved out of a cluster placement group, reducing network throughput.
C.The security group rules were modified during patching, restricting traffic.
D.The route tables were updated, causing traffic to traverse a NAT gateway.
AnswerB

Cluster placement groups provide low-latency, high-throughput networking; leaving the placement group can significantly reduce network performance.

Why this answer

A cluster placement group provides low-latency, high-bandwidth network connectivity between instances by placing them in the same high-speed, non-blocking rack. Moving instances out of a cluster placement group removes this benefit, reducing network throughput between the SAP PAS and HANA instances, which directly causes performance degradation.

Exam trap

The trap here is that candidates often confuse EBS-optimization with network throughput, or assume security group changes are the primary cause of performance degradation after patching, when in fact the placement group change is a subtle but critical networking change that directly impacts inter-instance bandwidth.

How to eliminate wrong answers

Option A is wrong because EBS-optimization affects storage I/O throughput to EBS volumes, not network throughput between EC2 instances. Option C is wrong because security group rules control traffic allowed to/from instances; modifying them would either block or allow traffic, not gradually reduce throughput. Option D is wrong because route table changes that force traffic through a NAT gateway would add latency and potentially reduce throughput, but this is a less likely outcome of a patching activity compared to placement group changes, and NAT gateways are typically used for outbound internet traffic, not inter-instance communication within a VPC.

Full explanation →
1171
MCQhard

An SAP HANA database on AWS is experiencing high latency. The operations team suspects a network bottleneck. The SAP application and HANA are on different subnets within the same VPC. Which AWS feature can help reduce latency?

A.NAT Gateway
B.Elastic Network Adapter (ENA)
C.VPC Peering
D.Internet Gateway
AnswerB

ENA provides enhanced networking performance.

Why this answer

(Elastic Network Adapter) is correct. ENA provides higher bandwidth and lower latency for HANA workloads. Option A (NAT Gateway) is incorrect because NAT Gateway adds latency and is used for outbound internet access, not for internal communication within a VPC.

Option C (VPC Peering) is incorrect because VPC Peering connects different VPCs, not subnets within the same VPC, and does not reduce latency within a single VPC. Option D (Internet Gateway) is incorrect because it provides internet access and would add latency.

Full explanation →
1172
MCQmedium

An SAP HANA database is running on an EC2 instance with an attached gp2 volume of 500 GiB. The exhibit shows the volume attributes. The database performance is degrading during peak hours. What is the most likely cause?

A.The volume is sized too small; it needs to be at least 1 TB to provide sufficient IOPS.
B.The volume is not EBS-optimized.
C.The volume's burst balance has been depleted due to sustained high I/O.
D.The volume type is gp2 and should be changed to gp3 for better performance.
AnswerC

gp2 volumes have burst credits; when exhausted, IOPS drop to baseline.

Why this answer

Gp2 volumes use a burst bucket that provides credits for I/O above the baseline of 3 IOPS per GiB. For a 500 GiB volume, the baseline is 1500 IOPS. Sustained high I/O consumes burst credits, and once depleted, performance drops to baseline, causing degradation.

Option A is incorrect: IOPS are not solely size-dependent; gp2 offers 3 IOPS/GiB baseline, and 500 GiB provides 1500 baseline IOPS, which may be sufficient. Option B is incorrect: EBS optimization is an EC2 instance feature, not a volume attribute; the issue is with the volume itself. Option D is incorrect: while gp3 offers higher baseline performance, the immediate cause here is burst balance depletion, not volume type.

Full explanation →
1173
MCQmedium

A company is planning to run SAP Business Suite on AWS with an Oracle database. The database requires a shared file system for Oracle Grid Infrastructure (GI). Which AWS storage service should be used?

A.Amazon Elastic File System (EFS).
B.Amazon S3 with a file gateway.
C.Amazon FSx for NetApp ONTAP.
D.Multiple Amazon EBS volumes with a cluster-aware file system.
AnswerC

Supports NFS with features required by Oracle GI.

Why this answer

Amazon FSx for NetApp ONTAP provides a fully managed, shared file system that supports the NFS and SMB protocols required by Oracle Grid Infrastructure (GI) for clusterware and Oracle RAC. It offers high availability, consistent performance, and the ability to present a single namespace across multiple Availability Zones, which is essential for Oracle GI's shared-storage architecture.

Exam trap

The trap here is that candidates often assume Amazon EFS is sufficient for any shared file system need, but Oracle Grid Infrastructure requires specific cluster-aware features (like SCSI-3 persistent reservations and support for Oracle ASM) that only FSx for NetApp ONTAP provides among the listed options.

How to eliminate wrong answers

Option A is wrong because Amazon EFS is a general-purpose NFS file system that does not support the SMB protocol or the specific locking and cluster-aware features required by Oracle Grid Infrastructure for RAC. Option B is wrong because Amazon S3 with a file gateway provides a file interface to S3 but introduces latency and does not offer the low-latency, consistent shared storage needed for Oracle GI's cluster heartbeat and voting disks. Option D is wrong because multiple Amazon EBS volumes with a cluster-aware file system (e.g., GFS2) are not natively supported on AWS for Oracle RAC; AWS does not provide a cluster-aware file system service, and managing such a setup manually is complex and not recommended for production SAP workloads.

Full explanation →
1174
Multi-Selectmedium

Which TWO actions can be taken to improve the resilience of an SAP HANA database running on AWS? (Choose two.)

Select 2 answers
A.Deploy the application in a single Availability Zone.
B.Use EBS snapshots for automated backup.
C.Configure SAP HANA system replication across Availability Zones.
D.Increase the CPU capacity of the database server.
E.Enable cross-region replication of the database.
AnswersB, C

Enables recovery from failures.

Why this answer

EBS snapshots provide a reliable, automated backup mechanism for SAP HANA data volumes, enabling point-in-time recovery and disaster recovery without requiring additional SAP HANA-specific replication. These snapshots are stored in Amazon S3 and can be used to restore the database to a consistent state, improving resilience against data corruption or accidental deletion.

Exam trap

The trap here is that candidates may confuse performance scaling (option D) with resilience, or mistakenly think cross-region replication (option E) is a simple built-in feature for SAP HANA on AWS, when in fact it requires complex setup and is not a standard resilience improvement for the database itself.

Full explanation →
1175
MCQhard

A company runs SAP HANA on AWS and wants 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. Which solution meets these requirements?

A.Configure HANA System Replication (HSR) to a small instance in the DR region and scale up on failover.
B.Take daily EBS snapshots of the HANA data volumes and copy them to the DR region.
C.Use AWS Database Migration Service (DMS) to replicate HANA to an RDS instance in the DR region.
D.Use AWS Elastic Disaster Recovery (DRS) to replicate the HANA server to the DR region.
AnswerD

DRS provides continuous replication with low RPO.

Why this answer

AWS Elastic Disaster Recovery (DRS) provides continuous block-level replication of the entire SAP HANA server, including OS, application, and data volumes, with sub-minute RPO and RTO of minutes to hours. This meets the 15-minute RPO and 2-hour RTO requirements by enabling rapid failover to a fully provisioned instance in the DR region without manual scaling or data loss from periodic snapshots.

Exam trap

The trap here is that candidates often assume HANA System Replication (HSR) is the only valid DR method for SAP HANA on AWS, overlooking that AWS DRS provides a simpler, fully automated solution that meets strict RPO/RTO without requiring HANA-level replication or manual scaling.

How to eliminate wrong answers

Option A is wrong because HANA System Replication (HSR) to a small instance requires manual scale-up on failover, which cannot guarantee a 2-hour RTO due to provisioning delays and lacks automated DR orchestration for the full server. Option B is wrong because daily EBS snapshots provide an RPO of up to 24 hours, far exceeding the 15-minute requirement, and copying them to the DR region adds latency and potential data loss. Option C is wrong because AWS DMS is designed for database migration and continuous replication to RDS, but RDS does not support SAP HANA as a target engine, and DMS cannot replicate the full HANA server or its custom configurations.

Full explanation →
1176
MCQhard

A company is migrating a large SAP HANA workload to AWS. The source system runs on IBM Power Systems. They need to ensure that the target AWS infrastructure meets SAP certification requirements. Which EC2 instance type should they choose?

A.m5.24xlarge
B.c5.18xlarge
C.i3en.24xlarge
D.x1e.32xlarge
AnswerD

x1e instances are SAP HANA certified and memory-optimized.

Why this answer

x1e.32xlarge is certified for SAP HANA production workloads. Therefore, Option D is correct. Option A (m5.24xlarge) is a general-purpose instance and not certified for SAP HANA.

Option B (c5.18xlarge) is compute-optimized and not suitable for SAP HANA's memory requirements. Option C (i3en.24xlarge) is storage-optimized and not SAP HANA certified.

Full explanation →
1177
MCQmedium

A company runs an SAP HANA database on an EC2 instance. During a maintenance window, an administrator needs to stop the instance but ensure that the data in the attached EBS volumes is preserved and the instance can be started later without data loss. Which action should the administrator take?

A.Hibernate the instance from the AWS Management Console.
B.Terminate the instance from the AWS Management Console.
C.Stop the instance from the AWS Management Console.
D.Reboot the instance from the AWS Management Console.
AnswerC

Stopping an EBS-backed instance preserves all data on EBS volumes; the instance can be started later.

Why this answer

Stopping an EBS-backed EC2 instance preserves the data on the EBS volumes, allowing the instance to be started later without data loss. Option A (hibernate) is for instances with specific configurations and may not preserve all SAP HANA states. Option B (terminate) would delete the instance and potentially the volumes, causing data loss.

Option D (reboot) does not stop the instance and does not provide a clean state for maintenance.

Full explanation →
1178
Multi-Selecteasy

A company is migrating SAP applications to AWS and needs to ensure that the environment meets SAP certification. Which TWO AWS services are specifically designed to help validate SAP workloads on AWS?

Select 2 answers
A.AWS Config
B.AWS Launch Wizard for SAP
C.Amazon Inspector
D.AWS Well-Architected Tool
E.AWS Trusted Advisor
AnswersB, E

AWS Launch Wizard for SAP validates SAP architecture and recommends best practices.

Why this answer

AWS Launch Wizard for SAP (Option B) is specifically designed to guide you through the sizing, configuration, and deployment of SAP systems on AWS, automatically generating a CloudFormation template that adheres to SAP certification requirements. AWS Trusted Advisor (Option E) provides checks for SAP-specific best practices, such as verifying that your EC2 instances are SAP-certified and that your storage configuration meets SAP's performance requirements. Both services directly help validate that your SAP workload meets SAP's certification criteria on AWS.

Exam trap

The trap here is that candidates often confuse general governance or security services (like AWS Config or Inspector) with SAP-specific validation tools, failing to recognize that only services with explicit SAP certification logic (Launch Wizard and Trusted Advisor) can validate SAP workloads for certification.

Full explanation →
1179
MCQhard

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?

A.Increase the frequency of EBS snapshots to offload I/O.
B.Change the EBS volume type from gp2 to gp3 with higher IOPS and throughput.
C.Upgrade to a larger EC2 instance type with more CPU and memory.
D.Disable the HANA delta merge operation to reduce I/O load.
AnswerB

gp3 provides better performance and is cost-effective.

Why this answer

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.

Exam trap

The trap here is that candidates often assume upgrading the EC2 instance type (Option C) will resolve I/O bottlenecks, but the PAS-C01 exam tests the understanding that EBS volume performance is independent of instance size (as long as the instance is EBS-optimized), and the correct fix is to change the volume type or provisioned performance.

How to eliminate wrong answers

Option A is wrong because increasing EBS snapshot frequency does not offload I/O; snapshots are asynchronous and consume additional I/O bandwidth during the snapshot process, worsening the problem. Option C is wrong because upgrading to a larger instance type (e.g., r5.8xlarge) increases CPU and memory but does not change the EBS volume's IOPS or throughput limits; the bottleneck remains the gp2 volume's performance cap. Option D is wrong because disabling HANA delta merge would prevent the database from consolidating delta storage into main storage, leading to increased read I/O and degraded query performance over time, not a reduction in I/O load.

Full explanation →
1180
Multi-Selectmedium

A company is designing an SAP HANA disaster recovery solution on AWS. The primary system is in us-east-1, and the DR system must be in us-west-2. The RPO is 15 minutes, and RTO is 1 hour. Which TWO approaches meet these requirements? (Choose TWO.)

Select 2 answers
A.Use AWS Database Migration Service (DMS) with ongoing replication from the primary HANA database to a target HANA database in us-west-2.
B.Take EBS snapshots of HANA data volumes every 15 minutes and copy them to us-west-2.
C.Use Amazon S3 Cross-Region Replication to copy HANA backup files to us-west-2.
D.Configure SAP HANA System Replication (HSR) from the primary to a secondary HANA instance in us-west-2.
E.Use AWS Application Migration Service (MGN) to replicate the entire HANA server to us-west-2.
AnswersA, D

DMS can replicate changes continuously, meeting RPO.

Why this answer

AWS DMS with ongoing replication can capture and apply changes from the primary SAP HANA database to a target HANA database in us-west-2 with low latency, supporting an RPO of 15 minutes. DMS uses log-based CDC (Change Data Capture) to replicate transactions continuously, making it suitable for near-real-time replication. This approach meets the RTO of 1 hour because the target database can be promoted quickly.

Exam trap

The trap here is that candidates often confuse server-level replication (MGN) or backup-based approaches (EBS snapshots, S3 replication) with database-level replication, failing to recognize that only HSR and DMS provide the transaction-consistent, low-latency replication needed for SAP HANA's RPO and RTO requirements.

Full explanation →
1181
MCQeasy

A company runs SAP Business Warehouse (BW) on AWS. The system uses an SAP HANA database that is also used for other SAP systems. The company wants to set up monitoring to ensure that the HANA database is performing optimally. They have installed the AWS CloudWatch agent on the HANA server to collect operating system metrics. However, they also need to collect HANA-specific metrics such as memory usage and SQL execution times. Which additional step should the company take to collect these metrics?

A.Set up SAP Solution Manager to send metrics to CloudWatch via an API.
B.Install and configure the SAP HANA CloudWatch agent on the HANA server.
C.Use Amazon CloudWatch Logs to capture HANA trace files and create metric filters.
D.Enable AWS CloudTrail to log HANA database API calls.
AnswerB

The SAP HANA agent collects HANA-specific metrics and sends them to CloudWatch.

Why this answer

The AWS-provided SAP HANA CloudWatch agent is specifically designed to collect HANA-specific metrics such as memory usage, SQL execution times, and other database-level performance counters. It connects to the HANA database using the SQLDBC protocol and pushes the metrics directly to CloudWatch, complementing the OS-level metrics collected by the standard CloudWatch agent. This is the only option that directly addresses the requirement to gather HANA-specific metrics without additional custom development.

Exam trap

The trap here is that candidates may confuse the standard CloudWatch agent (which collects OS metrics) with the specialized SAP HANA CloudWatch agent, or assume that CloudWatch Logs or CloudTrail can be repurposed to capture database-level performance data, when in fact a purpose-built agent is required.

How to eliminate wrong answers

Option A is wrong because SAP Solution Manager is a system management tool that does not natively send metrics to CloudWatch via an API; it would require custom integration or a third-party connector, and it is not the standard AWS-recommended approach for this use case. Option C is wrong because capturing HANA trace files via CloudWatch Logs and creating metric filters would require parsing unstructured log data, which is inefficient, not real-time, and does not provide structured HANA-specific metrics like memory usage or SQL execution times. Option D is wrong because AWS CloudTrail logs API calls to AWS services, not internal database operations within the HANA server; it cannot capture HANA-specific metrics such as memory usage or SQL execution times.

Full explanation →
1182
MCQeasy

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

A.r5.24xlarge
B.c5.18xlarge
C.t3.2xlarge
D.x1e.32xlarge
AnswerD

X1e instances are memory-optimized and certified for SAP HANA.

Why this answer

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.

Exam trap

The trap here is that candidates may confuse general memory-optimized instances (like r5) with SAP HANA-certified instances, not realizing that only specific instance families (x1e, x1, and newer u-6tb1) are officially certified for production SAP HANA workloads.

How to eliminate wrong answers

Option A is wrong because the r5.24xlarge, while memory-optimized, is not SAP HANA-certified for production workloads and lacks the specific memory capacity (768 GB) and architecture required for SAP HANA. Option B is wrong because the c5.18xlarge is compute-optimized, designed for CPU-intensive workloads, not memory-intensive SAP HANA, and is not SAP-certified for HANA. Option C is wrong because the t3.2xlarge is a burstable general-purpose instance with limited memory (32 GB) and is unsuitable for SAP HANA's high memory and consistent performance demands.

Full explanation →
1183
MCQeasy

A company is migrating an SAP system to AWS and needs to retain the same hostname for the SAP application server after migration. Which configuration should the company use?

A.Assign an Elastic IP to the EC2 instance and update the /etc/hosts file
B.Create a private hosted zone in Amazon Route 53 with an A record
C.Create a CNAME record in a public hosted zone pointing to the EC2 instance
D.Use a public hosted zone in Route 53 with an A record
AnswerB

Provides internal DNS resolution within VPC.

Why this answer

A private hosted zone in Amazon Route 53 allows you to create an A record that maps a custom hostname to the private IP address of an EC2 instance. This ensures that the SAP application server retains the same hostname after migration, as DNS resolution within the VPC will consistently return the instance's private IP, regardless of instance changes or restarts.

Exam trap

The trap here is that candidates often confuse Elastic IPs with hostname persistence, assuming a static public IP is sufficient, but SAP systems rely on internal hostname resolution via DNS or /etc/hosts, not public IPs, and a private hosted zone provides the necessary centralized, scalable DNS solution within the VPC.

How to eliminate wrong answers

Option A is wrong because assigning an Elastic IP to the EC2 instance only provides a static public IP, but the hostname resolution still relies on DNS or /etc/hosts; updating /etc/hosts is a manual, non-scalable solution that does not provide centralized DNS management and can break if the instance IP changes. Option C is wrong because a CNAME record in a public hosted zone points to a DNS name (e.g., the EC2 instance's public DNS), not to the instance directly, and public hosted zones are accessible from the internet, which is unnecessary and introduces security risks for an internal SAP system. Option D is wrong because a public hosted zone with an A record would expose the SAP application server's hostname to the public internet, which is not required for internal migration and violates security best practices.

Full explanation →
1184
MCQhard

A company is using SAP HANA in a multi-node scale-out configuration on AWS. The operations team needs to automate the patching of the operating system on all nodes with minimal downtime. Which approach is most suitable?

A.Stop all HANA nodes, patch the OS on each node, then start them all together.
B.Create new EC2 instances from a patched AMI and terminate the old ones.
C.Use AWS Systems Manager Patch Manager to apply patches to all nodes simultaneously.
D.Use a rolling patching strategy: patch one node at a time after isolating it from the HANA cluster.
AnswerD

Rolling updates minimize downtime by maintaining cluster availability.

Why this answer

A rolling patching strategy, where one node is isolated from the HANA cluster, patched, then reintegrated before moving to the next, minimizes downtime. Option D is correct because it avoids full cluster outage. Option A is wrong because stopping all nodes causes complete downtime.

Option B is wrong because creating new instances from a patched AMI requires data reload and may not be seamless for a scale-out HANA cluster. Option C is wrong because applying patches to all nodes simultaneously can cause cluster instability or downtime due to lack of coordination.

Full explanation →
1185
MCQmedium

A company is migrating a highly critical SAP HANA database to AWS. They need to ensure data consistency and minimal downtime. Which approach should they use?

A.Create an AMI of the on-premises HANA server and launch it on AWS
B.Use AWS DMS with ongoing replication
C.Export HANA data to S3 and import into a new HANA instance
D.Use SAP HANA system replication and AWS Launch Wizard
AnswerD

System replication provides low RPO/RTO; Launch Wizard simplifies deployment.

Why this answer

Using SAP HANA system replication (HSR) with AWS Launch Wizard ensures minimal downtime by providing real-time data replication to an AWS-hosted HANA instance, with Launch Wizard automating the setup and configuration. Option A (AMI) is incorrect because an AMI snapshots the entire server state but does not guarantee HANA data consistency and requires downtime. Option B (AWS DMS with ongoing replication) is not the best fit because DMS may not fully support HANA-specific replication features and can introduce complexity.

Option C (export to S3 and import) is incorrect because it incurs significant downtime for export/import and does not provide continuous replication.

Full explanation →
1186
Multi-Selecthard

An SAP HANA database is running on an EC2 instance with multiple EBS volumes for data, log, and shared storage. The administrator needs to ensure that the volumes are backed up consistently to avoid data corruption. Which THREE measures should be taken? (Select THREE.)

Select 3 answers
A.Use the application-consistent snapshot feature of AWS Backup with pre/post scripts.
B.Take snapshots of all volumes simultaneously using the EBS multi-volume snapshot feature.
C.Ensure that the snapshots are taken in the correct order: data volumes first, then log volumes.
D.Freeze the filesystem using xfs_freeze before taking snapshots.
E.Stop the EC2 instance before taking snapshots.
AnswersB, C, D

Using the EBS multi-volume snapshot feature allows snapshots of all volumes to be taken simultaneously, ensuring crash consistency.

Why this answer

Options B, C, and D are correct. Option B: Using the EBS multi-volume snapshot feature allows snapshots of all volumes to be taken simultaneously, ensuring crash consistency. Option C: Taking snapshots in the correct order (data volumes first, then log volumes) is important for SAP HANA to maintain transactional consistency.

Option D: Freezing the filesystem with xfs_freeze (or equivalent) before taking snapshots ensures filesystem consistency and prevents data corruption. Option A is incorrect because although AWS Backup provides application-consistent snapshots, the question asks for measures the administrator should take directly; the recommended practice for SAP HANA on EC2 with EBS is to use the EBS multi-volume snapshot feature in conjunction with filesystem freeze and proper ordering. Option E is incorrect because stopping the instance causes downtime and is not necessary if using the other measures.

Full explanation →
1187
MCQhard

Refer to the exhibit. An SAP HANA database backup fails with the error shown. The backup target is an EFS file system mounted at /backup. The EC2 instance has the appropriate IAM role to access EFS. What is the MOST likely cause of this error?

A.The IAM role attached to the EC2 instance does not have permissions to write to EFS.
B.The SAP HANA database user does not have write permissions on the backup directory.
C.The EFS file system has insufficient IOPS for the backup operation.
D.The EFS file system is out of storage capacity.
AnswerB

The error clearly states 'Permission denied', indicating a file permission issue.

Why this answer

The error 'Permission denied' indicates that the SAP HANA user (e.g., <sid>adm) does not have write permissions to the backup directory on the EFS file system. Option A is wrong because the error is not about disk space. Option C is wrong because EFS does not have IOPS limits like EBS.

Option D is wrong because the IAM role is for accessing EFS, but file permissions are separate.

Full explanation →
1188
MCQmedium

A company runs an SAP HANA database on an EC2 instance with EBS volumes. The operations team needs to ensure that snapshots of the database volumes are consistent. Which step should be taken before initiating the EBS snapshot?

A.Use hdbsql to execute BACKUP DATA FULL USING FILE ('/backup/snapshot_prep')
B.Run the Linux 'sync' command on the instance
C.Stop the HANA database service
D.Create the EBS snapshot directly without any preparation
AnswerA

This command prepares HANA for a snapshot-consistent backup.

Why this answer

Running hdbsql with BACKUP DATA and USING FILE creates a snapshot-consistent backup. Option B is wrong because 'sync' only flushes OS buffers but does not guarantee HANA consistency. Option C is wrong because stopping HANA is excessive.

Option D is wrong because EBS snapshots alone do not ensure application consistency.

Full explanation →
1189
MCQmedium

A company runs SAP HANA on AWS using EC2 instances with HANA data replication between two Availability Zones. The operations team needs to test a disaster recovery failover. What is the correct procedure to promote the secondary HANA system to primary?

A.Stop the primary HANA system on the primary EC2 instance
B.Use the HANA takeover command on the secondary system
C.Modify the DNS record to point to the secondary instance
D.Shut down the primary EC2 instance and wait for automatic failover
AnswerB

The takeover command promotes the secondary to primary.

Why this answer

For HANA system replication, the secondary must be taken over using HANA Studio or hdbsql. Stopping the primary or shutting down EC2 instances does not trigger a clean takeover; modifying DNS without promoting the database would cause data inconsistency.

Full explanation →
1190
MCQeasy

A company is designing storage for an SAP HANA database on AWS. The database requires high throughput and low latency for data files. Which storage solution should be used for SAP HANA data volumes?

A.Amazon EBS gp3 or io2 volumes
B.Amazon S3
C.EC2 Instance Store
D.Amazon EFS
AnswerA

EBS gp3 and io2 provide the needed performance and persistence for HANA data.

Why this answer

Amazon EBS gp3 or io2 volumes are the correct choice for SAP HANA data volumes because they provide the high throughput, low latency, and consistent IOPS required for SAP HANA's in-memory database operations. gp3 offers baseline performance with the ability to scale independently, while io2 provides provisioned IOPS for critical workloads, both meeting SAP's certification requirements for HANA on AWS.

Exam trap

The trap here is that candidates often confuse the high performance of EC2 Instance Store with persistence, forgetting that SAP HANA requires durable storage for data volumes, or they overestimate the suitability of Amazon EFS or S3 for database workloads due to their scalability features, ignoring the strict latency and IOPS requirements of SAP HANA.

How to eliminate wrong answers

Option B is wrong because Amazon S3 is an object storage service with higher latency and lower throughput than block storage, making it unsuitable for the real-time, low-latency I/O demands of SAP HANA data files. Option C is wrong because EC2 Instance Store provides ephemeral, non-persistent storage that does not survive instance stops or terminations, which violates SAP HANA's requirement for durable, persistent data storage. Option D is wrong because Amazon EFS is a file-level NFS storage service with higher latency and lower IOPS compared to EBS block storage, and it is not certified for SAP HANA data volumes due to performance limitations.

Full explanation →
1191
Matchingmedium

Match the AWS storage service to its characteristic relevant to SAP.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Up to 256K IOPS per volume

Object storage for backups and archives

Offline data migration for large SAP datasets

POSIX-compliant file storage for SAP

Why these pairings

For SAP on AWS, EBS is used for HANA data/log volumes (block), S3 for backup/archiving (object), EFS for shared directories (file), and FSx for Lustre for high-performance analytics.

Full explanation →
1192
MCQmedium

A company uses AWS Organizations with multiple accounts. The security team wants to ensure that all newly created S3 buckets in any account are automatically tagged with a 'CostCenter' tag. Which solution requires the least operational overhead?

A.Create an SCP that denies s3:CreateBucket unless the request includes the CostCenter tag.
B.Use AWS Config rules to detect untagged buckets and trigger a Lambda function to add tags.
C.Configure each account's S3 bucket creation process to include tagging.
D.Use AWS CloudTrail to monitor bucket creation and send alerts to the security team.
AnswerA

Prevents creation of untagged buckets, enforcing compliance proactively.

Why this answer

A Service Control Policy (SCP) that denies s3:CreateBucket unless the request includes the CostCenter tag enforces tagging at the organization level, preventing any bucket creation without the required tag. This approach requires no ongoing maintenance, no additional services, and no per-account configuration, making it the least operational overhead solution.

Exam trap

The trap here is that candidates often choose AWS Config or Lambda solutions because they are familiar with remediation workflows, but they overlook that SCPs provide preventive enforcement with zero operational overhead, which is the key requirement in the question.

How to eliminate wrong answers

Option B is wrong because it is reactive: AWS Config rules detect untagged buckets after creation, and the Lambda function must add tags retroactively, which incurs ongoing compute costs and potential delays. Option C is wrong because it relies on manual or custom automation per account, which is error-prone and does not scale across many accounts in an organization. Option D is wrong because CloudTrail only logs bucket creation events; it does not enforce tagging or automatically remediate untagged buckets, leaving the security team to manually intervene.

Full explanation →
1193
MCQhard

A company runs SAP on AWS with an Oracle database. They want to implement a disaster recovery strategy with a Recovery Point Objective (RPO) of less than 15 minutes and a Recovery Time Objective (RTO) of less than 2 hours. Which combination of AWS services should they use?

A.Oracle Data Guard for replication and Amazon Route 53 for DNS failover.
B.AWS Database Migration Service (DMS) for ongoing replication to a DR instance, and automated snapshots for fast recovery.
C.Amazon S3 cross-region replication for database files and a script to import them.
D.AWS Backup to take weekly snapshots and restore in the DR region.
AnswerB

AWS DMS with ongoing replication can achieve RPO <15 min, and automated snapshots allow recovery within RTO <2 hours.

Why this answer

AWS DMS can perform ongoing replication from an Oracle source database to a target DR instance with minimal latency, enabling an RPO of less than 15 minutes. Automated snapshots of the DR instance allow fast recovery within the 2-hour RTO. This combination meets the stated RPO and RTO requirements without relying on Oracle-specific licensing or complex manual scripts.

Exam trap

AWS often tests the misconception that Oracle Data Guard is the only viable replication method for Oracle databases on AWS, but the question specifically requires an AWS-native solution that meets strict RPO/RTO targets without additional Oracle licensing costs.

How to eliminate wrong answers

Option A is wrong because Oracle Data Guard requires Oracle Database Enterprise Edition with the Active Data Guard option, which incurs additional licensing costs and does not leverage AWS-native services for automated failover; Amazon Route 53 alone cannot manage database-level failover. Option C is wrong because Amazon S3 cross-region replication for database files is not designed for transactional consistency and cannot guarantee an RPO of less than 15 minutes; importing files via a script would likely exceed the 2-hour RTO. Option D is wrong because AWS Backup weekly snapshots provide an RPO of up to 7 days, far exceeding the required 15-minute RPO, and restoring from snapshots in a DR region would not meet the 2-hour RTO.

Full explanation →
1194
MCQeasy

A company has a production AWS account that contains an Amazon RDS for MySQL DB instance. The database is critical and must have automated backups enabled with a retention period of 30 days. The company also requires point-in-time recovery to any second within the retention period. The operations team has configured automated backups with a retention period of 30 days, but they notice that the automated backups are not being taken consistently. The DB instance is in a Multi-AZ deployment and has a storage size of 500 GB. The team checks the backup window and finds that it is set to 02:00-03:00 UTC. The backup window is non-overlapping with the maintenance window. The DB instance is actively used during the backup window with heavy write traffic. Which of the following is the MOST likely reason for the inconsistent automated backups?

A.The storage size of 500 GB exceeds the maximum backup size limit.
B.The heavy write traffic during the backup window causes I/O suspension and backup failures.
C.The Multi-AZ deployment does not support automated backups.
D.The backup window overlaps with the maintenance window.
AnswerB

High write activity can interfere with the backup process, leading to failures.

Why this answer

The heavy write traffic during the backup window causes I/O suspension, which can lead to backup failures. When an RDS for MySQL DB instance experiences high write activity during a backup, the backup process may be delayed or fail due to I/O suspension, especially if the instance is under heavy load. This is because automated backups require a consistent snapshot, and excessive write I/O can prevent the snapshot from completing within the backup window.

Exam trap

The trap here is that candidates may overlook the impact of heavy write traffic on backup consistency, assuming that Multi-AZ or non-overlapping windows guarantee reliable backups, or mistakenly think that storage size limits or Multi-AZ incompatibility are the root cause.

How to eliminate wrong answers

Option A is wrong because RDS for MySQL does not have a maximum backup size limit; the backup storage is automatically provisioned and can scale up to the DB instance's allocated storage. Option C is wrong because Multi-AZ deployments fully support automated backups, and in fact, automated backups are taken from the standby instance to reduce performance impact. Option D is wrong because the scenario explicitly states that the backup window is non-overlapping with the maintenance window, so this is not a contributing factor.

Full explanation →
1195
MCQmedium

An SAP system on AWS is experiencing high latency between the application server and the database server. Both are in the same VPC but different subnets. What is the most effective way to reduce latency?

A.Move the database to a different Availability Zone.
B.Use a VPN connection between subnets.
C.Increase the instance size of both servers.
D.Place both instances in a placement group in the same Availability Zone.
AnswerD

Placement groups provide low-latency network.

Why this answer

Placing both the SAP application server and database server in a placement group within the same Availability Zone ensures they are in close physical proximity, often on the same rack or within the same cluster. This minimizes network hops and reduces latency to single-digit microseconds, which is critical for SAP's high-throughput, low-latency communication between application and database layers.

Exam trap

The trap here is that candidates often assume increasing instance size or changing subnets will fix latency, but AWS explicitly tests the understanding that physical proximity via placement groups is the only way to guarantee minimal network latency within a single Availability Zone.

How to eliminate wrong answers

Option A is wrong because moving the database to a different Availability Zone increases physical distance and network latency, often adding 1–2 milliseconds of inter-AZ latency, which would worsen the high-latency issue. Option B is wrong because a VPN connection between subnets introduces encryption overhead and additional network hops, increasing latency rather than reducing it; VPNs are for secure connectivity across networks, not for optimizing intra-VPC performance. Option C is wrong because increasing instance sizes improves compute or memory capacity but does not reduce network latency between instances; latency is determined by network path and physical proximity, not instance size.

Full explanation →
1196
MCQmedium

A company is running SAP on AWS and wants to ensure high availability for the SAP Central Services (ASCS) instance. They have two EC2 instances in different Availability Zones within a single AWS Region. Which AWS service should be used to automatically fail over the ASCS instance if the primary instance fails?

A.Application Load Balancer (ALB)
B.AWS Auto Scaling
C.AWS CloudFormation
D.Amazon Route 53
AnswerD

Route 53 health checks and failover routing can direct traffic to the healthy instance.

Why this answer

Amazon Route 53 can be configured with a health check that monitors the primary ASCS instance. When the health check fails, Route 53 automatically updates DNS records to point to the secondary instance in the other Availability Zone, enabling failover routing. This provides a DNS-level failover mechanism that is suitable for SAP Central Services, which requires a stable IP address or hostname for client connections.

Exam trap

The trap here is that candidates often assume a load balancer (ALB) is needed for high availability, but SAP ASCS requires a single active endpoint and cannot use load balancing, making Route 53's DNS failover the correct choice.

How to eliminate wrong answers

Option A is wrong because an Application Load Balancer (ALB) operates at Layer 7 and distributes traffic across multiple targets, but SAP ASCS typically requires a single active IP address and does not support load-balanced connections; ALB cannot perform automatic failover with a single active instance. Option B is wrong because AWS Auto Scaling is designed to automatically adjust the number of EC2 instances based on demand, not to fail over a specific instance role like ASCS; it does not provide health-check-driven DNS failover. Option C is wrong because AWS CloudFormation is an infrastructure-as-code service for provisioning and managing resources, not a runtime failover mechanism; it cannot react to instance failures and redirect traffic automatically.

Full explanation →
1197
MCQhard

An SAP administrator needs to perform an OS-level patching of the underlying EC2 instances hosting an SAP HANA database in a production environment. The HANA database is configured with system replication across two Availability Zones. What is the best practice to minimize downtime?

A.Stop the EC2 instance, apply patches, and start.
B.Take a snapshot of the volume, patch the OS, and restore if needed.
C.Fail over to the secondary HANA instance, apply patches to the primary, then fail back.
D.Stop the HANA database, apply patches, and restart.
AnswerC

Minimizes downtime.

Why this answer

Failing over to the secondary and patching the primary reduces downtime. Option A is wrong because stopping HANA causes downtime. Option B is wrong because stopping EC2 instance causes downtime.

Option D is wrong because stopping HANA causes downtime.

Full explanation →
1198
MCQmedium

A company is migrating an on-premises SAP HANA database to AWS. The current HANA system uses 2 TB of storage and requires high IOPS. The company wants to use Amazon EBS for storage. Which EBS volume type is most suitable for the HANA data volume?

A.sc1
B.st1
C.gp3
D.io2 Block Express
AnswerD

io2 Block Express offers up to 256,000 IOPS and low latency, meeting HANA requirements.

Why this answer

SAP HANA requires high IOPS and low latency, and io2 Block Express provides the highest performance for such requirements. Option A is wrong because sc1 is a cold HDD, which provides low IOPS and is not suitable for SAP HANA. Option B is wrong because st1 is throughput-optimized HDD, designed for large sequential workloads, not for high IOPS.

Option C is wrong because gp3 is a general-purpose SSD; while it can provide up to 16,000 IOPS, io2 Block Express offers higher and more consistent IOPS and lower latency, making it the preferred choice for SAP HANA data volumes.

Full explanation →
1199
MCQeasy

An SAP customer wants to reduce the cost of running a non-production SAP system on AWS. The system is used only during business hours (8 AM to 6 PM) on weekdays. What is the most cost-effective solution?

A.Purchase Reserved Instances for 1-year term.
B.Purchase Compute Savings Plans for 3-year term.
C.Run the instances as On-Demand without any schedule.
D.Use AWS Instance Scheduler to stop instances outside business hours.
AnswerD

Instance Scheduler automates shutdown, saving costs.

Why this answer

Using AWS Instance Scheduler allows you to automatically stop instances outside business hours, reducing costs significantly for systems used only during specific times. Option A is incorrect because Reserved Instances are best for steady-state usage and would still incur costs for hours when the system is not needed. Option B is incorrect because Compute Savings Plans also require consistent usage to be cost-effective and do not eliminate charges for idle hours.

Option C is incorrect because running On-Demand instances without scheduling does not reduce costs, as you pay for every hour regardless of usage.

Full explanation →
1200
MCQhard

Refer to the exhibit. An SAP administrator receives reports that an application server is slow. The administrator checks the CloudWatch alarm for high CPU but it shows 'OK' state. The get-metric-statistics output shows CPU utilization around 90-95%. What is the most likely reason the alarm is not triggering?

A.The alarm is configured to evaluate based on a longer period than the data shown
B.The alarm is disabled or the action is not configured
C.The alarm threshold is set to 95% and the average is exactly 95%
D.The alarm threshold is set to 90% and the evaluation period is 1 hour
AnswerA

The alarm may require sustained high CPU over 15+ minutes; the data only shows 10 minutes.

Why this answer

The alarm is in OK state despite high CPU, likely because the alarm threshold is set higher than 95% or the evaluation period is longer than the data points shown. The data shows high CPU for only 10 minutes; if the alarm requires sustained high CPU over a longer period, it may not have breached yet.

Full explanation →
Page 15

Page 16 of 22

Page 17

All pages

12345678910111213141516171819202122

Practice PAS-C01 by domain

Target a specific domain to shore up weak areas.

Design of SAP Workloads on AWSTechnologyMigrationOperations and Maintenance
See all domains with question counts →