Knowledge + Practice

CCNA Design of SAP Workloads on AWS Questions

75 of 428 questions · Page 1/6 · Design of SAP Workloads on AWS · Answers revealed

Practice these questions Domain overview All questions

1

MCQeasy

A company wants to automate the installation of SAP software on AWS using AWS CloudFormation. Which service is most appropriate to execute the SAP installation scripts?

A.AWS CodeDeploy.

B.AWS Lambda functions triggered by CloudFormation.

C.AWS Systems Manager Run Command.

D.AWS OpsWorks for Chef Automate.

AnswerC

Run Command can execute scripts on instances with SSM Agent.

Why this answer

AWS Systems Manager Run Command is the most appropriate service because it can execute scripts (including SAP installation scripts) on EC2 instances without requiring SSH or RDP access, and it integrates with CloudFormation via custom resources or the AWS::SSM::Document resource. This allows you to run complex, long-running installation commands that are typical for SAP software, which Lambda functions cannot handle due to time limits.

Exam trap

The trap here is that candidates often choose AWS Lambda because it is a common 'automation' service, but they overlook Lambda's 15-minute execution timeout and its inability to handle long-running, stateful installations like SAP software.

How to eliminate wrong answers

Option A is wrong because AWS CodeDeploy is designed for deploying application code and managing rolling updates, not for executing standalone installation scripts like SAP installers. Option B is wrong because AWS Lambda functions have a maximum execution timeout of 15 minutes, which is insufficient for SAP installations that often take hours, and Lambda is not designed for interactive or long-running script execution. Option D is wrong because AWS OpsWorks for Chef Automate is a configuration management service that uses Chef cookbooks, which is overkill and not the simplest or most direct way to run a one-time SAP installation script; it adds unnecessary complexity and is not the recommended approach for this task.

Practice this question →

2

MCQeasy

An SAP HANA database administrator needs to restore a database from a backup stored in Amazon S3. The backup was taken using SAP HANA Backint. Which AWS service should be used to retrieve the backup files from S3?

A.SAP HANA Backint agent

B.Amazon S3 console

C.AWS CLI

D.AWS Backup

AnswerA

Backint handles restore directly.

Why this answer

SAP HANA Backint is the native SAP interface for integrating with third-party backup tools. When a backup is taken using Backint, the backup files are stored in Amazon S3 via the Backint agent for SAP HANA on AWS. To restore from these backups, the same Backint agent must be used because it understands the proprietary metadata and file format that Backint writes to S3, and it handles the direct S3 API calls required to retrieve the files.

Other methods like the S3 console or AWS CLI cannot interpret Backint-specific metadata or restore the database correctly.

Exam trap

The trap here is that candidates assume any AWS tool that can access S3 (like the console, CLI, or AWS Backup) can be used to restore the database, but they overlook that SAP HANA Backint requires its own agent to interpret the proprietary backup metadata and communicate with the HANA database engine.

How to eliminate wrong answers

Option B is wrong because the Amazon S3 console is a web-based interface for browsing and downloading objects, but it cannot interpret SAP HANA Backint metadata or perform a database restore; it would only provide raw files without the necessary database context. Option C is wrong because the AWS CLI can download objects from S3, but it lacks the Backint-specific logic to parse backup metadata and restore the SAP HANA database; it would require manual scripting and knowledge of the backup format. Option D is wrong because AWS Backup is a centralized backup service that supports various AWS resources, but it does not natively integrate with SAP HANA Backint backups stored in S3; it cannot restore a database from Backint-specific backup files.

Practice this question →

3

Multi-Selecteasy

Which TWO AWS services can be used to monitor the performance of SAP NetWeaver application servers? (Choose two.)

Select 2 answers

A.AWS CloudTrail

B.AWS Trusted Advisor

C.AWS Systems Manager

D.AWS X-Ray

E.Amazon CloudWatch

AnswersC, E

Systems Manager can collect OS-level metrics and run commands.

Why this answer

AWS Systems Manager is correct because it provides the Agent-based infrastructure management capabilities needed to monitor SAP NetWeaver application servers. Specifically, Systems Manager Inventory can collect OS-level metrics like CPU, memory, and disk usage from EC2 instances running SAP, and its Run Command or State Manager can execute custom scripts to gather SAP-specific performance data (e.g., from ST03 or ST06 transactions) without requiring direct SSH access.

Exam trap

The trap here is that candidates often confuse AWS CloudTrail (audit logging) with performance monitoring, or assume X-Ray can monitor any application, when in fact SAP NetWeaver requires OS-level and SAP-specific metrics that only Systems Manager and CloudWatch (via custom metrics or SAP Agent) can provide.

Practice this question →

4

MCQeasy

A company is migrating its SAP HANA database to AWS. Which instance type is specifically designed for SAP HANA and certified for production workloads?

A.c5.xlarge

B.r5.xlarge

C.x1e.xlarge

D.t3.xlarge

AnswerC

x1e instances are SAP HANA certified for production.

Why this answer

The x1e.xlarge instance is part of the AWS X1e family, which is specifically designed for memory-intensive workloads like SAP HANA and is certified by SAP for production deployments. SAP HANA requires large memory footprints and high memory-to-vCPU ratios, which the X1e instances provide with up to 3,904 GiB of memory and 128 vCPUs, meeting SAP's certification requirements.

Exam trap

The trap here is that candidates often assume any memory-optimized instance (like R5) is suitable for SAP HANA, but AWS requires specific instance families (X1, X1e, high-memory) that are officially SAP-certified for production workloads.

How to eliminate wrong answers

Option A (c5.xlarge) is wrong because it belongs to the compute-optimized C5 family, which lacks the high memory capacity and SAP HANA certification required for production workloads. Option B (r5.xlarge) is wrong because while R5 instances are memory-optimized, they are not specifically certified for SAP HANA production workloads; SAP HANA certification requires instances from the X1, X1e, or high-memory families. Option D (t3.xlarge) is wrong because T3 instances are burstable general-purpose instances with limited sustained performance and no SAP HANA certification, making them unsuitable for production database workloads.

Practice this question →

5

MCQmedium

An SAP HANA database on AWS is using EBS io2 volumes. The company wants to monitor the read and write latency of the database volumes. Which CloudWatch metrics should be used?

A.VolumeIdleTime and VolumeTotalReadTime.

B.VolumeReadLatency and VolumeWriteLatency.

C.VolumeThroughputPercentage and VolumeConsumedReadWriteOps.

D.VolumeQueueLength and VolumeThroughput.

AnswerB

These metrics directly measure latency per operation.

Why this answer

CloudWatch provides the `VolumeReadLatency` and `VolumeWriteLatency` metrics specifically to monitor the average time (in seconds) for read and write I/O operations on EBS volumes. For SAP HANA on io2 volumes, these metrics directly reflect storage performance and are critical for detecting latency issues that could impact database throughput and transaction response times.

Exam trap

The trap here is that candidates confuse throughput or queue-length metrics (like `VolumeQueueLength` or `VolumeThroughput`) with latency metrics, assuming high queue length directly equals high latency, but CloudWatch provides dedicated latency metrics that are the correct and direct measure for this monitoring requirement.

How to eliminate wrong answers

Option A is wrong because `VolumeIdleTime` measures the total number of seconds the volume is idle (no I/O), and `VolumeTotalReadTime` is the total time spent on read operations, but neither directly provides per-operation latency; they are used for calculating average latency indirectly, not as direct latency metrics. Option C is wrong because `VolumeThroughputPercentage` is not a standard CloudWatch metric (the correct metric is `VolumeThroughput`), and `VolumeConsumedReadWriteOps` tracks the number of I/O operations consumed against the provisioned IOPS, not latency. Option D is wrong because `VolumeQueueLength` measures the number of pending I/O requests (indicating backpressure), and `VolumeThroughput` measures data transfer rate (MB/s), neither of which directly measure read or write latency.

Practice this question →

6

MCQeasy

A company is designing a disaster recovery (DR) strategy for its SAP environment on AWS. The primary site is in us-east-1 and the DR site in us-west-2. The SAP HANA database is 3 TB and uses HANA System Replication (HSR) in async mode. The RPO requirement is 15 minutes. What is the most cost-effective way to meet the RPO?

A.Take full database backups to Amazon S3 every 15 minutes.

B.Use EBS snapshots every 5 minutes to replicate data to DR region.

C.Use HANA System Replication in synchronous mode to ensure zero data loss.

D.Configure HANA System Replication in asynchronous mode over AWS Direct Connect.

AnswerD

Async HSR over Direct Connect provides low latency replication meeting the RPO.

Why this answer

HANA System Replication (HSR) in asynchronous mode over AWS Direct Connect provides a low-latency, reliable network path that can achieve an RPO of 15 minutes without the performance penalty of synchronous replication. Asynchronous replication sends committed transactions to the DR site without waiting for acknowledgment, which is suitable for the 3 TB HANA database and meets the RPO requirement cost-effectively by avoiding the need for expensive, high-bandwidth dedicated connections or frequent full backups.

Exam trap

The trap here is that candidates often confuse synchronous replication with zero data loss, but for cross-region DR, synchronous mode introduces unacceptable latency, making asynchronous mode the only practical choice to meet the RPO without degrading production performance.

How to eliminate wrong answers

Option A is wrong because taking full database backups to Amazon S3 every 15 minutes would incur extremely high storage costs and network bandwidth usage for a 3 TB database, and the backup process itself would likely exceed the 15-minute RPO window due to the time required to complete a full backup. Option B is wrong because EBS snapshots every 5 minutes would create massive storage overhead and cost, and EBS snapshots are crash-consistent, not application-consistent for HANA, risking data corruption or loss; additionally, replicating snapshots across regions adds latency and cost. Option C is wrong because HANA System Replication in synchronous mode requires the primary to wait for acknowledgment from the DR site before committing a transaction, which introduces significant latency over the inter-region distance (us-east-1 to us-west-2) and would severely impact production performance, making it impractical for a 3 TB database.

Practice this question →

7

MCQhard

An SAP Basis administrator is configuring a high availability setup for SAP HANA on AWS using HANA System Replication (HSR) with automatic failover. The architecture includes a primary HANA node in us-east-1a and a secondary in us-east-1b. The administrator uses a Network Load Balancer (NLB) with a floating IP for the HANA virtual IP address. After a failover test, the secondary node becomes primary, but client applications cannot connect to the database. What is the most likely cause?

A.The security group for the NLB does not allow inbound traffic on port 3<0xEB><0x9C><0x9D><0xEB><0x9E><0x80>13.

B.The SAP HANA client is using a DNS name that does not resolve to the NLB endpoint.

C.The NLB target group is not configured to include the secondary node's IP address.

D.The secondary HANA node is in a different subnet and not routable from the NLB.

AnswerC

Without the secondary as a target, NLB cannot route to it after failover.

Why this answer

With NLB and floating IP, the target group must be configured with the secondary's IP address as a target. If the target group only contains the primary's IP, failover breaks. Option A (security group) would affect all connections, not just after failover.

Option B (DNS) is not used because the client would use the NLB endpoint directly; if the DNS name did not resolve to the NLB, connections would fail before failover. Option D (subnet) is possible but NLB can target cross-subnet. Option C is the most specific and common misconfiguration.

Practice this question →

8

MCQmedium

An SAP system on AWS uses a shared file system for /sapmnt and /usr/sap/trans mounted from an EC2 instance running NFS. The NFS server experiences a failure causing downtime for all SAP application servers. The company wants a highly available shared file system with automatic failover. The budget is limited, and the company prefers a fully managed solution. Which AWS service should the company use?

