Knowledge + Practice

AWS Certified SAP on AWS Specialty PAS-C01 (PAS-C01) — Questions 76–150

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

Take a mock exam Exam hub

Page 2 of 22

76

Multi-Selecteasy

A company is planning to run SAP HANA on AWS. Which three are best practices for configuring the EC2 instance for SAP HANA? (Choose THREE.)

Select 3 answers

A.Enable CPU hyper-threading

B.Use burstable instance types (T2/T3)

C.Use EBS-optimized instances

D.Allocate swap space on the instance

E.Use placement groups for HANA instances

AnswersA, C, E

Hyper-threading is recommended for HANA.

Why this answer

(Enable CPU hyper-threading) is correct. For SAP HANA, hyper-threading is enabled by default and recommended for production workloads as it improves performance. Option C (Use EBS-optimized instances) is correct because EBS-optimized instances provide dedicated throughput between EC2 and EBS, ensuring consistent storage performance for HANA data and log volumes.

Option E (Use placement groups for HANA instances) is correct. Placement groups enable low-latency, high-throughput networking between instances in the same group, which is critical for HANA scale-out or HA setups. Option B (Use burstable instance types (T2/T3)) is incorrect because burstable instances rely on CPU credits and are not designed for sustained high CPU utilization; they are not suitable for production HANA workloads.

Option D (Allocate swap space on the instance) is incorrect because SAP HANA relies on in-memory processing and swap space is not recommended; it can degrade performance and is typically disabled.

Full explanation →

77

Multi-Selecthard

A company is planning to migrate its SAP HANA database to AWS. The database is 5 TB in size and requires high IOPS for online transaction processing (OLTP) workloads. Which THREE AWS storage options are suitable for SAP HANA data volumes? (Choose THREE.)

Select 3 answers

A.EC2 instance store (NVMe SSD)

B.Amazon EBS io2 Block Express volumes

C.Amazon S3

D.Amazon EBS gp3 volumes

E.Amazon EFS

AnswersA, B, D

Instance store provides very high IOPS, but data is ephemeral; suitable for /hana/data with replication.

Why this answer

EC2 instance store (NVMe SSD) provides very high IOPS and low latency directly attached to the host, which is suitable for SAP HANA data volumes that require high performance for OLTP workloads. However, instance store is ephemeral, so it must be used with replication or backup strategies for persistence.

Exam trap

The trap here is that candidates may confuse Amazon S3 or EFS as suitable for database workloads due to their scalability, but they lack the block-level access and consistent high IOPS required for SAP HANA data volumes.

Full explanation →

78

Multi-Selecthard

An SAP system on AWS is experiencing high latency. Which THREE metrics should be examined in Amazon CloudWatch to diagnose the issue?

Select 3 answers

A.NetworkIn/NetworkOut

B.DiskReadBytes

C.StatusCheckFailed

D.CPUUtilization

E.EBS VolumeQueueLength

AnswersA, D, E

Network metrics can reveal congestion.

Why this answer

Options A, D, and E are correct. A (NetworkIn/NetworkOut) can indicate network bandwidth saturation, which causes latency. D (CPUUtilization) can indicate CPU bottleneck, leading to processing delays.

E (EBS VolumeQueueLength) indicates storage I/O wait, a common cause of latency in SAP systems. B (DiskReadBytes) alone is less informative without queue length; high read/write bytes don't necessarily indicate latency. C (StatusCheckFailed) is for instance health, not performance latency.

Full explanation →

79

Drag & Dropmedium

Drag and drop the steps to set up an SAProuter connection between an on-premises network and AWS for SAP support access 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

SAProuter setup involves deploying instance, configuring SAProuter, opening port, establishing connectivity, and routing.

Full explanation →

80

MCQmedium

An SAP administrator runs the AWS CLI command shown in the exhibit to describe an EBS volume attached to an EC2 instance running SAP HANA. The instance is in the us-east-1a Availability Zone. The administrator needs to create a volume in us-east-1b and copy the data from the existing volume. What is the most efficient way to achieve this?

A.Use rsync to copy data from the instance to a new volume in us-east-1b over the network

B.Detach the volume from the instance and attach it to an instance in us-east-1b

C.Create a snapshot of the volume and then create a new volume in us-east-1b from the snapshot

D.Create an AMI from the instance and launch a new instance in us-east-1b

AnswerC

Snapshots are AZ-independent and can be used to create volumes in different AZs.

Why this answer

Creating a snapshot of the existing volume is the most efficient way to copy data across Availability Zones. Then, create a new volume in us-east-1b from that snapshot. Detaching the volume and attaching it to an instance in us-east-1b is not possible because the volume is tied to its AZ.

Creating an AMI is unnecessary overhead. Using rsync over the network would require an instance in the same AZ and network bandwidth.

Full explanation →

81

MCQeasy

An operations team needs to monitor the disk space usage of SAP application servers running on EC2. Which combination of AWS services should they use?

A.Amazon CloudWatch and AWS CloudTrail

B.Amazon CloudWatch agent and Amazon CloudWatch alarms

C.AWS Lambda and Amazon DynamoDB

D.Amazon S3 and Amazon SNS

AnswerB

CloudWatch agent collects disk metrics, and alarms can notify when thresholds are exceeded.

Why this answer

Amazon CloudWatch agent is required to collect custom metrics like disk space usage from EC2 instances, as the standard CloudWatch metrics only cover CPU, memory, network, and disk I/O. By installing the agent and configuring it to report disk space metrics, you can then set CloudWatch alarms to trigger notifications when thresholds are breached, enabling proactive monitoring of SAP application servers.

Exam trap

The trap here is that candidates assume standard EC2 CloudWatch metrics include disk space usage, but they only include disk read/write operations (I/O), not percentage of disk space used, so the CloudWatch agent is mandatory for this specific monitoring requirement.

How to eliminate wrong answers

Option A is wrong because AWS CloudTrail records API activity and governance events, not system-level metrics like disk space usage; it cannot monitor disk space. Option C is wrong because AWS Lambda and Amazon DynamoDB are serverless compute and database services, not designed for collecting or alerting on EC2 disk metrics; they lack native agent-based metric collection. Option D is wrong because Amazon S3 is object storage and Amazon SNS is a notification service; while SNS can send alerts, S3 cannot collect or analyze disk space data from EC2 instances, and this combination omits the necessary metric collection agent.

Full explanation →

82

MCQeasy

A company runs SAP Business Suite on AWS and wants to implement a disaster recovery (DR) solution with a Recovery Time Objective (RTO) of 4 hours and a Recovery Point Objective (RPO) of 1 hour. The primary site is in us-east-1, and DR site will be in us-west-2. The database is running on SAP ASE. The company wants to minimize changes to the existing SAP environment and avoid complex replication setups. What is the most suitable DR approach?

A.Deploy a Multi-AZ database in the primary region.

B.Set up SAP ASE native replication to a standby database in the DR region.

C.Use AWS Backup to schedule snapshots of the EBS volumes and copy them to the DR region.

D.Use AWS Database Migration Service to continuously replicate data to the DR region.

AnswerC

Simple and meets RPO/RTO with proper scheduling.

Why this answer

AWS Backup can schedule EBS snapshots every hour, meeting the RPO of 1 hour, and snapshots can be copied to the DR region (us-west-2). Restoring from these snapshots can be automated to achieve the RTO of 4 hours. This approach requires minimal changes to the existing SAP environment and avoids complex replication setups.

Option A is incorrect because Multi-AZ replication is for high availability within a single region, not for disaster recovery across regions. Option B is incorrect because SAP ASE native replication would require significant changes to the database configuration and licensing, contradicting the requirement to minimize changes. Option D is incorrect because AWS Database Migration Service is designed for ongoing data replication and is not the best fit for a simple backup/restore DR strategy.

Full explanation →

83

Multi-Selecthard

A company is migrating an SAP ERP system to AWS using a heterogeneous migration. Which THREE components must be converted or migrated?

Select 3 answers

A.Database schema

B.Networking configuration

C.Data

D.Operating system

E.Custom ABAP code and stored procedures

AnswersA, C, E

Schema must be converted to target format.

Why this answer

Schema (using AWS SCT), data (using AWS DMS), and custom ABAP code (using SCT) are all required for a heterogeneous migration. Networking configuration is not part of the data migration; operating system is not migrated as part of database migration.

Full explanation →

84

MCQhard

A company is migrating an SAP HANA workload to Amazon EC2. Which configuration ensures data encryption at rest and in transit without performance degradation?

A.Use client-side encryption with AWS KMS for SAP HANA data files.

B.Use EBS encryption with AWS KMS for at-rest and VPC peering for in-transit.

C.Disable encryption to maximize performance; use security groups for isolation.

D.Enable Amazon EBS encryption with SSE-EBS for at-rest and enable in-transit encryption using TLS.

AnswerD

SAP HANA TDE with AWS KMS provides efficient at-rest encryption, and TLS provides efficient in-transit encryption, meeting the performance requirement.

Why this answer

Amazon EBS encryption (SSE-EBS) provides at-rest encryption with minimal performance overhead (handled at the hypervisor layer with hardware acceleration), and TLS secures data in transit. Option A is incorrect because client-side encryption adds CPU overhead on the EC2 instance, potentially degrading SAP HANA performance. Option B is incorrect because VPC peering does not encrypt traffic in transit; TLS must be used.

Option C is incorrect as it compromises security.

Full explanation →

85

Multi-Selecthard

A company is designing a disaster recovery solution for SAP HANA on AWS using HANA System Replication. The primary site is in us-east-1 and the DR site is in us-west-2. Which component is required to enable replication across Regions?

Select 1 answer

A.AWS Site-to-Site VPN or AWS Direct Connect between the two Regions

B.VPC peering between the two VPCs

C.Automated EBS snapshots of /hana/data and /hana/log volumes in us-east-1, copied to us-west-2

D.AWS Global Accelerator

E.Amazon S3 Transfer Acceleration

AnswersA

Correct. Low-latency, reliable network connectivity between regions is essential for continuous log shipping and data synchronization in HSR. AWS Site-to-Site VPN or Direct Connect provides this.

Why this answer

To enable HANA System Replication (HSR) across AWS Regions, a reliable, low-latency network connection is required. AWS Site-to-Site VPN or AWS Direct Connect provides a dedicated, secure network path that meets SAP's latency and stability requirements. The other options (VPC peering, automated EBS snapshots, Global Accelerator, S3 Transfer Acceleration) are not required for HSR; HSR performs its own initial data synchronization, and VPC peering does not guarantee the required performance for HANA replication.

Exam trap

A common mistake is assuming that you need to copy data volumes via snapshots before starting HSR. In reality, HSR performs its own initial sync, so snapshots are unnecessary. Another trap is thinking VPC peering is sufficient, but it lacks the guaranteed performance needed for cross-region HSR.

Full explanation →

86

MCQmedium

An SAP administrator runs the CLI commands shown in the exhibit for a production EC2 instance. The output indicates that the instance is running but the system status is impaired. Which action should the administrator take to recover the instance?

A.Reboot the instance using the AWS console.

B.Restart the SAP application services.

C.Configure EC2 Auto Recovery and wait for recovery.

D.Stop and start the instance.

AnswerC

EC2 Auto Recovery is the correct automated method to recover from a system status impairment, moving the instance to healthy hardware.

Why this answer

EC2 Auto Recovery is the correct action when the system status check fails (impaired) because it automatically recovers the instance by moving it to new hardware while preserving its configuration. Option A (reboot) does not address underlying hardware issues. Option B (restart SAP services) is irrelevant to hardware impairment.

Option D (stop and start) does move the instance to new hardware, but it is a manual process and not the recommended automated recovery method. EC2 Auto Recovery is designed specifically for this scenario.

Exam trap

