Courseiva

AWS Certified SAP on AWS Specialty PAS-C01 (PAS-C01) — Questions 1576–1616

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

Take a mock examExam hub
Page 21

Page 22 of 22

1576
MCQhard

An SAP Basis administrator is migrating an SAP ERP system from an on-premises environment to AWS. The system uses an SAP HANA database. The migration must have minimal downtime. The administrator plans to use SAP HANA System Replication (HSR) to synchronize data to an AWS HANA instance. However, the network latency between on-premises and AWS is consistently around 50 ms. What should the administrator do to ensure that HSR can maintain synchronization without impacting source system performance?

A.Use synchronous replication with a lower sync timeout setting to avoid blocking.
B.Configure HSR in asynchronous mode with full sync disabled to avoid affecting source transaction performance.
C.Keep synchronous replication but increase the replication timeout value in the HANA global.ini file.
D.Enable HANA delta merge operations during replication to reduce the amount of data transferred.
AnswerB

Asynchronous replication does not wait for acknowledgment, so source performance is unaffected; suitable for high-latency links.

Why this answer

With 50 ms network latency, synchronous replication would block source transactions while waiting for acknowledgment from the target, severely impacting performance. Asynchronous mode with full sync disabled allows HSR to send log buffers without waiting for the target to confirm, ensuring source system performance is unaffected while still maintaining eventual consistency for migration.

Exam trap

The trap here is that candidates confuse synchronous replication with 'safer' replication, not realizing that high latency makes synchronous mode impractical for performance-sensitive source systems, and that 'full sync' is a separate HSR parameter controlling whether the secondary must be fully in sync before the primary commits.

How to eliminate wrong answers

Option A is wrong because synchronous replication with a lower sync timeout would cause frequent timeouts and transaction failures, not avoid blocking. Option C is wrong because increasing the replication timeout in synchronous mode still blocks source transactions during the wait period, only delaying the timeout event. Option D is wrong because delta merge operations are a HANA internal memory optimization unrelated to replication data transfer; they do not reduce the amount of data sent via HSR.

Full explanation →
1577
MCQhard

A company runs SAP Business Suite on AWS. They plan to use the SAP Landscape Management (LaMa) connector to automate system copy and relocation. What is a prerequisite for using the AWS LaMa connector?

A.An EC2 Auto Scaling group configured for the SAP application tier
B.AWS Systems Manager managed instances for all SAP servers
C.An IAM role with permissions for EC2, EBS, and CloudFormation actions
D.SSH keys for all SAP instances to allow LaMa to connect
AnswerC

LaMa needs IAM permissions to provision EC2, attach EBS, and use CloudFormation for automation.

Why this answer

The AWS LaMa connector automates SAP system copy and relocation by orchestrating EC2, EBS, and CloudFormation actions. An IAM role with permissions for these services is required so that LaMa can programmatically manage infrastructure resources (e.g., stop/start instances, snapshot volumes, create CloudFormation stacks) without manual intervention. This role is assumed by the LaMa connector when executing workflows.

Exam trap

The trap here is that candidates often assume SSH keys or Systems Manager are needed for LaMa to connect to SAP instances, but the connector's primary mechanism is AWS API calls via an IAM role, not direct host-level access.

How to eliminate wrong answers

Option A is wrong because an EC2 Auto Scaling group is not a prerequisite for LaMa; LaMa manages individual instances directly, not via scaling groups, and Auto Scaling is unrelated to system copy/relocation automation. Option B is wrong because AWS Systems Manager managed instances are not required; LaMa communicates with SAP instances via SSH or SAP protocols, not through Systems Manager. Option D is wrong because SSH keys are not a prerequisite for the LaMa connector itself; LaMa uses the IAM role for AWS API calls, and while SSH may be used for host-level operations, the connector's core automation relies on IAM permissions, not SSH keys.

Full explanation →
1578
MCQmedium

An SAP administrator is migrating an SAP Business Suite system from on-premises to AWS. The system uses an Oracle database that is 2 TB in size. The bandwidth between the on-premises data center and AWS is limited to 100 Mbps. The migration must be completed within a weekend (48 hours). The administrator decides to use AWS DMS for ongoing replication after an initial full load. However, the initial full load takes too long. What should the administrator do to accelerate the initial full load?

A.Disable encryption on the database backup to reduce transfer overhead.
B.Increase the size of the DMS replication instance to the largest available.
C.Use Amazon S3 Transfer Acceleration to speed up the upload.
D.Use AWS Snowball Edge to physically transfer the database backup to AWS, then restore and use DMS for ongoing replication.
AnswerD

Snowball bypasses network limitations.

Why this answer

The 2 TB database over a 100 Mbps link would take approximately 47 hours just for the transfer (2 TB * 8 / 100 Mbps / 3600 seconds ≈ 47.6 hours), leaving no time for restore and validation. AWS Snowball Edge provides a physical shipping alternative that bypasses network bandwidth constraints entirely, allowing the full load to be completed within the weekend. After restoring the backup from Snowball, AWS DMS can be used for ongoing replication of changes.

Exam trap

The trap here is that candidates often assume that increasing compute resources (DMS instance size) or using network acceleration (S3 Transfer Acceleration) can overcome a hard bandwidth constraint, but they fail to calculate the raw transfer time and recognize that physical shipping is the only way to move terabytes within a tight window.

How to eliminate wrong answers

Option A is wrong because disabling encryption on the database backup does not significantly reduce the data size (encryption overhead is minimal, typically <1%), and the bottleneck is network bandwidth, not encryption processing. Option B is wrong because increasing the DMS replication instance size improves processing throughput but does not increase the network bandwidth of 100 Mbps, which is the limiting factor for the initial full load transfer. Option C is wrong because Amazon S3 Transfer Acceleration uses optimized network paths and edge locations to improve transfer speeds, but it cannot overcome the fundamental limitation of a 100 Mbps link; the theoretical maximum transfer time for 2 TB remains constrained by the pipe size.

Full explanation →
1579
MCQmedium

Your organization runs SAP S/4HANA on AWS. The system is critical and must have high availability. The architecture includes two SAP application servers behind an Application Load Balancer, and the HANA database uses replication to a standby in another Availability Zone. During a recent test of a failure scenario, you noticed that when the standby HANA instance takes over, the application servers cannot connect because the database hostname changes. What is the best solution to ensure application servers can connect to the database without manual intervention after a failover?

A.Configure the application servers with both database IP addresses and retry logic
B.Use Amazon Route 53 with a weighted record that points to the primary and standby instances, and use health checks to automatically fail over
C.Place the database behind a Network Load Balancer
D.Update the application server configuration to use the standby hostname as a fallback
AnswerB

Route 53 health checks can detect primary failure and route to the standby.

Why this answer

Amazon Route 53 can be configured with a weighted or failover routing policy that uses health checks to automatically update DNS resolution. When the primary HANA instance fails, the health check detects the failure and Route 53 directs traffic to the standby instance, ensuring application servers can connect without manual intervention or hostname changes.

Full explanation →
1580
MCQhard

A company is migrating its SAP environment to AWS and wants to use SAP HANA as a Service on AWS (HANA database on AWS). The SAP application tier will run on EC2 instances behind an Application Load Balancer. The company requires high availability for the database with automatic failover in case of an AZ failure. Which architecture should the company implement?