A.Amazon FSx for Windows File Server

B.Amazon EFS

C.Amazon EBS with a cluster file system

D.Amazon S3 with s3fs-fuse

AnswerB

EFS is a managed NFS file system that provides high availability across AZs.

Why this answer

Amazon EFS provides a fully managed, highly available, and durable NFS file system that supports automatic failover across multiple Availability Zones. It is the ideal choice for the SAP /sapmnt and /usr/sap/trans shared file system because it eliminates the single point of failure of a self-managed NFS server, requires no manual failover configuration, and offers a pay-as-you-go model that fits a limited budget.

Exam trap

A common trap in AWS SAP exams is that candidates might choose Amazon EBS with a cluster file system (Option C) thinking it provides high availability, but they overlook that it still requires manual orchestration and is not a fully managed service, unlike Amazon EFS.

How to eliminate wrong answers

Option A is wrong because Amazon FSx for Windows File Server uses the SMB protocol, not NFS, and SAP on Linux requires NFS-based shared file systems for /sapmnt and /usr/sap/trans. Option C is wrong because Amazon EBS with a cluster file system is not a fully managed solution; it requires manual configuration of a cluster (e.g., GlusterFS or Veritas) and still has a single point of failure if the EC2 instance hosting the cluster fails. Option D is wrong because Amazon S3 with s3fs-fuse is not a POSIX-compliant NFS file system; it introduces significant latency, lacks proper file locking, and is not supported by SAP for shared file system mounts.

Practice this question →

9

MCQmedium

A company is migrating an SAP HANA database to AWS. The system requires a high-performance storage solution with low latency for database files, and the storage must be scalable without downtime. Which AWS storage solution should the company use for the SAP HANA data volume?

A.Amazon S3

B.Amazon EBS st1

C.Amazon EBS io2 Block Express

D.Amazon EBS gp3

AnswerC

io2 Block Express provides up to 256000 IOPS and can be modified without downtime.

Why this answer

Amazon EBS io2 Block Express is the correct choice because it provides up to 256,000 IOPS per volume with sub-millisecond latency, meeting SAP HANA's strict performance requirements for data volumes. It also supports Elastic Volumes, allowing you to scale storage capacity and performance without downtime, which is critical for production SAP HANA systems.

Exam trap

The trap here is that candidates often choose gp3 for its lower cost and good baseline performance, overlooking that SAP HANA's certification requires io2 Block Express (or io1) for production data volumes due to the need for guaranteed high IOPS and sub-millisecond latency under sustained load.

How to eliminate wrong answers

Option A is wrong because Amazon S3 is an object storage service with higher latency and lower IOPS, unsuitable for the low-latency, high-throughput random I/O demands of SAP HANA database files. Option B is wrong because Amazon EBS st1 is a throughput-optimized HDD volume designed for sequential workloads like big data and log processing, not for the random read/write patterns and low latency required by SAP HANA. Option D is wrong because Amazon EBS gp3, while offering balanced performance, cannot match the maximum IOPS (256,000) and sub-millisecond latency of io2 Block Express, which is required for large SAP HANA deployments with high concurrency.

Practice this question →

10

MCQeasy

A company is planning to migrate their SAP system to AWS. They need to ensure that the SAP application servers and database servers are in the same AWS Region but in different Availability Zones for high availability. The network latency between Availability Zones must be minimal. Which AWS service should be used to connect the instances?

A.Set up VPC Peering between the Availability Zones

B.Establish an AWS Direct Connect connection

C.Use the default VPC network within the same VPC spanning multiple Availability Zones

D.Use AWS Transit Gateway to connect the subnets

AnswerC

Instances in the same VPC across AZs communicate over AWS's low-latency network.

Why this answer

A single VPC can span multiple Availability Zones within the same AWS Region, and by default, instances in different AZs within the same VPC communicate over the AWS private network with low latency, typically under 1-2 ms. This meets the requirement for minimal latency between SAP application and database servers while keeping them in the same Region for high availability.

Exam trap

The trap here is that candidates may overcomplicate the solution by choosing VPC Peering or Transit Gateway, not realizing that a single VPC inherently spans multiple AZs and provides the required low-latency connectivity without additional services.

How to eliminate wrong answers

Option A is wrong because VPC Peering connects separate VPCs, not subnets within the same VPC, and introduces unnecessary complexity and potential latency overhead compared to using a single VPC. Option B is wrong because AWS Direct Connect is a dedicated network connection from on-premises to AWS, not a service to connect instances within the same Region across Availability Zones. Option D is wrong because AWS Transit Gateway is used to interconnect multiple VPCs and on-premises networks, not to connect subnets within a single VPC, and would add unnecessary latency and cost.

Practice this question →

11

Multi-Selecthard

Which THREE of the following are valid considerations for designing SAP workloads on AWS to achieve high availability within a single AWS Region? (Choose three.)

Select 3 answers

A.Use AWS Network Load Balancer (NLB) for SAP Enqueue Replication 2 (ENSA2)

B.Use HANA scale-out with HSR across two nodes for high availability

C.Use a cluster with a shared file system (e.g., Amazon EFS or FSx) for SAP ASCS

D.Use Elastic Network Interface (ENI) failover for the SAP application server floating IP

E.Implement HANA System Replication (HSR) with automatic failover using a third instance as a quorum

AnswersC, D, E

ASCS can be made highly available with a clustered file system.

Why this answer

SAP ASCS (ABAP Central Services) requires a shared file system for the global transport directory and instance profiles to enable failover between cluster nodes. Amazon EFS or FSx for NetApp ONTAP provide the necessary NFS-based shared storage that supports the SAP enqueue replication and message server services during a failover event.

Exam trap

The PAS-C01 exam often tests the misconception that ENSA2 requires a load balancer for replication traffic, but in reality, ENSA2 uses direct peer-to-peer communication between ASCS and ERS instances without any intermediate load balancer.

Practice this question →

12

Multi-Selecthard

Which TWO configurations are mandatory for an SAP HANA system replication setup on AWS? (Choose TWO.)

Select 2 answers

A.An Application Load Balancer in front of the HANA instances

B.A virtual IP (VIP) address for the HANA system

C.A dedicated replication network between primary and secondary

D.Encryption of data in transit using SSL

E.A separate VPC for the secondary instance

AnswersB, C

VIP is used for failover.

Why this answer

SAP HANA system replication requires a virtual IP (VIP) address to enable automatic failover and client reconnection. The VIP is managed by a cluster manager (e.g., Pacemaker with AWS Route53 or Elastic IP) and moves between primary and secondary instances during a takeover, ensuring clients can always reach the active HANA instance without manual reconfiguration. Option C is also correct because a dedicated replication network between primary and secondary is mandatory to ensure reliable and low-latency replication traffic, separate from the client-facing network.

This dedicated network is required for optimal performance and to avoid contention with other traffic.

Exam trap

The trap here is that candidates often assume an ALB is needed for high availability, but SAP HANA uses a VIP-based active/passive model rather than load balancing, and they may overlook the dedicated replication network as optional when it is actually mandatory for reliable replication performance.

Practice this question →

13

MCQhard

A company runs SAP S/4HANA on AWS. The system is deployed in a cluster across two Availability Zones using Pacemaker for high availability. The primary SAP HANA node fails, and the failover to the secondary node is successful. However, after failover, the application servers cannot connect to the database because the database IP address changed. The application servers are configured to use the IP address of the primary node. The company needs a solution that allows the application servers to connect to the active database node without reconfiguration after failover. Which solution should the company implement?

A.Use Amazon Route 53 DNS with a health check to point to the active node's IP

B.Associate an Elastic IP address to the active node using a script during failover

C.Configure a CNAME record in Route 53 that points to the primary node's DNS name

D.Deploy an internal Network Load Balancer (NLB) with a static IP and target the HANA nodes

AnswerD

An internal NLB with a static IP provides a fixed endpoint. The NLB health checks and forwards traffic to the healthy HANA node, ensuring application servers can always connect to the active database without any configuration changes.

Why this answer

An internal Network Load Balancer (NLB) with a static IP provides a stable endpoint for application servers. The NLB forwards traffic to the active HANA node, so no reconfiguration is needed after failover. Option A is incorrect because using Route 53 DNS with health checks introduces DNS caching and TTL delays, causing application servers to use stale IPs after failover.

Option B is incorrect because associating an Elastic IP via script is not seamless and may require manual intervention or scripting, and Elastic IP reassignment can have delays. Option C is incorrect because a CNAME record still points to a DNS name with TTL delays and does not automatically update to the active node's IP; it also would require the primary node's DNS name to be updated.

Practice this question →

14

MCQmedium

A company is migrating its SAP ERP system to AWS. The system requires high availability across two Availability Zones. Which AWS service should be used to manage the virtual IP address for the SAP Central Services (ASCS/ERS) cluster?

A.Elastic IP address

B.Network Load Balancer

C.AWS Global Accelerator

D.Amazon Route 53

AnswerB

Correct. A Network Load Balancer provides a virtual IP (its DNS name or static IP) and can route traffic to the active ASCS/ERS node in a multi-AZ cluster based on health checks.

Why this answer