The trap is confusing a stop/start action with EC2 Auto Recovery. Both move the instance to new hardware, but Auto Recovery is automated and triggered by the status check failure, while stop/start is manual and may cause additional downtime.

Full explanation →

87

MCQmedium

An SAP administrator needs to migrate an on-premises SAP HANA system to AWS. The total size of the HANA data and log volumes is 5 TB. The administrator wants to minimize downtime and use the fastest possible initial data transfer method. Which approach should they use?

A.Use Amazon S3 Transfer Acceleration to upload the data over the internet

B.Use AWS Snowball Edge to physically ship the data

C.Use AWS Direct Connect to transfer the data over a dedicated network connection

D.Use VPC Peering to connect on-premises to AWS and copy data

AnswerB

Snowball Edge can transfer 5 TB quickly and securely, minimizing downtime.

Why this answer

AWS Snowball Edge provides a physical data transfer device that can be shipped to the on-premises site, loaded with the 5 TB of SAP HANA data and log volumes, and then shipped back to AWS for ingestion into an S3 bucket. This approach offers the fastest initial transfer for large datasets (multi-TB) over a WAN, as it bypasses network bandwidth limitations entirely, minimizing downtime compared to internet-based or dedicated network transfers.

Exam trap

The trap here is that candidates often choose Direct Connect (Option C) assuming a dedicated network is always fastest, but for large initial bulk transfers (multi-TB), physical shipping via Snowball Edge is faster because it avoids network bandwidth constraints and transfer time, which is a key concept tested in the PAS-C01 exam for minimizing downtime during SAP HANA migrations.

How to eliminate wrong answers

Option A is wrong because Amazon S3 Transfer Acceleration still relies on internet connectivity and is limited by available bandwidth; for 5 TB, it would take significantly longer than a physical shipment, especially with typical on-premises upload speeds. Option C is wrong because AWS Direct Connect provides a dedicated network connection but is still constrained by the provisioned bandwidth (e.g., 1 Gbps or 10 Gbps); transferring 5 TB over even a 10 Gbps link would take over an hour, and setup latency plus potential throttling make it slower than a physical shipment for initial bulk transfer. Option D is wrong because VPC Peering is a networking feature for connecting VPCs within AWS, not for on-premises to AWS connectivity; it cannot be used to transfer data from on-premises to AWS, and even if combined with a VPN, it would still be network-bound and slower than Snowball Edge.

Full explanation →

88

MCQeasy

An SAP system uses a custom RFC destination to an external SOAP web service. After a recent network change, the RFC call fails with a timeout error. The SAP administrator has verified that the web service is reachable from the SAP application server using ping. What is the MOST likely cause of the timeout?

A.The DNS resolution is incorrect for the web service hostname.

B.The SAP router configuration is blocking the connection.

C.The SSL certificate of the web service has expired.

D.A firewall between the application server and the web service is blocking the required port.

AnswerD

Firewall rules may block the specific port while allowing ICMP.

Why this answer

The RFC call uses a specific port (e.g., 443 for HTTPS or 80 for HTTP) to communicate with the SOAP web service. A firewall blocking that port would cause a timeout, as the ping test (ICMP) succeeds but the TCP handshake on the required port fails. The SAP administrator's verification of reachability via ping only confirms ICMP-level connectivity, not application-layer port access.

Exam trap

The trap here is that candidates confuse ICMP reachability (ping) with TCP port-level connectivity, assuming that if a server responds to ping, all network paths are open.

How to eliminate wrong answers

Option A is wrong because DNS resolution issues would typically cause a 'host not found' error, not a timeout; the ping success already indicates DNS is working. Option B is wrong because the SAP router is used for SAP-specific RFC traffic between SAP systems, not for external SOAP web service calls via RFC destinations. Option C is wrong because an expired SSL certificate would cause a handshake failure or certificate validation error, not a timeout; the connection would still be established before the SSL/TLS negotiation fails.

Full explanation →

89

MCQeasy

An SAP system uses Amazon EFS for shared file storage for transport directories. The system is deployed across multiple Availability Zones. Which EFS performance mode is most suitable for this workload?

A.Max I/O performance mode.

B.Provisioned Throughput mode.

C.General Purpose performance mode.

D.Bursting Throughput mode.

AnswerC

General Purpose provides low latency for file operations.

Why this answer

General Purpose performance mode is the most suitable for SAP transport directories because it provides the lowest latency for file operations, which is critical for the frequent, small I/O operations typical of SAP transport processes. Max I/O mode, while offering higher throughput for large sequential I/O, introduces higher latency that can degrade SAP performance. General Purpose mode is the default and recommended mode for most EFS workloads, including SAP shared file systems.

Exam trap

The trap here is that candidates confuse performance modes (General Purpose vs. Max I/O) with throughput models (Bursting vs. Provisioned), leading them to select a throughput option like Provisioned or Bursting when the question explicitly asks for the most suitable performance mode for a latency-sensitive SAP workload.

How to eliminate wrong answers

Option A is wrong because Max I/O performance mode is designed for highly parallel, large-file workloads (e.g., big data, media processing) and has higher latency per operation, which is unsuitable for the latency-sensitive, small-file I/O patterns of SAP transport directories. Option B is wrong because Provisioned Throughput mode is a throughput setting, not a performance mode; it can be applied to either General Purpose or Max I/O modes to set a baseline throughput independent of file system size, but it does not define the latency or concurrency characteristics needed for this workload. Option D is wrong because Bursting Throughput mode is also a throughput model (not a performance mode) that allows throughput to burst based on accumulated credits; while it can be used with General Purpose mode, it is not a performance mode choice and does not address the latency requirements of SAP transport directories.

Full explanation →

90

MCQhard

An SAP system administrator is troubleshooting an issue where an application cannot connect to an SAP HANA database running on an EC2 instance. The security group for the HANA instance allows inbound traffic on port 39013 (SQL) from the application server's security group. The network ACLs for the subnet allow all traffic. What could be the cause of the connectivity issue?

A.The security group for the HANA instance does not allow inbound traffic on port 39013 from the application server's IP address.

B.The network ACL for the application server's subnet does not allow outbound traffic on port 39013.

C.The network ACL for the HANA instance's subnet is missing an outbound rule to allow return traffic on ephemeral ports.

D.The security group for the application server does not allow outbound traffic on port 39013.

AnswerC

C is correct: NACLs are stateless; outbound rules for return traffic are required.

Why this answer

The network ACL is stateless and must allow both inbound and outbound traffic; the outbound rule for ephemeral ports may be missing. Option A is incorrect because the security group allows the port. Option B is incorrect because the NACL allows all inbound traffic.

Option D is incorrect because the security group allows the application server's security group.

Full explanation →

91

MCQhard

An organization is deploying a large SAP HANA system on AWS. They need to ensure that the EBS volumes for the /hana/data and /hana/log directories are configured with optimal performance and resilience. Which configuration should they use?

A.Use io2 Block Express volumes with /hana/data on a RAID 1 set and /hana/log on a RAID 0 set

B.Use a single large gp3 EBS volume for both /hana/data and /hana/log

C.Use io2 Block Express volumes with /hana/data on a RAID 0 set and /hana/log on a RAID 1 set

D.Use io2 Block Express volumes with /hana/data on one volume and /hana/log on another, no RAID

AnswerC

RAID 0 for data performance, RAID 1 for log resilience.

Why this answer

SAP HANA requires high IOPS and low latency for /hana/data, which benefits from RAID 0 striping across multiple io2 Block Express volumes to maximize throughput and capacity. For /hana/log, RAID 1 mirroring provides the necessary resilience to protect against volume failure while maintaining the write performance critical for transaction log durability. io2 Block Express volumes offer up to 256,000 IOPS and 4,000 MB/s throughput per volume, making them ideal for this high-performance workload.

Exam trap

The trap here is that candidates often assume RAID 1 is always for data and RAID 0 for logs, but SAP HANA specifically requires RAID 0 for /hana/data to maximize performance and RAID 1 for /hana/log to ensure resilience, reversing the common intuition.

How to eliminate wrong answers

Option A is wrong because it reverses the RAID configurations: /hana/data should use RAID 0 for performance, not RAID 1, and /hana/log should use RAID 1 for resilience, not RAID 0. Option B is wrong because a single gp3 volume cannot provide the high IOPS and low latency required for SAP HANA, and mixing /hana/data and /hana/log on one volume violates SAP's separation best practices, risking performance interference and single points of failure. Option D is wrong because using individual volumes without RAID for /hana/data fails to aggregate IOPS and throughput across multiple volumes, and for /hana/log it lacks the mirroring needed to protect against volume failure, which is critical for transaction log integrity.

Full explanation →

92

MCQhard

An architect is designing a storage solution for an SAP Business Warehouse (BW) system on AWS. The system requires high throughput for data extraction and transformation. The existing on-premises system uses SAN storage with 10,000 IOPS. Which Amazon EBS volume type should the architect choose to meet or exceed this performance at the lowest cost?

A.sc1 with 10,000 IOPS

B.io1 with 10,000 Provisioned IOPS

C.gp3 with 10,000 IOPS and 500 MB/s throughput

D.st1 with 10,000 IOPS

AnswerC

gp3 can achieve 10,000 IOPS at lower cost than io1, and throughput is adequate.

Why this answer

Amazon EBS gp3 volumes can provision up to 16,000 IOPS and 1,000 MB/s throughput independently, making them suitable for SAP BW workloads requiring 10,000 IOPS. gp3 offers a lower cost than io1 because it includes a baseline performance (3,000 IOPS and 125 MB/s) and only charges for additional provisioned IOPS and throughput, whereas io1 charges for every provisioned IOPS. This makes gp3 the most cost-effective choice to meet or exceed the required 10,000 IOPS and 500 MB/s throughput.

Exam trap

The trap here is that candidates may assume io1 is the only option for guaranteed IOPS due to its 'Provisioned IOPS' branding, overlooking gp3's ability to provision IOPS independently at a lower cost, or they may incorrectly think HDD-based volumes (sc1, st1) can achieve high IOPS values.

How to eliminate wrong answers

Option A is wrong because sc1 (Cold HDD) is a throughput-optimized volume designed for infrequently accessed data, with a maximum IOPS of 250 per volume and cannot achieve 10,000 IOPS. Option B is wrong because io1 (Provisioned IOPS SSD) can provide 10,000 IOPS but at a higher cost than gp3, as io1 charges for every provisioned IOPS regardless of usage, making it less cost-effective for this requirement. Option D is wrong because st1 (Throughput Optimized HDD) is designed for large, sequential workloads with a maximum IOPS of 500 per volume and cannot sustain 10,000 IOPS.

Full explanation →

93

MCQmedium

A company is running an SAP HANA database on an EC2 instance with EBS volumes. The database experiences high write latency during peak hours. Which configuration change would most effectively reduce latency?

A.Switch to gp3 EBS volumes with maximum throughput.

B.Increase the EC2 instance size to a compute-optimized type.

C.Use EBS io2 Block Express volumes with multi-attach enabled.

D.Migrate the data to instance store volumes.

AnswerC

io2 Block Express volumes offer up to 256,000 IOPS and sub-millisecond latency, meeting SAP HANA performance requirements.

Why this answer

SAP HANA is a high-performance in-memory database that requires extremely low-latency storage for its data and log volumes. EBS io2 Block Express volumes provide up to 256,000 IOPS per volume with single-digit millisecond latency, and multi-attach enables a cluster configuration for high availability. This directly addresses high write latency during peak hours by delivering consistent, ultra-low latency performance that gp3 or larger instances cannot match.

Exam trap

The trap here is that candidates often choose gp3 (Option A) because it is the newer, cost-effective general-purpose volume, but they overlook that SAP HANA's strict latency requirements demand the premium io2 Block Express, not just high throughput.