A.Configure HANA replication to Amazon S3 for point-in-time recovery.
B.Set up HANA System Replication between two EC2 instances in different AZs with automatic failover.
C.Use HANA System Replication with a synchronous secondary in the same AZ.
D.Deploy a single HANA database on a large EC2 instance in one AZ with regular backups to S3.
AnswerB

HANA System Replication across AZs provides high availability and automatic failover.

Why this answer

HANA System Replication configured between two EC2 instances in different Availability Zones (AZs) with automatic failover ensures high availability and resilience against an AZ failure. Option A is incorrect because replicating HANA to Amazon S3 is meant for backups and point-in-time recovery, not for real-time automatic failover. Option C is incorrect because synchronous replication within the same AZ does not protect against an AZ failure; it only provides protection against instance or host failure.

Option D is incorrect because a single HANA database instance in one AZ, even with regular backups to S3, cannot provide automatic failover if the AZ fails; it would require manual recovery.

Full explanation →
1581
Multi-Selectmedium

Which TWO of the following are required components for an SAP HANA scale-out deployment on AWS that uses shared storage for /hana/shared? (Choose two.)

Select 2 answers
A.Amazon EFS file system
B.EC2 instance store
C.Amazon S3 bucket
D.Amazon FSx for NetApp ONTAP
E.Amazon EBS volume
AnswersA, D

EFS provides NFS shared storage.

Why this answer

Amazon EFS is required for an SAP HANA scale-out deployment on AWS that uses shared storage for /hana/shared because it provides a fully managed, POSIX-compliant NFS file system that can be mounted concurrently across multiple EC2 instances. SAP HANA scale-out nodes require a shared file system for /hana/shared to exchange configuration and log data, and EFS supports the necessary NFSv4 protocol with the required throughput and latency characteristics for this workload.

Exam trap

The trap here is that candidates often assume Amazon EBS with multi-attach is a valid shared storage option for SAP HANA, but multi-attach is not supported for SAP HANA scale-out, and they may overlook that both EFS and FSx for ONTAP are the only AWS-managed NFS solutions that meet SAP's certification requirements for /hana/shared.

Full explanation →
1582
MCQeasy

Refer to the exhibit. An IAM policy is attached to an IAM role used by an EC2 instance. The EC2 instance has an Elastic IP address of 203.0.113.5 and is running in a VPC with CIDR 10.0.0.0/16. When the application on the instance tries to upload an object to the S3 bucket 'my-bucket', it receives an Access Denied error. What is the MOST likely cause?

A.The policy does not allow the s3:PutObject action.
B.The resource ARN is incorrect; it should be arn:aws:s3:::my-bucket without the asterisk.
C.The policy is missing a Deny statement for other IP addresses.
D.The condition checks the source IP address, but the EC2 instance uses a private IP address within the VPC when communicating with S3 via a VPC endpoint.
AnswerD

When using a VPC endpoint, the source IP is the private IP of the instance, which is within the allowed range, but the condition is evaluated against the public IP? Actually, the condition is on the source IP, which for traffic through a VPC endpoint is the private IP. The private IP (10.x.x.x) matches the condition. However, if the instance is communicating via the internet, the source IP would be the Elastic IP, which is not in the allowed range. But the error suggests the condition is blocking. The most likely cause is that the condition is checking the public IP, but the instance is using a VPC endpoint? Actually, the correct answer is D: the condition checks the source IP, but if using a VPC endpoint, the source IP is the private IP, which is within range, so it would work. The error occurs if the instance is communicating via the internet and the Elastic IP is not in the allowed range. Since the condition specifies 10.0.0.0/16, which is the VPC CIDR, it expects the private IP. If the instance uses a VPC endpoint, it works. If not, it fails. The exhibit does not specify a VPC endpoint, so likely the instance is using the internet, and the source IP is the Elastic IP, which is not in the allowed range. So answer D is correct because the condition is checking the source IP, but the instance's public IP is not in the allowed range. The explanation in the JSON is slightly off but the key idea is correct.

Why this answer

The IAM policy condition likely includes an `aws:SourceIp` condition that allows only the Elastic IP address (203.0.113.5). However, when the EC2 instance communicates with S3 via a VPC endpoint, traffic uses a private IP from the VPC CIDR (10.0.0.0/16) as the source IP, not the Elastic IP. This mismatch causes the condition to evaluate to False, resulting in Access Denied.

Exam trap

Candidates may think the Elastic IP is always used as the source IP, but with a VPC endpoint, the source IP becomes a private IP from the VPC, which may not match the `aws:SourceIp` condition expecting the Elastic IP.

How to eliminate wrong answers

Option A is wrong because the policy explicitly allows `s3:PutObject` under the `Action` element, so the action is permitted. Option B is wrong because the resource ARN `arn:aws:s3:::my-bucket/*` is correct for granting access to objects within the bucket; omitting the asterisk would restrict access to the bucket itself, not its objects. Option C is wrong because the policy does not need a Deny statement for other IP addresses; the existing Allow with a condition already restricts access to only the specified IP, and adding a Deny would be redundant and could cause unintended conflicts.

Full explanation →
1583
MCQeasy

A company wants to migrate its on-premises SAP system to AWS. The system consists of an SAP NetWeaver application server and an SAP HANA database. The database requires ultra-low latency storage. Which AWS storage solution is most suitable for the SAP HANA data volume?

A.Amazon EBS io2 Block Express volumes
B.EC2 Instance Store
C.Amazon S3
D.Amazon EFS file system
AnswerA

Provides consistent low latency and high IOPS for SAP HANA.

Why this answer

Amazon EBS io2 Block Express volumes are the most suitable storage solution for SAP HANA data volumes because they provide ultra-low latency, high durability, and up to 256,000 IOPS per volume with sub-millisecond latency. This meets the stringent performance requirements of SAP HANA, which demands consistent, low-latency storage for its in-memory database operations. io2 Block Express is certified by SAP for production HANA workloads on AWS.

Exam trap

The trap here is that candidates often confuse EC2 Instance Store's low latency with durability, overlooking that SAP HANA requires persistent, non-ephemeral storage for production data.

How to eliminate wrong answers

Option B is wrong because EC2 Instance Store provides ephemeral, non-persistent storage that does not survive instance stops or terminations, making it unsuitable for critical SAP HANA data that requires durability and persistence. Option C is wrong because Amazon S3 is an object storage service with higher latency and does not support block-level access or the low-latency IOPS required for SAP HANA database volumes. Option D is wrong because Amazon EFS is a file-level NFS storage system with higher latency and lower IOPS compared to EBS io2 Block Express, and it is not certified for SAP HANA data volumes.

Full explanation →
1584
Drag & Dropmedium

Drag and drop the steps to configure an SAP S/4HANA high-availability cluster using AWS Resilience Hub into the correct order.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4

Why this order

Resilience Hub helps assess and improve HA by defining stack, assessing policy, implementing changes, testing, and monitoring.

Full explanation →
1585
MCQeasy

A company is migrating a legacy on-premises Oracle database to Amazon RDS for Oracle. They need to minimize downtime. Which AWS service should they use for ongoing replication during the migration?

A.AWS Schema Conversion Tool (SCT)
B.AWS Server Migration Service (SMS)
C.AWS Database Migration Service (DMS)
D.AWS DataSync
AnswerC