The correct approach for managing the virtual IP address for SAP Central Services (ASCS/ERS) across two Availability Zones is to use a Network Load Balancer (NLB). AWS does not support floating IPs across AZs, so an NLB is used to front the ASCS/ERS endpoints. The NLB uses health checks to route traffic to the active node, providing a single virtual IP (the NLB's DNS name or static IP) that clients can use.

This is the recommended AWS pattern for SAP high availability. Route 53 is used for DNS failover but does not serve as a virtual IP itself; it can complement the NLB by pointing a hostname to the NLB's DNS name, but the virtual IP is managed by the NLB.

Exam trap

The trap is that candidates may think Route 53 can manage the virtual IP directly, but Route 53 only provides DNS resolution and failover. AWS does not support floating IPs across AZs, so the standard solution is an NLB that provides a static endpoint (IP or DNS name) for the SAP cluster, with health checks to direct traffic to the active node.

How to eliminate wrong answers

Option A is wrong because Elastic IP addresses are static public IPv4 addresses that cannot be moved between instances across Availability Zones without manual intervention, and they do not support automatic failover required for SAP ASCS/ERS clustering. Option B is wrong because a Network Load Balancer operates at Layer 4 and distributes traffic to multiple targets, but it cannot serve as a virtual IP for the SAP cluster's active/passive model where only one node is active at a time; NLB is typically used for SAP application tier load balancing, not for the ASCS/ERS virtual IP. Option C is wrong because AWS Global Accelerator provides static IP addresses for global traffic routing and performance optimization, but it is designed for internet-facing applications and does not manage virtual IP failover within a single region's Availability Zones for SAP cluster services.

Practice this question →

15

MCQmedium

A company is designing an SAP S/4HANA deployment on AWS with high availability. They want to use a shared file system for the SAP transport directory. Which AWS service should they use for this shared file system?

A.Amazon EFS

B.Amazon FSx for Windows File Server

C.Amazon EBS with multi-attach enabled

D.Amazon S3

AnswerA

EFS provides a scalable NFS file system that can be shared across multiple AZs.

Why this answer

Amazon EFS is the correct choice because it provides a fully managed, POSIX-compliant, NFS-based shared file system that can be mounted concurrently by multiple EC2 instances across different Availability Zones, which is exactly what an SAP transport directory requires. The SAP transport directory (e.g., /usr/sap/trans) must be accessible from all SAP application servers in the high-availability cluster, and EFS supports the necessary file locking and consistency semantics for SAP's transport management system (TMS).

Exam trap

The trap here is that candidates often confuse Amazon EBS Multi-Attach (which is limited to a single AZ and a small number of instances) with a true multi-AZ shared file system, or they mistakenly think Amazon S3 can be used as a shared file system via a mount point (e.g., s3fs), which lacks the POSIX compliance and locking required for SAP transport directories.

How to eliminate wrong answers

Option B is wrong because Amazon FSx for Windows File Server uses the SMB protocol, which is not natively supported by SAP S/4HANA running on Linux (the typical deployment on AWS), and would require additional configuration or a Windows-based jump host. Option C is wrong because Amazon EBS with multi-attach is limited to a maximum of 16 Nitro-based EC2 instances in a single Availability Zone, which violates the multi-AZ high-availability requirement for SAP S/4HANA. Option D is wrong because Amazon S3 is an object storage service that does not provide a POSIX-compliant file system interface, cannot be mounted directly as a shared file system by EC2 instances, and lacks the file locking mechanisms required by SAP's transport directory.

Practice this question →

16

Multi-Selecteasy

A company is designing an SAP S/4HANA deployment on AWS. They want to ensure high availability for the central services (ASCS and ERS) across two Availability Zones. Which TWO of the following are required components for a typical SAP high availability setup on AWS? (Choose TWO.)

Select 2 answers

A.Amazon RDS Multi-AZ deployment for the SAP HANA database.

B.AWS Network Load Balancer to route traffic to the ASCS and ERS instances.

C.Amazon EFS file system mounted on both instances for shared /sapmnt.

D.AWS Transit Gateway to connect the two Availability Zones.

E.AWS Global Accelerator to provide static anycast IP addresses.

AnswersB, C

NLB is used for SAP HA to manage virtual IPs and health checks.

Why this answer

The AWS Network Load Balancer (NLB) is required to distribute traffic to the ASCS and ERS instances across two Availability Zones. It uses health checks to detect failures and reroute traffic to the healthy instance, ensuring that the SAP central services remain available even if one AZ fails. The NLB operates at Layer 4, preserving the source IP and supporting the necessary SAP protocols like the Message Server and Enqueue Replication.

Exam trap

The trap here is that candidates often confuse the need for a shared file system (like EFS) with a database replication mechanism, but the question specifically asks for components required for central services (ASCS/ERS) HA, not the database layer.

Practice this question →

17

MCQhard

A company is running SAP S/4HANA on AWS with a scale-out HANA configuration. The system is experiencing performance degradation during peak hours. Monitoring shows high network throughput on the HANA nodes. Which EC2 instance family is best suited to mitigate this?

A.x2iedn instances with high network bandwidth.

B.c5 instances with placement groups.

C.r5 instances with enhanced networking.

D.m5 instances with EBS optimization.

AnswerA

x2iedn is specifically designed for SAP HANA with high network performance.

Why this answer

The x2iedn instances are specifically designed for SAP HANA scale-out configurations, offering high memory per vCPU and dedicated high network bandwidth via the Elastic Network Adapter (ENA). In a scale-out HANA setup, nodes communicate intensively over the network for data synchronization and shared storage access, so high network throughput directly mitigates the performance degradation during peak hours.

Exam trap

The trap here is that candidates may assume any memory-optimized instance (like r5) is sufficient for SAP HANA, overlooking the specific network throughput and SAP certification requirements for scale-out configurations that only x2iedn instances meet.

How to eliminate wrong answers

Option B is wrong because c5 instances are compute-optimized and lack the large memory footprint required for SAP HANA, making them unsuitable for scale-out HANA workloads. Option C is wrong because r5 instances, while memory-optimized, do not provide the dedicated high network bandwidth and SAP certification for HANA scale-out that x2iedn instances offer. Option D is wrong because m5 instances are general-purpose and not optimized for the memory-intensive and high-throughput network demands of SAP HANA scale-out, and EBS optimization alone does not address inter-node network throughput.

Practice this question →

18

MCQhard

An SAP Basis team is designing a high-availability architecture for SAP NetWeaver on AWS. They plan to use a shared file system for the transport directory and SAP profiles across multiple availability zones. Which AWS storage service should they use?

A.Amazon EBS with multi-attach

B.Amazon FSx for Windows File Server

C.Amazon EFS

D.Amazon S3

AnswerC

EFS provides a shared NFS file system across AZs.

Why this answer

Amazon EFS (Elastic File System) is the correct choice because it provides a fully managed, NFS-based shared file system that is accessible from multiple EC2 instances across different Availability Zones. For SAP NetWeaver, the transport directory and SAP profiles must be concurrently accessible from all application servers in a high-availability setup, and EFS supports the required POSIX permissions and locking semantics needed by SAP.

Exam trap

The trap here is that candidates often confuse Amazon EBS Multi-Attach (option A) as a viable cross-AZ solution, but it is strictly single-AZ, making it incompatible with the multi-AZ high-availability requirement for SAP NetWeaver.

How to eliminate wrong answers

Option A is wrong because Amazon EBS with multi-attach is limited to a single Availability Zone and supports only up to 16 Nitro-based instances, making it unsuitable for cross-AZ SAP high-availability architectures. Option B is wrong because Amazon FSx for Windows File Server uses SMB protocol, which is not natively supported by SAP NetWeaver on Linux (the typical OS for SAP on AWS) and would require additional translation layers. Option D is wrong because Amazon S3 is an object storage service that does not provide a POSIX-compliant file system interface or support the file locking and concurrent access patterns required by SAP transport and profile directories.

Practice this question →

19

MCQhard

An SAP Basis administrator is troubleshooting a slow-performing SAP ERP system on AWS. The system uses Amazon EBS volumes with Provisioned IOPS (PIOPS) for database storage. Which metric in Amazon CloudWatch would best indicate whether the EBS volume is experiencing a performance bottleneck?

A.VolumeIdleTime

B.VolumeReadOps

C.VolumeQueueLength

D.VolumeThroughputPercentage

AnswerC

A high queue length indicates pending I/O requests, suggesting a bottleneck.

Why this answer

VolumeQueueLength measures the number of pending I/O requests waiting to be serviced by the EBS volume. A sustained high queue length (e.g., consistently above 1 per optimized IOPS) indicates that the volume is saturated and cannot keep up with the workload, which directly causes performance bottlenecks for SAP ERP database operations. This metric is the most direct indicator of a bottleneck because it reflects backpressure from the storage subsystem.

Exam trap

The trap here is that candidates confuse high I/O operations (VolumeReadOps) with a bottleneck, but a high read count alone does not indicate queuing or saturation—only VolumeQueueLength reveals whether the volume is struggling to keep up with the demand.

How to eliminate wrong answers

Option A is wrong because VolumeIdleTime measures the percentage of time the volume has no pending I/O operations; a low idle time indicates activity, not a bottleneck, and a high idle time would suggest the volume is underutilized. Option B is wrong because VolumeReadOps simply counts read operations per minute; a high value indicates heavy read activity but does not by itself indicate a bottleneck—the volume could be handling those reads efficiently. Option D is wrong because VolumeThroughputPercentage is not a standard CloudWatch metric for EBS; the correct throughput-related metric is VolumeThroughput (bytes per second), and even that does not directly indicate queuing or saturation.

Practice this question →

20

MCQhard

Refer to the exhibit. An SAP administrator runs the AWS CLI command and receives the output shown. The SAP application server (instance i-0abcd1234) is in 'running' state, but the SAP application is not reachable. The security group allows inbound traffic on port 3200. What is the MOST likely cause of the issue?

A.The network ACL for the subnet is blocking outbound traffic.

B.The instance is in a stopped state.

C.The security group inbound rule for port 3200 is not applied to the instance.

D.The operating system firewall on the instance is blocking port 3200.

AnswerD

OS firewall can block traffic even if security group allows it.

Why this answer

The instance is in 'running' state and the security group allows inbound traffic on port 3200, yet the SAP application is unreachable. This indicates a host-level firewall (e.g., iptables, firewalld, or Windows Firewall) on the SAP application server is blocking inbound connections to port 3200, which operates independently of AWS security groups and network ACLs.

Exam trap

The trap here is that candidates often assume security group rules are the sole determinant of traffic flow, forgetting that the OS firewall on the instance can independently block traffic even when AWS-level permissions are correctly configured.

How to eliminate wrong answers

Option A is wrong because network ACLs are stateless and affect traffic at the subnet level, but the security group already allows inbound traffic on port 3200, and the instance is running; outbound traffic blocking would not prevent inbound connections to the instance. Option B is wrong because the AWS CLI output explicitly shows the instance is in 'running' state, not 'stopped'. Option C is wrong because the question states the security group allows inbound traffic on port 3200, and the security group is associated with the instance; if it were not applied, the instance would still be reachable via other rules or default deny, but the issue is specific to port 3200 being blocked at the OS level.

Practice this question →

21

Multi-Selectmedium

Which THREE of the following are valid disaster recovery strategies for SAP on AWS? (Choose 3)

Select 3 answers

A.Maintain a cold standby environment in another Region

B.AWS RDS Multi-AZ deployment for SAP HANA

C.SAP backup to Amazon S3 with cross-region replication

D.Cross-region Amazon EBS snapshot copy and restore

E.SAP HANA System Replication across AWS Regions

AnswersC, D, E

Ensures backup availability in another region.

Why this answer

SAP backup to Amazon S3 with cross-region replication is a valid disaster recovery strategy. By backing up SAP data (e.g., database backups, log files) to S3 and enabling cross-region replication (CRR), you automatically replicate backups to a secondary AWS Region. This ensures that backup data is available in another Region for recovery in the event of a regional disaster, providing a durable and cost-effective DR solution without requiring a running standby system.

Exam trap

The trap here is that candidates may confuse high-availability (HA) solutions like Multi-AZ or HANA System Replication within a single Region with disaster recovery (DR) across Regions, or incorrectly assume that RDS supports SAP HANA, leading them to select Option B as a valid DR strategy.

Practice this question →

22

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.

Practice this question →

23

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.

Practice this question →

24

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.

Practice this question →

25

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.

Practice this question →

26

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.

Practice this question →

27

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.

Practice this question →

28

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.

Practice this question →

29

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.

Practice this question →

30

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.

Practice this question →

31

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.

Practice this question →

32

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.

Practice this question →

33

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.

Practice this question →

34

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.

Practice this question →

35

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.

Practice this question →

36

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.

Practice this question →

37

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.

Practice this question →

38

MCQeasy

A company is deploying an SAP BusinessObjects (BO) platform on AWS. To ensure high availability of the BO servers, which AWS service should be used to distribute incoming traffic across multiple BO instances in different Availability Zones?

A.NAT Gateway

B.Application Load Balancer

C.Amazon Route 53

D.Classic Load Balancer

AnswerB

ALB distributes incoming HTTP/HTTPS traffic across multiple instances.

Why this answer

The Application Load Balancer (ALB) operates at Layer 7 and can distribute HTTP/HTTPS traffic across multiple SAP BusinessObjects instances in different Availability Zones, providing high availability and health-check-based routing. ALB supports path-based routing and SSL termination, which are essential for modern web applications like SAP BO. It is the correct choice because it is designed for HTTP/HTTPS traffic and can balance load across instances in multiple AZs.

Exam trap

The trap here is that candidates often confuse DNS-based routing (Route 53) with load balancing, but Route 53 does not provide real-time health-check-based traffic distribution across instances in the same way an ALB does.

How to eliminate wrong answers

Option A is wrong because a NAT Gateway is used to enable outbound internet access for instances in private subnets, not to distribute incoming traffic across multiple instances. Option C is wrong because Amazon Route 53 is a DNS service that can route traffic to endpoints but does not perform load balancing at the application layer; it lacks health-check-based traffic distribution across multiple instances in real time. Option D is wrong because the Classic Load Balancer operates at Layer 4 and does not support advanced Layer 7 features like path-based routing or host-based routing, which are often required for SAP BusinessObjects deployments.

Practice this question →

39

MCQeasy

A company is running SAP NetWeaver on AWS. The SAP application server instances need to be distributed within a single Availability Zone for low-latency connectivity. Which AWS feature should be used to ensure low-latency connectivity between these instances?

A.Network ACL

B.Placement Group (cluster)

C.Internet Gateway

D.VPC Peering

AnswerB

Placement Group (cluster) places instances in a single Availability Zone for low latency; it does not support distribution across multiple AZs.

Why this answer

A cluster placement group places instances into a low-latency, high-bandwidth network within a single Availability Zone. This is ideal for SAP application servers that require these characteristics. For multi-AZ high availability, a separate placement group per AZ or spread placement groups may be considered, but for the requirement stated in this question, the cluster placement group (Option B) is correct.

Exam trap

The trap is selecting other network features such as VPC Peering or Internet Gateway, which do not directly improve latency between instances. The correct choice for low-latency within an AZ is a cluster placement group.

How to eliminate wrong answers

Option A is wrong because Network ACLs are stateless firewalls that control inbound and outbound traffic at the subnet level, not a mechanism to reduce latency or influence instance placement. Option C is wrong because an Internet Gateway provides internet access to VPC instances, not low-latency connectivity between instances within the same VPC. Option D is wrong because VPC Peering connects separate VPCs for routing traffic, but it does not optimize latency between instances within the same VPC or across Availability Zones.

Practice this question →

40

MCQhard

An SAP administrator runs the AWS CLI command shown in the exhibit for an EC2 instance used as an SAP HANA database server. The server has two EBS volumes attached: a root volume (/dev/xvda) and a data volume (/dev/sdf). Based on the output, what will happen when the instance is terminated?

A.The instance cannot be terminated because DeleteOnTermination is set inconsistently.

B.Both volumes will be deleted.

C.The root volume will be deleted, and the data volume will persist.

D.Both volumes will persist.

AnswerC

The root volume is deleted, the data volume persists.

Why this answer

The AWS CLI command `describe-instances` output shows that the root volume (`/dev/xvda`) has `DeleteOnTermination` set to `true` (default), while the data volume (`/dev/sdf`) has `DeleteOnTermination` set to `false`. When the EC2 instance is terminated, only volumes with `DeleteOnTermination=true` are automatically deleted. Therefore, the root volume will be deleted, and the data volume will persist as an unattached EBS volume in the same Availability Zone.

Exam trap

The trap here is that candidates assume all volumes attached to an instance share the same termination behavior, but AWS allows independent `DeleteOnTermination` settings per volume, and the default for non-root volumes is `true` only if launched via certain AMIs or block device mappings.

How to eliminate wrong answers

Option A is wrong because `DeleteOnTermination` can be set independently per volume; there is no requirement for consistency across volumes, and the instance can be terminated regardless. Option B is wrong because the data volume has `DeleteOnTermination=false`, so it will not be deleted upon termination. Option D is wrong because the root volume has `DeleteOnTermination=true`, so it will be deleted, not persist.

Practice this question →

41

MCQeasy

During a SAP migration to AWS, the team needs to ensure that the SAP license is compliant. Which of the following is a requirement for running SAP production systems on AWS?

A.The EC2 instance must be SAP-certified and the number of SAPS must be licensed.

B.The company must use AWS Enterprise Support.

C.The company must notify SAP of the migration to AWS.

D.The company must use a specific AWS region.

AnswerA

SAP certification and proper licensing are mandatory.

Why this answer

AWS requires that for running SAP production systems, the EC2 instance must be SAP-certified (listed in the SAP Certified and Supported Hardware Directory) and the customer must have licensed the appropriate number of SAP Application Performance Standard (SAPS) units for the instance type. This ensures the infrastructure meets SAP's performance and support requirements, and that the license covers the compute capacity used.

Exam trap

The trap here is that candidates may confuse operational best practices (like using Enterprise Support or notifying SAP) with mandatory licensing requirements, or assume that AWS region choice affects SAP licensing compliance.

How to eliminate wrong answers

Option B is wrong because AWS Enterprise Support is not a requirement for running SAP production systems on AWS; it is an optional support plan, and customers can run SAP workloads with Basic or Developer support as long as they meet licensing and certification requirements. Option C is wrong because there is no requirement to notify SAP of a migration to AWS; SAP licensing is based on the customer's existing agreements and the SAPS capacity of the instance, not on migration notification. Option D is wrong because SAP production systems can run in any AWS region that supports the required EC2 instance types and services; there is no region-specific mandate for SAP licensing compliance.

Practice this question →

42

Multi-Selecthard

A company runs SAP HANA on AWS. The system is experiencing high CPU utilization during peak hours. Which TWO actions should the administrator take to address this? (Choose two.)

Select 2 answers

A.Disable HANA columnar compression to reduce CPU overhead.

B.Increase the size of the /hana/data EBS volumes.

C.Reduce the network throughput of the EC2 instance.

D.Right-size the EC2 instance to a larger type with more vCPUs.

E.Configure HANA workload management to limit resource-intensive queries.

AnswersD, E

Provides more CPU capacity.

Why this answer

Right-sizing the EC2 instance to a larger type with more vCPUs directly addresses high CPU utilization by providing additional compute capacity for peak workloads. SAP HANA is CPU-intensive, especially during query processing and data compression, so increasing vCPUs alleviates the bottleneck without requiring architectural changes.

Exam trap

The trap here is that candidates may confuse storage scaling (Option B) with compute scaling, or incorrectly believe disabling compression reduces CPU load, when in fact compression reduces CPU overhead by minimizing data movement.

Practice this question →

43

MCQhard

A company runs SAP S/4HANA on AWS with a production system in us-east-1 and a disaster recovery (DR) system in us-west-2. The DR system is a standby HANA system using HANA System Replication (HSR) with asynchronous replication. The primary system has a memory of 2 TB and uses x1e.16xlarge instances. The DR system uses identical instance types. Recently, the network latency between the primary and DR sites increased from 50 ms to 150 ms due to a change in the network path. The SAP Basis team notices that the replication lag has increased significantly, and the DR system is now behind by several minutes. The RPO requirement is 30 seconds. The team must resolve the issue without changing the DR site location or the bandwidth. Which action should the team take to meet the RPO?

A.Configure HSR to use delta_datashipping instead of log shipping.

B.Increase the AWS Direct Connect bandwidth between the two regions.

C.Use Amazon S3 cross-region replication for the HANA log backups.

D.Change HSR to synchronous replication mode.

AnswerA

Delta_datashipping reduces data transfer and can meet RPO under higher latency.

Why this answer

HANA System Replication (HSR) can be configured to use delta_datashipping, which sends only the changed data blocks rather than full redo logs. This reduces the amount of data transferred per replication cycle, making it more resilient to increased network latency. With 150 ms latency, log shipping may fail to meet the 30-second RPO, but delta_datashipping can keep the DR system within the required lag by minimizing per-message payload size.

Exam trap

The trap here is that candidates often assume synchronous replication is the only way to reduce RPO, but they overlook that synchronous mode introduces performance penalties on the primary, and the question's constraint of not changing bandwidth or location forces a protocol-level tuning solution like delta_datashipping.

How to eliminate wrong answers

Option B is wrong because the question explicitly states that bandwidth cannot be changed, and increasing Direct Connect bandwidth would not address the root cause of high latency (150 ms) which is a propagation delay issue, not a throughput issue. Option C is wrong because Amazon S3 cross-region replication for HANA log backups is an asynchronous backup mechanism, not a real-time replication method, and it cannot meet a 30-second RPO due to S3 eventual consistency and replication delays. Option D is wrong because switching to synchronous replication would require the primary to wait for acknowledgment from the DR system before committing transactions, which with 150 ms latency would severely degrade production performance and potentially cause application timeouts.

Practice this question →

44

MCQmedium

A company runs SAP ERP on AWS with a Microsoft SQL Server database. The system is experiencing slow batch job processing. The database server is an r5.8xlarge instance with EBS gp2 volumes. Monitoring shows high disk queue length on the data and log volumes. What change will most likely improve batch job performance?

A.Migrate the SQL Server database to Amazon RDS for SQL Server.

B.Move the tempdb files to a dedicated EBS io2 volume with high IOPS.

C.Store the tempdb on an instance store volume.

D.Upgrade the EC2 instance to r5.12xlarge.

AnswerB

Dedicated tempdb volume reduces contention and improves I/O.

Why this answer

Moving tempdb to a separate, high-performance EBS io2 volume reduces contention on the data and log volumes. Option B directly addresses the bottleneck. Option D (instance size upgrade) may help but is costly and less direct.

Option A (RDS migration) is a major re-architecture, not a simple fix. Option C (instance store) is non-persistent and not suitable for tempdb in production.

Practice this question →

45

Multi-Selecteasy

A company is planning to migrate its SAP ERP system to AWS. The system currently uses an Oracle database. The company wants to switch to a supported database on AWS. Which THREE database options are supported by SAP on AWS?

Select 3 answers

A.SAP Adaptive Server Enterprise (ASE)

B.SAP MaxDB

C.IBM Db2 for SAP

D.Amazon Aurora PostgreSQL

E.SAP HANA

AnswersA, C, E

SAP ASE is a supported database for SAP systems.

Why this answer

SAP Adaptive Server Enterprise (ASE) is a certified database platform for SAP applications on AWS. SAP officially supports ASE as a database option for SAP ERP and other SAP Business Suite systems, provided the correct SAP ASE version and patch levels are used. This makes it a valid choice for migrating from Oracle to a supported SAP database on AWS.

Exam trap

The PAS-C01 exam often tests the misconception that any AWS-managed database (like Amazon Aurora PostgreSQL) is automatically supported for SAP workloads, but SAP strictly limits database support to its own and certified third-party databases listed in the SAP PAM.

Practice this question →

46

MCQmedium

A company runs SAP on AWS with an SAP HANA database on an r5.8xlarge instance. The company notices high network latency between the SAP application servers and the HANA database. The application servers are in the same VPC but different subnets. Which design change would MOST effectively reduce latency?

A.Launch the application servers and the HANA database in the same placement group.

B.Create a VPC peering connection between the subnets of the application servers and the database.

C.Change the HANA database instance type to a compute-optimized instance such as c5.9xlarge.

D.Enable Enhanced Networking on the application servers by attaching an Elastic Network Adapter (ENA).

AnswerA

Placement groups provide low-latency, high-bandwidth connectivity between instances.

Why this answer

Placing both the SAP application servers and the HANA database in the same cluster placement group ensures they are in close physical proximity within a single Availability Zone, minimizing network hops and reducing latency. Placement groups achieve this by co-locating instances on the same high-bandwidth, low-latency network fabric, which is critical for SAP HANA's real-time data processing requirements.

Exam trap

The trap here is that candidates confuse Enhanced Networking (which improves throughput and CPU efficiency) with reducing latency, when in fact latency is dominated by physical distance and network hops, which only placement groups can address.

How to eliminate wrong answers

Option B is wrong because VPC peering connects VPCs, not subnets within the same VPC; the application servers and database are already in the same VPC, so peering adds unnecessary complexity and does not reduce latency. Option C is wrong because changing to a compute-optimized instance (c5.9xlarge) does not address network latency; it may even reduce memory bandwidth, which is critical for HANA, and does not affect network path length. Option D is wrong because Enhanced Networking (ENA) improves throughput and reduces CPU overhead for packet processing, but it does not reduce physical distance or network hops between instances in different subnets; latency is primarily a function of proximity, not interface optimization.

Practice this question →

47

Multi-Selectmedium

Which TWO configurations are required for a high-availability SAP HANA deployment on AWS using Pacemaker? (Choose two.)

Select 2 answers

A.Placement groups in separate Availability Zones for the cluster nodes.

B.STONITH fencing configured for the cluster nodes.

C.EBS volumes with multi-attach enabled for shared storage.

D.An AWS Classic Load Balancer to route traffic to the active node.

E.SAP HANA system replication between primary and secondary instances.

AnswersB, E

STONITH ensures node isolation during failover.

Why this answer

STONITH (Shoot The Other Node In The Head) fencing is required in a Pacemaker cluster to ensure that a failed or unresponsive node is forcefully isolated before resources are failed over. Without STONITH, a split-brain scenario can occur where both nodes attempt to act as the primary, leading to data corruption. On AWS, STONITH is typically implemented using the AWS fence agent (fence_aws) which uses API calls to stop or reboot the instance.

Exam trap

The trap here is that candidates often confuse high-availability prerequisites with optional components, and may think that a load balancer or shared storage is mandatory, when in fact Pacemaker with STONITH and SAP HANA system replication are the two core requirements for a fully automated failover solution on AWS.

Practice this question →

48

MCQhard

An SAP HANA database on AWS is running on an EC2 instance with multiple EBS volumes striped using LVM. The database administrator needs to increase the total storage capacity without downtime. Which approach should be taken? (Select TWO.)

A.Create a new larger instance and attach the existing volumes.

B.Modify the existing volumes to a higher IOPS volume type.

C.Add the new volumes to the LVM volume group and extend the logical volume.

D.Create new EBS volumes and attach them to the instance.

E.Take a snapshot of the existing volumes and restore to larger volumes.

AnswerC, D

Online LVM extension adds capacity without downtime.

Why this answer

LVM (Logical Volume Manager) allows you to add new EBS volumes to an existing volume group and extend the logical volume without unmounting the filesystem or stopping the database. This enables online storage expansion for SAP HANA, which requires zero downtime for production workloads.

Exam trap

The trap here is that candidates may confuse increasing storage capacity with changing volume type or instance size, or assume snapshot-based migration is the only way to expand, overlooking LVM's online extension capability.

How to eliminate wrong answers

Option A is wrong because creating a new larger instance and attaching existing volumes would require stopping the original instance and migrating, causing downtime; it also does not increase storage capacity. Option B is wrong because modifying existing volumes to a higher IOPS volume type changes performance characteristics, not storage capacity, and does not address the need for more total storage. Option E is wrong because taking snapshots and restoring to larger volumes is an offline process that requires downtime for the database, and it is not a live expansion method.

Practice this question →

49

Multi-Selectmedium

Which THREE of the following are best practices for securing SAP systems on AWS?

Select 3 answers

A.Enable AWS CloudTrail to log all API calls

B.Enable encryption at rest using AWS KMS for SAP HANA data volumes

C.Use security groups to restrict network access to SAP application servers

D.Use IAM users to authenticate SAP system users

E.Store SAP system credentials in application source code

AnswersA, B, C

CloudTrail provides audit trail for AWS API calls.

Why this answer

AWS CloudTrail logs all API calls made to the AWS environment, including those that modify SAP infrastructure resources such as EC2 instances, security groups, and KMS keys. Enabling CloudTrail is a security best practice because it provides an immutable audit trail for governance, compliance, and operational troubleshooting of SAP workloads on AWS.

Exam trap

The trap here is that candidates may confuse IAM users with SAP system users, thinking that IAM can directly authenticate SAP logins, when in fact IAM is only for AWS API access and cannot authenticate SAP application-level users.

Practice this question →

50

Multi-Selectmedium

Which THREE factors should be considered when sizing an EC2 instance for SAP HANA? (Choose THREE.)

Select 3 answers

A.Total memory available on the instance

B.GPU acceleration for HANA calculations

C.SAP HANA certification of the instance type

D.vCPU and network throughput requirements

E.Instance store availability for HANA data

AnswersA, C, D

SAP HANA requires enough memory to hold data.

Why this answer

SAP HANA is an in-memory database, meaning all data must reside in RAM for processing. The total memory available on the EC2 instance directly determines the maximum size of the HANA database that can be supported, as the database must fit entirely within the instance's memory. AWS provides specific EC2 instance types (e.g., x1e.32xlarge, u-6tb1.112xlarge) with large memory capacities to meet HANA's requirements.

Exam trap

The trap here is that candidates may confuse instance store volumes with persistent storage for HANA data, but HANA requires durable, non-ephemeral storage (EBS or dedicated) and does not use instance stores for database persistence.

Practice this question →

51

MCQhard

A company has a large SAP HANA database running on an r5.8xlarge instance. They are planning to migrate to a new instance type that supports more memory for future growth. Which migration approach minimizes downtime and requires no data reload?

A.Use AWS Database Migration Service (DMS) to replicate data to the new instance.

B.Perform a full HANA database backup and restore to the new instance.

C.Stop the instance, change the instance type, and start the instance.

D.Create an Amazon EBS snapshot of the root volume, launch a new instance with the desired type, and attach the snapshot.

AnswerC

Correct. Stopping the instance, changing the instance type, and starting the instance keeps all attached EBS volumes intact, preserving HANA data without any reload. This is the quickest approach.

Why this answer

Stopping the instance, changing the instance type, and starting the instance preserves all attached EBS volumes, including the HANA data and log volumes. This approach requires no data backup or restore, minimizing downtime to just the stop/start cycle. Option D is incorrect because SAP HANA data is typically stored on separate EBS volumes (not the root volume), so an EBS snapshot of only the root volume would not capture the HANA data, necessitating a full data reload.

Options A and B both involve time-consuming data replication or backup/restore, resulting in more downtime.

Exam trap

The trap is that candidates may think taking an EBS snapshot of the root volume (Option D) is sufficient, but in standard SAP HANA deployments on AWS, HANA data and log volumes are separate. Stopping the instance and changing the instance type (Option C) is the simplest and fastest method that preserves all data.

How to eliminate wrong answers

Option A is wrong because AWS DMS is designed for heterogeneous or homogeneous database migrations and would require a full data load and ongoing replication, which introduces significant downtime and complexity for a large SAP HANA database; it does not simply change the instance type. Option B is wrong because performing a full HANA backup and restore to a new instance requires a lengthy backup process, data transfer, and restore operation, resulting in substantial downtime and a full data reload. Option C is wrong because stopping the instance and changing the instance type is the correct approach, but the option as stated does not specify that the instance type change is performed via the AWS console/CLI after stopping; however, the key issue is that Option C is actually a valid method (stop, change type, start) and is not incorrect—this is a trap because the question asks for the approach that minimizes downtime and requires no data reload, and Option C achieves that, but the exam expects the candidate to recognize that Option D is the same concept but with an unnecessary EBS snapshot step; in reality, Option C is the simplest and correct method, but the question's phrasing and answer choices are designed to mislead candidates into thinking a snapshot is required.

Option D is the officially correct answer in the exam context, even though Option C is functionally equivalent and simpler.

Practice this question →

52

MCQmedium

An SAP administrator needs to set up a fault-tolerant architecture for SAP NetWeaver on AWS. The architecture must survive an entire Availability Zone failure. Which configuration is the most appropriate?

A.Deploy all SAP application servers in one Availability Zone and use Amazon EBS snapshots for backup.

B.Deploy SAP application servers across multiple AZs but without a load balancer.

C.Use a single large EC2 instance for all SAP components.

D.Use an Auto Scaling group to launch SAP application servers across multiple AZs behind an Application Load Balancer.

AnswerD

Provides fault tolerance and load distribution.

Why this answer

Deploying SAP application servers across multiple Availability Zones (AZs) behind an Application Load Balancer (ALB) provides fault tolerance at the AZ level. The ALB distributes traffic to healthy instances in different AZs, ensuring that if one AZ fails, the remaining AZs continue to serve requests without interruption. This architecture aligns with SAP's recommended high-availability pattern for the ABAP stateless application tier.

Exam trap

The trap here is that candidates may think deploying across multiple AZs alone (Option B) is sufficient for fault tolerance, but without a load balancer to automate traffic distribution and health checks, the architecture cannot survive an AZ failure without manual intervention.

How to eliminate wrong answers

Option A is wrong because deploying all SAP application servers in a single AZ creates a single point of failure; an AZ outage would take down the entire application tier, and Amazon EBS snapshots only provide data backup, not real-time failover. Option B is wrong because deploying across multiple AZs without a load balancer means there is no mechanism to distribute traffic or automatically route requests away from failed AZs, so clients would need manual intervention to reach healthy servers. Option C is wrong because a single large EC2 instance for all SAP components (including the database) is a monolithic design that cannot survive an AZ failure; if the instance or its AZ fails, the entire SAP landscape is lost.

Practice this question →

53

MCQhard

A company has an SAP HANA database running on an EC2 instance with 1.9 TB of memory. The database requires persistent storage. The solutions architect must choose a storage configuration that provides the highest IOPS and throughput while maintaining data durability. Which storage option should the architect choose?

A.Use multiple io2 EBS volumes with Block Express striped together using LVM.

B.Use a single io2 Block Express EBS volume of the required size.

C.Use multiple gp3 EBS volumes striped together with LVM.

D.Use NVMe instance store volumes for the HANA data and log areas.

AnswerA

Striping multiple io2 Block Express volumes provides high IOPS and throughput with durability.

Why this answer

It combines multiple io2 Block Express EBS volumes striped via LVM, which delivers the highest possible IOPS and throughput for SAP HANA on AWS. io2 Block Express volumes support up to 256,000 IOPS and 4,000 MB/s throughput per volume, and striping multiple volumes linearly scales these limits to meet the demands of a 1.9 TB memory HANA database. This configuration also ensures data durability through EBS replication within an Availability Zone, unlike instance store volumes.

Exam trap

The trap here is that candidates often assume a single high-performance EBS volume (io2 Block Express) is sufficient, but they overlook that SAP HANA's performance requirements for a 1.9 TB memory database exceed the per-volume IOPS and throughput limits, necessitating striping of multiple volumes.

How to eliminate wrong answers

Option B is wrong because a single io2 Block Express EBS volume, while high-performance, cannot achieve the aggregate IOPS and throughput required for a 1.9 TB memory HANA workload; the maximum per-volume limits (256,000 IOPS, 4,000 MB/s) are insufficient for such a large in-memory database that demands parallel I/O. Option C is wrong because gp3 volumes have lower maximum IOPS (16,000 per volume) and throughput (1,000 MB/s per volume) compared to io2 Block Express, and striping them still cannot match the performance needed for SAP HANA's high-throughput log and data writes. Option D is wrong because NVMe instance store volumes are ephemeral and do not provide persistent storage; data is lost if the instance stops, terminates, or fails, violating the durability requirement for SAP HANA.

Practice this question →

54

MCQmedium

A company is preparing to migrate its SAP ECC 6.0 system to SAP S/4HANA on AWS. The current on-premises system includes a single application server and a database server running Oracle. The total database size is 1.5 TB. The company plans to use a homogeneous migration approach by exporting the existing Oracle database and importing it into a new SAP HANA database running on AWS. The migration must be completed within a tight weekend window. The company has established a 1 Gbps AWS Direct Connect connection to AWS. Which migration strategy should the company use to minimize downtime?

A.Use the SAP Software Update Manager (SUM) with Database Migration Option (DMO). Perform the migration in a weekend window using the delta replication feature.

B.Use AWS Database Migration Service (DMS) to continuously replicate the Oracle database to HANA, and then switch over.

C.Use an Application Load Balancer to redirect traffic to the new HANA system after exporting the data to S3.

D.Use the SAP HANA Studio migration wizard to export the Oracle database and import it into HANA. This is the simplest method.

AnswerA

DMO provides efficient migration with minimal downtime.

Why this answer

SAP Software Update Manager (SUM) with Database Migration Option (DMO) supports a homogeneous migration from Oracle to SAP HANA while performing both the system update and database migration in a single step. The delta replication feature allows initial full load followed by continuous replication of changes, enabling a short downtime window by switching over only after the delta catch-up is complete. This approach is specifically designed for tight migration windows and leverages the 1 Gbps Direct Connect for efficient data transfer.

Exam trap

The trap here is that candidates often confuse general-purpose migration tools like AWS DMS with SAP-specific tools, assuming DMS can handle SAP HANA migrations, but DMS lacks support for SAP HANA as a target and cannot maintain SAP application consistency.

How to eliminate wrong answers

Option B is wrong because AWS Database Migration Service (DMS) does not support SAP HANA as a target for homogeneous migrations from Oracle in the context of SAP systems; DMS is designed for general-purpose database migrations and lacks the SAP-specific schema, data type, and application-level consistency required for SAP S/4HANA. Option C is wrong because an Application Load Balancer operates at Layer 7 and cannot redirect traffic from an Oracle database to a HANA database; it is used for HTTP/HTTPS traffic distribution, not for database-level migration or switchover. Option D is wrong because the SAP HANA Studio migration wizard is intended for heterogeneous migrations (e.g., from other databases to HANA) but does not include delta replication capabilities, making it unsuitable for a tight weekend window as it requires a full export/import with extended downtime.

Practice this question →

55

MCQhard

A company runs SAP S/4HANA on AWS with a multi-Node HA cluster using Pacemaker and SUSE Linux Enterprise Server. The SAP application and database are on separate EC2 instances. After a planned failover test, the secondary node fails to take over the database role. What is the most likely cause?

A.The SAP HANA system replication is using asynchronous mode.

B.STONITH fencing is not configured for the cluster.

C.The EBS volumes are not configured with multi-attach enabled.

D.The SAP HANA system replication is not configured with ENSA2.

AnswerB

Without STONITH, the secondary node cannot safely take over.

Why this answer

In a Pacemaker HA cluster, STONITH (Shoot The Other Node In The Head) fencing is mandatory to ensure that a failed node is forcibly isolated before the cluster can safely promote the secondary node. Without STONITH, the cluster cannot guarantee that the primary node is truly dead, so it refuses to promote the secondary to avoid a split-brain scenario. This is why the secondary node fails to take over the database role after a planned failover test.

Exam trap

The trap here is that candidates often assume the failover failure is due to replication mode or storage configuration, but the root cause is the mandatory fencing requirement in Pacemaker clusters, which is a fundamental design principle for HA in SAP on AWS.

How to eliminate wrong answers

Option A is wrong because asynchronous SAP HANA system replication is a valid replication mode and does not prevent the secondary from taking over; it only affects data freshness and potential data loss, not the ability to promote. Option C is wrong because EBS multi-attach is not used for SAP HANA on EC2; HANA requires dedicated EBS volumes per instance, and the cluster manages volume attachment via scripts, not multi-attach. Option D is wrong because ENSA2 (Enqueue Server 2) is an SAP NetWeaver feature for enqueue replication, not related to SAP HANA database failover or Pacemaker cluster behavior.

Practice this question →

56

Multi-Selectmedium

Which TWO metrics should be monitored to ensure the health of an SAP HANA database running on AWS? (Select two.)

Select 2 answers

A.Elastic Load Balancer Latency

B.S3 Bucket Size

C.Disk I/O (read/write throughput)

D.HANA System Replication Lag

E.CPU Credit Balance

AnswersC, D

HANA is I/O intensive, so I/O performance is key.

Why this answer

Disk I/O (read/write throughput) is critical for SAP HANA because HANA is an in-memory database that relies on persistent storage for savepoints, log writes, and data recovery. Insufficient disk throughput can cause performance degradation or system hangs, making it a key health metric.

Exam trap

The trap here is that candidates may confuse general AWS infrastructure metrics (like ELB latency or CPU credits) with database-specific health indicators, overlooking that HANA's in-memory architecture makes disk I/O and replication lag the direct measures of database stability.

Practice this question →

57

MCQhard

An SAP architect is designing a new SAP S/4HANA system on AWS. The system must be PCI DSS compliant. The architect plans to use AWS KMS for encryption at rest and AWS CloudTrail for audit logging. The database will be SAP HANA on an r5.24xlarge instance with EBS gp3 volumes. What additional step is required to meet PCI DSS encryption requirements?

A.Store all SAP audit logs in Amazon S3 with server-side encryption.

B.Enable SAP HANA data volume encryption using the HANA database engine.

C.Use Amazon RDS for Oracle instead of SAP HANA to leverage native encryption.

D.Set up a VPN connection between the SAP system and the corporate network.

AnswerB

HANA data volume encryption encrypts data within the database, meeting PCI DSS requirements.

Why this answer

PCI DSS requires encryption of cardholder data at rest. While AWS KMS encrypts EBS volumes at the block level, SAP HANA's data volume resides in its own persistence layer and is not automatically encrypted by EBS encryption. Enabling SAP HANA data volume encryption ensures that data is encrypted within the database.

Option A (S3 with SSE) is for audit logs, not the database. Option C (Amazon RDS for Oracle) is not applicable because the system uses SAP HANA. Option D (VPN) is for network encryption, not at rest.

Practice this question →

58

MCQeasy

An SAP administrator created the IAM policy shown in the exhibit to allow an EC2 instance to back up to an S3 bucket. However, the backup fails with an access denied error. What is the most likely issue?

A.The policy does not grant permissions on the bucket itself.

B.The actions specified are insufficient for backup operations.

C.The resource ARN is incorrectly formatted.

D.The bucket is in a different region than the EC2 instance.

AnswerA

Missing s3:ListBucket permission on the bucket resource.

Why this answer

The IAM policy shown in the exhibit grants permissions on individual objects within the S3 bucket (using the `arn:aws:s3:::bucket-name/*` resource ARN) but does not grant any permissions on the bucket itself (using `arn:aws:s3:::bucket-name`). For backup operations, the EC2 instance typically needs to list the bucket or check its existence before writing objects, which requires `s3:ListBucket` or similar actions on the bucket resource. Without these bucket-level permissions, the backup fails with an access denied error.

Exam trap

The trap here is that candidates often focus on the object-level actions being correct and overlook the need for separate bucket-level permissions, assuming that granting `s3:PutObject` on `bucket-name/*` implicitly allows listing the bucket.

How to eliminate wrong answers

Option B is wrong because the actions specified (e.g., `s3:PutObject`, `s3:GetObject`) are sufficient for the actual object upload and retrieval steps of a backup; the failure is due to missing bucket-level permissions, not insufficient actions. Option C is wrong because the resource ARN for objects (`arn:aws:s3:::bucket-name/*`) is correctly formatted; the issue is the omission of the bucket-level ARN, not a formatting error. Option D is wrong because S3 is a global service and cross-region access between an EC2 instance and an S3 bucket works without additional permissions; the access denied error is purely an IAM policy issue, not a regional mismatch.

Practice this question →

59

MCQhard

An SAP administrator configures Route 53 failover routing as shown. The health check associated with the primary record is failing. What will happen to client requests for sap.example.com?

A.Route 53 will return the ALIAS record for the primary load balancer

B.Route 53 will return the secondary CNAME record

C.Route 53 will return an error

D.Route 53 will return both records

AnswerB

Failover routing directs to the secondary record when primary health check fails.

Why this answer

When the health check associated with the primary record fails, Route 53 automatically fails over to the secondary record. In this configuration, the primary record is an ALIAS record pointing to a load balancer, and the secondary record is a CNAME record. Since the primary is unhealthy, Route 53 returns the secondary CNAME record, directing clients to the failover endpoint.

Exam trap

The trap here is that candidates may assume Route 53 returns an error or both records when a health check fails, but failover routing is designed to seamlessly switch to the secondary record without returning errors or multiple answers.

How to eliminate wrong answers

Option A is wrong because Route 53 will not return the ALIAS record for the primary load balancer when its health check is failing; failover routing only returns the primary record if it is healthy. Option C is wrong because Route 53 does not return an error; it gracefully fails over to the secondary record as configured. Option D is wrong because Route 53 does not return both records; failover routing returns only one record at a time based on health check status.

Practice this question →

60

MCQeasy

A company is migrating its SAP HANA database to AWS. The system requires high network throughput and low latency between the application and database tiers. Which AWS service should be used to achieve this?

A.Amazon Route 53 latency-based routing

B.Amazon EC2 placement group

C.AWS Global Accelerator

D.Amazon EBS io2 Block Express volumes

AnswerB

Placement groups, specifically cluster placement groups, place EC2 instances in a single Availability Zone within a single rack, providing non-blocking, low-latency 10 Gbps or 25 Gbps network throughput between SAP HANA and application tiers. This satisfies the stem’s constraint of high network throughput and low latency by minimising physical distance and eliminating cross-switch hops.

Why this answer

Amazon EC2 placement groups, specifically cluster placement groups, provide low-latency, high-throughput networking by placing instances in a single Availability Zone within a logical group, ensuring they are physically close to each other. This minimizes network latency and maximizes throughput for tightly coupled workloads like SAP HANA, where application and database tiers require consistent, high-speed communication.

Exam trap

The trap here is that candidates often confuse network-level optimizations (like Global Accelerator or Route 53) with compute-level placement strategies, mistakenly believing that global traffic management or storage performance can solve inter-instance latency, when the core requirement is physical proximity between application and database servers.

How to eliminate wrong answers

Option A is wrong because Amazon Route 53 latency-based routing directs DNS traffic to the region with the lowest latency for end users, but it does not reduce latency between application and database tiers within AWS; it only optimizes client-to-application routing. Option C is wrong because AWS Global Accelerator improves performance for global users by routing traffic over the AWS global network, but it does not address intra-AZ or inter-instance latency between application and database tiers; it is designed for edge-to-region traffic, not internal tier-to-tier communication. Option D is wrong because Amazon EBS io2 Block Express volumes provide high-performance block storage with low latency, but they do not affect network throughput or latency between compute instances; they are storage-level optimizations, not network-level ones.

Practice this question →

61

MCQhard

A company runs its SAP ERP system on AWS with an Oracle database on an EC2 instance. The system is used by thousands of users globally. Recently, the database has been experiencing slow query performance, especially during end-of-month processing. The administrator notices that the database instance is an r5.8xlarge with 32 vCPUs and 256 GB of memory, running on a single EBS io1 volume with 20,000 IOPS for the data files. The administrator has already optimized the SQL queries and increased the SGA size. However, performance remains poor. The Amazon CloudWatch metrics show that the EBS volume's Average Queue Length is consistently above 10 and the read latency spikes to over 100 ms during peak times. The CPU utilization is around 70%. Which action should the administrator take to resolve the I/O bottleneck?

A.Change the volume type to gp3 and increase the baseline IOPS.

B.Create multiple EBS io1 volumes and stripe them using RAID 0 at the OS level.

C.Increase the IOPS of the existing io1 volume to 40,000.

D.Upgrade the EC2 instance to an r5.12xlarge with more network bandwidth.

AnswerB

Correct. RAID 0 striping increases parallelism, distributing I/O across volumes to reduce queue depth and latency.

Why this answer

Striping multiple EBS io1 volumes using RAID 0 at the OS level increases I/O parallelism, distributing the workload across multiple volumes and reducing the average queue length and latency. Option A is incorrect because gp3 volumes may not provide sufficient IOPS for this demanding workload, and a single volume still creates a bottleneck. Option C is incorrect because increasing IOPS on a single volume may not resolve the queue length issue if the volume is already at its throughput limit.

Option D is incorrect because upgrading the instance does not directly improve EBS performance; the bottleneck is at the storage layer.

Practice this question →

62

MCQeasy

An SAP system uses a secondary IP address for the SAP application. After an instance reboot, the secondary IP address is no longer attached. What is the most likely cause?

A.The Elastic IP address was not associated with the instance

B.The secondary IP address is not automatically re-attached after instance stop/start

C.The security group removed the IP address

D.The Elastic Network Interface (ENI) was deleted

AnswerB

Secondary IPs are not persistent across stop/start; they must be re-attached or use an ENI.

Why this answer

When an EC2 instance is stopped and started, any secondary private IP addresses assigned to its primary Elastic Network Interface (ENI) are automatically released and not re-attached. The SAP application relies on this secondary IP address, so after a stop/start cycle the address is lost, requiring manual re-assignment or automation to restore it.

Exam trap

The trap here is that candidates confuse the behavior of Elastic IP addresses (which persist across stop/start if associated with an ENI) with secondary private IP addresses, which do not persist on the primary ENI after a stop/start cycle.

How to eliminate wrong answers

Option A is wrong because an Elastic IP address is a public IPv4 address that can be associated with an instance or ENI, but the question specifies a secondary IP address (private IPv4), not a public Elastic IP. Option C is wrong because security groups are stateful virtual firewalls that control inbound/outbound traffic based on rules; they do not assign or remove IP addresses from an instance. Option D is wrong because the ENI itself is not deleted during a stop/start cycle; only the secondary private IP address is released from the primary ENI when the instance is stopped.

Practice this question →

63

Drag & Dropmedium

Drag and drop the steps to set up an SAP HANA system replication in AWS using the SAP HANA Cockpit 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

SAP HANA system replication requires two instances, network connectivity, enabling replication on primary, registering secondary, and then starting replication.

Practice this question →

64

MCQmedium

A company is deploying SAP S/4HANA on AWS and needs to ensure that the database and application servers are in the same placement group to minimize latency. However, the instance types required for the HANA database are not available in the same placement group due to insufficient capacity. What should the company do to maintain low latency?

A.Use a spread placement group instead of a cluster placement group.

B.Place all instances in the same Availability Zone without a placement group.

C.Use a different instance type for the database that is available in the placement group.

D.Place the database in a different AWS Region and use AWS Direct Connect.

AnswerA

Spread placement groups distribute instances across distinct hardware, reducing capacity issues while still minimizing latency.

Why this answer

A spread placement group is the correct choice because it spreads instances across distinct underlying hardware, reducing the risk of correlated failures while still keeping them in the same Availability Zone to minimize latency. Unlike a cluster placement group, which requires all instances to be on the same rack and can suffer from capacity constraints, a spread placement group does not enforce a single rack placement, so it can accommodate different instance types even when the cluster placement group lacks capacity. This ensures low latency for SAP S/4HANA communication between database and application servers without violating placement group constraints.

Exam trap

The trap here is that candidates assume only a cluster placement group can provide low latency, overlooking that a spread placement group in the same Availability Zone still offers significantly lower latency than no placement group, while avoiding the capacity limitations of a cluster placement group.

How to eliminate wrong answers

Option B is wrong because placing instances in the same Availability Zone without a placement group does not guarantee that they will be on the same physical hardware or even close together, which can introduce higher latency than a placement group provides. Option C is wrong because changing the database instance type may not meet the performance or memory requirements of SAP HANA, and it does not solve the underlying capacity issue in the cluster placement group. Option D is wrong because placing the database in a different AWS Region introduces significant cross-Region latency, which is unacceptable for SAP S/4HANA’s low-latency requirements, and AWS Direct Connect does not reduce latency between Regions.

Practice this question →

65

Multi-Selecthard

A company runs SAP ERP on AWS with an Oracle database. The architect wants to implement a backup strategy that provides point-in-time recovery (PITR) with an RPO of 5 minutes and an RTO of 2 hours. Which TWO solutions should the architect consider? (Choose TWO.)

Select 2 answers

A.AWS Database Migration Service (DMS) with ongoing replication to an Oracle instance in another AZ

B.Oracle Recovery Manager (RMAN) with archivelog mode backing up to Amazon S3

C.Amazon S3 Lifecycle policies to move backups to Glacier

D.Amazon S3 Transfer Acceleration for backup uploads

E.EBS snapshots every 5 minutes

AnswersA, B

DMS ongoing replication can achieve low RPO and provides a standby for failover.

Why this answer

AWS DMS with ongoing replication can continuously replicate changes from the Oracle source database to a target Oracle instance in another Availability Zone, enabling point-in-time recovery with an RPO as low as 5 minutes. This approach supports near-real-time replication and can be combined with automatic failover to meet the RTO of 2 hours, as the target instance is already synchronized and ready.

Exam trap

The trap here is that candidates often assume EBS snapshots can be taken at very high frequencies (like every 5 minutes) to achieve low RPO, but AWS enforces a 60-minute minimum cooldown between snapshots, making this option infeasible for the stated RPO.

Practice this question →

66

MCQeasy

Which AWS service should be used to capture and analyze operating system-level metrics from an EC2 instance running SAP, such as memory utilization and disk I/O, and to set alarms based on thresholds?

A.AWS Config

B.AWS Trusted Advisor

C.Amazon CloudWatch with the CloudWatch Agent

D.Amazon Inspector

AnswerC

CloudWatch Agent collects OS metrics and supports alarms.

Why this answer

Amazon CloudWatch with the CloudWatch Agent is the correct choice because the CloudWatch Agent can collect custom operating system-level metrics (such as memory utilization and disk I/O) from EC2 instances, including those running SAP. The agent sends these metrics to CloudWatch, where you can set alarms based on thresholds. AWS Config, Trusted Advisor, and Inspector do not provide OS-level metric collection or alarm capabilities.

Exam trap

The trap here is that candidates often assume the default EC2 metrics in CloudWatch include memory and disk I/O, but those are only available if you install the CloudWatch Agent, as the hypervisor cannot see inside the guest OS.

How to eliminate wrong answers

Option A is wrong because AWS Config is a service for evaluating and auditing resource configurations against rules (e.g., checking if an EC2 instance has a specific tag), not for capturing OS-level metrics or setting alarms. Option B is wrong because AWS Trusted Advisor provides best-practice recommendations (e.g., cost optimization, security checks) but does not collect or analyze memory utilization or disk I/O metrics from EC2 instances. Option D is wrong because Amazon Inspector is a vulnerability assessment service that scans for software vulnerabilities and unintended network exposure; it does not capture OS-level performance metrics or support alarm thresholds.

Practice this question →

67

MCQhard

A company runs SAP Business Suite on AWS with Oracle Database. The system is experiencing high read latency on the database server. The current storage configuration uses EBS gp2 volumes. Which change would most effectively reduce read latency?

A.Migrate to io2 Block Express volumes with provisioned IOPS.

B.Increase the size of the EBS gp2 volumes to increase baseline IOPS.

C.Configure a RAID 0 stripe across multiple EBS volumes.

D.Use EBS st1 volumes for better throughput.

AnswerA

Migrating to io2 Block Express volumes reduces read latency by providing consistent, high-performance IOPS with sub-millisecond latency, directly addressing the high read latency constraint of the gp2 burst-bucket model. Unlike gp2, which throttles performance when burst credits are exhausted, io2 Block Express delivers provisioned IOPS independently of volume size, ensuring sustained throughput for SAP’s read-heavy Oracle workloads.

Why this answer

Io2 Block Express volumes provide consistent, high-performance IOPS with sub-millisecond latency, which directly addresses the high read latency issue. Unlike gp2, which relies on burst credits and has variable performance, io2 Block Express delivers provisioned IOPS up to 256,000 per volume, making it ideal for latency-sensitive SAP workloads with Oracle Database.

Exam trap

The trap here is that candidates often assume increasing gp2 volume size (Option B) or striping volumes (Option C) will solve latency issues, but the PAS-C01 exam tests the understanding that for consistent low-latency random I/O, provisioned IOPS volumes like io2 Block Express are required, not just higher throughput or IOPS aggregation.

How to eliminate wrong answers

Option B is wrong because increasing gp2 volume size only raises the baseline IOPS (at a rate of 3 IOPS per GB), but does not guarantee low latency under sustained high read loads, as gp2 performance can still degrade when burst credits are exhausted. Option C is wrong because RAID 0 striping across multiple EBS volumes improves throughput and IOPS but does not inherently reduce read latency; it can even introduce additional overhead from the RAID controller and increase the risk of data loss if a single volume fails. Option D is wrong because EBS st1 volumes are throughput-optimized HDDs designed for large, sequential workloads, not for low-latency random reads, and they have higher latency than SSD-based volumes like gp2 or io2.

Practice this question →

68

MCQhard

A company runs SAP HANA on AWS with a multi-AZ deployment using HANA System Replication (HSR). The primary site is in us-east-1a and the secondary in us-east-1b. Each site has an ASCS and PAS. The HANA database uses a virtual IP address managed by a Route 53 health check with a failover routing policy. During a recent AZ failure in us-east-1a, the automatic failover to the secondary site took over 15 minutes. The recovery time objective (RTO) is 5 minutes. Analysis shows that the Route 53 health check failed but the failover did not trigger quickly because the DNS TTL was set to 300 seconds. What changes should be made to meet the RTO?

A.Increase the DNS TTL to 600 seconds to ensure stability.

B.Replace Route 53 with an Application Load Balancer for the virtual IP.

C.Reduce the DNS TTL to 60 seconds and use a weighted routing policy with health checks.

D.Remove the health check and use a simple routing policy with a low TTL.

AnswerC

Lower TTL speeds up DNS propagation; weighted routing allows immediate failover.

Why this answer

Reducing the DNS TTL to 60 seconds ensures that DNS resolvers cache the failover record for a shorter duration, allowing the Route 53 failover routing policy to propagate the new IP address more quickly after a health check failure. Combined with a weighted routing policy and health checks, this enables failover within the 5-minute RTO by minimizing DNS propagation delay, which was the bottleneck at 300 seconds.

Exam trap

The trap here is that candidates may think increasing TTL improves stability (Option A) or that an ALB can replace a virtual IP for HANA HSR (Option B), but the core issue is DNS propagation delay, and only reducing TTL with a failover routing policy directly addresses the RTO requirement.

How to eliminate wrong answers

Option A is wrong because increasing the DNS TTL to 600 seconds would worsen the failover time, extending the delay beyond 15 minutes and making it impossible to meet the 5-minute RTO. Option B is wrong because an Application Load Balancer (ALB) does not support virtual IP addresses for SAP HANA HSR; ALBs operate at Layer 7 and cannot handle the static IP requirements of HANA System Replication, which relies on a fixed virtual IP for client connections. Option D is wrong because removing the health check eliminates the automated failure detection mechanism, and using a simple routing policy without health checks would not trigger failover at all, leaving the system unable to recover from an AZ failure.

Practice this question →

69

MCQmedium

A company is running SAP on AWS and needs to ensure that its SAP HANA database is backed up daily with minimal impact on performance. The database is 2 TB in size and runs on an r5.8xlarge instance. Which backup strategy meets these requirements?

A.Perform a full backup to Amazon EBS volumes attached to the instance

B.Use the SAP HANA Backint agent to back up directly to Amazon S3

C.Use AWS Backup to create snapshots of the entire EC2 instance

D.Use AWS Storage Gateway to back up to Amazon S3 Glacier

AnswerB

Backint integrates with SAP HANA for efficient, performant backups.

Why this answer

The SAP HANA Backint agent integrates directly with SAP HANA to stream backup data to Amazon S3, which offloads the backup workload from the database instance's CPU and I/O. This minimizes performance impact compared to local EBS snapshots or volume-based backups, as Backint uses S3's scalable throughput without consuming instance storage bandwidth.

Exam trap

The trap here is that candidates often assume EBS snapshots (via AWS Backup) are the simplest and least impactful method, but they fail to recognize that snapshots still cause I/O pauses and require database consistency, whereas Backint to S3 is the native, low-impact SAP HANA backup strategy on AWS.

How to eliminate wrong answers

Option A is wrong because performing a full backup to EBS volumes attached to the instance consumes significant I/O and CPU resources on the r5.8xlarge instance, impacting SAP HANA performance during the backup window. Option C is wrong because AWS Backup snapshots of the entire EC2 instance capture the full volume state, which requires a database-consistent snapshot (e.g., via pre-script hooks) and still incurs I/O overhead during snapshot creation, plus it is not a native SAP HANA backup method. Option D is wrong because AWS Storage Gateway is designed for hybrid storage scenarios and does not provide a direct, low-impact backup path for SAP HANA; backing up to S3 Glacier adds retrieval latency and is not suitable for daily operational backups.

Practice this question →

70

Multi-Selecteasy

A company is migrating SAP workloads to AWS and needs to choose storage for SAP HANA. Which two storage options are supported for SAP HANA data volumes? (Select TWO.)

Select 2 answers

A.Amazon EBS io2 Block Express volumes.

B.Amazon S3.

C.Amazon EFS.

D.Instance Store (NVMe SSD) volumes.

E.Amazon EBS gp3 volumes.

AnswersA, E

Supports high IOPS and low latency required by HANA.

Why this answer

Amazon EBS io2 Block Express volumes are supported for SAP HANA data volumes because they provide high durability (99.999% durability) and sub-millisecond latency with up to 256,000 IOPS per volume, meeting SAP's performance requirements for production HANA workloads. Amazon EBS gp3 volumes are also supported for SAP HANA data volumes, offering a baseline of 3,000 IOPS and 125 MB/s throughput with the ability to scale independently, making them suitable for non-production or smaller production environments.

Exam trap

The trap here is that candidates often confuse supported storage for SAP HANA data volumes with log volumes, where Instance Store (NVMe SSD) is supported for log volumes but not for data volumes, leading to incorrect selection of Option D.

Practice this question →

71

MCQmedium

A company runs SAP HANA on AWS and needs to ensure that the database can survive a single Availability Zone failure without manual intervention. The SAP HANA system is currently deployed on a single EC2 instance. Which solution meets this requirement?

A.Use an Auto Scaling group to launch a new SAP HANA instance if the current instance fails

B.Configure SAP HANA System Replication with a secondary instance in a different Availability Zone and enable automatic takeover

C.Deploy the SAP HANA instance in a placement group within a single Availability Zone

D.Take daily EBS snapshots and copy them to another AWS Region

AnswerB

System Replication with automatic takeover ensures failover without manual intervention.

Why this answer

SAP HANA System Replication (HSR) with automatic takeover provides synchronous or asynchronous data replication to a secondary instance in a different Availability Zone (AZ). When the primary fails, the secondary automatically becomes the new primary without manual intervention, ensuring database survival during a single AZ failure. This is the only option that meets the requirement for automatic failover across AZs.

Exam trap

The trap here is that candidates confuse instance-level recovery (Auto Scaling) with database-level replication, assuming that launching a new EC2 instance automatically restores the SAP HANA database, when in fact HANA data is ephemeral unless explicitly replicated or backed up.

How to eliminate wrong answers

Option A is wrong because an Auto Scaling group launches a new EC2 instance but does not restore the SAP HANA database state from the failed instance; it would start with an empty or outdated volume, losing all transactions committed after the last snapshot or backup. Option C is wrong because a placement group within a single AZ actually increases the risk of simultaneous failure and does not provide any cross-AZ redundancy or automatic failover. Option D is wrong because daily EBS snapshots copied to another Region provide disaster recovery but not automatic failover; restoring from a snapshot requires manual intervention and can lose up to 24 hours of data, failing the 'without manual intervention' and 'survive a single AZ failure' requirements.

Practice this question →

72

Multi-Selectmedium

An architect is designing a highly available SAP NetWeaver architecture on AWS. The system uses an SAP Central Services (ASCS) instance. Which THREE components are required to achieve high availability for the SAP environment? (Choose THREE.)

Select 3 answers

A.Shared file storage (e.g., Amazon EFS or EBS Multi-Attach)

B.A cluster manager such as Pacemaker

C.A NAT Gateway for outbound traffic

D.An Internet Gateway for inbound traffic

E.A Network Load Balancer to distribute traffic to ASCS

AnswersA, B, E

Shared storage ensures data consistency after failover.

Why this answer

A cluster manager like Pacemaker is required to orchestrate failover between the two ASCS nodes. Shared file storage (e.g., Amazon EFS or EBS Multi-Attach) provides a shared file system for /sapmnt and /usr/sap, which must be accessible from both nodes. A Network Load Balancer (NLB) distributes traffic to the active ASCS instance and performs health checks to detect failures.

Options C and D are incorrect because a NAT Gateway and Internet Gateway are not required for SAP HA; they are used for outbound/inbound internet connectivity.

Practice this question →

73

MCQmedium

A company is designing a disaster recovery (DR) strategy for SAP S/4HANA on AWS. The primary region is us-east-1 and the DR region is us-west-2. The RPO is 15 minutes and RTO is 1 hour. Which approach should be used to replicate SAP HANA data?

A.Configure HANA System Replication across regions

B.Use AWS Database Migration Service (DMS) with ongoing replication

C.Use Amazon S3 Cross-Region Replication for backup files

D.Use AWS Backup cross-region copy of EBS snapshots

AnswerA

HANA System Replication (HSR) for cross-region DR uses asynchronous replication (typically with log shipping) to meet the 15-minute RPO and 1-hour RTO. Synchronous replication is not feasible across regions due to latency.

Why this answer

HANA System Replication (HSR) is the only option that meets the 15-minute RPO and 1-hour RTO for SAP HANA data replication across regions. HSR uses log-based asynchronous replication to continuously ship redo logs to the DR region, enabling near-real-time data synchronization with minimal data loss. This is the native SAP-recommended method for cross-region DR of SAP HANA databases.

Exam trap

The trap here is that candidates often confuse AWS-native services (DMS, S3 CRR, AWS Backup) as viable for SAP HANA DR, but they fail to recognize that only HANA System Replication provides the sub-15-minute RPO and sub-1-hour RTO required for SAP-certified DR on AWS.

How to eliminate wrong answers

Option B is wrong because AWS DMS with ongoing replication does not support SAP HANA as a source for continuous change data capture (CDC) in a production-grade DR scenario; DMS is designed for heterogeneous migrations, not for low-latency, log-based replication of SAP HANA. Option C is wrong because S3 Cross-Region Replication of backup files can only achieve RPOs measured in hours (due to backup frequency and replication delays), not the required 15 minutes, and it does not provide a mechanism for rapid database recovery within 1 hour. Option D is wrong because AWS Backup cross-region copy of EBS snapshots typically has an RPO of at least 1 hour (snapshot intervals) and an RTO of several hours (restore time), failing both the 15-minute RPO and 1-hour RTO requirements.

Practice this question →

74

Multi-Selecteasy

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

Select 2 answers

A.Deploy HANA in a single Availability Zone to reduce costs.

B.Disable hyper-threading on the HANA instance.

C.Store HANA data on instance store volumes for better performance.

D.Use EBS-optimized instances for HANA workloads.

E.Use EBS snapshots for backup of HANA data volumes.

AnswersD, E

EBS-optimized instances dedicate network bandwidth exclusively to Amazon EBS I/O, preventing contention between storage traffic and other network flows. This satisfies the SAP HANA requirement for consistent, low-latency access to persistent storage, as HANA’s savepoint and log writes demand predictable disk performance without throttling from shared network resources.

Why this answer

EBS-optimized instances provide dedicated network bandwidth for Amazon EBS I/O, which is critical for SAP HANA's high-throughput, low-latency storage requirements. Without EBS optimization, network traffic can contend with EBS traffic, causing performance degradation and potential SLA violations for HANA workloads.

Exam trap

The trap here is that candidates often confuse 'disabling hyper-threading' (a requirement for on-premises HANA deployments) with AWS best practices, where hyper-threading must remain enabled to leverage the full CPU capacity of the instance.

Practice this question →

75

MCQmedium

A company is implementing SAP S/4HANA on AWS and wants to ensure that the system is backed up properly. They need to back up the HANA database and the application layer. Which approach is recommended for backing up the HANA database?

A.Use EBS snapshots for the HANA data volumes

B.Configure an S3 lifecycle policy to archive the HANA log files

C.Use AWS Backup with a backup plan that includes the HANA instance

D.Use the AWS Backint agent to back up HANA to Amazon S3

AnswerD

AWS Backint agent provides application-consistent backups of HANA to S3 via SAP Backint interface.

Why this answer

The AWS Backint agent is the recommended and supported method for backing up SAP HANA databases on AWS. It integrates directly with SAP HANA's native backup interface (backint for SAP HANA) to stream backup data to Amazon S3, ensuring consistent, incremental, and catalog-aware backups without relying on file-system-level snapshots.

Exam trap

The trap here is that candidates confuse crash-consistent EBS snapshots (Option A) or generic AWS Backup plans (Option C) with the application-consistent, HANA-integrated backup method required for SAP workloads, assuming any snapshot-based approach is sufficient for database consistency.

How to eliminate wrong answers

Option A is wrong because EBS snapshots are crash-consistent, not application-consistent, and cannot guarantee HANA database integrity without additional pre-freeze/post-thaw scripts; they also do not integrate with HANA's backup catalog. Option B is wrong because an S3 lifecycle policy archives log files but does not perform a database backup; HANA requires a proper backup of data and log volumes, not just archival of logs. Option C is wrong because AWS Backup does not natively support SAP HANA's backint interface; it can back up EC2 instances via EBS snapshots, but those lack HANA-consistent backup capabilities and catalog integration.

Practice this question →

Page 1 of 6 · 428 questions totalNext →

Ready to test yourself?

Try a timed practice session using only Design of SAP Workloads on AWS questions.

Start 20-question session