How to eliminate wrong answers

Option A is wrong because gp3 volumes, while offering baseline performance, have a maximum IOPS of 16,000 per volume (without bursting) and cannot match the sub-millisecond latency and high IOPS required by SAP HANA under heavy write loads. Option B is wrong because increasing the EC2 instance size to a compute-optimized type (e.g., C5) does not improve storage latency; compute-optimized instances are designed for CPU-intensive tasks, not for addressing EBS volume performance bottlenecks. Option D is wrong because instance store volumes are ephemeral and do not persist data across stops or terminations, making them unsuitable for a production SAP HANA database that requires durable, consistent storage for logs and data.

Full explanation →

94

MCQhard

A company is planning a migration of their SAP ERP system to AWS. They want to use SAP HANA as the database. The current on-premises database size is 2 TB. The migration must have minimal downtime. Which combination of AWS services and methods should be used to achieve a near-zero downtime migration?

A.Use AWS DMS with a SAP HANA source and target, configuring ongoing replication to minimize downtime

B.Use AWS Database Migration Service (DMS) with an SAP HANA source and S3 as target

C.Use SAP HANA System Replication (HSR) to replicate data to an EC2 instance in AWS

D.Use AWS Backup to perform a continuous backup of the on-premises HANA database and restore to AWS

AnswerA

DMS supports ongoing replication to keep data in sync with minimal downtime.

Why this answer

AWS DMS with a SAP HANA source and target, configuring ongoing replication, is correct because it supports near-zero downtime migration by continuously replicating changes from the on-premises HANA database to the target HANA database on AWS until cutover. DMS uses log-based change data capture (CDC) to capture ongoing transactions, allowing the source to remain operational during the bulk load and then switch with minimal interruption.

Exam trap

The trap here is that candidates may confuse SAP HANA System Replication (HSR) as a native AWS service or assume AWS Backup can handle on-premises continuous backups, when in fact AWS DMS with CDC is the only option that provides a managed, near-zero downtime migration path for SAP HANA to AWS.

How to eliminate wrong answers

Option B is wrong because using S3 as a target for AWS DMS with a SAP HANA source is not a valid migration path for SAP HANA; DMS cannot replicate directly to S3 for a HANA target, and S3 is not a database target for HANA workloads. Option C is wrong because SAP HANA System Replication (HSR) replicates data to an EC2 instance, but this requires a pre-configured HANA instance on AWS and does not provide a managed migration service; it also involves complex setup and potential downtime during the initial synchronization and cutover. Option D is wrong because AWS Backup does not support continuous backup of on-premises HANA databases; it is designed for AWS resources, and even if used, it would require a full backup and restore, which cannot achieve near-zero downtime due to the time needed for backup transfer and restoration.

Full explanation →

95

Multi-Selecthard

A company is designing a disaster recovery (DR) strategy for its SAP system on AWS. The primary site is in us-east-1, and the DR site is in us-west-2. The system uses SAP HANA as the database. Which THREE components must be configured to enable a successful DR failover?

Select 3 answers

A.SAP HANA system replication across regions.

B.Amazon Route53 DNS failover configuration.

C.AWS Backup cross-region backup copy for the HANA database.

D.S3 Cross-Region Replication for SAP transport files.

E.AWS Transit Gateway peering between the two regions.

AnswersA, B, C

SAP HANA system replication across regions ensures data consistency and near-synchronous replication for DR failover.

Why this answer

The correct three components are SAP HANA system replication across regions (A), Amazon Route53 DNS failover configuration (B), and AWS Backup cross-region backup copy for the HANA database (C). SAP HANA system replication ensures data consistency and near-synchronous replication between the primary and DR sites. Route53 DNS failover automatically redirects traffic to the DR site in case of a failure.

AWS Backup cross-region copy provides an additional backup of the HANA database in the DR region, ensuring backup availability. Option D (S3 Cross-Region Replication) is not essential for HANA replication; transport files can be handled separately. Option E (AWS Transit Gateway peering) provides network connectivity but is not a DR failover component.

Full explanation →

96

MCQmedium

A company runs a critical web application on EC2 instances behind an Application Load Balancer. The application uses Auto Scaling and a MySQL RDS Multi-AZ DB instance. Users report intermittent connection timeouts, and CloudWatch metrics show CPUUtilization spikes to 90% on the DB instance. The application queries are read-heavy with occasional writes. What is the MOST cost-effective design change to improve performance?

A.Implement ElastiCache Redis cluster to cache query results and reduce DB load.

B.Enable RDS Performance Insights and create a CloudWatch alarm to reboot the DB instance on high CPU.

C.Add an RDS read replica in the same region and configure the application to route read queries to the replica.

D.Switch the DB instance to a larger instance type to handle the load.

AnswerC

A read replica offloads read traffic, reducing CPU on the primary, and is cost-effective for read-heavy workloads.

Why this answer

The most cost-effective design change because adding an RDS read replica offloads read-heavy queries from the primary DB instance, reducing CPU utilization without requiring a larger instance. Since the workload is read-heavy with occasional writes, a read replica handles SELECT traffic while the Multi-AZ primary manages writes, improving performance at a lower cost than scaling up.

Exam trap

The trap here is that candidates often choose ElastiCache (Option A) thinking caching always reduces DB load, but for a read-heavy workload with occasional writes, an RDS read replica is more cost-effective and directly addresses the CPU spikes from read queries without the overhead of cache invalidation and additional infrastructure.

How to eliminate wrong answers

Option A is wrong because ElastiCache Redis caches query results, which reduces DB load for repeated queries but does not address the root cause of high CPU from read-heavy queries that may not be cacheable; it also adds complexity and cost for a workload better served by a read replica. Option B is wrong because enabling Performance Insights and rebooting the DB instance on high CPU is a reactive measure that does not prevent CPU spikes, and rebooting causes downtime, which is unacceptable for a critical application. Option D is wrong because switching to a larger instance type increases cost significantly without optimizing the read-heavy workload, whereas a read replica provides dedicated read capacity at a lower incremental cost.

Full explanation →

97

MCQeasy

A company is migrating its SAP system to AWS and needs to maintain compliance with regulatory requirements that mandate data encryption at rest. Which AWS service should be used to manage encryption keys for Amazon EBS volumes?

A.AWS Secrets Manager

B.AWS Certificate Manager (ACM)

C.AWS Key Management Service (KMS)

D.AWS CloudHSM

AnswerC

KMS is the managed service for encryption keys and integrates with EBS.

Why this answer

WS Key Management Service (KMS). KMS is used to create and control encryption keys for encrypting Amazon EBS volumes. Option A (AWS Secrets Manager) is for managing secrets like database credentials, not encryption keys.

Option B (AWS Certificate Manager) handles SSL/TLS certificates. Option D (AWS CloudHSM) provides hardware security modules but is more complex and typically used for specific compliance needs; KMS is the standard service for managing EBS encryption keys.

Full explanation →

98

MCQeasy

A company runs a critical SAP application on AWS. The SAP team needs to reduce network latency between application servers and the database. Which AWS service should be used to achieve this?

A.Amazon Route 53

B.AWS Global Accelerator

C.VPC Peering

D.Placement Groups (cluster)

AnswerD

Cluster placement groups place instances in a single AZ with low-latency networking.

Why this answer

Placement Groups with a cluster placement strategy are designed to provide the lowest possible network latency and highest throughput by ensuring that EC2 instances are placed in a single Availability Zone with low-latency, high-bandwidth networking. For a critical SAP application where the application servers and database must communicate with minimal latency, a cluster placement group is the correct choice because it leverages non-blocking, fully bisectional bandwidth between instances, reducing network hops and jitter.

Exam trap

The trap here is that candidates often confuse AWS Global Accelerator (which improves latency for external users) with internal network optimization, or they assume VPC Peering provides performance benefits, when in fact only placement groups directly reduce latency between EC2 instances in the same Availability Zone.

How to eliminate wrong answers

Option A is wrong because Amazon Route 53 is a DNS and traffic routing service that does not reduce network latency between EC2 instances; it only resolves domain names to IP addresses. Option B is wrong because AWS Global Accelerator improves latency for global users by directing traffic to the nearest edge location, but it does not reduce latency between application servers and a database within the same AWS region or VPC. Option C is wrong because VPC Peering connects VPCs at the network layer but does not optimize or reduce latency between instances within the same VPC; it simply enables routing between separate VPCs without any performance guarantees.

Full explanation →

99

Multi-Selectmedium

A company is planning to deploy SAP S/4HANA on AWS with high availability. Which action should be taken to achieve high availability for the SAP Central Services (ASCS/ERS) instance?

Select 1 answer

A.Deploy ASCS and ERS in the same Availability Zone.

B.Run both ASCS and ERS on the same EC2 instance.

C.Place ASCS and ERS in the same subnet.

D.Deploy ASCS and ERS in different Availability Zones.

E.Use a cluster placement group for ASCS and ERS instances.

AnswersD

Correct: Deploying ASCS and ERS in different Availability Zones ensures that an AZ failure does not bring down both components, enabling failover via Pacemaker.

Why this answer

The correct action is to deploy ASCS and ERS in different Availability Zones (Option D). This ensures that if one AZ fails, the instance can fail over to the other AZ, providing high availability. Option E (using a cluster placement group) is incorrect because cluster placement groups are confined to a single AZ and cannot span multiple AZs, making them incompatible with the cross-AZ requirement.

Options A, B, and C all violate HA principles by placing both instances in the same AZ or same instance. Therefore, only Option D is a valid action for achieving high availability.

Exam trap

Candidates often mistakenly think that a cluster placement group (option E) can be used for cross-AZ HA, but placement groups are intra-AZ only and not suitable for SAP Central Services HA.

Full explanation →

100

MCQhard

A company runs SAP ERP Central Component (ECC) on AWS with an Oracle database. The system is deployed on a single EC2 instance with EBS volumes. The company has scheduled a maintenance window for applying Oracle patches. The database administrator (DBA) will apply the patches during the maintenance window, which requires the database to be shut down. The DBA wants to minimize downtime and ensure that if the patching fails, the system can be rolled back quickly. The current setup includes daily EBS snapshots of the data volume, but these are taken at midnight. What should the DBA do to minimize downtime and ensure a quick rollback?

A.Create a snapshot of the EBS data volume immediately before applying the patches. If the patching fails, restore the volume from the snapshot.

B.Use AWS Database Migration Service (DMS) to create a replica of the database before patching. If patching fails, redirect traffic to the replica.

C.Create an AMI of the entire EC2 instance before the maintenance window. If patching fails, launch a new instance from the AMI.

D.Stop the EC2 instance, create a snapshot of the data volume, then apply the patches. If patching fails, restore from the snapshot.

AnswerA

A snapshot provides a quick rollback point without additional downtime.

Why this answer

Creating a snapshot of the EBS data volume immediately before applying the patches captures a point-in-time, crash-consistent state of the Oracle database. Since the database will be shut down during the maintenance window, this snapshot provides a reliable restore point. If patching fails, the DBA can quickly restore the volume from this snapshot, minimizing downtime by avoiding the need to restore from the older midnight snapshot, which would lose an entire day's worth of transactions.

Exam trap

The trap here is that candidates may overthink the solution and choose a more complex option like DMS or AMI, not realizing that a simple EBS snapshot taken immediately before patching provides the fastest and most cost-effective rollback for a single-instance SAP ECC with Oracle, as it avoids the overhead of instance recreation or replication setup.

How to eliminate wrong answers

Option B is wrong because AWS Database Migration Service (DMS) is designed for ongoing replication or one-time migrations between heterogeneous or homogeneous databases, not for creating a quick, rollback-ready replica of a running Oracle database for patching. DMS requires setup time, incurs additional costs, and does not provide a simple, immediate rollback mechanism for a single-instance SAP ECC system. Option C is wrong because creating an AMI of the entire EC2 instance captures the OS, application, and data volumes, but it is a heavier, slower operation compared to a data volume snapshot.