AWS Database Migration Service with ongoing replication (CDC) allows near-zero downtime migration.

Why this answer

AWS Database Migration Service (DMS) with ongoing replication (change data capture) allows near-zero downtime migration. Option A (AWS Schema Conversion Tool) is wrong because it is a schema conversion tool, not a replication service. Option B (AWS Server Migration Service) is wrong because it is for server migration, not database replication.

Option D (AWS DataSync) is wrong because it is for file/object storage, not database replication.

Full explanation →
1586
MCQmedium

A company is running a critical web application on EC2 instances behind an Application Load Balancer. During a recent deployment, a new version of the application was released, and within minutes, the error rate spiked. The operations team rolled back the deployment, but the error rate remained high. The team suspects that the ALB is still routing traffic to unhealthy instances. Which step should the team take to immediately stop routing traffic to the problematic instances?

A.Modify the ALB listener rules to point to a different target group.
B.Modify the health check interval to 5 seconds and the unhealthy threshold to 2.
C.Stop the EC2 instances from the AWS Management Console.
D.Deregister the instances from the target group.
AnswerD

Deregistering immediately stops routing traffic to those instances.

Why this answer

Deregistering the problematic EC2 instances from the target group immediately stops the Application Load Balancer from routing any new traffic to them. The ALB performs health checks on registered targets, but if an instance is unhealthy, it still remains in the target group and can receive traffic if the health check logic is misconfigured or if the instance is in a 'draining' state. Deregistration forces the ALB to complete any in-flight requests and then remove the instance from the routing table, providing an immediate stop to traffic.

Exam trap

The trap here is that candidates often confuse 'health check failure' with 'immediate traffic removal,' not realizing that health checks only update the instance's status but do not stop traffic until the instance is explicitly deregistered or the health check threshold is met, which introduces a delay.

How to eliminate wrong answers

Option A is wrong because modifying the ALB listener rules to point to a different target group does not stop traffic to the problematic instances; it only changes the routing target for new requests, but the original target group and its unhealthy instances remain active and could still receive traffic if the listener rules are not fully replaced or if there are overlapping rules. Option B is wrong because modifying the health check interval to 5 seconds and the unhealthy threshold to 2 would only accelerate the detection of unhealthy instances, but it does not immediately stop traffic; the ALB would still route requests to instances until they are marked unhealthy, which could take up to 10 seconds (2 checks × 5 seconds), and during that time errors persist. Option C is wrong because stopping the EC2 instances from the AWS Management Console will terminate the instances, but this action is disruptive and does not leverage the ALB's built-in traffic control; it also does not gracefully drain connections, potentially causing dropped requests, and it is not the recommended method for removing instances from load balancing.

Full explanation →
1587
MCQhard

A systems administrator is troubleshooting an SAP HANA database that runs on an EC2 instance. The exhibit shows the block device mappings of the EC2 instance. The administrator needs to ensure that the data volumes (/dev/sdf and /dev/sdg) are not accidentally terminated when the instance is terminated. However, the administrator also wants to take a nightly snapshot of these volumes using AWS Backup. Which of the following is a potential issue with the current configuration?

A.The volume /dev/sdf has DeleteOnTermination set to false, which will cause data persistence issues.
B.The device names /dev/sdf and /dev/sdg are reserved for NVMe instance storage and should not be used for EBS.
C.The volumes are attached to a running instance, which prevents snapshot creation.
D.The volumes are not tagged, so AWS Backup may not automatically include them in backup plans.
AnswerD

AWS Backup typically uses tags to identify resources.

Why this answer

AWS Backup uses resource tags to identify which resources to include in backup plans. If the volumes /dev/sdf and /dev/sdg are not tagged with the appropriate key-value pairs that match the backup plan's tag-based selection criteria, AWS Backup will not automatically discover and include them in nightly snapshots. This can lead to missing backups for critical SAP HANA data volumes.

Exam trap

The trap here is that candidates may overlook AWS Backup's tag-based resource selection and assume that all attached volumes are automatically backed up, or they may confuse DeleteOnTermination behavior with backup inclusion logic.

How to eliminate wrong answers

Option A is wrong because setting DeleteOnTermination to false is the correct configuration to prevent accidental termination of the volumes when the EC2 instance is terminated; it does not cause data persistence issues—it ensures the volumes persist independently. Option B is wrong because /dev/sdf and /dev/sdg are not reserved for NVMe instance storage; NVMe instance store volumes use device names like /dev/nvme0n1, and EBS volumes can be attached using /dev/sd* or /dev/xvd* names. Option C is wrong because EBS volumes can be snapshotted while attached to a running instance; AWS Backup and the EBS Snapshot API support creating snapshots of in-use volumes, though a brief filesystem freeze is recommended for consistency.

Full explanation →
1588
MCQhard

An SAP system administrator notices that an SAP HANA database on AWS is experiencing high memory usage and slow query performance. The administrator wants to identify the root cause. Which Amazon CloudWatch metric should be analyzed first?

A.SwapUsage
B.NetworkIn
C.CPUUtilization
D.DiskQueueDepth
AnswerA

SwapUsage is the correct metric. High swap usage indicates memory pressure, which can cause slow query performance.

Why this answer

SwapUsage is the correct metric to analyze first because high swap usage indicates that the system is running out of physical memory, causing it to use disk-based swap space. This can directly lead to slow query performance due to increased I/O and memory pressure. The other metrics are less directly related: CPUUtilization may not reflect memory issues, NetworkIn is unrelated to memory, and DiskQueueDepth relates to disk I/O, not memory.

Full explanation →
1589
MCQmedium

A company is migrating its SAP system to AWS and wants to use a high-availability setup for the database layer. Which AWS service should the company use to achieve automatic failover for SAP HANA?

A.Amazon CloudFront
B.Elastic Load Balancing (ELB)
C.Amazon Route 53 with health checks
D.AWS Global Accelerator
AnswerC

Route 53 can route traffic to the standby HANA instance if the primary fails.

Why this answer

Amazon Route 53 can be configured with DNS failover using health checks to automatically redirect traffic to a standby SAP HANA database in the event of a primary failure. Option A is wrong because Amazon CloudFront is a content delivery network, not relevant for database failover. Option B is wrong because Elastic Load Balancing is designed for distributing traffic across multiple instances, not for database layer failover.

Option D is wrong because AWS Global Accelerator improves application performance by routing traffic over the AWS global network, but it does not provide automatic failover for SAP HANA.

Full explanation →
1590
MCQmedium

During a migration of an SAP system, the team notices that the source system uses a custom kernel parameter that is not supported on the target Amazon EC2 instance. What should the migration team do?

A.Disable the kernel parameter in the source before migration.
B.Change the EC2 instance type to one that supports the parameter.
C.Consult the SAP on AWS documentation for equivalent parameter settings.
D.Keep the same kernel parameter and proceed with the migration.
AnswerC

AWS documentation provides guidance for SAP kernel parameters.

Why this answer

When a custom kernel parameter is not supported on the target EC2 instance, the recommended approach is to consult the SAP on AWS documentation for equivalent or alternative parameter settings that achieve the same effect within AWS's supported configurations. Option A is incorrect because disabling the parameter in the source before migration could affect the SAP system's performance or functionality during migration. Option B is incorrect because changing the EC2 instance type may not necessarily support the parameter, and it might introduce other compatibility issues.

Option D is incorrect because proceeding with an unsupported kernel parameter could lead to system instability or failure on AWS.

Full explanation →
1591
MCQeasy

An organization is migrating a large on-premises data lake (500 TB) to Amazon S3. The migration must complete within 2 weeks. The network bandwidth is 1 Gbps. Which AWS service should be used?

A.AWS Direct Connect with a 10 Gbps connection
B.AWS Database Migration Service (DMS)
C.Amazon S3 Transfer Acceleration
D.AWS Snowball Edge
AnswerD

Snowball Edge provides physical devices that can transfer large volumes quickly.

Why this answer

(AWS Direct Connect with 10 Gbps) would require 10 Gbps bandwidth, but the organization only has 1 Gbps available, and provisioning a 10 Gbps connection takes weeks, so it cannot meet the 2-week timeline. Option B (DMS) is designed for database migrations, not large data lakes. Option C (S3 Transfer Acceleration) improves transfer speed over the internet but with only 1 Gbps bandwidth, it would still take over 50 days to transfer 500 TB, exceeding the 2-week deadline.

Option D (AWS Snowball Edge) is a physical device that can transfer 500 TB in about 10 days (including shipping), making it the correct choice given the bandwidth constraint and time requirement.

Full explanation →
1592
MCQhard

A company runs SAP on AWS with a distributed system: an SAP Central Services (ASCS) instance, a primary application server (PAS), and additional dialog instances (DI). All instances are in a single Availability Zone. The company wants to implement high availability for the ASCS instance using a shared filesystem for the /sapmnt directory. The ASCS instance uses a single EBS volume for /sapmnt. The operations team plans to use a Network File System (NFS) solution to share /sapmnt between instances. Which approach should the team use to achieve a highly available shared filesystem?

A.Use Amazon FSx for Windows File Server to host the /sapmnt share.
B.Use an instance store volume on the ASCS instance and share it via NFS.
C.Create a secondary EBS volume and attach it to both the ASCS and PAS instances, then use a cluster-aware filesystem like OCFS2.
D.Deploy Amazon EFS and mount it on all instances as /sapmnt.
AnswerD

EFS is a managed NFS service that is highly available and persistent.

Why this answer

Amazon EFS provides a managed NFS filesystem that is highly available and durable across multiple Availability Zones, eliminating the single point of failure. It can be mounted on multiple EC2 instances simultaneously, making it suitable for sharing /sapmnt. Option A is incorrect because Amazon FSx for Windows File Server is designed for Windows-based workloads, not Linux-based SAP systems.

Option B is incorrect because instance store volumes are ephemeral and data is lost on instance stop/termination. Option C is incorrect because a single EBS volume cannot be attached to multiple instances simultaneously (except with a cluster filesystem like OCFS2, which is complex and not recommended for this use case).

Exam trap

Candidates may think that a shared EBS volume with a cluster filesystem is the way to go, but Amazon EFS is a fully managed NFS solution that provides high availability without requiring manual clustering.

Full explanation →
1593
MCQmedium

An SAP application is experiencing high latency when writing to an Amazon EBS volume. The volume is a gp2 type attached to an m5.4xlarge instance. Which change would improve write performance?

A.Increase the size of the gp2 volume to 1 TB.
B.Change the volume type to st1.
C.Enable EBS optimization on the EC2 instance.
D.Change the volume type to io2 and provision sufficient IOPS.
AnswerD

io2 volumes provide consistent low-latency performance.

Why this answer

The gp2 volume's baseline performance of 3 IOPS per GiB (max 16,000 IOPS) is insufficient for the SAP application's write-intensive workload, causing high latency. Changing to io2 with provisioned IOPS ensures consistent, high-performance writes by decoupling IOPS from volume size, directly addressing the latency issue.

Exam trap

The trap here is that candidates assume increasing gp2 volume size (Option A) will linearly improve performance, but they overlook that gp2's IOPS scaling is capped at 16,000 IOPS and burst credits are finite, whereas io2 provides predictable, provisioned performance.

How to eliminate wrong answers

Option A is wrong because increasing the gp2 volume size to 1 TB only raises the baseline IOPS to 3,000 (3 IOPS/GiB), which may still be inadequate for high-write SAP workloads and does not guarantee low latency. Option B is wrong because st1 is a throughput-optimized HDD volume designed for large, sequential workloads, not for low-latency random writes required by SAP applications. Option C is wrong because EBS optimization is already enabled by default on all current-generation instances like m5.4xlarge, so enabling it again provides no benefit.

Full explanation →
1594
MCQeasy

Your company runs an SAP ERP system on AWS. The SAP application servers are in an Auto Scaling group across two Availability Zones. The SAP HANA database runs on a single EC2 instance with multiple EBS volumes. Recently, the database instance experienced a failure due to an underlying hardware issue, and you had to recover from an EBS snapshot. The recovery took longer than expected, and management wants to reduce the recovery time objective (RTO). What should you do to achieve a lower RTO for the HANA database?

A.Create more frequent EBS snapshots and store them in Amazon S3
B.Increase the size of the EBS volumes and use Provisioned IOPS
C.Use an Auto Scaling group for the database instance
D.Set up SAP HANA System Replication to a secondary instance in a different Availability Zone
AnswerD

System replication provides a hot standby that can be failed over quickly.

Why this answer

SAP HANA System Replication to a secondary instance in a different Availability Zone provides near-synchronous replication, enabling automatic failover in minutes. This significantly reduces RTO compared to recovering from EBS snapshots, which can take hours depending on volume size. Option D is correct because it directly addresses the need for faster recovery.

Full explanation →
1595
MCQeasy

An SAP HANA database is running on an r5.8xlarge instance. The administrator notices high swap usage and suspects memory pressure. Which AWS metric should be monitored to confirm memory utilization?

A.AWS/Lambda namespace metrics
B.CWAgent namespace metrics
C.EC2 namespace metrics
D.EBS namespace metrics
AnswerB

The CloudWatch agent publishes memory metrics under the CWAgent namespace.

Why this answer

The CWAgent namespace metrics are correct because the CloudWatch agent, when installed on the EC2 instance, can capture detailed OS-level memory utilization metrics (such as `mem_used_percent` and `mem_available_percent`) that are not available in the default EC2 or EBS namespaces. This allows the administrator to directly confirm memory pressure causing high swap usage on the SAP HANA database.

Exam trap

The trap here is that candidates assume EC2 namespace metrics include memory utilization, but AWS intentionally omits guest OS memory from EC2 metrics, requiring the CloudWatch agent to capture it.

How to eliminate wrong answers

Option A is wrong because AWS/Lambda namespace metrics are specific to AWS Lambda functions and have no relevance to monitoring memory utilization on an EC2 instance running SAP HANA. Option C is wrong because EC2 namespace metrics (e.g., `CPUUtilization`, `NetworkIn`) do not include memory utilization metrics; EC2 does not expose guest OS memory usage by default. Option D is wrong because EBS namespace metrics (e.g., `VolumeReadBytes`, `VolumeQueueLength`) measure block storage performance, not memory utilization.

Full explanation →
1596
MCQhard

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