Restoring from an AMI would require launching a new instance, reconfiguring networking, and reattaching volumes, leading to significantly longer downtime than a simple volume restore. Option D is wrong because stopping the EC2 instance before creating the snapshot adds unnecessary downtime; the database must be shut down for patching anyway, but the snapshot can be taken while the instance is running (with the database shut down) or even with a brief quiesce, making the stop step redundant and increasing total downtime.

Full explanation →

101

MCQhard

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

A.Enhanced Networking is disabled

B.Incorrect Oracle DB parameter settings

C.EBS snapshot schedule is too frequent

D.EBS volume queue depth is too low causing I/O throttling

AnswerD

Low queue depth leads to I/O bottlenecks and rollback segments issues.

Why this answer

'ORA-1555 snapshot too old' errors occur when Oracle needs to read consistent undo data that has been overwritten. In AWS, EBS volume queue depth that is too low can cause I/O throttling, leading to longer transaction times and increased likelihood of undo segment overwrites before a query completes. Option A is wrong because Enhanced Networking affects network throughput, not storage I/O.

Option B is incorrect because while Oracle DB parameters like UNDO_RETENTION can influence this error, the question asks for an AWS-specific parameter. Option C is wrong because EBS snapshots are point-in-time copies and do not directly cause live transaction rollbacks.

Full explanation →

102

Multi-Selectmedium

An SAP system administrator is troubleshooting a failed HANA database backup to Amazon S3. The backup job returns an error: 'Access Denied'. Which TWO actions should the administrator take to resolve the issue?

Select 2 answers

A.Review the S3 bucket policy for any deny statements that may block the backup.

B.Enable S3 Transfer Acceleration on the bucket.

C.Check the IAM role attached to the EC2 instance for S3 permissions.

D.Verify that the S3 bucket's KMS key is enabled.

E.Set up a VPC endpoint for S3.

AnswersA, C

Bucket policies can explicitly deny access to certain principals.

Why this answer

Options A and C are correct because reviewing the S3 bucket policy for deny statements that may block the backup is a direct step to resolve an 'Access Denied' error, and checking the IAM role attached to the EC2 instance for S3 permissions is also a primary cause of access issues. Option B is incorrect because S3 Transfer Acceleration improves speed, not access. Option D is incorrect because the KMS key being enabled is not a direct cause of access denied; rather, the IAM role must have permission to use the key.

Option E is incorrect because a VPC endpoint is not required if using public S3.

Full explanation →

103

Multi-Selectmedium

Which THREE of the following are best practices for securing an SAP HANA database on AWS? (Choose 3.)

Select 3 answers

A.Assign a public IP address to the HANA instance for easy access

B.Disable the HANA password policy to simplify user access

C.Enable encryption at rest for EBS volumes attached to the HANA instance

D.Enable SAP HANA data encryption for data in transit and at rest

E.Use security groups to restrict inbound traffic to the HANA database

AnswersC, D, E

Encryption protects data at rest.

Why this answer

Encrypting EBS volumes at rest protects the underlying storage of the SAP HANA database from unauthorized physical access or snapshot theft. AWS KMS-managed keys or customer-managed keys can be used to enforce encryption for all data written to the EBS block devices, which is a fundamental security best practice for any sensitive workload on AWS.

Exam trap

The trap here is that candidates may think disabling password policies simplifies management (Option B) or that public IPs are needed for remote access (Option A), but the exam tests understanding that security hardening requires encryption, access restriction, and strong authentication, not convenience.

Full explanation →

104

Multi-Selecteasy

Which TWO AWS services can be used to automate the deployment of SAP infrastructure using infrastructure as code? (Choose 2)

Select 2 answers

A.AWS Service Catalog

B.AWS CloudFormation

C.AWS OpsWorks

D.AWS CodeDeploy

E.AWS Elastic Beanstalk

AnswersA, B

Correct. AWS Service Catalog allows you to deploy pre-approved CloudFormation templates, automating SAP infrastructure deployment as infrastructure as code.

Why this answer

AWS CloudFormation (Option B) allows you to define and provision SAP infrastructure using infrastructure as code templates. AWS Service Catalog (Option A) enables you to create, manage, and deploy pre-approved CloudFormation templates for SAP infrastructure, automating the deployment process. Options C (OpsWorks) is for configuration management with Chef/Puppet, not for infrastructure as code.

Option D (CodeDeploy) handles application deployments, not infrastructure provisioning. Option E (Elastic Beanstalk) is a PaaS service for web applications, not used for automating SAP infrastructure deployment as infrastructure as code.

Full explanation →

105

MCQeasy

An SAP system administrator needs to ensure high availability for an SAP HANA database using AWS services. What is the recommended architecture?

A.Deploy SAP HANA on EC2 instances in a cluster across multiple Availability Zones with synchronous replication

B.Use Amazon RDS for SAP HANA with Multi-AZ deployment

C.Use Amazon RDS Multi-AZ for SAP HANA database

D.Deploy a single EC2 instance in one Availability Zone and take daily snapshots

AnswerA

SAP HANA can be deployed as a multi-node cluster using EC2 instances in different AZs with synchronous replication and automatic failover using cluster software like Pacemaker.

Why this answer

SAP HANA can be deployed as a multi-node cluster using EC2 instances in different Availability Zones with synchronous replication and automatic failover using cluster software like Pacemaker. RDS does not support SAP HANA. A single EC2 instance in one AZ is not highly available.

Multi-AZ RDS is for other databases, not SAP HANA.

Full explanation →

106

Multi-Selecthard

Which TWO AWS services can be used to monitor the health and performance of an SAP HANA database on AWS?

Select 2 answers

A.AWS Trusted Advisor

B.Amazon CloudWatch

C.AWS Config

D.SAP HANA monitoring tools (e.g., HANA cockpit)

E.VPC Flow Logs

AnswersB, D

CloudWatch can monitor metrics and logs from HANA.

Why this answer

Amazon CloudWatch (option B) can monitor OS-level metrics and custom metrics from SAP HANA via the CloudWatch agent or API. SAP HANA monitoring tools like HANA cockpit (option D) provide built-in health and performance monitoring. AWS Trusted Advisor (option A) offers best-practice recommendations, not real-time monitoring.

AWS Config (option C) tracks resource configuration changes. VPC Flow Logs (option E) capture network traffic metadata.

Full explanation →

107

MCQhard

A company runs SAP HANA on AWS using a multi-node scale-out configuration. During a routine maintenance window, the administrator needs to apply an HANA database software update. What is the BEST practice to minimize downtime?

A.Perform a rolling update by updating one node at a time while keeping the system operational.

B.Use HANA System Replication to fail over to a standby system, then update the primary.

C.Stop all HANA services, apply the update to all nodes, then restart.

D.Create a new HANA cluster with the updated version and migrate data.

AnswerA

Correct. Rolling updates allow updating nodes individually without taking the entire system offline, minimizing downtime.

Why this answer

HANA scale-out supports rolling updates, allowing nodes to be updated one by one while the system remains operational, minimizing downtime. Option B is less optimal because using HSR failover adds complexity and is typically reserved for planned migration or disaster recovery, not routine updates. Option C would cause full downtime as it requires stopping all services.

Option D is inefficient for a minor software update as it involves creating a new cluster and migrating data.

Full explanation →

108

MCQhard

A company is deploying SAP S/4HANA on AWS and needs to ensure high availability for the central services (ASCS and ERS). The architecture uses two EC2 instances in different Availability Zones with a shared file system using Amazon EFS for /sapmnt. The SAP system is configured with an enqueue replication server. The operations team needs to automate the failover of the ASCS instance in case of a failure. The team is considering using AWS services for this purpose. Which approach should the team use?

A.Use Amazon Route 53 with health checks and a custom script to update DNS record on failover.

B.Use an Application Load Balancer with a target group containing both ASCS instances.

C.Use an Auto Scaling group with a minimum of 2 instances and a lifecycle hook to handle failover.

D.Enable EC2 Auto Recovery to automatically recover the ASCS instance on new hardware.

AnswerA

DNS-based failover can redirect clients to the secondary ASCS instance.

Why this answer

Route 53 health checks can monitor the ASCS instance and a custom script can update DNS records to point to the standby instance on failure, enabling failover across Availability Zones. Option B is incorrect because an Application Load Balancer cannot properly direct traffic to a single active ASCS instance and does not handle the stateful nature of SAP enqueue replication. Option C is incorrect because Auto Scaling is designed for scaling out, not for failover of stateful services like ASCS.

Option D is incorrect because EC2 Auto Recovery only recovers the same instance on new hardware if it fails, but it does not failover to a different Availability Zone, which is required for high availability.

Full explanation →

109

MCQhard

An SAP HANA database on AWS experiences a failover from the primary to the secondary node. After the failover, the secondary node (now primary) is running on a different AZ. The SAP application cannot connect to the new primary. What is the MOST likely cause?

A.HANA system replication is not configured correctly.

B.The security group for the new primary does not allow inbound traffic from the app.

C.The EBS volumes are not attached to the new primary.

D.The application connection string points to the old primary's IP address.

AnswerD

After failover, the new primary has a different private IP; the app must use a virtual IP or DNS that updates.

Why this answer

After a failover, the new primary node has a different private IP address than the old primary. The SAP application's connection string likely points to the old primary's IP, so it cannot connect to the new primary. Option A is incorrect because HANA system replication can be configured correctly and still cause connectivity issues if the application does not update its connection information.

Option B is incorrect because security groups are attached to instances and can be updated, but the issue is typically the IP address change. Option C is incorrect because EBS volumes are automatically attached during a managed failover; connectivity issues stem from network configuration, not storage.

Full explanation →

110

MCQmedium

A company is migrating its SAP ERP system to AWS. The SAP application requires low-latency access to the database and high network throughput between application and database tiers. Which AWS architecture should the company use?

A.Place the SAP application servers in a different AWS Region than the database.

B.Use Amazon S3 as the database storage layer.

C.Place the SAP application servers in one Availability Zone and the database in another Availability Zone.

D.Use a placement group with enhanced networking for both application and database instances.

AnswerD

Placement groups provide low latency and high throughput within a single AZ.

Why this answer

Using a placement group with enhanced networking for both application and database instances ensures low latency and high network throughput between tiers. Option A is incorrect because placing the SAP application servers in a different AWS Region than the database adds significant latency due to geographic distance. Option B is incorrect because Amazon S3 is an object storage service, not a suitable database storage layer for SAP ERP, which requires block storage with low latency.

Option C is incorrect because placing the application servers in one Availability Zone and the database in another Availability Zone introduces additional network latency compared to placing them in the same AZ with a placement group.

Full explanation →

111

MCQmedium

An SAP administrator wants to ensure that the SAP application server can communicate with the HANA database using the private IP address within the same VPC. What configuration is necessary?

A.Attach an Internet Gateway to the VPC.

B.Set up a NAT Gateway for the database subnet.

C.Establish a VPN connection to the on-premises network.

D.Configure a security group rule allowing traffic on the HANA database port from the application server's security group.

AnswerD

Security groups control traffic within VPC.

Why this answer

Within the same VPC, AWS resources can communicate using private IP addresses without internet or VPN connectivity. The key requirement is that the security group attached to the HANA database must allow inbound traffic on the HANA database port (typically 3<span+>15<span+>17 or 3<span+>00<span+>15 for HANA) from the security group associated with the SAP application server. This ensures that only traffic originating from the application server is permitted, maintaining security while enabling private IP communication.

Exam trap