A.Use AWS DMS to replicate the HANA database to a standby instance.
B.Configure SAP HANA Backint agent to back up directly to Amazon S3 every 15 minutes.
C.Schedule SAP HANA backups to an EBS volume and copy to S3.
D.Use AWS Backup with EBS snapshots every hour.
AnswerB

Backint to S3 supports frequent backups and fast restore.

Why this answer

The SAP HANA Backint agent can back up directly to Amazon S3, allowing frequent backups (every 15 minutes) to achieve an RPO of 15 minutes. HANA Backint backups are fast and reliable, and restoring from S3 can meet the 2-hour RTO. Option A (AWS DMS replication) is for ongoing data replication, not backup; it may not support HANA backup requirements and could exceed RTO.

Option C (backups to EBS volume then copy to S3) introduces delays and manual processes, making it difficult to achieve a 15-minute RPO. Option D (AWS Backup with EBS snapshots) typically has a minimum interval of 1 hour, insufficient for a 15-minute RPO, and restoring a 10 TB database from snapshots may exceed the 2-hour RTO.

Full explanation →
1597
Multi-Selecthard

An SAP administrator is configuring high availability for SAP HANA using HANA system replication (HSR) across multiple Availability Zones. The administrator must ensure that the replication traffic is encrypted and uses the most efficient network path. Which TWO configurations meet these requirements? (Choose TWO.)

Select 2 answers
A.Enable SAP HANA system replication with TLS/SSL encryption.
B.Store replication data in Amazon S3 and have the secondary instance pull it.
C.Use AWS Direct Connect to connect the Availability Zones.
D.Use VPC peering between the subnets in different Availability Zones.
E.Configure a VPN connection between the Availability Zones.
AnswersA, D

HSR supports TLS encryption for secure replication traffic.

Why this answer

SAP HANA system replication (HSR) supports TLS/SSL encryption natively, which encrypts the replication traffic between the primary and secondary HANA instances. This ensures data confidentiality and integrity without requiring additional network infrastructure, and it uses the most efficient network path because the replication occurs directly over the existing network between the Availability Zones.

Exam trap

The trap here is that candidates may assume AWS Direct Connect or VPN are required for encryption and efficient routing between Availability Zones, but SAP HANA's native TLS/SSL encryption and VPC peering (which uses the AWS backbone) already satisfy both requirements without additional services.

Full explanation →
1598
MCQhard

A company is migrating their SAP HANA database to AWS. The on-premises HANA system is 10 TB and runs on a physical server. They need to minimize the migration time and cannot afford more than 4 hours of downtime. The network bandwidth is limited to 500 Mbps. They decide to use AWS Snowball Edge to transfer the data. After copying the data to Snowball, they ship it to AWS. However, upon receiving the data, they find that the checksum verification fails. What should they do to resolve this issue and complete the migration within the downtime window?

A.Re-copy the data to a new Snowball and reship
B.Use AWS DMS over the existing network to transfer the data incrementally
C.Contact AWS Support to perform a remote data verification and import
D.Order an AWS Direct Connect connection to increase bandwidth
AnswerC

AWS Support can help recover data without reshipping.

Why this answer

If the checksum verification fails, AWS Support can perform a remote data verification and potentially import the data without needing to reship the Snowball, which would exceed the 4-hour downtime window. Option A is incorrect because re-copying and reshipping would take days, not fitting the downtime requirement. Option B is incorrect because even incremental transfer via DMS over a 500 Mbps link would take too long for 10 TB.

Option D is incorrect because ordering Direct Connect can take weeks to provision, which also exceeds the allowed downtime.

Full explanation →
1599
Multi-Selecthard

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

Select 3 answers
A.VolumeQueueLength
B.VolumeReadBytes
C.VolumeWriteBytes
D.CPUCreditBalance
E.BurstBalance
AnswersA, B, C

Indicates pending I/O requests.

Why this answer

Options A, B, and C are correct. VolumeQueueLength indicates the number of pending I/O requests, which can point to performance bottlenecks. VolumeReadBytes and VolumeWriteBytes measure the throughput of read and write operations, respectively.

Option D (CPUCreditBalance) is related to CPU credits for burstable instances, not EBS performance. Option E (BurstBalance) tracks EBS burst credits but is not among the primary metrics to confirm EBS volume performance issues; the three chosen metrics directly address I/O queue depth and throughput.

Exam trap

While BurstBalance is an EBS metric for volumes with burst capability (gp2, st1, sc1), it is not one of the three metrics that directly confirm a performance bottleneck. A low BurstBalance indicates that burst credits are depleted, but the primary indicators of a performance issue are I/O queue depth (VolumeQueueLength) and throughput (VolumeReadBytes/VolumeWriteBytes). Candidates may mistakenly think BurstBalance is a primary metric, but it is not among the top three for troubleshooting performance.

Full explanation →
1600
MCQmedium

A company is migrating a legacy .NET application to AWS. The application uses Windows Authentication and relies on Active Directory for user authentication. The company wants to minimize changes to the application code. Which AWS service should be used to integrate Active Directory with the migrated application?

A.AWS Directory Service for Microsoft Active Directory
B.Amazon Cognito
C.AD Connector
D.Simple AD
AnswerA

Provides full managed AD with native support for Windows Authentication.

Why this answer

AWS Directory Service for Microsoft Active Directory is the correct choice because it provides a fully managed Microsoft Active Directory in the AWS cloud, which natively supports Windows Authentication and Kerberos-based authentication without requiring any code changes. This service allows the migrated .NET application to seamlessly integrate with the existing on-premises Active Directory through a trust relationship or by extending the directory directly into AWS, preserving the application's authentication logic.

Exam trap

The trap here is that candidates often confuse AD Connector with a full Active Directory service, not realizing that AD Connector only proxies LDAP queries and does not support Windows Authentication or Kerberos, which are essential for legacy .NET applications using integrated security.

How to eliminate wrong answers

Option B (Amazon Cognito) is wrong because it is designed for consumer identity and access management (CIAM) using standards like OAuth 2.0, SAML, and OpenID Connect, and does not support Windows Authentication or Kerberos protocols natively, requiring significant code changes to the .NET application. Option C (AD Connector) is wrong because it acts as a proxy to redirect directory requests to an on-premises Active Directory without storing any directory data locally, but it does not support features like Group Policy or Kerberos authentication for the application, and it requires the application to be configured to use LDAP over SSL, which may necessitate code modifications. Option D (Simple AD) is wrong because it is a standalone, Samba-based Active Directory compatible service that does not support Windows Authentication or Kerberos in the same way as native Microsoft AD, and it lacks features like trust relationships with on-premises AD, making it unsuitable for seamless integration without code changes.

Full explanation →
1601
Multi-Selecteasy

Which TWO AWS services can be used to monitor the performance of an SAP system running on EC2?

Select 2 answers
A.AWS CloudTrail
B.AWS Shield
C.Amazon CloudWatch
D.Amazon CloudWatch Logs
E.AWS Config
AnswersC, D

CloudWatch monitors EC2 metrics and can trigger alarms.

Why this answer

Amazon CloudWatch (C) is correct because it provides detailed monitoring of EC2 instances, including CPU, memory, disk I/O, and network metrics, which are essential for tracking SAP system performance. Amazon CloudWatch Logs (D) is correct because it allows you to collect, monitor, and analyze log files from SAP applications and the underlying OS, enabling you to detect errors, performance bottlenecks, and system health issues in real time.

Exam trap

The trap here is that candidates often confuse AWS CloudTrail (audit logs) with CloudWatch Logs (application logs), or think AWS Config can monitor performance when it only tracks configuration changes, not runtime metrics.

Full explanation →
1602
MCQmedium

A company is running SAP S/4HANA on AWS. The application team reports that batch jobs are failing intermittently with database connection timeouts. The SAP system uses a single Availability Zone deployment. Which design change should the architect recommend to improve database availability?

A.Use Amazon EBS Multi-Attach to attach the same volume to multiple EC2 instances
B.Implement an Amazon RDS for SAP HANA read replica
C.Configure SAP HANA System Replication across two Availability Zones
D.Scale up the SAP HANA instance to a larger instance type
AnswerC

SAP HANA System Replication with automatic failover ensures high availability across AZs.

Why this answer

SAP HANA System Replication (HSR) across two Availability Zones provides synchronous or asynchronous data replication at the database level, ensuring that if the primary HANA instance fails, the secondary can take over with minimal downtime. This directly addresses the intermittent database connection timeouts by eliminating the single point of failure in a single-AZ deployment, as the application can failover to the replica without manual intervention.

Exam trap

AWS often tests the misconception that scaling up or adding storage redundancy (like Multi-Attach) solves database availability issues, but the key is that SAP HANA requires database-level replication (HSR) to handle AZ failures, not just infrastructure-level changes.

How to eliminate wrong answers

Option A is wrong because Amazon EBS Multi-Attach allows multiple EC2 instances to attach to the same EBS volume, but SAP HANA does not support shared storage for its data and log volumes; HANA requires exclusive access to its storage for consistency and performance, and Multi-Attach does not provide database-level replication or automatic failover. Option B is wrong because Amazon RDS for SAP HANA does not exist; RDS supports several database engines (e.g., MySQL, PostgreSQL) but not SAP HANA, and read replicas are used for read scaling, not for high availability of a primary database. Option D is wrong because scaling up the instance type increases compute and memory capacity but does not eliminate the single point of failure; if the underlying host or Availability Zone fails, the database still becomes unavailable, and timeouts will persist.

Full explanation →
1603
Multi-Selecthard

A company runs SAP HANA on EC2 with a Multi-AZ deployment. The database uses EBS volumes for /hana/data and /hana/log. The operations team needs to implement a disaster recovery strategy with a Recovery Point Objective (RPO) of 15 minutes and Recovery Time Objective (RTO) of 2 hours. Which THREE actions should be taken? (Choose THREE.)

Select 3 answers
A.Take periodic EBS snapshots of the data and log volumes
B.Use AWS CloudFormation to automate the creation of DR infrastructure
C.Migrate the database to Amazon RDS for SAP HANA
D.Configure SAP HANA system replication to a secondary instance in a different AWS Region
E.Use AWS Database Migration Service (DMS) for continuous replication
AnswersA, B, D

Snapshots provide additional recovery points.

Why this answer

Options A, B, and D are correct. A: EBS snapshots provide a backup mechanism for data and log volumes, contributing to the RPO. B: AWS CloudFormation automates the creation of DR infrastructure in another region, helping to achieve the RTO.

D: SAP HANA system replication provides near-synchronous replication to a secondary instance, meeting the RPO of 15 minutes. C is incorrect because Amazon RDS for SAP HANA is not suitable for DR of an existing EC2-based HANA system; it would require migration and does not align with the given architecture. E is incorrect because AWS DMS is designed for database migrations, not for continuous replication of SAP HANA.

Full explanation →
1604
Multi-Selecteasy

An SAP Basis administrator needs to apply security patches to the operating system of SAP EC2 instances. The administrator wants to use AWS Systems Manager Patch Manager. Which THREE steps are required to set up patching? (Choose THREE.)

Select 3 answers
A.Create a patch baseline in AWS Systems Manager.
B.Create an AWS Lambda function to invoke the patching process.
C.Install the AWS Systems Manager Agent (SSM Agent) on each EC2 instance.
D.Configure Amazon CloudWatch Logs to store patch logs.
E.Associate the instances with a maintenance window.
AnswersA, C, E

The patch baseline defines approved and rejected patches.

Why this answer

To set up patching with AWS Systems Manager Patch Manager, you need three steps: Create a patch baseline (A) to define which patches to apply. Install the SSM Agent on each EC2 instance (C) to allow Systems Manager to communicate with the instances. Associate the instances with a maintenance window (E) to schedule when patching occurs.

Options B and D are not required: Lambda is not needed because Patch Manager handles the patching process, and CloudWatch Logs are not mandatory for patching operations.

Full explanation →
1605
MCQmedium

The following IAM trust policy is attached to a role named CrossAccountBackupRole in account 123456789012: { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "AWS": "arn:aws:iam::111111111111:role/SAPAdminRole" }, "Action": "sts:AssumeRole", "Condition": {} } ] } What does this policy enable?

A.The SAPAdminRole directly receives permissions to access S3.
B.The SAPAdminRole can assume the CrossAccountBackupRole.
C.The CrossAccountBackupRole can be assumed by any IAM user.
D.The SAPAdminRole can list S3 buckets in account 123456789012.
AnswerB

Correct. The policy explicitly allows SAPAdminRole to assume CrossAccountBackupRole via sts:AssumeRole.

Why this answer

The trust policy explicitly allows the IAM role SAPAdminRole (in account 111111111111) to perform sts:AssumeRole on the CrossAccountBackupRole. This enables SAPAdminRole to assume CrossAccountBackupRole and inherit its permissions. The policy does not grant direct S3 access; that would require a separate permissions policy attached to CrossAccountBackupRole.

Exam trap

A common trap is to assume that the trust policy alone grants resource permissions (like S3 access). In reality, the trust policy only allows assumption of the role; the permissions policy attached to the role defines what actions the assumed role can perform.

How to eliminate wrong answers

Option A is wrong because the policy does not directly grant permissions to the SAPAdminRole; it only allows the SAPAdminRole to assume the CrossAccountBackupRole, which then may have S3 permissions. Option C is wrong because the policy specifically restricts the principal to the SAPAdminRole (arn:aws:iam::111111111111:role/SAPAdminRole), not any IAM user or role. Option D is wrong because the policy only allows the sts:AssumeRole action, not any S3 actions like listing buckets; S3 permissions would require separate IAM policies attached to the CrossAccountBackupRole.

Full explanation →
1606
MCQhard

An SAP ERP system on AWS is experiencing performance degradation. A review shows that the Amazon EBS volumes used for SAP transport directories are gp2 with high throughput but high latency. The SAP team needs improved I/O performance without changing the total storage capacity. Which action should be taken?

A.Change the volume type to gp3 and increase baseline IOPS.
B.Move the transport directories to instance store volumes.
C.Enable EBS throughput optimization on the EC2 instance.
D.Change the volume type to io2 Block Express with provisioned IOPS.
AnswerD

io2 provides consistent low latency and high IOPS, ideal for SAP transport directories.

Why this answer

Io2 Block Express volumes provide consistent, high-performance IOPS with sub-millisecond latency, which directly addresses the high-latency issue with gp2 volumes. This option improves I/O performance without changing storage capacity, as required by the SAP team. gp2 volumes suffer from burst bucket limitations, leading to high latency under sustained throughput, while io2 Block Express offers provisioned IOPS for predictable performance.