The trap here is that candidates often confuse the need for external connectivity (internet or VPN) with internal VPC communication, mistakenly thinking that a NAT Gateway or Internet Gateway is required for any traffic between subnets, when in fact AWS VPCs natively route private IP traffic within the same VPC using the VPC router and security groups for access control.

How to eliminate wrong answers

Option A is wrong because an Internet Gateway is used to enable communication between a VPC and the internet, not for private IP communication within the same VPC; attaching an IGW would expose the resources unnecessarily and does not facilitate internal routing. Option B is wrong because a NAT Gateway is used to allow instances in a private subnet to initiate outbound traffic to the internet (e.g., for updates) while preventing inbound internet traffic; it is not required for internal VPC communication between application and database servers. Option C is wrong because a VPN connection is used to connect an on-premises network to the AWS VPC, not for communication between two AWS resources already within the same VPC; it adds unnecessary complexity and latency.

Full explanation →

112

MCQhard

An SAP system running on AWS is experiencing intermittent connectivity issues between the SAP application servers and the database server. Both are in the same VPC but different subnets. The security groups and network ACLs are correctly configured. The issue occurs only during peak hours. Which of the following is the most likely cause?

A.Security group outbound rules are blocking return traffic.

B.The VPC peering connection is throttling traffic.

C.Network ACLs do not have rules to allow ephemeral ports for return traffic.

D.Security group inbound rules are misconfigured.

AnswerC

NACLs are stateless; failing to allow ephemeral ports can cause intermittent connectivity during high traffic.

Why this answer

The intermittent connectivity issue during peak hours points to a resource exhaustion problem. Network ACLs are stateless, meaning they must explicitly allow both inbound and outbound traffic, including ephemeral ports (typically 1024-65535) used for return traffic. If the NACL outbound rules do not allow these ephemeral ports, return traffic from the database server to the application server will be dropped, especially under high load when many connections are established simultaneously.

Exam trap

The trap here is that candidates often confuse the stateless nature of network ACLs with the stateful behavior of security groups, assuming that allowing inbound traffic automatically permits return traffic, which is not the case for NACLs.

How to eliminate wrong answers

Option A is wrong because security group outbound rules are stateful; if outbound rules were blocking return traffic, the issue would be persistent, not intermittent, and security groups automatically allow return traffic for allowed inbound connections. Option B is wrong because the question states both servers are in the same VPC, so no VPC peering connection is involved; VPC peering throttling would only apply to cross-VPC traffic. Option D is wrong because security group inbound rules are stateful and correctly configured per the question; misconfigured inbound rules would cause a persistent failure, not an intermittent one during peak hours.

Full explanation →

113

MCQeasy

A company runs SAP S/4HANA on AWS with a single-instance deployment. The database is hosted on an r5.8xlarge instance with 5000 provisioned IOPS EBS volumes. Recently, the system experienced a performance degradation during peak hours. CloudWatch metrics show that the EBS volume read latency is consistently above 10 ms, and the queue length is frequently peaking at 20. The instance is in the same Availability Zone as the EBS volumes. What should the administrator do to resolve the performance issue?

A.Move the instance to a different Availability Zone to reduce network latency.

B.Increase the provisioned IOPS on the EBS volumes to 10000.

C.Move the database to an instance with instance store volumes for better performance.

D.Migrate the EBS volumes to gp3 volume type with baseline performance.

AnswerB

Higher IOPS reduces latency and queue depth, improving performance.

Why this answer

The CloudWatch metrics show high read latency (>10 ms) and a queue length peaking at 20, which indicates that the EBS volume is throttling due to insufficient IOPS for the workload. Increasing provisioned IOPS from 5000 to 10000 directly addresses the bottleneck by allowing more I/O operations per second, reducing queue depth and latency. Since the instance and volumes are in the same Availability Zone, network latency is not a factor, and instance store volumes are ephemeral and unsuitable for persistent SAP HANA data.

Exam trap

The trap here is that candidates may assume high latency is due to network distance (Option A) or that gp3 volumes always provide better performance (Option D), but the key metric is queue length, which directly points to IOPS exhaustion on the provisioned IOPS volume.

How to eliminate wrong answers

Option A is wrong because moving the instance to a different Availability Zone would increase network latency between the instance and the EBS volumes, worsening the performance issue, not resolving it. Option C is wrong because instance store volumes are ephemeral (data is lost on stop/termination) and do not provide the durability or snapshot capabilities required for SAP HANA database persistence; they are also not available on all instance types. Option D is wrong because gp3 volumes have a baseline of 3000 IOPS regardless of size, which is lower than the current 5000 IOPS, and while they can be provisioned with additional IOPS, the default baseline performance would degrade the workload further; the immediate fix is to increase IOPS on the existing io1/io2 volumes.

Full explanation →

114

MCQeasy

A company is planning to migrate its SAP HANA database to AWS. The database size is 3 TB, and they need high I/O performance with low latency. The SAP workload is critical and requires high availability. Which AWS storage solution should they choose for the HANA data volume?

A.Amazon EBS gp3 volumes.

B.EC2 Instance Store volumes.

C.Amazon EFS with Provisioned Throughput.

D.Amazon EBS io2 Block Express volumes.

AnswerD

io2 Block Express offers high performance, low latency, and high durability, making it ideal for SAP HANA.

Why this answer

AWS strongly recommends using Amazon EBS io2 Block Express volumes for SAP HANA data volumes due to their high performance, low latency, and high durability, which meet SAP's critical workload and high availability requirements. Option A (EBS gp3) is cost-effective but may not provide the consistent low latency required for SAP HANA. Option B (EC2 Instance Store) offers low latency but is ephemeral and does not provide data persistence, making it unsuitable for database data.

Option C (EFS with Provisioned Throughput) is a file system, not block storage, and is not supported for SAP HANA data volumes.

Full explanation →

115

Multi-Selectmedium

A company is migrating an SAP system to AWS and needs to ensure backup compliance. The SAP database is SAP HANA. Which TWO AWS services can be used to back up SAP HANA databases?

Select 2 answers

A.Backint agent for SAP HANA

B.Amazon S3 lifecycle policies

C.AWS Storage Gateway

D.AWS Database Migration Service (DMS)

E.AWS Backup

AnswersA, E

Backint is SAP-certified for HANA backups to S3.

Why this answer

AWS Backup (option E) provides a fully managed backup service that can automate and centrally manage backups of SAP HANA databases. The Backint agent for SAP HANA (option A) is an SAP-certified backup integration that allows HANA to directly stream backups to Amazon S3, and it integrates with AWS Backup for scheduling and retention. Option B (Amazon S3 lifecycle policies) is a storage management feature, not a backup service.

Option C (AWS Storage Gateway) enables hybrid cloud storage but does not provide native backup capabilities for SAP HANA. Option D (AWS Database Migration Service) is used for database migrations, not backups.

Full explanation →

116

MCQmedium

A company manages a multi-account AWS environment using AWS Organizations. The operations team needs to ensure that all accounts have CloudTrail enabled and that logs are delivered to a centralized S3 bucket. What is the MOST efficient way to enforce this configuration?

A.Configure CloudTrail in the management account with an S3 bucket policy that grants access to all member accounts.

B.Deploy an AWS CloudFormation StackSet with a template that enables CloudTrail and configures the S3 bucket in every account and region.

C.Create a custom script using AWS CLI to enable CloudTrail in each account and region.

D.Use AWS Service Catalog to publish a CloudTrail product and require each account to launch it.

AnswerB

StackSets provide centralized, consistent deployment and drift detection.

Why this answer

AWS CloudFormation StackSets allow you to deploy a CloudTrail configuration template across multiple accounts and regions in a single, automated operation. This approach ensures consistent enforcement of the policy without manual intervention, leveraging the centralized management capabilities of AWS Organizations.

Exam trap

The trap here is that candidates often assume a single CloudTrail configuration in the management account with a shared S3 bucket is sufficient, but CloudTrail must be enabled independently in each account to capture its own API activity.

How to eliminate wrong answers

Option A is wrong because configuring CloudTrail in the management account only enables it for that account, not for member accounts; the S3 bucket policy alone does not enable CloudTrail in other accounts. Option C is wrong because a custom CLI script is less efficient, error-prone, and does not provide automated drift detection or centralized rollback compared to StackSets. Option D is wrong because AWS Service Catalog requires each account to manually launch the product, which does not enforce the configuration automatically across all accounts.

Full explanation →

117

MCQhard

An SAP administrator runs the AWS CLI command shown in the exhibit. The SAP HANA instance is running on an r5.4xlarge in us-east-1a. The administrator wants to change the instance type to r5.8xlarge to improve performance. What must the administrator do first?

A.Create an AMI of the instance and launch a new instance with the larger type.

B.Detach the EBS volumes and attach them to a new instance.

C.Stop the instance from the AWS Management Console.

D.Modify the instance type in the instance settings while it is running.

AnswerC

Instance must be stopped to modify instance type.

Why this answer

To change the instance type of an EC2 instance, the instance must first be stopped. While stopped, you can modify the instance type via the AWS Management Console, CLI, or SDK. After the instance is stopped, the administrator can change the type from r5.4xlarge to r5.8xlarge and then start the instance again.

Exam trap

The trap here is that candidates may think the instance type can be changed while running (Option D) because some instance attributes can be modified on the fly, but the instance type specifically requires the instance to be stopped.

How to eliminate wrong answers

Option A is wrong because creating an AMI and launching a new instance is unnecessary and more disruptive; the instance type can be changed directly on a stopped instance without rebuilding from an AMI. Option B is wrong because detaching EBS volumes and attaching them to a new instance is overly complex and not required; the instance type change does not affect the attached EBS volumes. Option D is wrong because the instance type cannot be modified while the instance is running; the instance must be in the 'stopped' state to change the instance type.

Full explanation →

118

MCQhard

An SAP environment on AWS uses Amazon FSx for NetApp ONTAP for shared storage. The system is experiencing high write latency. The storage administrator suspects the volume is not optimized for SAP workloads. Which configuration change would most likely reduce write latency?

A.Enable data compression on the volume.

B.Enable tiering policy to allow all data to be served from the SSD tier.

C.Enable the capacity pool tiering to auto-tier cold data to Amazon S3.

D.Increase the size of the volume.

AnswerB

Moving data to SSD tier reduces latency compared to HDD.

Why this answer

Enabling the tiering policy to allow all data to be served from the SSD tier ensures that all volume data resides on the high-performance SSD storage pool of the FSx for ONTAP file system. This eliminates read/write latency caused by accessing data from the capacity pool (Amazon S3), which has higher latency. For SAP workloads that require consistent low-latency I/O, keeping all data on the SSD tier is critical to reduce write latency.

Exam trap

The trap here is that candidates may confuse tiering policies with performance optimization, thinking that moving cold data to S3 (Option C) improves performance, when in fact it increases latency for any data that is accessed after being tiered, and does not reduce write latency for active SAP workloads.

How to eliminate wrong answers

Option A is wrong because data compression reduces storage space but adds CPU overhead for compression/decompression, which can increase write latency rather than reduce it. Option C is wrong because enabling auto-tiering to move cold data to Amazon S3 would move some data to the capacity pool, increasing latency when that data is accessed, and does not address write latency for active SAP data. Option D is wrong because increasing the volume size does not inherently improve performance; it only provides more capacity, and write latency is determined by the underlying storage tier and configuration, not volume size.

Full explanation →

119

MCQeasy

An SAP system on AWS needs to send alerts when the CPU utilization of the application server exceeds 90% for more than 5 minutes. Which AWS service should be used to set up this monitoring?

A.AWS Config

B.Amazon Inspector

C.AWS CloudTrail

D.Amazon CloudWatch

AnswerD

CloudWatch monitors metrics and can trigger alarms.

Why this answer