Exam trap

The trap here is that candidates may choose gp3 (Option A) thinking it always improves latency, but gp3 still shares resources and cannot match the consistent low latency of io2 Block Express for demanding SAP workloads.

How to eliminate wrong answers

Option A is wrong because changing to gp3 increases baseline IOPS but does not guarantee the ultra-low latency required for SAP transport directories, as gp3 still uses a shared performance model that can introduce variability. Option B is wrong because instance store volumes are ephemeral and data is lost on instance stop or termination, making them unsuitable for persistent SAP transport directories. Option C is wrong because EBS throughput optimization is not a feature; EC2 instances have EBS-optimized by default on current generations, and enabling it does not resolve latency issues caused by volume type limitations.

Full explanation →
1607
Multi-Selecteasy

A company is planning to migrate their SAP HANA database to AWS. Which TWO of the following are valid EC2 instance types for SAP HANA? (Choose 2.)

Select 2 answers
A.c5.9xlarge
B.t3.2xlarge
C.i3.8xlarge
D.x1e.32xlarge
E.r5.8xlarge
AnswersD, E

x1e is memory-optimized and certified for SAP HANA.

Why this answer

(x1e.32xlarge) is correct because it is part of the X1e instance family, which is specifically certified by SAP for production HANA workloads. These instances offer high memory (up to 3,904 GiB) and are optimized for large in-memory databases like SAP HANA, meeting the SAP memory and vCPU requirements for OLAP and OLTP scenarios.

Exam trap

The trap here is that candidates often confuse general-purpose or compute-optimized instances (like c5 or t3) with SAP HANA requirements, overlooking that SAP HANA mandates high-memory, SAP-certified instance families such as X1e, R5, or U-6tb1.

Full explanation →
1608
MCQeasy

An administrator needs to restore an SAP HANA database from a backup stored in Amazon S3. The backup was created using AWS Backup. Which AWS service should be used to perform the restore?

A.AWS Backup
B.AWS Systems Manager
C.Amazon S3
D.AWS Database Migration Service
AnswerA

AWS Backup can restore HANA backups to EC2 instances.

Why this answer

AWS Backup is the correct service because the backup was created using AWS Backup, and AWS Backup provides native restore capabilities for SAP HANA databases. It automates the restore process by directly interacting with the underlying Amazon S3 storage where the backup resides, ensuring consistency with the backup metadata and recovery point objectives (RPOs).

Exam trap

The trap here is that candidates mistakenly think Amazon S3 itself can perform the restore, overlooking that AWS Backup is the service that manages the backup lifecycle and restore orchestration for SAP HANA databases.

How to eliminate wrong answers

Option B (AWS Systems Manager) is wrong because it is an operations management service for patching, automation, and configuration, not a backup restore tool for SAP HANA databases. Option C (Amazon S3) is wrong because while S3 stores the backup data, it does not provide the orchestration or SAP HANA-specific restore logic required to recover the database; AWS Backup handles the restore workflow. Option D (AWS Database Migration Service) is wrong because it is designed for migrating databases to AWS or between database engines, not for restoring from a backup created by AWS Backup.

Full explanation →
1609
MCQhard

A company is implementing an SAP S/4HANA system on AWS. The system must be highly available across multiple Availability Zones. Which of the following strategies should the company implement for the SAP Central Services (ASCS) instance to meet high availability requirements?

A.Deploy a single EC2 instance with a large instance type to handle failover.
B.Configure SAP HANA System Replication between two Availability Zones.
C.Deploy a Pacemaker cluster with two EC2 instances across Availability Zones using a shared file system.
D.Use Amazon RDS for SAP Central Services with Multi-AZ deployment.
AnswerC

Pacemaker cluster ensures automatic failover for ASCS.

Why this answer

SAP Central Services (ASCS) requires a highly available cluster that can manage the Enqueue and Message Server processes. A Pacemaker cluster across two Availability Zones, using a shared file system (e.g., Amazon EFS or a replicated file system), provides the necessary fencing, resource monitoring, and failover for ASCS. This architecture ensures that if the primary ASCS instance fails, the secondary instance in the other AZ can take over with minimal downtime, meeting the high availability requirement.

Exam trap

The trap here is that candidates often confuse SAP HANA System Replication (Option B) as a solution for all SAP high availability needs, but it only applies to the database layer, not to the ASCS application services.

How to eliminate wrong answers

Option A is wrong because deploying a single EC2 instance, even with a large instance type, does not provide any failover capability across Availability Zones; it represents a single point of failure. Option B is wrong because SAP HANA System Replication is designed for the SAP HANA database layer, not for the ASCS instance; ASCS requires cluster management of application services, not database replication. Option D is wrong because Amazon RDS does not support SAP Central Services; RDS is a managed database service, and SAP ASCS is an application-level component that must run on EC2 instances with a cluster manager.

Full explanation →
1610
MCQhard

An SAP Basis team is troubleshooting a performance issue on an SAP HANA database running on AWS. The HANA index server is consuming high CPU. The team suspects that the underlying EC2 instance is throttled. Which CloudWatch metric should be checked to confirm CPU throttling?

A.CPUUtilization
B.NetworkIn
C.CPUCreditBalance
D.DiskReadOps
AnswerC

Indicates CPU throttling for T2/T3 instances.

Why this answer

CPUCreditBalance indicates the number of CPU credits available for burstable performance instances. If the credit balance is depleted, the instance is throttled, which can cause high CPU usage with limited performance. Option A (CPUUtilization) shows CPU usage but does not directly indicate throttling.

Option B (NetworkIn) and Option D (DiskReadOps) are unrelated to CPU throttling.

Full explanation →
1611
Multi-Selectmedium

A company is designing an SAP environment on AWS and needs to ensure high availability for SAP HANA. Which TWO AWS services or features are commonly used to achieve this? (Choose TWO.)

Select 2 answers
A.Amazon EFS with Multi-AZ mount targets
B.Amazon S3 cross-region replication
C.Amazon Route 53 with failover routing
D.SAP HANA system replication across Availability Zones
E.AWS Global Accelerator with endpoint weights
AnswersC, D

Route 53 can redirect traffic to the secondary HANA instance upon failure.

Why this answer

Amazon Route 53 with failover routing is correct because it allows DNS-based routing to redirect traffic to a secondary SAP HANA instance in another Availability Zone if the primary fails. This is a common pattern for achieving high availability for SAP HANA on AWS, as it works in conjunction with SAP HANA system replication to provide automatic failover at the DNS level.

Exam trap

The trap here is that candidates often confuse high availability with disaster recovery, leading them to select cross-region replication (option B) or Global Accelerator (option E) instead of recognizing that within a single region, SAP HANA system replication and Route 53 failover routing are the standard AWS services for high availability.

Full explanation →
1612
MCQeasy

A company runs SAP Business Warehouse (BW) on AWS. The BW system uses a single HANA database instance on an r5.12xlarge EC2 instance with 4 EBS io1 volumes for data. The company has noticed that during peak data loads, the CPU utilization on the HANA instance reaches 90%. An SAP consultant recommends increasing the CPU capacity. The company wants to minimize costs and avoid over-provisioning. What is the most cost-effective solution to increase CPU capacity for the HANA instance?