Amazon CloudWatch is the correct service because it can monitor CPU utilization metrics for EC2 instances and trigger alarms based on thresholds. You can configure a CloudWatch alarm to evaluate the CPUUtilization metric over a 5-minute period and send notifications via Amazon SNS when the 90% threshold is breached.

Exam trap

The trap here is that candidates often confuse AWS CloudTrail (API logging) with CloudWatch (metrics and alarms), or think AWS Config can monitor performance metrics because it tracks configuration changes.

How to eliminate wrong answers

Option A is wrong because AWS Config is used for resource inventory, configuration history, and compliance auditing, not for real-time metric monitoring or alerting. Option B is wrong because Amazon Inspector is a vulnerability assessment service that scans for software vulnerabilities and unintended network exposure, not for tracking CPU utilization metrics. Option C is wrong because AWS CloudTrail records API activity and governance events, not performance metrics like CPU utilization.

Full explanation →

120

MCQhard

A customer runs SAP HANA on an AWS Multi-AZ deployment with a primary and secondary instance. They want to ensure automatic failover in case of instance failure. What is the recommended approach?

A.Implement SAP HANA System Replication in a multi-AZ configuration with automatic failover using AWS services.

B.Set up a Route 53 health check to redirect traffic to the secondary instance manually.

C.Use Amazon RDS for SAP HANA with Multi-AZ enabled.

D.Configure an Auto Scaling group with a lifecycle hook to launch a new HANA instance.

AnswerA

HANA System Replication with automatic failover is the recommended method.

Why this answer

SAP HANA System Replication (HSR) in a multi-AZ configuration, combined with AWS services like Amazon Route 53 health checks and custom scripts for automatic failover, provides the recommended approach for ensuring automatic failover upon instance failure. HSR replicates data synchronously or asynchronously between primary and secondary HANA instances, and when integrated with AWS, you can automate the failover process without manual intervention, meeting the requirement for high availability.

Exam trap

The trap here is that candidates may assume Amazon RDS supports SAP HANA because RDS offers Multi-AZ for other databases, but SAP HANA is not a supported RDS engine, and the correct approach involves native SAP HANA replication with AWS infrastructure automation.

How to eliminate wrong answers

Option B is wrong because Route 53 health checks can only redirect traffic based on endpoint health, but they do not perform the actual failover of the SAP HANA database; manual intervention is still required to promote the secondary instance, which contradicts the requirement for automatic failover. Option C is wrong because Amazon RDS does not support SAP HANA as a database engine; RDS supports engines like MySQL, PostgreSQL, Oracle, and SQL Server, but not SAP HANA, making this option technically invalid. Option D is wrong because Auto Scaling groups are designed to launch new EC2 instances based on scaling policies, but they do not handle the complex stateful failover of SAP HANA, such as promoting a secondary instance or ensuring data consistency, and lifecycle hooks cannot automate the HANA replication promotion process.

Full explanation →

121

MCQhard

A company is migrating an SAP ECC 6.0 system to SAP S/4HANA on AWS. They plan to use SAP DMO. Which AWS service can be used to accelerate the data transfer during the migration?

A.AWS Database Migration Service (AWS DMS)

B.AWS Snowball Edge

C.AWS DataSync

D.AWS Direct Connect

AnswerB

Snowball Edge can be integrated with SAP DMO for offline data transfer.

Why this answer

AWS Snowball Edge can be used with SAP DMO to transfer data offline, especially for large databases. AWS Direct Connect improves network speed but is not a service for acceleration. AWS DataSync is for file data.

AWS DMS is not used with DMO.

Full explanation →

122

MCQeasy

A company runs its SAP system on AWS and uses a Multi-AZ RDS for Oracle database for the SAP Central Services (SCS) instance. The SCS instance is currently on a single EC2 instance in one Availability Zone. The company wants to ensure high availability for the SCS service. What should they do?

A.Implement an SAP ASCS/ERS cluster using two EC2 instances and a shared file system.

B.Place the SCS instance on a larger EC2 instance and use EBS snapshots for recovery.

C.Use an Application Load Balancer to distribute traffic to multiple SCS instances.

D.Configure the SCS instance on the existing RDS for Oracle database.

AnswerA

This is the standard HA setup for SAP Central Services on AWS.

Why this answer

SAP Central Services (SCS) can be made highly available by implementing an SAP ASCS/ERS cluster using two EC2 instances and a shared file system (such as Amazon FSx for Windows or EBS Multi-Attach) with a floating IP. This provides automatic failover in case of instance or AZ failure. Option B is incorrect because placing the SCS on a larger EC2 instance with EBS snapshots does not provide high availability; it only offers data backup and recovery, not automatic failover.

Option C is incorrect because an Application Load Balancer is designed for HTTP/HTTPS traffic and cannot handle SAP-specific protocols used by SCS. Option D is incorrect because the RDS for Oracle database is used for the SAP database, not for the SCS instance; the SCS requires its own file system and cannot run on RDS.

Full explanation →

123

Multi-Selecthard

An organization has an SAP S/4HANA system running on AWS. The system uses a multi-node HANA scale-out configuration. The company wants to implement a disaster recovery solution with an RPO of less than 1 hour and an RTO of less than 2 hours. The DR site is in a different AWS Region. Which THREE components should be included in the DR plan?

Select 3 answers

A.Cross-region Amazon Machine Image (AMI) copies for the SAP application servers.

B.AWS Global Accelerator to route traffic to the closest Region.

C.Amazon Route 53 DNS failover routing policy to redirect traffic to the DR Region in case of failure.

D.SAP HANA System Replication from the primary to the DR region using asynchronous replication.

E.Daily EBS snapshots of all volumes copied to the DR Region.

AnswersA, C, D

Pre-copied AMIs allow quick instance launch in DR.

Why this answer

AMI copies can be automated to replicate SAP application server configurations across regions, enabling rapid recovery of stateless application servers within the RTO. Since SAP application servers are stateless and can be recreated from AMIs, cross-region AMI copies provide a fast and reliable method to restore the application tier in the DR region without relying on storage-level replication.

Exam trap

The trap here is that candidates often assume daily EBS snapshots are sufficient for DR, but they fail to meet the strict RPO of less than 1 hour because snapshots are not continuous replication, and the restore time from snapshots can easily exceed the 2-hour RTO for large SAP HANA volumes.

Full explanation →

124

Multi-Selectmedium

Which TWO actions should be taken to improve the high availability of a single-instance SAP HANA database running on EC2? (Choose two.)

Select 2 answers

A.Set up HANA System Replication to a second EC2 instance in a different Availability Zone.

B.Enable Multi-AZ on the RDS instance.

C.Move the HANA data files to Amazon FSx for Lustre.

D.Increase the instance size to a larger type.

E.Configure automated EBS snapshots for the HANA data volumes.

AnswersA, E

HANA System Replication provides automatic failover across AZs.

Why this answer

HANA System Replication provides a standby instance in a different Availability Zone for automatic failover, improving high availability. Option E is correct because automated EBS snapshots enable point-in-time recovery, reducing recovery time after a failure. Option B is incorrect because Multi-AZ RDS is a feature for RDS databases, not for EC2-hosted SAP HANA.

Option C is incorrect because moving HANA data files to FSx for Lustre does not inherently improve availability. Option D is incorrect because increasing instance size improves performance, not availability.

Full explanation →

125

MCQhard

An SAP Basis administrator notices that the SAP application server logs show repeated connection timeouts to the database. The database is running on an RDS for SAP HANA instance. The application server and database are in the same VPC but different subnets. The security groups allow inbound traffic from the application server's security group on port 3xx17. Network ACLs allow both inbound and outbound traffic on ephemeral ports. Despite this, connections fail intermittently. What is the most likely cause?

A.The RDS instance's DNS name resolves to a different IP address intermittently.

B.The network ACL is stateful and blocking return traffic.

C.The security group for the RDS instance does not allow inbound traffic on the HANA internal communication port (e.g., 3xx18).

D.The application server's subnet has a route table that points to a NAT gateway instead of the database subnet.

AnswerC

Correct. SAP HANA requires an additional internal communication port (e.g., 3xx18) to be allowed in the security group. Without it, connections may fail intermittently.

Why this answer

SAP HANA uses multiple ports for internal communication. While port 3xx17 (SQL) is allowed, the missing inbound rule for the HANA internal communication port (e.g., 3xx18) causes intermittent connection timeouts. Option A is incorrect because RDS DNS names are stable and do not change intermittently.

Option B is incorrect because network ACLs are stateless, but the problem states both inbound and outbound are allowed on ephemeral ports, so return traffic is not blocked. Option D is incorrect because route tables within a VPC use local routes for database traffic, and NAT gateways do not affect intra-VPC traffic.

Full explanation →

126

Multi-Selecthard

A company runs SAP Business Suite on AWS and wants to implement a disaster recovery solution using a pilot light approach. Which THREE components should be pre-provisioned in the DR region to reduce recovery time?

Select 3 answers

A.An Amazon RDS for SAP HANA instance

B.Running EC2 instances for all SAP components

C.Pre-allocated Elastic IP addresses

D.Custom AMIs for SAP application servers

E.Pre-provisioned EBS volumes with HANA data replicated via log shipping

AnswersC, D, E

Elastic IPs can be quickly associated to recovered instances.

Why this answer

Pre-allocated Elastic IP addresses (Option C) are correct because in a pilot light DR setup, you need to ensure that the Elastic IPs are reserved in the DR region ahead of time. This allows you to quickly remap them to the recovered EC2 instances during failover, avoiding the delay of requesting new IPs or dealing with IP address conflicts. By pre-provisioning the Elastic IPs, you reduce the time required to restore network connectivity and DNS mappings, which is critical for meeting RTO objectives.

Exam trap

The trap here is that candidates often confuse a pilot light approach with a warm standby or multi-site active-active setup, leading them to incorrectly select running EC2 instances (Option B) instead of understanding that pilot light keeps only the data layer ready and application servers are launched on demand.

Full explanation →

127

Multi-Selectmedium

Which THREE factors should be considered when planning a recovery point objective (RPO) and recovery time objective (RTO) for an SAP system on AWS?

Select 3 answers

A.Storage type (EBS vs. instance store)

B.AWS Region and Availability Zone

C.EC2 instance type and size

D.Number of SAP users

E.Backup frequency and retention period

AnswersA, C, E

EBS volumes can be restored faster, affecting RTO.

Why this answer

RPO is determined by backup frequency and replication lag; RTO is affected by instance size and storage type; cross-region replication can help but RTO depends on failover time.

Full explanation →

128

Multi-Selecteasy

A company is deploying SAP S/4HANA on AWS and needs to ensure high availability for the database layer. Which TWO actions should the company take?

Select 2 answers

A.Store HANA backups in Amazon S3 Standard-IA

B.Configure SAP HANA System Replication across two Availability Zones

C.Use Amazon EFS as the data volume for HANA

D.Provision Amazon EBS io2 Block Express volumes for HANA data

E.Enable EC2 Auto Scaling for the HANA instance

AnswersB, D

HANA System Replication provides synchronous replication for HA.

Why this answer

SAP HANA System Replication (HSR) across two Availability Zones provides synchronous or asynchronous data replication at the database level, ensuring automatic failover and high availability for the HANA database. This is a core requirement for SAP S/4HANA on AWS, as it protects against AZ-level failures and meets SAP's HA architecture guidelines.

Exam trap

The trap here is that candidates may confuse backup storage (S3) or file storage (EFS) with high availability mechanisms, or incorrectly assume that Auto Scaling can be applied to stateful database instances, when in fact HANA requires dedicated replication and block storage for HA.

Full explanation →

129

Multi-Selecthard

An SAP system running on AWS is experiencing high latency in the application layer. The system uses a load balancer to distribute traffic across multiple EC2 instances. Which THREE actions could help diagnose the latency issue? (Choose THREE.)

Select 3 answers

A.Monitor the EC2 instance CPU and memory utilization using Amazon CloudWatch metrics.

B.Check AWS Config rules for any non-compliant resources.

C.Use Amazon CloudWatch detailed monitoring to get 1-minute metrics for EC2 instances.

D.Enable and analyze the Application Load Balancer access logs to identify slow requests.

E.Review VPC Flow Logs to check for packet loss or throttling.

AnswersA, C, D

High CPU/memory can cause latency.

Why this answer

High application-layer latency in an SAP system on AWS can stem from insufficient CPU or memory resources on the EC2 instances. Amazon CloudWatch metrics for CPU utilization and memory utilization (via the CloudWatch agent) directly reveal whether the instances are resource-constrained, which is a common cause of slow request processing. Monitoring these metrics helps isolate whether the latency is due to compute bottlenecks rather than network or load balancer issues.

Exam trap

The trap here is that candidates may confuse VPC Flow Logs (which show network metadata) with tools that measure actual packet loss or throttling, but Flow Logs only record whether packets were accepted or rejected by security groups/NACLs, not performance metrics like latency or throughput.

Full explanation →

130

MCQmedium

A company runs an SAP HANA system on AWS. The system uses a three-node cluster with HANA System Replication (HSR) in a scale-out configuration. The cluster spans three Availability Zones. Which architecture ensures the highest availability for the SAP HANA database?

A.Use a cluster of nodes across three Availability Zones with HANA System Replication and automatic failover.

B.Configure HANA System Replication in active/active mode across all nodes.

C.Use Amazon RDS for SAP HANA with Multi-AZ deployment.

D.Deploy all nodes in a single Availability Zone with synchronous replication.

AnswerA

B is correct: multi-AZ with HSR provides high availability.

Why this answer

Deploying a three-node cluster across three Availability Zones with HANA System Replication and automatic failover maximizes availability by distributing the data across multiple AZs and ensuring automatic failover in case of an AZ failure. Option B is incorrect because HANA System Replication in active/active mode is not supported for scale-out configurations; typical HSR implementations use active/standby or multi-target replication. Option C is incorrect because Amazon RDS for SAP HANA does not exist; SAP HANA on AWS must be deployed on EC2 instances.

Option D is incorrect because deploying all nodes in a single Availability Zone introduces a single point of failure, reducing availability compared to a multi-AZ deployment.

Full explanation →

131

Matchingmedium

Match the AWS managed service to its SAP-related capability.

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

Concepts

Matches

Track SAP license usage and compliance

Patch management and automation for SAP instances

Monitoring SAP metrics and logs

Best practice checks for SAP on AWS

Why these pairings

Correct matches: Amazon EFS for shared file storage, Amazon FSx for Windows File Server for SMB storage, Amazon Route 53 for DNS, Amazon CloudWatch for monitoring. Common confusions include mistaking EFS for block storage and FSx for Lustre for SAP HANA.

Full explanation →

132

MCQmedium

A company runs SAP NetWeaver on AWS and notices that the application server is experiencing high CPU utilization during peak hours. They need to scale out the SAP application tier. What is the best approach?

A.Use AWS Global Accelerator to distribute traffic

B.Increase the instance size of the existing application server

C.Manually launch additional EC2 instances and configure them as application servers

D.Use an Auto Scaling group to automatically launch additional application servers and register them with the SAP application load balancer

AnswerD

Auto Scaling enables dynamic scaling and load distribution.

Why this answer

It provides an automated, elastic scaling solution for the SAP application tier. An Auto Scaling group can dynamically launch additional EC2 instances based on CPU utilization metrics and automatically register them with the SAP application load balancer, ensuring seamless distribution of incoming user traffic across multiple application servers without manual intervention.

Exam trap

The trap here is that candidates often confuse scaling up (increasing instance size) with scaling out (adding more instances), or they assume manual provisioning is acceptable, missing the requirement for automation and elasticity in a production SAP environment.

How to eliminate wrong answers

Option A is wrong because AWS Global Accelerator improves network performance and traffic distribution at the edge, but it does not scale out the SAP application tier; it only directs traffic to existing endpoints. Option B is wrong because scaling up (increasing instance size) addresses vertical scaling, not horizontal scaling (scale out), and may still hit resource limits during peak hours without adding more instances. Option C is wrong because manually launching EC2 instances and configuring them as application servers is error-prone, lacks automation, and does not provide elasticity or self-healing; it also requires manual registration with the load balancer, which is inefficient for dynamic scaling.

Full explanation →

133

Multi-Selectmedium

A company is migrating an SAP HANA system to AWS using SAP HANA System Replication (HSR). The migration must have a Recovery Point Objective (RPO) of less than 15 minutes and a Recovery Time Objective (RTO) of less than 2 hours. Which TWO actions should the company take to meet these objectives?

Select 2 answers

A.Deploy the target system in a different Availability Zone

B.Use Amazon EBS snapshots for data replication

C.Place the target system in a different AWS Region

D.Use a single Availability Zone for both source and target

E.Configure SAP HANA System Replication in synchronous mode

AnswersA, E

Multi-AZ deployment enables fast failover and meets RTO requirements.

Why this answer

To meet an RPO of less than 15 minutes and an RTO of less than 2 hours for an SAP HANA migration using HSR, the company should deploy the target system in a different Availability Zone (option A) and configure SAP HANA System Replication in synchronous mode (option E). Synchronous replication ensures that data is written to both source and target before the transaction is committed, providing near-zero RPO. In the event of a failure, the target can be promoted quickly, meeting the RTO of under 2 hours.

Option B (using EBS snapshots) would not achieve the required RPO as snapshots are periodic and not continuous. Option C (placing the target in a different region) would introduce higher latency and potential RPO/RTO challenges. Option D (single Availability Zone) does not provide redundancy and would increase risk.

Full explanation →

134

MCQmedium

A company runs SAP on AWS and needs to implement a disaster recovery (DR) strategy. The primary site is in us-east-1, and the DR site is in us-west-2. The database is SAP HANA. Which approach provides the lowest RPO?

A.SAP HANA system replication in asynchronous mode.

B.Database backups to S3 and cross-region replication of S3 bucket.

C.EBS snapshots replicated to the DR region using cross-region snapshot copy.

D.SAP HANA system replication in synchronous mode across regions.

AnswerD

Synchronous replication ensures data is committed at both sites, minimizing data loss.

Why this answer

SAP HANA system replication in synchronous mode across regions provides near-zero RPO (Recovery Point Objective) as data is replicated synchronously to the DR region, ensuring minimal data loss. Option A (asynchronous mode) may have higher RPO due to potential data loss in case of failover. Options B and C (backups to S3 with cross-region replication and EBS snapshots) have significantly higher RPO as they are point-in-time backups, not real-time replication.

Full explanation →

135

MCQmedium

An organization is migrating a large data lake (500 TB) from on-premises HDFS to Amazon S3. The migration must be completed within 3 weeks. The network bandwidth between on-premises and AWS is 1 Gbps. What is the MOST efficient migration approach?

A.Use AWS DataSync over the existing internet connection.

B.Order a dedicated AWS Direct Connect circuit at 10 Gbps and use AWS DataSync.

C.Use Amazon S3 Transfer Acceleration to speed up the transfer over the internet.

D.Use multiple AWS Snowball Edge devices to transfer the data in parallel.

AnswerD

Snowball Edge provides high-capacity offline storage and multiple devices can be used concurrently, meeting the deadline.

Why this answer

Given the 500 TB data volume and a 3-week deadline, the 1 Gbps network bandwidth yields a theoretical maximum transfer of only ~340 TB in 3 weeks (1 Gbps * 21 days * 86400 seconds / 8 bits per byte), which is insufficient. AWS Snowball Edge devices provide a petabyte-scale, offline data transfer solution that bypasses network constraints entirely, allowing parallel transfers to meet the timeline. This is the most efficient approach because it avoids network bottlenecks and leverages physical shipping for massive datasets.

Exam trap

The trap here is that candidates underestimate the time required for network-based transfers over limited bandwidth and overestimate the effectiveness of acceleration technologies like S3 Transfer Acceleration or Direct Connect, failing to recognize that physical shipping is the only viable option for hundreds of terabytes within a strict deadline.

How to eliminate wrong answers

Option A is wrong because AWS DataSync over a 1 Gbps internet connection would take approximately 46 days to transfer 500 TB (accounting for overhead and realistic throughput), far exceeding the 3-week deadline. Option B is wrong because even with a dedicated 10 Gbps Direct Connect circuit, the transfer would still take ~4.6 days under ideal conditions, but provisioning and configuring a 10 Gbps circuit typically takes weeks, making it impractical for the 3-week window. Option C is wrong because S3 Transfer Acceleration only optimizes network path routing and does not increase bandwidth; it cannot overcome the fundamental limitation of a 1 Gbps link, which would still require over 46 days for 500 TB.

Full explanation →

136

MCQmedium

A company runs SAP on AWS and has configured a cross-region DR strategy using Amazon EBS snapshots. The DR region is in us-west-2. After a region-wide outage, the administrator attempts to restore the snapshots but finds the latest snapshot is incomplete. What is the most likely cause?

A.The IAM role used for copying snapshots does not have permissions

B.The latest snapshot copy had not completed before the outage

C.The snapshots are encrypted with a KMS key that is not available in us-west-2

D.The snapshot ID used for recovery is not valid

AnswerB

Cross-region copy takes time; if outage occurs during copy, snapshot may be partial.

Why this answer

Cross-region snapshot copies are asynchronous and may fail if the source region becomes unavailable. Option A is wrong because IAM does not prevent copying. Option C is wrong because KMS keys can be used cross-region with proper configuration.

Option D is wrong because the snapshot ID would not become invalid.

Full explanation →

137

MCQhard

An SAP system uses a shared file system via Amazon FSx for Windows File Server. The system administrators report that file locks are not being released properly, causing application errors. What is the most likely cause and solution?

A.Increase the throughput capacity of the FSx file system.

B.Enable the file lock duration feature on the FSx file system to automatically release stale locks.

C.The file system is using NFSv3 protocol; switch to NFSv4.

D.The file system is using Amazon S3 as the backing store; migrate to EFS.

AnswerB

FSx for Windows supports file lock duration to release locks automatically.

Why this answer

Amazon FSx for Windows File Server supports a file lock duration feature that can be configured to automatically release stale file locks after a specified timeout. This directly addresses the issue of locks not being released properly, which is a common cause of application errors in SAP systems relying on shared file systems.

Exam trap

The trap here is that candidates may confuse performance tuning (throughput) or protocol changes (NFS vs SMB) with the actual lock management feature, overlooking the specific FSx for Windows File Server capability to automatically release stale locks.

How to eliminate wrong answers

Option A is wrong because increasing throughput capacity improves I/O performance but does not affect file lock management or release stale locks. Option C is wrong because FSx for Windows File Server uses the SMB protocol, not NFS; switching to NFSv4 would not apply to this managed service. Option D is wrong because FSx for Windows File Server does not use Amazon S3 as a backing store; it uses a Windows-based file server, and migrating to EFS would change the protocol and not resolve lock release issues.

Full explanation →

138

MCQhard

A company is migrating their SAP Business Suite on SAP HANA to AWS. They need to transfer the data securely and efficiently. The source environment is in a different country with limited network bandwidth. The total data size is 100 TB. What is the most efficient migration approach?

A.Establish an AWS Direct Connect connection and use AWS DMS for full load and replication

B.Use AWS Snowball Edge for the initial data load, then AWS DMS for ongoing replication

C.Use a VPN connection and AWS DMS for both full load and continuous replication

D.Use AWS DataSync over the internet to transfer data and then switch to DMS

AnswerB