A.Change the EC2 instance type to a larger size in the r5 family, such as r5.16xlarge, to add more vCPUs.
B.Increase the provisioned IOPS on the EBS volumes to improve I/O performance.
C.Deploy additional HANA worker nodes and configure a scale-out system.
D.Migrate the HANA instance to a compute-optimized instance family, such as c5.
AnswerA

Instance resizing is simple and cost-effective.

Why this answer

The simplest and most cost-effective way to increase CPU capacity is to resize the EC2 instance to a larger instance type within the same family (e.g., r5.16xlarge or r5.24xlarge). This provides more vCPUs without needing to change the architecture. Option B is incorrect because increasing EBS volume IOPS does not add CPU capacity.

Option C is incorrect because launching additional HANA instances for scale-out is complex and more expensive. Option D is incorrect because using a different instance family (e.g., compute-optimized) may require reconfiguration and is not as straightforward as resizing within the same family.

Full explanation →
1613
Multi-Selecthard

An SAP system on AWS is experiencing performance issues due to high I/O wait times on the database server. The database runs on an EC2 instance with EBS volumes. Which THREE actions can improve the I/O performance? (Choose THREE.)

Select 3 answers
A.Reduce the volume size to increase the burst duration
B.Use instance store SSDs for the database logs
C.Use an EBS-optimized EC2 instance
D.Increase the provisioned IOPS of the EBS volumes
E.Configure RAID 0 of multiple gp2 volumes
AnswersB, C, D

Instance store offers low latency for temporary data.

Why this answer

Instance store SSDs provide very low latency and high IOPS directly attached to the EC2 host, which is ideal for database log files that require frequent, synchronous writes. By offloading the logs from EBS to instance store, you reduce contention on the EBS volumes and improve overall I/O performance for the SAP database.

Exam trap

The trap here is that candidates may think increasing volume size (Option A) improves burst performance, but AWS gp2 burst credits are based on volume size—larger volumes actually have higher baseline performance and longer burst duration, so reducing size is counterproductive.

Full explanation →
1614
Multi-Selectmedium

Which TWO of the following are best practices for monitoring SAP on AWS? (Choose 2)

Select 2 answers
A.Set up Amazon CloudWatch alarms for HANA database metrics
B.Use SAP EarlyWatch Alert to monitor the SAP system
C.Disable detailed monitoring on EC2 instances to reduce costs
D.Manually review system logs weekly
E.Take daily EBS snapshots of the HANA data volume
AnswersA, B

CloudWatch alarms provide automated notification of metric thresholds.

Why this answer

Options A and B are correct. A: Amazon CloudWatch alarms for HANA database metrics enable proactive detection of performance issues, such as high memory or CPU usage, which is critical for SAP systems. B: SAP EarlyWatch Alert (EWA) provides periodic health checks and recommendations, making it a standard best practice for monitoring.

Option C is incorrect because disabling detailed monitoring reduces visibility into EC2 instance performance, harming monitoring capabilities. Option D is incorrect because manual log reviews are not scalable or timely for production systems. Option E is incorrect because EBS snapshots are for backup and disaster recovery, not real-time monitoring.

Full explanation →
1615
MCQhard

A company is running SAP Business Suite on AWS and wants to improve the disaster recovery posture by replicating data to another AWS Region. The solution must have a recovery time objective (RTO) of less than 15 minutes and a recovery point objective (RPO) of less than 5 minutes. Which approach should they take?

A.Configure SAP HANA system replication with synchronous mode.
B.Use AWS Database Migration Service for continuous replication.
C.Use Amazon S3 cross-Region replication for transaction logs.
D.Use AWS Backup to create cross-Region EBS snapshots every 5 minutes.
AnswerA

Synchronous HANA replication ensures data is copied to the secondary before commit, achieving low RPO and RTO.

Why this answer

SAP HANA system replication in synchronous mode ensures that every committed transaction is replicated to the secondary region before acknowledging the commit, achieving an RPO of effectively zero (less than 5 minutes) and enabling rapid failover within seconds, meeting the RTO of under 15 minutes. This is the only native SAP solution that provides the required low-latency, consistent replication for SAP Business Suite on AWS.

Exam trap

The trap here is that candidates often confuse AWS-native replication services (like DMS, S3 CRR, or AWS Backup) with SAP-specific replication mechanisms, assuming any continuous replication can meet the strict RPO/RTO, but only SAP HANA system replication is designed for sub-minute failover and near-zero data loss for SAP workloads.

How to eliminate wrong answers

Option B is wrong because AWS Database Migration Service (DMS) is designed for heterogeneous database migrations and continuous replication of changes, but it does not support SAP HANA as a source for ongoing replication with the required RPO/RTO; it introduces latency and potential data inconsistency that cannot guarantee sub-5-minute RPO. Option C is wrong because Amazon S3 cross-Region replication for transaction logs is asynchronous and can have replication delays of minutes to hours, failing the RPO of less than 5 minutes; additionally, it requires manual log replay and does not provide automated failover for the SAP application. Option D is wrong because AWS Backup creating cross-Region EBS snapshots every 5 minutes cannot achieve an RPO of less than 5 minutes (snapshots are point-in-time and the interval itself is 5 minutes, plus snapshot creation and transfer time), and restoring from snapshots takes significantly longer than 15 minutes, failing the RTO requirement.

Full explanation →
1616
MCQhard

An SAP HANA system on AWS is experiencing slow backup performance when using Backint to Amazon S3. The backup throughput is only 200 MB/s. The environment uses an m5.24xlarge instance with 25 Gbps network. What is the most likely cause and solution?

A.The network bandwidth is insufficient. Enable S3 Transfer Acceleration.
B.The EBS volumes are too slow. Use instance store volumes for temporary storage.
C.The S3 bucket is not using multipart upload. Enable multipart upload on the bucket.
D.The Backint agent is configured with too few parallel streams. Increase the number of streams in the Backint configuration.
AnswerD

More streams increase parallelism and throughput.

Why this answer

The most likely cause is that the Backint agent is configured with too few parallel streams. Backint for SAP HANA on AWS uses multiple concurrent streams to upload backup data to S3; if the stream count is too low, it cannot saturate the available network bandwidth, resulting in throughput far below the instance's 25 Gbps capacity. Increasing the number of parallel streams in the Backint configuration allows the backup to fully utilize the network and achieve higher throughput.

Exam trap

The trap here is that candidates may assume network bandwidth or storage I/O is the bottleneck, when in fact the Backint agent's parallel stream count is a common misconfiguration that limits throughput despite ample infrastructure resources.

How to eliminate wrong answers

Option A is wrong because the m5.24xlarge instance has 25 Gbps network bandwidth, which is more than sufficient for 200 MB/s (1.6 Gbps); S3 Transfer Acceleration would not help as the bottleneck is not network latency or bandwidth. Option B is wrong because EBS volumes are not directly involved in Backint backups to S3; Backint streams data directly from memory to S3, and instance store volumes are not used for temporary storage in this workflow. Option C is wrong because Backint inherently uses multipart upload for large backups; enabling multipart upload on the bucket is not a configurable setting and is already the default behavior for S3 objects over 5 GB.

Full explanation →
Page 21

Page 22 of 22

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 →