AWS Snowball Edge allows offline transfer of large data volumes, bypassing bandwidth constraints. After the initial load, AWS DMS can handle ongoing replication. This is the most efficient approach.

Why this answer

For a 100 TB migration with limited network bandwidth, an offline transfer using AWS Snowball Edge is most efficient for the initial data load. After loading the data into AWS, AWS DMS can handle ongoing replication for any changes. This approach avoids the time and bandwidth constraints of network-based transfers.

Option A (Direct Connect + DMS) would still require significant network time for the full load. Option C (VPN + DMS) is also network-bound and slow. Option D (DataSync over internet) is not efficient for 100 TB.

Full explanation →

139

MCQmedium

An organization is migrating its SAP ECC system to AWS. The system currently uses a physical IBM Db2 database. The company wants to minimize licensing costs and management overhead after migration. The SAP system will be deployed on Amazon EC2. Which database option should the company choose?

A.Migrate to SAP ASE (Sybase) on EC2.

B.Continue using IBM Db2 on EC2 to avoid migration complexity.

C.Migrate to SAP HANA on EC2 to gain in-memory benefits.

D.Migrate to Oracle Database on Amazon RDS.

AnswerA

SAP ASE is supported and often lower cost.

Why this answer

SAP ASE (Sybase) is the recommended database for SAP workloads on AWS when minimizing licensing costs and management overhead is a priority. Unlike IBM Db2 or Oracle, SAP ASE has lower licensing fees and is fully supported by SAP for production use on EC2. It also avoids the complexity and higher cost of migrating to SAP HANA, which is unnecessary for an existing SAP ECC system that does not require in-memory capabilities.

Exam trap

The trap here is that candidates may assume SAP HANA is always the best choice for SAP workloads due to its in-memory performance benefits, but for existing ECC systems, the higher licensing cost and complexity outweigh the advantages, making SAP ASE the more practical option.

How to eliminate wrong answers

Option B is wrong because continuing with IBM Db2 on EC2 incurs high licensing costs and management overhead, contradicting the goal of minimizing both. Option C is wrong because migrating to SAP HANA on EC2 introduces significant licensing expense and operational complexity, and the in-memory benefits are not required for a standard SAP ECC system. Option D is wrong because Oracle Database on Amazon RDS is not a supported database platform for SAP workloads; SAP only supports specific databases like SAP ASE, IBM Db2, SAP HANA, and Oracle on EC2, not on RDS.

Full explanation →

140

Multi-Selecthard

A company is migrating its SAP system to AWS. The system uses a custom ABAP program that writes to a local file system. Which TWO AWS services can the company use to provide a shared file system accessible to multiple EC2 instances?

Select 2 answers

A.Amazon FSx for Lustre

B.Amazon RDS

C.Amazon S3

D.Amazon EFS

E.Amazon EBS

AnswersA, D

FSx for Lustre provides a POSIX-compliant file system for shared access.

Why this answer

Options A and D are correct. Amazon EFS provides a NFS file system that can be mounted on multiple EC2 instances. Amazon FSx for Lustre is a high-performance file system that can be shared across multiple instances.

Option B is wrong because Amazon RDS is a database service. Option C is wrong because Amazon S3 is object storage. Option E is wrong because Amazon EBS volumes can only be attached to one EC2 instance at a time.

Full explanation →

141

MCQmedium

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

A.Both instances are in the same Availability Zone, which defeats the purpose of high availability

B.The AMI ID is not specified correctly

C.The instance type m5.large is too small for SAP

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

AnswerA

HA requires instances in different AZs.

Why this answer

For high availability, ASCS and ERS should be in different Availability Zones to avoid a single point of failure. Option B is wrong because the instance type is acceptable for a test environment. Option C is wrong because the AMI is not specified, but that is not the main issue.

Option D is wrong because there is no security group defined, but that is a security issue, not an architectural HA issue.

Full explanation →

142

MCQmedium

A company runs SAP HANA on AWS and wants to back up the database using Backint integration. Which AWS service is required to store the backups?

A.Amazon S3 Glacier

B.Amazon EBS

C.Amazon EFS

D.Amazon S3

AnswerD

Backint for SAP HANA on AWS sends backups to an S3 bucket.

Why this answer

Backint for SAP HANA on AWS is an interface that allows SAP HANA to back up directly to Amazon S3. Amazon S3 is the supported storage service for Backint integration. Option A (Amazon S3 Glacier) is an archival storage class and not directly used by Backint for backups.

Option B (Amazon EBS) provides block storage volumes, but Backint does not interface with EBS for database backups. Option C (Amazon EFS) is a file storage service and is not compatible with the Backint API. Therefore, Option D (Amazon S3) is correct.

Full explanation →

143

Multi-Selecteasy

A company is planning to migrate its SAP NetWeaver system to AWS. Which TWO AWS services can be used to store the SAP transport directory?

Select 2 answers

A.Amazon S3

B.Amazon EFS

C.Amazon FSx for Windows File Server

D.Amazon RDS

E.Amazon EBS

AnswersB, C

EFS supports NFS, which is commonly used for SAP transport directories on Linux.

Why this answer

Options B and C are correct. Amazon EFS provides a scalable NFS file system suitable for the SAP transport directory, while Amazon FSx for Windows File Server offers SMB file shares if needed. Option A is incorrect because Amazon S3 is object storage, not a file system.

Option D is incorrect because Amazon RDS is a relational database service, not a shared file system. Option E is incorrect because Amazon EBS is block storage, which is not suitable for a shared transport directory across multiple instances.

Full explanation →

144

MCQmedium

Refer to the exhibit. An SAP administrator uses the CloudFormation template snippet to create an application server. After deployment, the administrator cannot connect to the instance using AWS Systems Manager Session Manager. What is the most likely missing configuration?

A.The UserData script fails to install the SSM Agent

B.The instance does not have an IAM instance profile with Systems Manager permissions

C.The security group does not allow outbound traffic to the Systems Manager endpoint

D.The instance type does not support Systems Manager

AnswerB

An IAM role with AmazonSSMManagedInstanceCore policy is required for Session Manager.

Why this answer

Session Manager requires the SSM Agent and an IAM role with proper permissions. The template installs the agent via UserData, but it does not attach an IAM instance profile. Without the profile, the instance cannot authenticate to Systems Manager.

The security group allows HTTPS inbound, but that is for web traffic, not SSM. The instance type is fine.

Full explanation →

145

MCQmedium

A company is migrating a critical SAP HANA database to AWS. They have a limited migration window and need to ensure data consistency. Which migration approach should they use?

A.Use AWS Backup to restore the latest backup of the HANA database to an EC2 instance.

B.Use SAP HANA System Replication to replicate data to a target HANA system on AWS.

C.Perform a heterogeneous migration using AWS SCT and AWS DMS.

D.Use AWS DMS with ongoing replication from the source HANA database to an Amazon RDS for HANA instance.

AnswerB

SAP HANA System Replication provides near-zero downtime and data consistency.

Why this answer

SAP HANA System Replication with HLI or EC2 allows near-zero downtime and data consistency. Heterogeneous migration with DMS and SCT is for different database engines. Backup and restore may have longer downtime.

SAP Landscape Transformation is for system consolidation, not direct HANA migration.

Full explanation →

146

MCQhard

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

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

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

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

D.Configure SAP HANA System Replication in asynchronous mode to the DR region.

AnswerD

Asynchronous replication allows cross-region replication with acceptable RPO.

Why this answer

SAP HANA System Replication with asynchronous mode can replicate across regions with RPO of seconds to minutes. Option A is wrong because AWS DMS does not support SAP HANA as a target database. Option B is wrong because synchronous mode over long distances introduces high latency and is not feasible for cross-region replication.

Option C is wrong because EBS snapshots alone cannot achieve a 15-minute RPO due to snapshot frequency limits and longer recovery time.

Full explanation →

147

MCQmedium

A company runs an SAP HANA database on an EC2 instance with a large EBS volume. The operations team receives alerts that the volume's burst balance has dropped to 10%. Which action should be taken to prevent performance degradation?

A.Change the volume type to io2 with provisioned IOPS.

B.Increase the volume size to increase the baseline IOPS.

C.Enable EBS optimization on the instance.

D.Convert the volume to gp3.

AnswerB

Increasing volume size raises baseline IOPS and improves burst balance replenishment.

Why this answer

Increasing the volume size increases the baseline IOPS and burst balance replenishment rate. Option A is wrong because io2 volumes do not have a burst bucket; they use provisioned IOPS instead and thus do not experience burst balance depletion. Option C is wrong because EBS optimization improves network throughput but does not affect burst balance.

Option D is wrong because converting to gp3 changes the volume type but does not directly address the burst balance issue; gp3 volumes have a baseline performance but may still have burst credits if the volume is small, so the correct action to replenish burst balance is to increase volume size.

Full explanation →

148

MCQeasy

A company runs SAP on AWS and needs to ensure that all changes to the SAP system's underlying infrastructure are recorded and auditable. Which AWS service should be enabled to meet this requirement?

A.Amazon CloudWatch Logs

B.AWS CloudTrail

C.AWS Config

D.AWS Trusted Advisor

AnswerB

CloudTrail records all AWS API calls for audit purposes.

Why this answer

AWS CloudTrail records API calls for auditing. CloudWatch Logs is for log monitoring. Config tracks resource configuration changes.

Trusted Advisor provides best-practice checks. CloudTrail is the primary service for API activity auditing.

Full explanation →

149

MCQeasy

A company is migrating a web application to AWS and wants to use a blue/green deployment strategy to minimize downtime. Which AWS service should be used to route traffic between the blue and green environments?

A.Amazon CloudFront

B.AWS Global Accelerator

C.Application Load Balancer (ALB)

D.Amazon Route 53

AnswerD

Route 53 supports weighted routing policy to shift traffic between blue and green environments.

Why this answer

Amazon Route 53 is correct because it supports weighted DNS routing, which allows you to shift traffic gradually between blue and green environments by adjusting the weight values for DNS records. This enables a blue/green deployment strategy with minimal downtime, as Route 53 can route a percentage of traffic to the new environment while keeping the old environment active for rollback.

Exam trap

The trap here is that candidates often confuse load balancers (ALB) with traffic routing services, assuming an ALB can directly manage blue/green environments, but ALB requires Route 53 or similar DNS-level routing to split traffic between separate environments.

How to eliminate wrong answers

Option A is wrong because Amazon CloudFront is a content delivery network (CDN) that caches content at edge locations; it does not provide the granular traffic shifting or weighted routing needed for blue/green deployments. Option B is wrong because AWS Global Accelerator improves performance by routing traffic over the AWS global network using anycast IPs, but it lacks the DNS-level weight-based traffic splitting required for blue/green deployments. Option C is wrong because an Application Load Balancer (ALB) distributes traffic to targets within a single environment; it cannot independently route traffic between two separate environments (blue and green) without additional infrastructure like multiple target groups and Route 53.

Full explanation →

150

MCQeasy

A company is planning to migrate an SAP ERP system to AWS. They want to use an existing software license with no additional cost. Which AWS service allows them to bring their own SAP license?

A.AWS Organizations

B.AWS License Manager

C.AWS Systems Manager

D.AWS Service Catalog

AnswerB

License Manager supports BYOL for SAP and other software.

Why this answer

AWS License Manager is the correct service for bring-your-own-license (BYOL) for SAP. Option A is wrong because AWS Organizations is for multi-account governance. Option C is wrong because AWS Systems Manager is for management, not licensing.

Option D is wrong because AWS Service Catalog is for provisioning approved services.

Full explanation →

Page 2 of 22

All pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22

Practice PAS-C01 by domain

Target a specific domain to shore up weak areas.

Design of SAP Workloads on AWS Technology Migration Operations and Maintenance

See all domains with question counts →