CCNA Design of SAP Workloads on AWS Questions — Page 5 of 6

301

Multi-Selecteasy

A company is planning to migrate its SAP landscape to AWS. They want to use AWS services to reduce operational overhead. Which TWO services can help automate the deployment and configuration of SAP systems? (Choose two.)

Select 2 answers

A.AWS Launch Wizard for SAP

B.Amazon CloudWatch

C.AWS Systems Manager

D.AWS CloudFormation

E.Amazon WorkSpaces

AnswersA, D

Launch Wizard automates the deployment of SAP systems on AWS.

Why this answer

AWS Launch Wizard for SAP is correct because it provides a guided, step-by-step process to size, configure, and deploy SAP systems on AWS, automatically provisioning the necessary EC2 instances, storage, and networking. It reduces operational overhead by automating the deployment and initial configuration of SAP landscapes, including HANA databases and NetWeaver applications.

Exam trap

The trap here is that candidates often confuse AWS Systems Manager's automation capabilities (e.g., Run Command, State Manager) with deployment automation, but Systems Manager is designed for ongoing management and remediation, not for the initial provisioning and configuration of SAP systems.

Practice this question →

302

MCQeasy

A company is deploying SAP NetWeaver on AWS and needs to ensure that the SAP application servers can automatically scale based on CPU utilization. Which AWS service should they use?

A.AWS Auto Scaling groups with CloudWatch alarms

B.Amazon CloudWatch to monitor CPU and send alerts

C.AWS Lambda to start and stop instances based on a schedule

D.Elastic Load Balancing (ELB) with health checks

AnswerA

Auto Scaling groups can dynamically adjust capacity based on CPU utilization metrics from CloudWatch.

Why this answer

AWS Auto Scaling groups with CloudWatch alarms allow SAP application servers to automatically scale in or out based on CPU utilization thresholds. This is the correct approach because Auto Scaling groups can dynamically adjust the number of EC2 instances in response to CloudWatch metric alarms, which is essential for handling variable SAP workload demands without manual intervention.

Exam trap

The trap here is that candidates often confuse CloudWatch's monitoring and alerting capability with the actual scaling action, forgetting that CloudWatch alone cannot modify the instance count without an Auto Scaling group.

How to eliminate wrong answers

Option B is wrong because Amazon CloudWatch alone only monitors CPU and sends alerts; it cannot automatically start or stop instances to scale the SAP application tier. Option C is wrong because AWS Lambda scheduled start/stop is for time-based actions, not dynamic scaling based on real-time CPU utilization. Option D is wrong because Elastic Load Balancing distributes traffic and performs health checks but does not automatically scale the number of instances; it requires an Auto Scaling group to handle scaling actions.

Practice this question →

303

MCQhard

An SAP system on AWS uses a Classic Load Balancer to distribute traffic to web dispatchers. The system is experiencing intermittent timeouts. What is the most likely cause?

A.The security group for the load balancer is blocking traffic.

B.Sticky sessions are enabled on the load balancer.

C.The load balancer health check interval is too short.

D.The load balancer idle timeout setting is too low.

AnswerD

Low idle timeout can cause premature connection termination.

Why this answer

The Classic Load Balancer has a default idle timeout of 60 seconds for TCP connections. If the SAP application or web dispatchers keep connections open longer than this without data transfer (e.g., during long-running reports or user think time), the load balancer will close the connection, causing intermittent timeouts. Increasing the idle timeout to match the application's keep-alive settings resolves this.

Exam trap

The trap here is that candidates confuse health check intervals with idle timeout, assuming a short health check interval causes timeouts, when in reality idle timeout is the direct cause of dropped connections during periods of inactivity.

How to eliminate wrong answers

Option A is wrong because security groups are stateful; if the load balancer's security group were blocking traffic, the issue would be consistent (all traffic blocked), not intermittent. Option B is wrong because sticky sessions (session affinity) do not cause timeouts; they ensure a client is routed to the same backend, which can actually reduce timeouts by maintaining session state. Option C is wrong because a health check interval that is too short would cause the load balancer to mark instances as unhealthy more frequently, leading to dropped connections, but the symptom would be persistent failures, not intermittent timeouts.

Practice this question →

304

Multi-Selecteasy

A company is planning to run SAP NetWeaver on AWS. Which TWO services are recommended for monitoring the SAP system? (Choose TWO.)

Select 2 answers

A.Amazon CloudWatch with SAP monitoring agent

B.Amazon Inspector

C.AWS Trusted Advisor

D.SAP Solution Manager

E.AWS Config

AnswersA, D

CloudWatch can collect SAP metrics via custom agents.

Why this answer

Amazon CloudWatch with the SAP monitoring agent is recommended because it collects SAP-specific metrics (e.g., work process usage, dialog response times, and queue lengths) and sends them to CloudWatch for custom dashboards and alarms. This integration is a standard AWS best practice for monitoring SAP NetWeaver health and performance. Additionally, SAP Solution Manager provides comprehensive monitoring and management capabilities for SAP landscapes, including real-time monitoring of SAP systems, alerting, and root cause analysis.

It is an essential SAP tool for monitoring and is fully supported on AWS.

Exam trap

The trap here is that candidates often confuse infrastructure monitoring (CloudWatch) with security or compliance tools (Inspector, Config, Trusted Advisor), forgetting that SAP-specific monitoring requires the SAP monitoring agent to bridge the gap between OS metrics and application-level health.

Practice this question →

305

MCQhard

An SAP system on AWS is experiencing high CPU ready time on the application server VMs. Which configuration change is most likely to reduce CPU contention?

A.Increase the number of vCPUs assigned to the instance

B.Move the instance to a dedicated host

C.Change instance tenancy to default

D.Increase the instance memory

AnswerB

Dedicated host provides dedicated physical cores, reducing contention.

Why this answer

CPU ready time indicates that the VM is ready to process instructions but is waiting for the physical CPU to become available, which is a symptom of CPU overcommitment on the host. Moving the instance to a dedicated host eliminates resource contention with other AWS customers' VMs by providing the instance with exclusive access to the physical CPU cores, thereby reducing or eliminating CPU ready time.

Exam trap

The trap here is that candidates often assume adding more vCPUs (Option A) will solve performance issues, but CPU ready time is a scheduling contention problem that requires physical isolation, not more virtual resources.

How to eliminate wrong answers

Option A is wrong because increasing the number of vCPUs does not address the underlying contention for physical CPU cycles; it may even worsen the problem by requiring more physical cores to be scheduled. Option C is wrong because changing instance tenancy to default (shared tenancy) would place the instance on a multi-tenant host where CPU overcommitment is more likely, increasing rather than decreasing CPU ready time. Option D is wrong because increasing instance memory does not affect CPU scheduling or contention; CPU ready time is a CPU-bound metric, not memory-bound.

Practice this question →

306

MCQmedium

An SAP administrator runs the AWS CLI command shown in the exhibit for an EC2 instance running SAP HANA. The administrator notices that the /dev/sdf volume does not have DeleteOnTermination set to true. What is the impact of this configuration?

A.The volume will be detached but not deleted.

B.The volume will be automatically deleted when the instance is terminated.

C.The volume cannot be attached to another instance.

D.The volume will persist after instance termination, preserving data.

AnswerD

The volume will be retained and can be reattached.

Why this answer

When the DeleteOnTermination attribute of an EBS volume is set to false (as indicated by the absence of 'true' in the AWS CLI output for /dev/sdf), the volume will not be automatically deleted when the EC2 instance is terminated. Instead, the volume enters a 'available' state and persists independently, preserving all data for later use or reattachment. This is critical for SAP HANA workloads where data volumes must survive instance termination for disaster recovery or migration scenarios.

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

307

MCQhard

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

A.Change the instance type to x1e.32xlarge for more CPU.

B.Scale up to a larger instance size within the r5 family, such as r5.12xlarge.

C.Use a burstable performance instance like t3.2xlarge.

D.Enable CPU hyper-threading on the instance.

AnswerB

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

308

MCQmedium

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

A.us-west-2a

B.us-east-1b

C.Any Availability Zone

D.us-east-1a

AnswerB

Different AZ in same region provides HA.

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

309

MCQeasy

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

A.AWS Launch Wizard for SAP

B.AWS OpsWorks

C.AWS CloudFormation

D.Amazon Elastic File System (EFS)

AnswerA

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

310

MCQhard

An administrator creates a CloudFormation stack with the template shown in the exhibit. The stack creates an Auto Scaling group with a desired capacity of 2. However, only one instance is launched. What is the most likely reason?

A.The instance type m5.large is not available in the selected AZs.

B.The DesiredCapacity is set incorrectly to 1.

C.The Auto Scaling group is unable to launch the second instance due to capacity constraints.

D.The MinSize is set to 1, so only one instance is allowed.

AnswerC

Capacity constraints in the AZs could prevent launching additional instances.

Why this answer

The Auto Scaling group's desired capacity of 2 cannot be met if there are insufficient EC2 instance resources (e.g., vCPU, memory, or network capacity) in the selected Availability Zones. AWS Auto Scaling will launch as many instances as possible up to the desired capacity, but if the second instance launch fails due to a capacity constraint (e.g., insufficient m5.large capacity in the specified AZs), only one instance will be launched. The stack creation will still succeed, but the Auto Scaling group will remain at the lower count until capacity becomes available.

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

311

MCQmedium

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

A.Increase the HANA replication timeout value to accommodate the latency.

B.Use asynchronous replication instead and accept the risk of data loss.

C.Continue with synchronous replication; the latency is acceptable for HA.

D.Deploy both HANA instances in the same Availability Zone to reduce network latency.

AnswerD

Same AZ reduces latency, making synchronous replication feasible.

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

312

MCQeasy

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

A.Network ACLs

B.IAM role

C.Security group

D.S3 bucket policy

AnswerC

EFS uses security groups to allow inbound NFS traffic.

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

313

Matchingmedium

Match the SAP sizing parameter to its AWS EC2 equivalent.

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

Concepts

Matches

Benchmark unit for CPU capacity

Instance RAM size

EBS bandwidth or instance storage performance

Placement group or instance type network performance

Why these pairings

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

Practice this question →

314

Multi-Selectmedium

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

Select 2 answers

A.Use a burstable instance type (e.g., t3) for non-production HANA systems.

B.Use EBS-optimized instances or instances with dedicated EBS bandwidth.

C.Use a dedicated EC2 instance for the HANA database, separate from application servers.

D.Configure a large swap space on the HANA instance to handle memory pressure.

E.Mount the HANA data volume using Amazon EFS for high throughput.

AnswersB, C

EBS optimization provides consistent performance for storage.

Why this answer

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

Exam trap

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

Practice this question →

315

MCQmedium

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

A.Amazon Elastic File System (EFS).

B.Amazon S3 with a file gateway.

C.Amazon FSx for NetApp ONTAP.

D.Multiple Amazon EBS volumes with a cluster-aware file system.

AnswerC

Supports NFS with features required by Oracle GI.

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

316

MCQhard

A company runs SAP HANA on AWS and wants to implement a disaster recovery (DR) strategy with a recovery point objective (RPO) of 15 minutes and a recovery time objective (RTO) of 2 hours. Which solution meets these requirements?

A.Configure HANA System Replication (HSR) to a small instance in the DR region and scale up on failover.

B.Take daily EBS snapshots of the HANA data volumes and copy them to the DR region.

C.Use AWS Database Migration Service (DMS) to replicate HANA to an RDS instance in the DR region.

D.Use AWS Elastic Disaster Recovery (DRS) to replicate the HANA server to the DR region.

AnswerD

DRS provides continuous replication with low RPO.

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

317

Multi-Selecteasy

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

Select 2 answers

A.AWS Config

B.AWS Launch Wizard for SAP

C.Amazon Inspector

D.AWS Well-Architected Tool

E.AWS Trusted Advisor

AnswersB, E

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

Why this answer

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

Exam trap

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

Practice this question →

318

MCQhard

An SAP Basis administrator is troubleshooting a performance issue on an SAP HANA database running on an EC2 instance. The administrator notices that the 'hdbcons' command shows high 'wait time' for 'disk I/O' operations. The instance is an r5.4xlarge with 500 GB of gp2 EBS volumes for /hana/data and /hana/log. Which of the following is the MOST effective action to improve disk I/O performance?

A.Increase the frequency of EBS snapshots to offload I/O.

B.Change the EBS volume type from gp2 to gp3 with higher IOPS and throughput.

C.Upgrade to a larger EC2 instance type with more CPU and memory.

D.Disable the HANA delta merge operation to reduce I/O load.

AnswerB

gp3 provides better performance and is cost-effective.

Why this answer

Changing the EBS volume type from gp2 to gp3 with higher IOPS and throughput is the most effective action because gp3 offers a baseline performance that can be increased independently of volume size, and it provides higher IOPS and throughput compared to gp2. This directly addresses the high disk I/O wait time. Upgrading the instance type (option C) may not resolve the I/O bottleneck if the volumes are the limiting factor.

Increasing snapshot frequency (option A) does not improve I/O performance. Disabling delta merge (option D) is not recommended and does not address disk I/O issues.

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

319

MCQeasy

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

A.Set up SAP Solution Manager to send metrics to CloudWatch via an API.

B.Install and configure the SAP HANA CloudWatch agent on the HANA server.

C.Use Amazon CloudWatch Logs to capture HANA trace files and create metric filters.

D.Enable AWS CloudTrail to log HANA database API calls.

AnswerB

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

320

MCQeasy

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

A.r5.24xlarge

B.c5.18xlarge

C.t3.2xlarge

D.x1e.32xlarge

AnswerD

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

Why this answer

The x1e.32xlarge instance is specifically designed and certified by SAP for production SAP HANA workloads on AWS. It offers 3.9 TB of memory and high storage throughput, meeting SAP's stringent memory-to-vCPU ratio and performance requirements for HANA databases.

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

321

MCQeasy

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

A.Amazon EBS gp3 or io2 volumes

B.Amazon S3

C.EC2 Instance Store

D.Amazon EFS

AnswerA

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

322

MCQhard

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

A.Oracle Data Guard for replication and Amazon Route 53 for DNS failover.

B.AWS Database Migration Service (DMS) for ongoing replication to a DR instance, and automated snapshots for fast recovery.

C.Amazon S3 cross-region replication for database files and a script to import them.

D.AWS Backup to take weekly snapshots and restore in the DR region.

AnswerB

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

323

MCQeasy

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

A.Purchase Reserved Instances for 1-year term.

B.Purchase Compute Savings Plans for 3-year term.

C.Run the instances as On-Demand without any schedule.

D.Use AWS Instance Scheduler to stop instances outside business hours.

AnswerD

Instance Scheduler automates shutdown, saving costs.

Why this answer

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

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

Practice this question →

324

MCQeasy

A company is running SAP ERP on AWS. The SAP application servers are in private subnets, and the database is in a separate private subnet. The company needs to allow the application servers to communicate with the database. Which AWS networking component should be configured to allow this traffic?

A.VPC Peering connection between subnets.

B.Internet Gateway

C.Network ACL with inbound rules for the database subnet.

D.Security Group rules allowing traffic between the security groups.

AnswerD

Security Groups allow stateful traffic between instances.

Why this answer

Security groups act as a virtual firewall for instances, and you can reference another security group as a source in inbound rules. This allows the application servers' security group to be specified as the source for the database security group's inbound rule, enabling traffic between the subnets without exposing the database to the entire subnet. This is the most secure and AWS-recommended method for controlling traffic between instances within the same VPC.

Exam trap

The trap here is that candidates often confuse Network ACLs (subnet-level, stateless) with Security Groups (instance-level, stateful) and incorrectly choose a Network ACL because they think it is required for inter-subnet traffic, not realizing that security groups can reference each other across subnets within the same VPC.

How to eliminate wrong answers

Option A is wrong because VPC Peering is used to connect two different VPCs, not subnets within the same VPC; subnets in the same VPC can already communicate via the VPC's internal routing table without any peering. Option B is wrong because an Internet Gateway is used to enable communication between a VPC and the internet, not for private traffic between subnets within the same VPC. Option C is wrong because a Network ACL is a stateless firewall that applies to an entire subnet, and while it can allow traffic, it is less granular and less secure than using security groups; the question specifically asks for allowing traffic between the application servers and the database, which is best achieved by security group rules that reference the application servers' security group.

Practice this question →

325

MCQhard

An SAP system on AWS is experiencing high write latency on the database layer. The DB is running on an r5.8xlarge instance with EBS gp2 volumes. The SAP team notices that the EBS volume write queue depth is frequently above 16. What is the MOST likely cause and what change should be made?

A.The instance type does not support EBS optimization. Switch to a network-optimized instance.

B.The EBS volume is not optimized for SAP. Use io1 with high provisioned IOPS.

C.The volume is too small for the workload. Increase the volume size to gain baseline IOPS.

D.The gp2 volume does not provide enough burst IOPS. Migrate to gp3.

AnswerC

Larger gp2 volumes have higher baseline IOPS, reducing queue depth.

Why this answer

Gp2 volume baseline IOPS scales linearly with size (3 IOPS per GiB). An r5.8xlarge instance supports EBS optimization, so the bottleneck is not the instance. With a write queue depth frequently above 16, the gp2 volume is likely too small to provide sufficient baseline IOPS, causing the queue to back up.

Increasing the volume size raises the baseline IOPS, reducing queue depth and write latency.

Exam trap

The trap here is that candidates assume high write queue depth always requires switching to provisioned IOPS (io1/io2) or gp3, when in fact simply increasing gp2 volume size to raise baseline IOPS is the most direct and cost-effective fix for a small gp2 volume.

How to eliminate wrong answers

Option A is wrong because the r5.8xlarge instance supports EBS optimization by default (dedicated bandwidth to EBS) and does not need to be switched to a network-optimized instance; the issue is volume-level, not instance-level. Option B is wrong because while io1 with high provisioned IOPS could solve the problem, it is not the 'most likely' cause — gp2 can be fixed by simply increasing volume size to gain baseline IOPS, which is a more direct and cost-effective first step. Option D is wrong because gp3 offers a baseline of 3000 IOPS regardless of size, but the question states the volume is 'too small' — increasing gp2 size is the most direct fix; migrating to gp3 might help but is not the most likely cause or the recommended first change given the specific symptom of small volume size.

Practice this question →

326

MCQeasy

A company is planning to migrate an SAP HANA database to AWS. They need to ensure that the instance type supports the required amount of memory and that the storage can handle high IOPS. Which AWS service can help determine the appropriate instance type and storage configuration based on the SAP workload requirements?

A.Amazon Inspector

B.AWS Config

C.AWS Pricing Calculator

D.AWS Trusted Advisor

AnswerC

It helps estimate costs and select instance types based on workload requirements.

Why this answer

AWS Pricing Calculator is the correct choice because it allows you to input specific SAP HANA workload requirements, such as memory size and expected IOPS, and then outputs a list of compatible EC2 instance types (e.g., x1e.32xlarge or u-6tb1.metal) and corresponding EBS or instance store configurations. It directly maps SAP-certified instance families and storage options to the required performance metrics, ensuring compliance with SAP's memory and IOPS guidelines.

Exam trap

The trap here is that candidates often confuse AWS Pricing Calculator with AWS Trusted Advisor, mistakenly thinking Trusted Advisor can recommend instance types for SAP workloads, when in fact it only provides generic best-practice checks and does not perform workload-specific sizing.

How to eliminate wrong answers

Option A is wrong because Amazon Inspector is a vulnerability management service that scans for software vulnerabilities and unintended network exposure, not for sizing or storage configuration. Option B is wrong because AWS Config is a service for evaluating, auditing, and recording resource configurations against rules, not for recommending instance types or storage based on workload requirements. Option D is wrong because AWS Trusted Advisor provides best-practice checks for cost optimization, security, fault tolerance, and performance limits, but it does not offer a workload-specific sizing tool for SAP HANA memory or IOPS requirements.

Practice this question →

327

Multi-Selecthard

Which THREE of the following are valid strategies for disaster recovery (DR) of SAP workloads on AWS? (Select THREE.)

Select 3 answers

A.Warm standby with a fully scaled-down environment that is manually scaled up during DR.

B.Pilot light environment with replicated data volumes that can be attached to EC2 instances in DR.

C.Regular backup of SAP systems to Amazon S3 and restore in another region.

D.SAP HANA System Replication across AWS Regions.

E.Multi-site active-active with real-time replication and automatic failover.

AnswersB, C, D

Pilot light uses replicated data that can be quickly activated.

Why this answer

A pilot light DR strategy for SAP on AWS involves replicating data volumes (e.g., using EBS snapshots or storage replication) to a secondary region and keeping a minimal set of core services running. In a disaster, EC2 instances are launched and the replicated volumes are attached, allowing the SAP application stack to be started quickly. This approach balances cost and recovery time by avoiding a fully scaled environment during normal operations.

Exam trap

The trap here is that candidates often confuse 'warm standby' with 'pilot light' because both involve a scaled-down environment, but the key distinction is that pilot light requires manual scaling of compute resources during DR, whereas warm standby typically runs a continuously running, reduced-capacity environment that can be promoted without manual scaling.

Practice this question →

328

MCQmedium

An SAP administrator is setting up a new SAP HANA system on AWS and needs to ensure that the system can recover from an Availability Zone failure. Which strategy should they implement for high availability?

A.Attach multiple Elastic Network Interfaces (ENIs) to the HANA instance

B.Configure the HANA database with Amazon RDS Multi-AZ

C.Set up HANA System Replication across two Availability Zones

D.Take EBS snapshots every hour and restore in another AZ

AnswerC

HANA System Replication synchronously replicates data to a secondary system in another AZ for HA.

Why this answer

HANA System Replication (HSR) is the native SAP mechanism for achieving high availability across Availability Zones (AZs). By replicating data synchronously or synchronously in-memory to a standby instance in a different AZ, it ensures automatic failover with minimal data loss in the event of an AZ failure. This directly meets the requirement for recovery from an AZ failure without relying on storage-level or database-agnostic approaches.

Exam trap

The trap here is that candidates confuse backup strategies (like EBS snapshots) with high availability, or mistakenly think that RDS Multi-AZ can be applied to SAP HANA, when in fact SAP HANA requires its own native replication mechanism (HSR) for cross-AZ failover.

How to eliminate wrong answers

Option A is wrong because attaching multiple Elastic Network Interfaces (ENIs) to a single HANA instance provides additional network bandwidth or separate network paths but does not provide any redundancy or failover capability for the instance itself; it cannot recover from an AZ failure. Option B is wrong because Amazon RDS Multi-AZ is a managed database service for relational databases like MySQL or PostgreSQL, not for SAP HANA, which requires a native SAP HANA deployment on EC2; RDS does not support SAP HANA as a database engine. Option D is wrong because taking EBS snapshots every hour and restoring in another AZ provides point-in-time recovery (backup) but not high availability; the recovery process is manual and can take significant time, resulting in up to one hour of data loss and unacceptable downtime for an HA solution.

Practice this question →

329

MCQeasy

A company wants to automate the installation of SAP HANA on AWS using CloudFormation. Which AWS service can provide a Quick Start for SAP HANA?

A.AWS Quick Start.

B.AWS Service Catalog.

C.AWS OpsWorks.

D.Amazon Elastic Kubernetes Service (EKS).

AnswerA

Quick Starts are reference deployments with CloudFormation templates.

Why this answer

AWS Quick Start is the correct service because it provides pre-built, automated reference deployments for SAP HANA on AWS, including CloudFormation templates that automate the installation and configuration of SAP HANA. This aligns directly with the requirement to use CloudFormation for automation, as Quick Starts are built on CloudFormation and include best-practice architectures.

Exam trap

The trap here is that candidates may confuse AWS Quick Start (a collection of reference deployments) with AWS Service Catalog (a governance tool), or assume that OpsWorks or EKS can handle SAP HANA automation, but SAP HANA requires specific OS-level tuning and direct EC2 access that container orchestration or configuration management tools do not natively provide.

How to eliminate wrong answers

Option B (AWS Service Catalog) is wrong because it is a service for creating and managing a catalog of approved IT services, not for providing pre-built Quick Start deployments for SAP HANA; it can deploy CloudFormation templates but does not itself provide the SAP HANA Quick Start. Option C (AWS OpsWorks) is wrong because it is a configuration management service using Chef or Puppet, not designed for automated SAP HANA installation via CloudFormation, and lacks pre-built SAP HANA templates. Option D (Amazon Elastic Kubernetes Service) is wrong because it is a container orchestration service for Kubernetes, not intended for deploying SAP HANA, which is a traditional enterprise application that requires direct EC2 instances with specific kernel parameters and HANA-optimized AMIs, not containers.

Practice this question →

330

MCQhard

A company is running SAP HANA on AWS. The HANA database is deployed on an r5.8xlarge instance. The company notices high CPU utilization on the instance during peak loads. The SAP team confirms that the HANA workload requires more CPU capacity. What is the most cost-effective way to increase CPU capacity without changing the instance family?

A.Add more EBS volumes with higher IOPS to offload CPU.

B.Launch additional r5.8xlarge instances and configure HANA scale-out.

C.Configure Auto Scaling to add instances during peak load.

D.Resize the instance to a larger instance type in the r5 family.

AnswerD

Larger instance type provides more CPU cores.

Why this answer

Resizing the instance to a larger type within the r5 family (e.g., r5.12xlarge or r5.16xlarge) directly increases vCPU and memory capacity without changing the instance family, which is the most cost-effective approach for a single-node SAP HANA deployment. This avoids the complexity, licensing costs, and network latency of scale-out configurations while meeting the CPU demand.

Exam trap

The trap here is that candidates may confuse SAP HANA's ability to scale out with the simpler and more cost-effective vertical scaling option, assuming that adding more instances is always the answer for increased CPU demand, when in fact resizing within the same family is the recommended approach for single-node workloads.

How to eliminate wrong answers

Option A is wrong because adding EBS volumes with higher IOPS does not offload CPU; it improves storage throughput but does not increase compute capacity, and CPU-bound workloads like SAP HANA are not alleviated by storage changes. Option B is wrong because launching additional r5.8xlarge instances for HANA scale-out introduces significant complexity, requires HANA scale-out licensing, and is less cost-effective than a single larger instance for a workload that simply needs more CPU on one node. Option C is wrong because Auto Scaling is not supported for SAP HANA; HANA is a stateful, in-memory database that cannot be horizontally scaled with Auto Scaling, and adding instances during peak load would break database consistency.

Practice this question →

331

MCQmedium

A company is designing a disaster recovery (DR) strategy for its SAP HANA database on AWS. The primary site is in us-east-1. The DR site must be in us-west-2. The company requires a Recovery Point Objective (RPO) of 15 minutes and a Recovery Time Objective (RTO) of 2 hours. Which AWS service should be used for replicating HANA data?

A.AWS Database Migration Service with ongoing replication.

B.Amazon EBS Snapshots copied to us-west-2 every hour.

C.Amazon S3 Cross-Region Replication for HANA data files.

D.SAP HANA System Replication to an EC2 instance in us-west-2.

AnswerD

HANA System Replication provides near real-time replication.

Why this answer

SAP HANA System Replication (HSR) is the native, SAP-supported mechanism for replicating HANA databases to a secondary site with low RPO (typically seconds to minutes) and RTO (minutes to hours). It continuously ships log entries from the primary to a standby EC2 instance in us-west-2, meeting the 15-minute RPO and 2-hour RTO requirements. AWS Database Migration Service, EBS Snapshots, and S3 Cross-Region Replication do not provide the log-level, consistent replication needed for SAP HANA's ACID compliance and failover semantics.

Exam trap

The trap here is that candidates often confuse generic data replication services (DMS, S3 CRR, EBS snapshots) with the SAP-native replication mechanism, failing to recognize that only HSR provides the log-level consistency and failover orchestration required for SAP HANA's strict RPO/RTO and ACID guarantees.

How to eliminate wrong answers

Option A is wrong because AWS DMS with ongoing replication is designed for heterogeneous database migrations and does not support SAP HANA as a target for continuous log-based replication; it cannot maintain the transactional consistency required for HANA failover. Option B is wrong because EBS Snapshots copied every hour cannot achieve a 15-minute RPO, and snapshots are crash-consistent but not application-consistent for HANA without additional pre-freeze steps, leading to potential data loss or corruption. Option C is wrong because S3 Cross-Region Replication operates at the file/object level and does not understand HANA's transaction logs or database state; replicating raw HANA data files would result in an inconsistent, unusable database upon recovery.

Practice this question →

332

MCQhard

A company is running SAP ERP on AWS and is experiencing high costs due to underutilized EC2 instances. The SAP system is non-production and can tolerate interruptions. Which approach would most cost-effectively reduce costs without compromising the ability to resume operations quickly?

A.Purchase Reserved Instances for the current usage to get a discount

B.Increase the instance size to improve performance and reduce runtime

C.Use EC2 Spot Instances for the application servers and configure them to be terminated gracefully

D.Use Dedicated Hosts to reduce licensing costs

AnswerC

Spot Instances offer significant cost savings and can be interrupted, which is acceptable for non-production systems.

Why this answer

EC2 Spot Instances offer significant cost savings (up to 90% compared to On-Demand) for fault-tolerant, non-production SAP workloads. By configuring graceful termination (e.g., using lifecycle hooks or AWS Systems Manager to drain SAP application server connections before the instance is interrupted), the system can resume quickly when capacity becomes available again, meeting the requirement for cost reduction without compromising rapid recovery.

Exam trap

The trap here is that candidates often assume Reserved Instances are always the best cost-saving option, but the question explicitly states the workload is non-production and can tolerate interruptions, making Spot Instances the most cost-effective choice despite their potential for interruption.

How to eliminate wrong answers

Option A is wrong because Reserved Instances require a 1- or 3-year commitment and are designed for steady-state, predictable usage; they do not address underutilization and would lock the company into paying for capacity that is not fully used. Option B is wrong because increasing instance size would raise costs further (larger instances cost more per hour) and does not solve underutilization; it may even increase idle resource waste. Option D is wrong because Dedicated Hosts are primarily used for licensing compliance (e.g., SAP per-socket licensing) and are more expensive than shared tenancy; they do not reduce costs for a non-production system that can tolerate interruptions.

Practice this question →

333

MCQeasy

A company is planning to run SAP NetWeaver on AWS and needs to ensure high availability for the database layer. Which AWS service can be used to achieve automatic failover of an SAP HANA database?

A.AWS Database Migration Service (DMS)

B.Application Load Balancer (ALB)

C.Amazon RDS Multi-AZ

D.SAP HANA System Replication (HSR)

AnswerD

HSR provides synchronous replication and automatic failover for HANA.

Why this answer

SAP HANA System Replication (HSR) is the native SAP mechanism for replicating data from a primary HANA database to one or more secondary systems, enabling automatic failover in the event of a primary failure. This is the correct approach for achieving high availability for SAP HANA on AWS, as it integrates with AWS services like Elastic IPs or Route53 for IP re-mapping during failover, and is fully supported by SAP for production workloads.

Exam trap

The trap here is that candidates may confuse Amazon RDS Multi-AZ (which provides automatic failover for managed databases) with SAP HANA's own replication mechanism, not realizing that SAP HANA is not a supported engine for RDS and must be self-managed on EC2.

How to eliminate wrong answers

Option A is wrong because AWS Database Migration Service (DMS) is designed for one-time or ongoing database migrations and replication between heterogeneous or homogeneous databases, not for automatic failover of an SAP HANA database in a high-availability cluster. Option B is wrong because an Application Load Balancer (ALB) operates at Layer 7 (HTTP/HTTPS) and cannot handle the proprietary SQL/MDX protocol or the TCP-level failover required for SAP HANA database connections. Option C is wrong because Amazon RDS Multi-AZ provides automatic failover for supported database engines like MySQL, PostgreSQL, Oracle, and SQL Server, but it does not support SAP HANA as a managed service; SAP HANA must be deployed on EC2 and managed by the customer.

Practice this question →

334

MCQeasy

An SAP administrator needs to back up the SAP HANA database daily to Amazon S3 using the Backint agent. What is the prerequisite for this integration?

A.Install the AWS Systems Manager Agent (SSM Agent) on the HANA host.

B.Create a backup vault in AWS Backup.

C.Mount an Amazon EFS file system to the HANA host for backup storage.

D.Configure AWS Database Migration Service (DMS) to replicate data to S3.

AnswerA

SSM Agent is required to run the Backint installation document.

Why this answer

The AWS Backint agent for SAP HANA requires the AWS Systems Manager Agent (SSM Agent) to be installed on the HANA host. The Backint agent uses SSM Agent to securely communicate with AWS Systems Manager, which orchestrates the backup workflow and enables the agent to write backup data directly to Amazon S3. Without the SSM Agent, the Backint agent cannot authenticate or transfer data to S3, making it a mandatory prerequisite.

Exam trap

The trap here is that candidates may assume AWS Backup is required for any backup to S3, but the Backint agent bypasses AWS Backup and writes directly to S3, making the SSM Agent the actual prerequisite.

How to eliminate wrong answers

Option B is wrong because creating a backup vault in AWS Backup is not a prerequisite for the Backint agent integration; AWS Backup is a separate service for centralized backup management, but the Backint agent writes directly to S3 without requiring AWS Backup. Option C is wrong because mounting an Amazon EFS file system is not required; the Backint agent streams backup data directly to S3 via the Backint API, not through a file system mount. Option D is wrong because AWS Database Migration Service (DMS) is used for database migration and continuous replication, not for backing up SAP HANA to S3 via the Backint agent; DMS does not integrate with the Backint protocol.

Practice this question →

335

MCQeasy

A company is migrating SAP ECC to AWS and needs to ensure low-latency connectivity between the SAP application and database servers. Which AWS service is most appropriate to achieve this?

A.VPC peering between the application and database subnets.

B.Placement groups for the application and database instances.

C.AWS Direct Connect to connect the application and database servers.

D.AWS Transit Gateway to connect the application and database subnets.

AnswerB

Cluster placement groups provide low-latency, high-throughput network.

Why this answer

Placement groups, specifically cluster placement groups, provide low-latency, high-throughput network connectivity by placing instances in a single Availability Zone within a low-latency, 10 Gbps network. This is ideal for SAP ECC where the application and database servers require consistent, sub-millisecond latency for optimal performance.

Exam trap

The trap here is that candidates confuse network connectivity services (VPC peering, Transit Gateway, Direct Connect) with compute-level placement strategies, assuming any 'connection' service can reduce latency, when only placement groups provide the physical proximity required for low-latency inter-instance communication.

How to eliminate wrong answers

Option A is wrong because VPC peering connects VPCs, not subnets within the same VPC, and does not inherently provide low-latency guarantees beyond normal VPC routing. Option C is wrong because AWS Direct Connect is a hybrid connectivity service for on-premises to AWS, not for inter-instance communication within the same AWS region. Option D is wrong because AWS Transit Gateway is a hub-and-spoke router for connecting multiple VPCs and on-premises networks, not a mechanism to reduce latency between instances in the same VPC.

Practice this question →

336

Multi-Selectmedium

A company is planning to migrate its SAP ERP system to AWS. The system requires high availability with automatic failover and minimal data loss. Which TWO strategies should the company implement to meet these requirements?

Select 2 answers

A.Implement daily snapshots of all SAP EBS volumes using AWS Backup.

B.Deploy the SAP ASCS instance in a Multi-AZ configuration using AWS services.

C.Configure SAP HANA System Replication with synchronous data replication and automatic takeover.

D.Use AWS Elastic Disaster Recovery to replicate the entire SAP environment to a different Region.

E.Use Amazon S3 cross-region replication for all SAP application files.

AnswersB, C

Multi-AZ provides automatic failover for the central services.

Why this answer

Deploying the SAP ASCS instance in a Multi-AZ configuration using AWS services (such as an Amazon RDS Multi-AZ DB instance for the SAP system database or a Multi-AZ deployment for the SAP Central Services) provides automatic failover to a standby instance in a different Availability Zone, ensuring high availability with minimal data loss. This setup leverages synchronous replication to keep the standby synchronized, so failover occurs without significant data loss.

Exam trap

The trap here is that candidates often confuse backup strategies (like snapshots or cross-region replication) with high-availability solutions, failing to recognize that automatic failover and minimal data loss require synchronous replication and active standby components, not periodic backups or asynchronous replication.

Practice this question →

337

MCQhard

A company runs its SAP HANA database on an EC2 instance with Amazon EBS volumes. The system is experiencing high write latency. The current EBS volume type is gp2. Which change should a solutions architect recommend to improve write performance for the SAP HANA data volume?

A.Use an io2 Block Express volume with sufficient IOPS.

B.Migrate the data to an instance store volume.

C.Change the volume type to gp3 with increased IOPS.

D.Use a Throughput Optimized HDD (st1) volume.

AnswerA

io2 Block Express provides high IOPS and low latency suitable for SAP HANA.

Why this answer

SAP HANA requires consistently low-latency, high-IOPS storage for its data volume. The io2 Block Express volume is the only EBS volume type that can deliver up to 256,000 IOPS per volume with sub-millisecond latency, meeting SAP HANA's demanding performance requirements. In contrast, gp2 volumes have burst limitations and cannot sustain the high write throughput needed for SAP HANA workloads.

Exam trap

The trap here is that candidates often choose gp3 (Option C) thinking increased IOPS alone solves latency, but they overlook that SAP HANA requires the specific io2 Block Express volume type for guaranteed low latency and durability, as gp3's performance can degrade under sustained high write loads due to its shared architecture.

How to eliminate wrong answers

Option B is wrong because instance store volumes are ephemeral and do not persist data across instance stops or terminations, making them unsuitable for SAP HANA's data volume which requires durability and high availability. Option C is wrong because gp3 volumes, while offering baseline IOPS up to 16,000, cannot match the ultra-low latency and high IOPS consistency of io2 Block Express, and SAP HANA explicitly requires io2 or io1 volumes for production workloads. Option D is wrong because Throughput Optimized HDD (st1) volumes are designed for sequential, throughput-intensive workloads and have poor random I/O performance, which is critical for SAP HANA's write operations.

Practice this question →

338

MCQmedium

An SAP administrator needs to back up an SAP HANA database running on an EC2 instance with EBS volumes. The backup must be consistent and restorable to any point in time. Which approach meets these requirements?

A.Use S3 lifecycle policies to transition backups to Glacier.

B.Take manual EBS snapshots of the database volumes before each backup.

C.Use AWS Backup with pre and post scripts for application-consistent snapshots and enable continuous backup.

D.Use AWS Backup with EBS snapshots every hour.

AnswerC

Pre/post scripts ensure consistency; continuous backup enables point-in-time recovery.

Why this answer

AWS Backup with pre and post scripts enables application-consistent snapshots by quiescing the SAP HANA database (via commands like hdbsql to trigger a snapshot or log flush) before taking the EBS snapshot, ensuring crash-consistent data. Enabling continuous backup (using AWS Backup's continuous backup and point-in-time recovery for EBS snapshots) allows restoration to any point in time within the retention window, meeting the requirement for point-in-time recovery.

Exam trap

The trap here is that candidates often assume any EBS snapshot (manual or scheduled) is sufficient for database backup, overlooking the need for application consistency and continuous point-in-time recovery, which are explicitly required for SAP HANA workloads.

How to eliminate wrong answers

Option A is wrong because S3 lifecycle policies to transition backups to Glacier only manage storage tiering of existing backups; they do not create backups or ensure application consistency or point-in-time recovery for SAP HANA. Option B is wrong because manual EBS snapshots without pre/post scripts do not quiesce the database, resulting in crash-consistent snapshots that may not be restorable to a consistent state for SAP HANA, and they cannot provide point-in-time recovery across multiple snapshots. Option D is wrong because AWS Backup with EBS snapshots every hour provides only periodic recovery points (hourly), not continuous point-in-time recovery, and without pre/post scripts the snapshots are not application-consistent.

Practice this question →

339

MCQmedium

An SAP HANA database is running on a Dedicated Host in us-east-1a. The system requires a disaster recovery site in us-west-2. What limitation does the use of a Dedicated Host impose on the DR setup?

A.The DR site must also use a Dedicated Host, which cannot be reserved in advance.

B.The DR site requires a separate Dedicated Host in us-west-2, increasing cost.

C.The Dedicated Host cannot be used with SAP HANA System Replication.

D.The HANA instance cannot be migrated to a different host, so DR is not possible.

AnswerB

Dedicated Hosts are per-AZ, so a new host is needed in the DR region.

Why this answer

A Dedicated Host in us-east-1a is a physical server dedicated to your use, and to set up disaster recovery in us-west-2, you must provision a separate Dedicated Host in that region. This increases costs as you are paying for two Dedicated Hosts instead of one, and the DR host cannot be shared or reserved in advance for a specific instance type without an active allocation.

Exam trap

The trap here is that candidates assume Dedicated Hosts are regionally bound or that DR can reuse the same host, but AWS requires a separate Dedicated Host per region, which directly impacts cost and provisioning planning.

How to eliminate wrong answers

Option A is wrong because Dedicated Hosts can be reserved in advance via a Dedicated Host Reservation, which offers a billing discount for a 1- or 3-year term; the limitation is not about inability to reserve but about the requirement for a separate host. Option C is wrong because SAP HANA System Replication works over the network and does not require both hosts to be on the same Dedicated Host; it can replicate across regions regardless of the underlying host type. Option D is wrong because HANA instances can be migrated to different hosts using AWS tools like AWS Launch Wizard or manual stop/start on a different Dedicated Host, and DR is fully possible with cross-region replication.

Practice this question →

340

MCQeasy

An SAP application on AWS needs to access an S3 bucket containing sensitive data. Which IAM policy element should be used to enforce encryption in transit?

A."Condition": {"Bool": {"aws:SecureTransport": "true"}}

B."Condition": {"StringEquals": {"s3:x-amz-server-side-encryption": "AES256"}}

C."Condition": {"Bool": {"aws:MultiFactorAuthPresent": true}}

D."Condition": {"IpAddress": {"aws:SourceIp": "10.0.0.0/8"}}

AnswerA

This ensures requests are made over HTTPS.

Why this answer

The `aws:SecureTransport` condition key in an IAM policy enforces that all requests to the S3 bucket must be made over HTTPS (TLS), ensuring encryption in transit. For an SAP application handling sensitive data, this prevents data exposure during transmission over the network. The `Bool` condition evaluates to `true` only when the request uses SSL/TLS.

Exam trap

The trap here is confusing encryption in transit (HTTPS/TLS) with encryption at rest (server-side encryption), leading candidates to select Option B, which addresses data encryption on disk, not during network transfer.

How to eliminate wrong answers

Option B is wrong because `s3:x-amz-server-side-encryption` enforces encryption at rest (server-side encryption with AES256), not encryption in transit. Option C is wrong because `aws:MultiFactorAuthPresent` enforces multi-factor authentication, which is an access control measure, not a transport encryption requirement. Option D is wrong because `aws:SourceIp` restricts requests based on IP address range, which controls network access but does not enforce encryption in transit.

Practice this question →

341

MCQmedium

A company is designing an SAP HANA workload on AWS. They need to ensure high availability for the SAP HANA database with automatic failover in case of an instance failure. Which AWS service should they use to achieve this?

A.Amazon RDS for SAP HANA

B.Pacemaker cluster on Amazon EC2 with EBS multi-attach

C.AWS Elastic Beanstalk

D.Amazon Route 53 health checks with DNS failover

AnswerB

Correct. Pacemaker coordinates failover using shared storage via EBS multi-attach.

Why this answer

Pacemaker is a high-availability cluster resource manager that, when combined with Amazon EC2 and EBS Multi-Attach, enables automatic failover for SAP HANA. EBS Multi-Attach allows the same EBS volume to be attached to multiple EC2 instances in the same Availability Zone, which is required for SAP HANA's shared-storage-based scale-up or scale-out HA configurations. This setup supports the SAP HANA system replication or storage replication failover mechanism, ensuring automatic recovery upon instance failure.

Exam trap

The trap here is that candidates confuse DNS-level failover (Route 53) with true database-level high availability, or assume a managed service like RDS exists for SAP HANA, when in fact SAP HANA on AWS requires self-managed clustering with Pacemaker and EBS Multi-Attach.

How to eliminate wrong answers

Option A is wrong because Amazon RDS for SAP HANA does not exist; AWS does not offer a managed RDS service for SAP HANA, and SAP HANA must be deployed on EC2 instances. Option C is wrong because AWS Elastic Beanstalk is a PaaS service for web applications and containers, not designed for running SAP HANA workloads or providing database-level high availability with automatic failover. Option D is wrong because Amazon Route 53 health checks with DNS failover only redirect traffic at the DNS level, which cannot handle the synchronous replication and automatic failover required for SAP HANA database instances; it lacks the cluster management and fencing capabilities needed for database-level HA.

Practice this question →

342

Multi-Selecthard

A company is using SAP S/4HANA on AWS and wants to optimize costs. Which THREE actions would help reduce costs without impacting performance? (Choose THREE.)

Select 3 answers

A.Implement automatic start/stop for development and test instances

B.Use AWS Compute Optimizer to right-size EC2 instances

C.Use Dedicated Hosts for better isolation

D.Replace io2 Block Express volumes with gp2 volumes

E.Purchase Reserved Instances for the production database server

AnswersA, B, E

Stopping instances when not in use reduces costs.

Why this answer

Development and test instances for SAP S/4HANA do not require 24/7 availability. Implementing automatic start/stop schedules using AWS Instance Scheduler or AWS Lambda reduces compute costs by up to 70% for these non-production instances without affecting production performance, as the instances are only active during business hours or testing windows.

Exam trap

The trap here is that candidates may confuse Dedicated Hosts with cost optimization, but Dedicated Hosts are primarily for licensing compliance and actually increase costs, while gp2 volumes are often mistakenly considered acceptable for SAP workloads despite their inability to meet the performance requirements of SAP S/4HANA.

Practice this question →

343

MCQmedium

A company is migrating its SAP Business Warehouse (BW) system to AWS. The source system runs on an on-premises IBM AIX server with an Oracle database. The target AWS environment will use SAP HANA as the database. The migration tool is SAP Software Provisioning Manager (SWPM). The company has a requirement to minimize downtime during the migration. The SAP BW system has 5 TB of data. The network bandwidth between on-premises and AWS is 1 Gbps. The migration team plans to use AWS Direct Connect for the data transfer. They estimate that the initial data load will take approximately 12 hours. However, the cutover window is limited to 8 hours. What should the migration team do to meet the cutover window?

A.Use AWS DataSync to accelerate the data transfer and then import into HANA.

B.Use SAP Landscape Transformation (SLT) to replicate data in real-time after the initial load, and then perform a final delta sync during the cutover window.

C.Perform a HANA system replication from the source to the target after the initial load.

D.Request a higher bandwidth Direct Connect connection to reduce the initial load time to under 8 hours.

AnswerB

SLT enables delta replication, reducing cutover time.

Why this answer

SAP Landscape Transformation (SLT) can replicate data in near real-time from the source Oracle database to the target SAP HANA using trigger-based replication. After the initial 12-hour data load is completed before the cutover window, SLT captures ongoing changes and applies them during the final delta sync within the 8-hour cutover window, minimizing downtime. This approach decouples the lengthy initial load from the limited cutover period, meeting the requirement.

Exam trap

The trap here is that candidates may assume increasing network bandwidth (Option D) is the only solution to meet the cutover window, overlooking the fact that the initial data load time is dominated by database export and import processing, not just network transfer speed.

How to eliminate wrong answers

Option A is wrong because AWS DataSync is designed for file-based data transfer, not for direct database replication into SAP HANA; it cannot handle the SAP-specific schema and delta synchronization required for a live migration. Option C is wrong because HANA system replication is a native HANA feature that requires both source and target to be SAP HANA databases, but the source is an Oracle database on IBM AIX, making this incompatible. Option D is wrong because even with increased bandwidth, the initial data load of 5 TB at 1 Gbps is constrained by the 12-hour estimate due to factors like disk I/O and database export overhead, not just network speed; requesting higher bandwidth alone cannot reduce the load time to under 8 hours.

Practice this question →

344

Multi-Selectmedium

Which TWO of the following are valid options for implementing high availability for SAP NetWeaver on AWS?

Select 2 answers

A.Use Amazon RDS Multi-AZ for SAP Central Services.

B.Use Amazon S3 for shared storage and configure manual failover.

C.Deploy two EC2 instances across Availability Zones with a shared file system (EFS) and a cluster manager.

D.Run SAP Central Services on a single large EC2 instance.

E.Use Windows Server Failover Cluster with Amazon FSx for Windows File Server.

AnswersC, E

This is a common HA pattern for SAP.

Why this answer

Deploying two EC2 instances across Availability Zones with a shared file system (Amazon EFS) and a cluster manager (e.g., Pacemaker for Linux or Windows Server Failover Cluster) provides the high-availability architecture required for SAP NetWeaver. The cluster manager monitors the SAP Central Services (ASCS/ERS) and automatically fails over to the standby instance if the primary fails, while EFS provides a shared, highly available file system that both instances can access. This setup meets SAP's HA guidelines for a multi-AZ deployment on AWS.

Exam trap

The trap here is that candidates often confuse SAP Central Services with a database layer and incorrectly assume RDS Multi-AZ can replace the need for a clustered ASCS/ERS setup, or they think S3 can serve as a shared file system for SAP, but S3 lacks the necessary file-locking and low-latency semantics required by SAP NetWeaver.

Practice this question →

345

Multi-Selecthard

Which THREE considerations are important when designing a SAP workload for high availability on AWS? (Select three.)

Select 3 answers

A.Use EBS Multi-Attach to share volumes between two EC2 instances

B.Deploy the SAP application across multiple Availability Zones

C.Run the SAP system on a single large instance

D.Use Amazon S3 for long-term backup storage

E.Configure SAP HANA System Replication between primary and standby

AnswersB, D, E

Deploying across multiple Availability Zones provides redundancy and failover capability, which is a core HA principle for SAP systems.

Why this answer

In SAP high availability on AWS, deploying across multiple Availability Zones (Option B) protects against AZ failures, SAP HANA System Replication (Option E) ensures database failover, and using Amazon S3 for long-term backup storage (Option D) is a critical component of disaster recovery, which is integral to overall high availability design. Option A (EBS Multi-Attach) is not a standard HA practice due to limitations with concurrent writes and cluster file system requirements; typical shared storage uses Amazon EFS or FSx. Option C (single large instance) provides no redundancy, thus is not HA.

Exam trap

The trap here is that candidates sometimes exclude backup strategies from high availability design, thinking they are separate from HA. However, backup and disaster recovery are integral to ensuring data availability in an HA architecture.

Practice this question →

346

MCQhard

An SAP system on AWS is experiencing high latency for database queries. The administrator notices that the EBS volume used for /hana/log has a baseline IOPS of 5000 but the workload requires 8000 IOPS. What should the administrator do to resolve this?

A.Enable EBS Multi-Attach

B.Enable volume bursting

C.Migrate to an io2 Block Express volume

D.Increase the volume size to gain additional baseline IOPS

AnswerD

Increasing gp3 volume size increases baseline IOPS proportionally.

Why this answer

Increasing the volume size of a gp3 or io1/io2 EBS volume directly increases its baseline IOPS performance. For gp3 volumes, baseline IOPS scales at a rate of 3 IOPS per GiB up to 16,000 IOPS, so increasing the volume size from approximately 1667 GiB (5000/3) to at least 2667 GiB (8000/3) would raise the baseline IOPS to 8000. This ensures consistent performance for /hana/log without relying on burst credits or migrating to a different volume type.

Exam trap

The trap here is that candidates may assume enabling bursting (Option B) solves sustained high IOPS requirements, but AWS EBS bursting is designed for spiky workloads and cannot guarantee consistent performance for a constant 8000 IOPS demand, whereas increasing volume size directly raises baseline IOPS for gp3 volumes.

How to eliminate wrong answers

Option A is wrong because EBS Multi-Attach allows a single volume to be attached to multiple EC2 instances, but it does not increase the IOPS capacity of the volume itself; it is designed for clustered applications like SAP HANA scale-out, not for resolving IOPS deficits. Option B is wrong because enabling volume bursting (available on gp2 volumes) relies on burst credits that can be exhausted, and the question specifies a baseline IOPS of 5000 (typical of gp3 or io1), where bursting is not the mechanism to sustain a constant 8000 IOPS workload; gp3 volumes do not use burst credits for IOPS. Option C is wrong because migrating to an io2 Block Express volume provides higher durability and IOPS per GiB, but it does not inherently grant additional baseline IOPS without also increasing the provisioned IOPS (which incurs cost) or volume size; the question's scenario requires a simple increase in baseline IOPS, which can be achieved by resizing the existing volume.

Practice this question →

347

MCQhard

An SAP application on AWS is experiencing high network latency and packet loss between the SAP application server and the SAP HANA database. The application and database are in the same AWS Region and Availability Zone. What is the most likely cause?

A.Jumbo frames are enabled on the application server but not on the database server.

B.The instances are not in a placement group.

C.TCP segmentation offloading (TSO) is enabled on the HANA database instance.

D.The Elastic Network Adapter (ENA) driver is not installed.

AnswerC

TSO can cause performance issues with HANA; it's recommended to disable it.

Why this answer

C is correct because TCP segmentation offloading (TSO) on the HANA database instance can cause the network interface to deliver oversized TCP segments to the SAP application server, which may not handle them correctly, leading to packet loss and high latency. This is a known issue in SAP on AWS environments where TSO offloads segmentation to the NIC, but if the receiving side lacks proper support or the network path has MTU mismatches, fragmentation and retransmissions occur.

Exam trap

The trap here is that candidates often assume jumbo frames or placement groups are the root cause of latency and packet loss, but the real issue is a TCP offload feature (TSO) causing segment size mismatches, which is a subtle but common problem in SAP HANA on AWS deployments.

How to eliminate wrong answers

Option A is wrong because jumbo frames (MTU 9001) are supported on both instances in the same Availability Zone, and enabling them on one but not the other would cause fragmentation only if the path MTU is mismatched, but the question states they are in the same AZ and the symptom is packet loss, not fragmentation; jumbo frames are actually recommended for SAP HANA to reduce overhead. Option B is wrong because placement groups improve network throughput and reduce latency by ensuring instances are in close proximity, but they are not required for low latency in the same AZ; the issue is packet loss, not placement. Option D is wrong because the ENA driver is essential for high-performance networking on supported instance types, but its absence would cause reduced throughput or connectivity issues, not specifically packet loss and high latency between two instances in the same AZ; the symptom described matches TSO misconfiguration.

Practice this question →

348

MCQmedium

An SAP system on AWS uses a large memory instance (x1e.32xlarge) for HANA. The administrator notices that the system is experiencing high swap usage. The HANA memory usage is at 90% of physical RAM. The instance has 4 TB of RAM, and the HANA data size is 3.8 TB. The administrator wants to avoid swap usage to maintain performance. Which solution should be implemented?

A.Migrate to a larger instance type, such as u-6tb1, with more RAM.

B.Enable swap space on the instance store volumes to offload memory pressure.

C.Optimize HANA column store compression to reduce memory footprint.

D.Increase the provisioned IOPS on the EBS volumes to reduce I/O latency.

AnswerA

More RAM eliminates need for swap.

Why this answer

The x1e.32xlarge instance has 4 TB of RAM, and with HANA using 90% (3.6 TB) and the data size at 3.8 TB, the memory is insufficient to hold the entire dataset, causing swap usage. Migrating to a u-6tb1 instance with 6 TB of RAM provides enough physical memory to accommodate the full HANA data footprint, eliminating the need for swap and maintaining performance.

Exam trap

The trap here is that candidates may think compression (Option C) is a quick fix, but they overlook that HANA's memory usage already includes compressed data, and the instance's RAM is simply too small for the dataset, making a larger instance the only viable solution.

How to eliminate wrong answers

Option B is wrong because enabling swap on instance store volumes does not resolve the root cause—it merely shifts swap to faster storage, but swap usage still degrades HANA performance due to latency. Option C is wrong because while column store compression can reduce memory footprint, the data size (3.8 TB) already exceeds physical RAM (4 TB), and compression gains are typically modest (20-30%), not enough to fit 3.8 TB into 3.6 TB of available memory. Option D is wrong because increasing EBS IOPS addresses I/O latency for storage operations, not memory pressure or swap usage, which is a RAM capacity issue.

Practice this question →

349

MCQmedium

A company is designing a disaster recovery (DR) strategy for SAP S/4HANA on AWS. The primary site is in us-east-1 and the DR site is in us-west-2. The SAP HANA database is 2 TB and requires Recovery Point Objective (RPO) of 15 minutes and Recovery Time Objective (RTO) of 4 hours. Which solution meets these requirements?

A.Use AWS S3 Cross-Region Replication to copy database backups every 15 minutes.

B.Configure SAP HANA System Replication (HSR) to an EC2 instance in us-west-2 with log replication in sync mode.

C.Take EBS snapshots of the HANA data volume every hour and copy them to us-west-2.

D.Use AWS Database Migration Service (DMS) to continuously replicate changes to a HANA instance in us-west-2.

AnswerB

HSR provides near real-time replication, meeting RPO.

Why this answer

SAP HANA System Replication (HSR) with synchronous log replication meets the RPO of 15 minutes and RTO of 4 hours because it continuously replicates transaction logs to the DR site in us-west-2, ensuring near-zero data loss. In sync mode, the primary waits for the secondary to acknowledge log writes, which keeps the DR database consistent and ready for takeover within minutes, well under the 4-hour RTO. This is the only option that provides continuous, database-level replication with the required recovery objectives.

Exam trap

The trap here is that candidates often confuse asynchronous backup-based solutions (like S3 CRR or EBS snapshots) with continuous replication, failing to recognize that only SAP HANA System Replication provides the sub-15-minute RPO and fast failover required for enterprise SAP DR scenarios.

How to eliminate wrong answers

Option A is wrong because S3 Cross-Region Replication (CRR) copies objects asynchronously and can take minutes to hours to propagate, making it impossible to guarantee a 15-minute RPO; additionally, it only replicates backup files, not live database changes, so recovery would require restoring from those backups, which exceeds the 4-hour RTO. Option C is wrong because EBS snapshots taken every hour cannot achieve a 15-minute RPO, and copying snapshots across regions adds further delay; moreover, restoring from snapshots requires stopping the database and replaying logs, which typically takes longer than 4 hours for a 2 TB HANA database. Option D is wrong because AWS DMS does not support SAP HANA as a target for continuous change data capture (CDC) replication in a way that maintains transactional consistency for HSR; DMS is designed for heterogeneous migrations, not for real-time HANA-to-HANA replication with the required RPO/RTO.

Practice this question →

350

MCQmedium

A company is migrating its SAP ERP system to AWS and wants to use storage that offers the highest IOPS for the SAP HANA database. Which storage option should be used?

A.General Purpose SSD (gp3) volumes

B.Provisioned IOPS SSD (io2) volumes

C.Instance Store volumes

D.Throughput Optimized HDD (st1) volumes

AnswerB

io2 volumes provide the highest IOPS and are recommended for production SAP HANA databases.

Why this answer

For SAP HANA databases on AWS, the highest IOPS is achieved using Provisioned IOPS SSD (io2) volumes, which are designed for latency-sensitive, I/O-intensive workloads. io2 volumes offer up to 256,000 IOPS per volume with 99.999% durability, making them the optimal choice for SAP HANA's demanding performance requirements.

Exam trap

The trap here is that candidates often confuse General Purpose SSD (gp3) as sufficient for SAP HANA due to its lower cost, but fail to recognize that SAP HANA's certified configurations on AWS explicitly require io1/io2 volumes for production workloads to meet the strict IOPS and latency SLAs.

How to eliminate wrong answers

Option A is wrong because General Purpose SSD (gp3) volumes provide a baseline of 3,000 IOPS with a maximum of 16,000 IOPS per volume, which is insufficient for the high IOPS demands of SAP HANA. Option C is wrong because Instance Store volumes are ephemeral and do not persist data across instance stops or terminations, making them unsuitable for a production SAP HANA database that requires durable, persistent storage. Option D is wrong because Throughput Optimized HDD (st1) volumes are designed for throughput-intensive workloads with low IOPS (maximum 500 IOPS per volume) and are not suitable for the random I/O patterns and high IOPS requirements of SAP HANA.

Practice this question →

351

MCQhard

An SAP administrator is troubleshooting a performance issue on an SAP HANA database running on an r5.24xlarge instance. The database is I/O bound during high load periods. The administrator has already verified that the EBS volumes are not saturated. What should the administrator check next?

A.Verify that EBS optimization is enabled

B.Increase the SWAP space on the instance

C.Upgrade to a compute-optimized instance like c5.24xlarge

D.Check the Elastic Network Adapter (ENA) settings and consider tuning the ring buffer size

AnswerD

Tuning ENA can improve network throughput, which may be the bottleneck for I/O bound operations.

Why this answer

On an r5.24xlarge instance, EBS optimization is always enabled by default, so verifying it again is unnecessary. The issue is I/O bound during high load, but EBS volumes are not saturated, indicating the bottleneck is likely at the network layer. The Elastic Network Adapter (ENA) ring buffer size can become overwhelmed under high network traffic, causing packet drops and increased latency, which manifests as I/O wait.

Tuning the ring buffer size (e.g., using `ethtool -G eth0 rx 4096 tx 4096`) can reduce drops and improve throughput for SAP HANA's network-intensive operations.

Exam trap

The trap here is that candidates assume EBS optimization must be manually verified or enabled, but on modern Nitro-based instances like r5, it is always active, so the real bottleneck is often the network adapter configuration.

How to eliminate wrong answers

Option A is wrong because EBS optimization is always enabled on r5.24xlarge instances by default; checking it again would not resolve an I/O performance issue when EBS volumes are not saturated. Option B is wrong because increasing SWAP space would only help with memory pressure, not I/O-bound performance; in fact, swapping can worsen I/O issues by adding disk writes. Option C is wrong because upgrading to a compute-optimized instance like c5.24xlarge would reduce CPU resources (c5 instances have fewer vCPUs and less memory than r5 instances) and is not designed for memory-intensive SAP HANA workloads; the bottleneck is network-related, not CPU-related.

Practice this question →

352

MCQeasy

An SAP workload is running on an EC2 instance in a private subnet. The application needs to access an S3 bucket for backups. Which AWS service should be used to enable private connectivity without traversing the internet?

A.Internet Gateway

B.NAT Gateway

C.VPC Endpoint (Gateway)

D.AWS Site-to-Site VPN

AnswerC

Gateway VPC Endpoint provides private connectivity to S3 without internet.

Why this answer

A VPC Endpoint (Gateway) allows private connectivity between an EC2 instance in a private subnet and an S3 bucket without traversing the internet. It uses AWS’s internal network and route table entries to direct S3 traffic through the endpoint, ensuring data never leaves the AWS backbone. This is the correct choice for SAP workloads requiring secure, low-latency backups to S3.

Exam trap

The trap here is that candidates often confuse NAT Gateway with providing private connectivity, but NAT Gateway still routes traffic through the internet, whereas a VPC Endpoint keeps traffic entirely within the AWS network.

How to eliminate wrong answers

Option A is wrong because an Internet Gateway (IGW) is a horizontally scaled, redundant component that allows communication between a VPC and the internet, not private connectivity; it would expose the EC2 instance to the public internet. Option B is wrong because a NAT Gateway enables outbound internet access from a private subnet but still routes traffic through the internet, not private connectivity to S3; it also incurs additional data transfer costs. Option D is wrong because AWS Site-to-Site VPN connects on-premises networks to a VPC over the internet via IPsec tunnels, not for VPC-to-S3 private access; it is irrelevant for EC2-to-S3 communication within the same AWS region.

Practice this question →

353

MCQeasy

A company runs SAP Business Suite on an SAP HANA database on AWS. The database uses EBS gp2 volumes. The operations team notices high latency during peak hours. The metrics show that the volume queue depth is consistently above the recommended threshold. What is the MOST cost-effective change to reduce latency?

A.Migrate from gp2 to io2 EBS volumes with the same size.

B.Modify the volume to use Provisioned IOPS (io1) with a higher IOPS value.

C.Add an additional EBS volume and stripe the volumes using LVM.

D.Increase the size of the existing EBS gp2 volume to a larger size.

AnswerD

Larger gp2 volumes have higher baseline IOPS, reducing queue depth.

Why this answer

Increasing the size of an existing gp2 volume is the most cost-effective solution because gp2 volumes have a baseline performance of 3 IOPS per GB, and they can burst up to 3,000 IOPS for volumes up to 1,000 GB. By increasing the volume size, you raise the baseline IOPS, which reduces the queue depth without incurring the higher per-GB cost of io1 or io2 volumes. This directly addresses the high latency caused by queue depth exceeding the recommended threshold during peak hours.

Exam trap

The trap here is that candidates often assume Provisioned IOPS (io1/io2) is always the solution for high latency, but they overlook the cost-effective burst capability of gp2 volumes when increased in size.

How to eliminate wrong answers

Option A is wrong because migrating to io2 volumes with the same size would increase cost significantly (io2 has a higher per-GB price and requires provisioning IOPS separately) without being necessary—gp2 can achieve the needed performance by simply increasing size. Option B is wrong because modifying to io1 with a higher IOPS value would also increase cost unnecessarily; gp2's burst mechanism can handle peak loads if the volume size is increased, and io1 is generally more expensive than gp2 for equivalent performance. Option C is wrong because adding an additional EBS volume and striping with LVM does not inherently reduce queue depth on the original volume—it distributes I/O across multiple volumes but does not increase the IOPS or throughput of the existing gp2 volume, and it adds complexity without addressing the root cause of queue depth.

Practice this question →

354

MCQmedium

A company is running an SAP HANA database on AWS using an i3.16xlarge instance. The database storage is configured with multiple EBS gp2 volumes in a RAID 0 stripe to meet IOPS requirements. During a workload spike, the application experiences increased latency and the database performance degrades. The CloudWatch metrics show high Average Queue Length (avg_queue_len) on the EBS volumes but not 100% utilization of the CPU. Which design change is MOST likely to resolve the performance issue?

A.Replace gp2 volumes with io2 Block Express volumes to provide consistent IOPS performance.

B.Move the database to an i3en.24xlarge instance to increase network and EBS bandwidth.

C.Enable EBS optimization on the existing instance to improve throughput.

D.Add two additional gp2 volumes to the RAID 0 stripe to increase throughput.

AnswerA

io2 Block Express offers provisioned IOPS with sustained performance, eliminating burst credit exhaustion.

Why this answer

The high Average Queue Length indicates that the EBS volumes are saturating their IOPS capacity, causing requests to queue up. gp2 volumes have a burst-bucket model that can exhaust credits under sustained high I/O, leading to throttled performance. io2 Block Express volumes provide consistent, provisioned IOPS without burst limitations, directly resolving the queuing issue without requiring instance or stripe changes.

Exam trap

The trap here is that candidates assume adding more volumes to a RAID 0 stripe will linearly increase IOPS, but they overlook that gp2 volumes have a shared burst credit pool per volume and that the bottleneck is IOPS credit exhaustion, not throughput.

How to eliminate wrong answers

Option B is wrong because moving to an i3en.24xlarge increases network and EBS bandwidth, but the bottleneck is IOPS saturation on the EBS side, not instance bandwidth or CPU; the CPU is not fully utilized, so a larger instance does not address the root cause. Option C is wrong because EBS optimization is already enabled by default on i3.16xlarge instances; toggling it would not change the IOPS ceiling of gp2 volumes. Option D is wrong because adding more gp2 volumes to the RAID 0 stripe increases total throughput (MB/s) but does not increase the per-volume IOPS credit pool or eliminate the burst-bucket exhaustion; the queue length will still spike once credits are depleted.

Practice this question →

355

Multi-Selectmedium

Which TWO options are best practices for securing SAP systems on AWS?

Select 2 answers

A.Enable encryption at rest for EBS volumes and RDS databases

B.Use the AWS account root user for daily administration

C.Place SAP application servers in a public subnet with direct internet access

D.Store SAP transport files in a public S3 bucket

E.Use security groups to control traffic to SAP instances

AnswersA, E

Encryption protects data at rest.

Why this answer

Enabling encryption at rest for EBS volumes and RDS databases ensures that SAP data stored on disk is protected using AWS Key Management Service (KMS) or a customer-managed key. This is a fundamental security best practice to meet compliance requirements and protect sensitive SAP data from unauthorized access if the underlying storage is compromised.

Exam trap

The trap here is that candidates often confuse the root user's power with convenience, or assume public subnets are acceptable for SAP application servers if a security group is applied, but the exam strictly requires private subnets and no direct internet exposure for production SAP systems.

Practice this question →

356

MCQeasy

A company plans to migrate their SAP HANA database to AWS. They require the highest availability with automatic failover in case of an AZ failure. Which architecture should they use?

A.Multi-AZ with HANA System Replication in sync mode and automatic failover.

B.Single AZ with HANA System Replication to a standby in the same AZ.

C.Single AZ with daily backups to Amazon S3.

D.Multi-AZ with HANA System Replication in async mode and manual failover.

AnswerA

Provides automatic failover across AZs.

Why this answer

It meets the requirement for highest availability with automatic failover in case of an AZ failure. HANA System Replication (HSR) in synchronous mode ensures zero data loss (RPO=0) by committing transactions only after they are replicated to the standby, and when combined with Multi-AZ deployment, it provides automatic failover across Availability Zones. This architecture is the AWS-recommended pattern for SAP HANA high availability, leveraging the AWS Multi-AZ concept with HSR's built-in automatic takeover capability.

Exam trap

The trap here is that candidates often confuse 'high availability' with 'disaster recovery' and select a backup-only option (C) or a Single AZ option (B), failing to recognize that automatic failover across AZs requires both Multi-AZ deployment and synchronous replication with automated takeover.

How to eliminate wrong answers

Option B is wrong because Single AZ deployment cannot protect against an AZ failure; if the entire AZ goes down, both primary and standby are lost. Option C is wrong because daily backups to Amazon S3 provide disaster recovery (point-in-time recovery) but do not offer automatic failover or high availability; recovery time can be hours, not seconds. Option D is wrong because HSR in async mode may result in data loss (RPO > 0) during a failover, and manual failover does not meet the 'automatic failover' requirement stated in the question.

Practice this question →

357

MCQmedium

A company is migrating its SAP HANA database to AWS. The SAP HANA database requires high throughput and low latency for data persistence. Which AWS storage solution should be used for the HANA data volume to meet performance requirements?

A.Use Amazon FSx for Lustre as primary persistent storage for HANA data.

B.Use Provisioned IOPS SSD (io1 or io2) EBS volumes for the data volume.

C.Use General Purpose SSD (gp2) EBS volumes for the data volume.

D.Use Throughput Optimized HDD (st1) EBS volumes for the data volume.

AnswerB

io1/io2 volumes provide consistent low latency and high IOPS for HANA.

Why this answer

SAP HANA is an in-memory database that relies on persistent storage for data volume writes during savepoints and log writes. Provisioned IOPS SSD (io1 or io2) EBS volumes deliver consistent, low-latency performance with configurable IOPS, which is required to meet SAP HANA's strict throughput and latency SLAs. AWS specifically certifies io1/io2 EBS volumes for SAP HANA data volumes in production environments.

Exam trap

The trap here is that candidates often confuse high-throughput file systems like FSx for Lustre with block storage requirements for databases, or assume that gp2's burst capability is sufficient for sustained SAP HANA workloads without considering the burst credit exhaustion under continuous load.

How to eliminate wrong answers

Option A is wrong because Amazon FSx for Lustre is a high-performance file system designed for HPC and batch processing, not for persistent database storage; it lacks the block-level consistency and durability guarantees required for SAP HANA data volumes. Option C is wrong because General Purpose SSD (gp2) EBS volumes use a burst-bucket model that cannot sustain high IOPS under continuous load, leading to latency spikes during savepoints. Option D is wrong because Throughput Optimized HDD (st1) volumes are optimized for sequential throughput, not random I/O, and have high latency that violates SAP HANA's performance requirements.

Practice this question →

358

MCQhard

An SAP system on AWS is experiencing high latency in database transactions. The SAP HANA database is running on an r5.24xlarge instance with GP3 EBS volumes. CloudWatch metrics show high Write IOPS but low Read IOPS. The application team expects high write throughput. What should be changed to improve write performance?

A.Increase the EBS read throughput

B.Use a larger instance type like r6i.32xlarge

C.Increase the GP3 volume IOPS

D.Switch to io2 Block Express volumes with higher IOPS

AnswerD

io2 provides consistent high IOPS for write-heavy workloads.

Why this answer

The workload requires high write throughput, and GP3 volumes have a baseline IOPS of 16,000 with a maximum of 16,000 IOPS at no additional cost, but burst credits are limited. io2 Block Express volumes offer up to 256,000 IOPS with consistent sub-millisecond latency, which directly addresses the high write IOPS demand without throttling. This aligns with SAP HANA's requirement for predictable, high-performance storage for database transactions.

Exam trap

The trap here is that candidates assume increasing GP3 IOPS (Option C) is sufficient, but they overlook that GP3's maximum IOPS (16,000) and throughput limits may still be inadequate for sustained high write throughput, whereas io2 Block Express is the only option that guarantees both high IOPS and low latency for SAP HANA workloads.

How to eliminate wrong answers

Option A is wrong because increasing EBS read throughput does not address high write IOPS; read throughput is irrelevant to write performance. Option B is wrong because upgrading to a larger instance type like r6i.32xlarge increases compute and memory but does not resolve EBS volume-level IOPS limitations; the bottleneck is storage, not instance capacity. Option C is wrong because GP3 volumes have a maximum IOPS of 16,000 (with additional cost up to 16,000 IOPS), which may still be insufficient for high write throughput; GP3 also has a throughput limit of 1,000 MiB/s, and increasing IOPS alone does not guarantee sustained write performance under heavy load.

Practice this question →

359

MCQmedium

An SAP Basis administrator is troubleshooting a performance issue on an SAP HANA database running on AWS. The database is on an EC2 instance of type r5.12xlarge with 8 x 1 TB EBS io2 Block Express volumes configured for maximum IOPS. The application team reports that batch jobs are taking longer than expected. The administrator checks Amazon CloudWatch metrics and sees that the EBS write latency averages 2 ms, which is within the expected range. However, the CPU utilization is at 95% consistently during batch runs. The HANA index server is using 70% of the CPU. The administrator also notices that the HANA threads are mostly waiting on 'lock wait' events. What is the MOST likely cause of the performance issue?

A.The EBS volumes are not providing enough IOPS for the workload.

B.The HANA parameter 'max_concurrency' is set too low.

C.There are SQL statement contention and locking issues in the HANA database.

D.The EC2 instance type is undersized for the HANA workload.

AnswerC

Lock waits indicate contention, often from poor SQL or application design.

Why this answer

The high CPU utilization (95%) combined with HANA threads waiting on 'lock wait' events indicates that SQL statement contention and locking issues are the primary bottleneck. Lock waits occur when multiple transactions compete for the same database resources, causing threads to spin or block, which consumes CPU cycles without making progress. This explains why CPU is saturated despite EBS write latency being normal (2 ms) and IOPS being sufficient.

Exam trap

The trap here is that candidates may attribute high CPU utilization to an undersized instance or insufficient IOPS, when in fact the CPU is busy spinning on lock waits, a classic symptom of application-level contention rather than infrastructure limits.

How to eliminate wrong answers

Option A is wrong because EBS write latency is only 2 ms, which is well within the expected range for io2 Block Express volumes, and the volumes are configured for maximum IOPS, so IOPS is not the bottleneck. Option B is wrong because 'max_concurrency' controls the number of parallel query execution threads, but lock waits are caused by contention on database objects (e.g., rows, tables), not by a limit on concurrency; lowering max_concurrency would reduce parallelism but not resolve lock contention. Option D is wrong because an r5.12xlarge instance provides 48 vCPUs and 384 GB of memory, which is a standard size for SAP HANA workloads, and the CPU is being fully utilized due to lock contention rather than being undersized for the workload.

Practice this question →

360

MCQhard

An SAP administrator notices that the SAP application server performance degrades during peak hours. The application servers are running on EC2 instances with gp2 EBS volumes. The administrator suspects the EBS volumes are experiencing burst bucket depletion. Which action should the administrator take to improve performance?

A.Change the volume type to gp3 and adjust the IOPS and throughput settings.

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

C.Move the data to instance store volumes for better performance.

D.Change the volume type to io1 and provision high IOPS.

AnswerA

gp3 provides baseline performance without burst credits.

Why this answer

The gp2 volume type uses a credit-based burst model where performance degrades once the burst bucket is depleted, especially under sustained high I/O. Changing to gp3 provides a baseline performance that does not rely on burst credits, and you can independently provision higher IOPS and throughput without increasing storage size, directly addressing the performance degradation during peak hours.

Exam trap

The trap here is that candidates may assume increasing gp2 volume size (Option B) is the only way to improve baseline IOPS, overlooking that gp3 provides a simpler, more cost-effective solution that directly addresses burst bucket depletion without requiring storage resizing.

How to eliminate wrong answers

Option B is wrong because increasing the size of gp2 volumes raises the baseline IOPS (at 3 IOPS per GB), but this is an indirect and potentially costly approach that still relies on burst credits for peak performance; it does not eliminate the burst bucket depletion issue. Option C is wrong because instance store volumes are ephemeral and data is lost on instance stop/termination, making them unsuitable for persistent SAP application data; they also do not solve the burst bucket depletion problem. Option D is wrong because io1 volumes are a provisioned IOPS SSD type that can provide consistent performance, but they are more expensive than gp3 and require manual provisioning of IOPS; gp3 is the more cost-effective and modern alternative that also avoids burst bucket depletion.

Practice this question →

361

MCQmedium

An SAP administrator wants to automate the creation of a DR environment for SAP HANA on AWS. The DR site should be in a different region and must be started only during a disaster. Which AWS service should be used to orchestrate the DR process?

A.AWS Systems Manager Automation to run DR scripts.

B.AWS CloudFormation StackSets to deploy the environment in the DR region.

C.Amazon S3 Cross-Region Replication to replicate SAP application data.

D.AWS Elastic Disaster Recovery (DRS) to replicate and orchestrate failover.

AnswerD

Elastic Disaster Recovery provides automated replication and orchestrated failover.

Why this answer

AWS Elastic Disaster Recovery (DRS) is the correct service because it provides continuous block-level replication for SAP HANA servers and includes built-in orchestration for failover and failback. This allows the DR environment to remain stopped until a disaster occurs, minimizing costs while ensuring rapid recovery.

Exam trap

The trap here is that candidates often confuse infrastructure deployment (CloudFormation) or data replication (S3 CRR) with the need for a fully orchestrated DR solution that includes both replication and automated failover, which only AWS DRS provides.

How to eliminate wrong answers

Option A is wrong because AWS Systems Manager Automation is designed for operational tasks like patching and configuration, not for orchestrating full DR failover with continuous replication and automated recovery. Option B is wrong because AWS CloudFormation StackSets deploy infrastructure templates across multiple accounts/regions but do not handle data replication, state management, or the orchestrated failover process required for SAP HANA DR. Option C is wrong because Amazon S3 Cross-Region Replication only replicates objects in S3 buckets, not the block-level storage volumes or SAP HANA database files needed for a complete DR environment.

Practice this question →

362

Matchingmedium

Match the SAP system type to its typical AWS deployment pattern.

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

Concepts

Matches

Single small instance, no HA

Medium instances, minimal redundancy

Medium instances, some HA

Large instances, multi-AZ, HA and DR

Why these pairings

SAP production systems require high availability and are typically deployed across multiple AZs. Development and sandbox systems have lower availability needs and are often in single AZs.

Practice this question →

363

Multi-Selecteasy

Which TWO are best practices for designing high availability for SAP NetWeaver on AWS? (Choose two.)

Select 2 answers

A.Use T2 or T3 burstable instances for cost savings.

B.Deploy SAP ASCS and PAS instances in separate Availability Zones.

C.Use EBS Multi-Attach volumes for the SAP application data.

D.Configure multiple Application Load Balancers in a failover configuration.

E.Use an Elastic Load Balancer to distribute traffic to multiple Web Dispatchers.

AnswersB, E

Multiple AZs provide failover if one AZ becomes unavailable.

Why this answer

Deploying SAP ASCS (ABAP SAP Central Services) and PAS (Primary Application Server) instances in separate Availability Zones ensures that if one AZ fails, the other can continue processing, providing high availability. This aligns with AWS best practices for SAP NetWeaver, which recommend distributing critical SAP components across AZs to achieve a Recovery Time Objective (RTO) of minutes and a Recovery Point Objective (RPO) of near-zero using SAP enqueue replication and failover mechanisms.

Exam trap

The trap here is that candidates often confuse high availability with cost optimization or assume that burstable instances are suitable for SAP production workloads, ignoring SAP's strict performance and certification requirements.

Practice this question →

364

MCQmedium

A company runs SAP on AWS with an SAP HANA database on a single EC2 instance. They want to implement a disaster recovery solution with a recovery time objective (RTO) of 15 minutes and a recovery point objective (RPO) of 1 hour. The DR site is in a different AWS Region. Which approach meets these requirements?

A.Set up an automated process to copy the EC2 instance AMI to the DR Region every hour.

B.Use Amazon S3 Cross-Region Replication to replicate the HANA data directory to the DR Region.

C.Perform periodic HANA database backups to S3 and restore in the DR Region when needed.

D.Configure SAP HANA System Replication to a secondary instance in the DR Region and use automated EBS snapshots for cross-Region replication.

AnswerD

HANA System Replication plus cross-Region snapshots meets RPO and RTO.

Why this answer

SAP HANA System Replication provides synchronous or asynchronous data replication to a secondary instance in another AWS Region, meeting the RPO of 1 hour and RTO of 15 minutes when combined with automated EBS snapshots for cross-Region replication. This approach ensures near-continuous database replication and rapid failover, while EBS snapshots provide additional consistency and recovery points.

Exam trap

The trap here is that candidates often confuse backup-based approaches (like AMI copies or S3 backups) with true replication, failing to recognize that only SAP HANA System Replication provides the low RTO and RPO required for disaster recovery in a different AWS Region.

How to eliminate wrong answers

Option A is wrong because copying an EC2 AMI every hour does not provide database-consistent recovery points; AMIs capture the entire instance state but cannot guarantee HANA transaction consistency, and the RPO of 1 hour is not reliably met due to AMI creation time. Option B is wrong because Amazon S3 Cross-Region Replication replicates objects at the S3 bucket level, not the HANA data directory; it does not ensure database consistency or support point-in-time recovery for HANA. Option C is wrong because periodic HANA backups to S3, while useful for backup, cannot achieve an RTO of 15 minutes due to the time required to restore a full database backup in the DR Region, and the RPO of 1 hour may be missed if backup intervals are not precisely aligned.

Practice this question →

365

MCQeasy

A company runs SAP Business Suite on AWS. The database size is 2 TB. They need to restore the database to a point-in-time from the last 24 hours. Which AWS service should be used to achieve this with minimal impact on production performance?

A.Use AWS Backup with a backup plan for the EC2 instance.

B.Use Amazon EBS snapshots of the database volume.

C.Configure SAP HANA Backup & Recovery using Backint agent to Amazon S3.

D.Use AWS Database Migration Service (DMS) for continuous replication.

AnswerC

Backint allows online backups to S3 with point-in-time recovery.

Why this answer

SAP HANA Backup & Recovery using the Backint agent to Amazon S3 is the native, AWS-integrated method for performing point-in-time recovery (PITR) of SAP HANA databases. Backint offloads backup and restore operations directly to S3, bypassing the EC2 instance's I/O stack, which minimizes performance impact on production workloads. This approach supports incremental and log backups, enabling precise PITR within the last 24 hours without requiring full-volume snapshots.

Exam trap

The trap here is that candidates often confuse crash-consistent EBS snapshots (Option B) with application-consistent backups, failing to recognize that SAP HANA requires log-based PITR via Backint to avoid database corruption and minimize production impact.

How to eliminate wrong answers

Option A is wrong because AWS Backup for EC2 instances performs full machine-level backups, which are not database-consistent for SAP HANA without pre- and post-scripts, and cannot provide granular point-in-time recovery at the database level. Option B is wrong because Amazon EBS snapshots capture the entire volume state, but they are crash-consistent, not application-consistent, and restoring a 2 TB database from snapshots would require stopping the database and could take hours, causing significant production impact. Option D is wrong because AWS Database Migration Service (DMS) is designed for continuous replication and migration between database engines, not for native SAP HANA backup and restore; it does not support point-in-time recovery of SAP HANA databases and would introduce latency and schema conversion issues.

Practice this question →

366

Multi-Selecthard

A company runs SAP on AWS and needs to monitor the performance of its SAP HANA database. The operations team wants to receive alerts when the CPU utilization exceeds 90% for more than 5 minutes. Which TWO steps should be taken to set up this monitoring and alerting?

Select 2 answers

A.Configure an Amazon SNS topic to send email or SMS notifications when the alarm state is reached.

B.Create a CloudWatch alarm that triggers when CPU utilization exceeds 90% for 5 consecutive minutes.

C.Create a CloudWatch metric filter on the HANA host's CPU utilization.

D.Enable CloudWatch Logs for the SAP application logs to detect performance issues.

E.Install the SAP Host Agent on the HANA instance and configure it to send metrics to SAP Solution Manager.

AnswersA, B

Correct. Amazon SNS is used to send notifications from CloudWatch alarms. Configuring an SNS topic for email or SMS alerts the operations team when the CPU utilization alarm triggers.

Why this answer

Amazon SNS is the standard AWS service for distributing notifications from CloudWatch alarms. By configuring an SNS topic to send email or SMS, the operations team receives alerts when the CPU utilization alarm triggers. Option B is correct because a CloudWatch alarm can be created to monitor the EC2 instance's CPU utilization metric directly; no metric filter is needed.

Option C is not required: CPU utilization is a pre-existing EC2 metric, not a log-based metric, so a metric filter is unnecessary. Option D is wrong because SAP application logs are not needed for CPU utilization monitoring. Option E is wrong because SAP Host Agent is not required for basic CloudWatch monitoring; CloudWatch and SNS provide a simpler native solution.

Exam trap

The trap is that candidates may assume they need to create a CloudWatch metric filter to capture CPU utilization, but CPU utilization is a standard EC2 metric available by default in CloudWatch. No metric filter is needed.

Practice this question →

367

MCQeasy

A company is migrating an SAP S/4HANA system to AWS and needs to choose the storage for the HANA database. The database requires high IOPS and low latency. Which AWS storage solution is most suitable?

A.Amazon EFS

B.Amazon EBS io2 Block Express volumes

C.Amazon S3

D.Amazon EBS st1 volumes

AnswerB

Amazon EBS io2 Block Express volumes deliver up to 256,000 IOPS per volume with single-digit millisecond latency, satisfying the SAP HANA database’s requirement for high IOPS and low latency. This is achieved through a dedicated Nitro system controller that bypasses the hypervisor for storage I/O, reducing jitter and ensuring consistent performance for latency-sensitive SAP workloads.

Why this answer

Amazon EBS io2 Block Express volumes are designed for mission-critical SAP HANA workloads, offering up to 256,000 IOPS per volume and sub-millisecond latency. They provide 99.999% durability and are the only EBS volume type certified by SAP for production HANA databases on AWS, meeting the high IOPS and low latency requirements.

Exam trap

The trap here is that candidates often confuse high-throughput HDD volumes (st1) with high-IOPS requirements, or mistakenly think that any EBS volume type can support SAP HANA, but only io2 Block Express meets SAP's certification and the specific low-latency, high-IOPS demands.

How to eliminate wrong answers

Option A is wrong because Amazon EFS is a shared file system (NFS) that does not provide the consistent, low-latency block-level IOPS required for SAP HANA database storage; it is suitable for shared file storage, not database volumes. Option C is wrong because Amazon S3 is an object storage service with higher latency and no support for database block-level operations; it cannot be used as the primary storage for a running HANA database. Option D is wrong because Amazon EBS st1 volumes are throughput-optimized HDD volumes designed for large, sequential workloads like big data and log processing, not for the high IOPS and low latency needed by SAP HANA; they cannot meet the performance requirements.

Practice this question →

368

Multi-Selectmedium

Which TWO of the following are best practices for securing SAP workloads on AWS?

Select 2 answers

A.Use IAM roles to grant EC2 instances access to AWS services.

B.Use security groups to control traffic to SAP application servers.

C.Disable encryption in transit between application and database tiers.

D.Allow SSH access from the internet for administration.

E.Store SAP backup files in a public S3 bucket for easy access.

AnswersA, B

IAM roles are secure and avoid storing credentials.

Why this answer

IAM roles allow EC2 instances to securely access AWS services (e.g., S3, DynamoDB) without embedding long-term credentials. By attaching an IAM role to an EC2 instance, the instance can obtain temporary credentials via the instance metadata service, which is a best practice for securing SAP workloads on AWS.

Exam trap

The trap here is that candidates might think disabling encryption in transit is acceptable for performance reasons, but AWS best practices mandate encryption in transit for all SAP data flows, especially between application and database tiers.

Practice this question →

369

MCQhard

An SAP administrator runs the command shown in the exhibit. The volume is attached to an EC2 instance. The administrator plans to increase the volume size to 1000 GiB. After resizing, the volume type remains gp2. What is the expected baseline IOPS for the resized volume?

A.4500 IOPS

B.16,000 IOPS

C.3000 IOPS

D.1500 IOPS

AnswerC

Baseline IOPS = 3 * 1000 = 3000.

Why this answer

Gp2 volumes have a baseline IOPS of 3 IOPS per GiB, up to a maximum of 16,000 IOPS. For a 1000 GiB gp2 volume, the calculation is 1000 × 3 = 3000 IOPS, which is below the 16,000 IOPS cap, so the expected baseline IOPS is exactly 3000.

Exam trap

The trap here is that candidates often confuse the gp2 baseline IOPS calculation (3 IOPS/GiB) with the gp3 baseline (3000 IOPS fixed for any size) or mistakenly apply the 16,000 IOPS cap as a default value for all gp2 volumes, rather than recognizing it as a maximum that only applies at larger sizes.

How to eliminate wrong answers

Option A is wrong because 4500 IOPS would correspond to a 1500 GiB gp2 volume (1500 × 3 = 4500), not a 1000 GiB volume. Option B is wrong because 16,000 IOPS is the maximum baseline IOPS for gp2 volumes, but this cap only applies when the volume size is 5334 GiB or larger (5334 × 3 ≈ 16,000); a 1000 GiB volume does not reach that cap. Option D is wrong because 1500 IOPS would be the baseline for a 500 GiB gp2 volume (500 × 3 = 1500), not for 1000 GiB.

Practice this question →

370

MCQmedium

An SAP system is running on AWS and uses Amazon EFS for the /sapmnt directory. The system is experiencing high latency during file operations. Which configuration change could improve the performance of the EFS file system?

A.Enable the Max I/O performance mode on the EFS file system.

B.Change the performance mode from Max I/O to General Purpose.

C.Migrate the /sapmnt directory to an Amazon EBS volume.

D.Increase the provisioned throughput of the EFS file system.

AnswerA

Max I/O mode provides higher throughput for large-scale workloads.

Why this answer

The Max I/O performance mode is designed for highly parallel, throughput-intensive workloads like SAP /sapmnt, which involves many concurrent file operations. It scales to higher levels of aggregate throughput and IOPS by distributing data across multiple servers, reducing latency under heavy load. General Purpose mode, while suitable for latency-sensitive workloads, cannot match the parallel throughput capabilities required by SAP systems.

Exam trap

The trap here is that candidates assume General Purpose mode is always better for latency, but for highly concurrent SAP workloads, Max I/O mode's parallelism actually reduces overall latency despite higher metadata latency.

How to eliminate wrong answers

Option B is wrong because changing from Max I/O to General Purpose would reduce the file system's ability to handle high concurrency and throughput, worsening latency for SAP workloads. Option C is wrong because migrating /sapmnt to an Amazon EBS volume would introduce a single-point-of-failure and lack the shared, multi-instance access that EFS provides for SAP's distributed architecture. Option D is wrong because increasing provisioned throughput addresses throughput limits but does not reduce latency caused by the file system's performance mode; Max I/O mode directly improves parallelism and reduces latency for high-concurrency operations.

Practice this question →

371

MCQeasy

An SAP administrator needs to back up an SAP HANA database running on an Amazon EC2 instance. The requirement is to perform daily backups to Amazon S3 with minimal cost and impact on database performance. Which backup strategy should be used?

A.Use AWS Backup with the SAP HANA plugin

B.Use SAP HANA Backint integration to back up to S3

C.Create EBS snapshots of the database volumes

D.Configure S3 Lifecycle policies to move logs

AnswerB

Backint agent sends data directly to S3 with low overhead.

Why this answer

SAP HANA Backint integration allows direct, streaming backups from the HANA database to Amazon S3, which minimizes performance impact by offloading backup processing to the Backint agent and avoids intermediate storage. This approach is cost-effective as it uses S3's low-cost storage and eliminates the need for additional infrastructure, meeting the requirement for daily backups with minimal cost and database performance impact.

Exam trap

The trap here is that candidates often confuse EBS snapshots as a simple, low-cost backup method for databases, but they fail to recognize the performance impact and lack of application consistency without additional configuration, making Backint integration the correct choice for SAP HANA on AWS.

How to eliminate wrong answers

Option A is wrong because AWS Backup with the SAP HANA plugin is not natively supported; AWS Backup does not have a direct SAP HANA plugin for Backint integration, and using it would require additional scripting or third-party tools, increasing complexity and cost. Option C is wrong because creating EBS snapshots of the database volumes captures the entire block-level data, which can cause performance degradation due to I/O freezing or snapshot latency, and does not provide application-consistent backups without additional steps like pre-freeze scripts. Option D is wrong because S3 Lifecycle policies are used for managing object lifecycle transitions and deletions, not for performing backups; they cannot initiate or manage the backup process of an SAP HANA database.

Practice this question →

372

Multi-Selecthard

A company is designing a disaster recovery solution for SAP S/4HANA. They need to meet an RPO of 15 minutes and an RTO of 2 hours. Which THREE components should be included in the DR plan? (Choose 3.)

Select 3 answers

A.EBS snapshots taken every 15 minutes

B.SAP HANA System Replication in async mode

C.AWS CloudEndure Disaster Recovery

D.Amazon Route 53 DNS failover

E.Pre-built AMIs for SAP application servers

AnswersB, D, E

Async replication can achieve RPO of minutes.

Why this answer

SAP HANA System Replication in async mode is correct because it can achieve an RPO of 15 minutes by asynchronously replicating log buffers from the primary to the DR HANA instance, and combined with a pre-configured DR system, it supports an RTO of 2 hours. This native SAP replication mechanism is optimized for HANA databases and avoids the overhead of storage-level snapshots or third-party tools.

Exam trap

The trap here is that candidates often assume storage-level snapshots (EBS) are sufficient for SAP HANA DR, but they fail to account for the database consistency requirements and the long restore times that make them unsuitable for a 2-hour RTO.

Practice this question →

373

MCQmedium

An SAP system on AWS needs to be highly available across multiple Availability Zones (AZs). The SAP Central Services (ASCS) and the database are both critical. Which architecture should be used?

A.Use an Application Load Balancer to distribute traffic across AZs.

B.Deploy ASCS with a cluster across two AZs, and use HANA System Replication across two AZs.

C.Place all components in a single AZ to avoid cross-AZ latency.

D.Use Amazon RDS Multi-AZ for the database and a single ASCS instance.

AnswerB

This provides HA for both ASCS and database across AZs.

Why this answer

SAP ASCS requires a cluster (e.g., Pacemaker with SBD fencing) across two AZs to provide failover for the central services, while HANA System Replication (HSR) synchronously replicates the database to a secondary AZ for automatic failover. This dual-cluster architecture ensures both critical components remain highly available, meeting SAP's certified HA patterns on AWS.

Exam trap

The trap here is that candidates often confuse AWS-managed services like RDS Multi-AZ with SAP-certified HA solutions, failing to recognize that SAP HANA requires native replication and that ASCS must be clustered, not simply load-balanced.

How to eliminate wrong answers

Option A is wrong because an Application Load Balancer operates at Layer 7 and cannot manage SAP ASCS or HANA database failover; it is designed for HTTP/HTTPS traffic distribution, not SAP-specific cluster heartbeats or replication. Option C is wrong because placing all components in a single AZ creates a single point of failure; AWS best practices require multi-AZ deployment to survive AZ outages, and cross-AZ latency is negligible (typically <1 ms) for SAP workloads. Option D is wrong because Amazon RDS Multi-AZ does not support SAP HANA or SAP-certified databases; SAP requires native HANA System Replication or a certified DBMS, and a single ASCS instance lacks the clustering needed for high availability.

Practice this question →

374

MCQeasy

An SAP system is running on an EC2 instance with an instance profile that grants access to an S3 bucket. The application is unable to read a specific object from the bucket. What is the first step to troubleshoot the issue?

A.Check the security group associated with the instance

B.Check the network ACLs

C.Check the IAM policy attached to the instance profile

D.Check the S3 bucket policy

AnswerC

The instance profile's IAM role must have s3:GetObject permission for the object.

Why this answer

The instance profile grants the EC2 instance permissions to access the S3 bucket via IAM roles. If the application cannot read a specific object, the most likely cause is that the IAM policy attached to the instance profile does not include the necessary permissions (e.g., s3:GetObject) for that object. Checking the IAM policy is the first logical step because it directly controls the identity-based access for the instance.

Exam trap

The trap here is that candidates often jump to checking the S3 bucket policy first, forgetting that the instance profile's IAM policy is the primary gatekeeper for EC2-based access, and bucket policies only come into play if the IAM policy allows the action.

How to eliminate wrong answers

Option A is wrong because security groups control network traffic at the instance level (Layer 3/4), not access to S3 objects, which is handled by IAM or bucket policies. Option B is wrong because network ACLs operate at the subnet level and also do not govern S3 object-level permissions. Option D is wrong because while the S3 bucket policy could deny access, the instance profile's IAM policy is the primary authorization mechanism for the EC2 instance; checking it first is more efficient, and bucket policies are typically used for cross-account or public access scenarios.

Practice this question →

375

MCQmedium

An SAP Basis administrator is setting up an SAP HANA database in a Multi-AZ deployment on AWS. They need to ensure that the database remains available during an Availability Zone failure. Which AWS services should be used together to achieve this?

A.AWS CloudWatch alarms and AWS Lambda

B.Auto Scaling groups and Elastic Load Balancer

C.SAP HANA System Replication and Amazon Route 53

D.Amazon RDS Multi-AZ and Route 53

AnswerC

HANA System Replication provides data replication, and Route 53 provides DNS failover.

Why this answer

SAP HANA System Replication (HSR) provides synchronous or asynchronous replication of HANA databases across Availability Zones, ensuring data consistency and failover capability. Amazon Route 53 with health checks and DNS failover routing automatically redirects client traffic to the standby HANA instance in the secondary AZ when the primary fails, together achieving Multi-AZ high availability for SAP HANA.

Exam trap

The trap here is that candidates confuse Amazon RDS Multi-AZ (which is a managed service for traditional databases like MySQL or Oracle) with SAP HANA, but SAP HANA on AWS requires self-managed replication via HSR and DNS-based routing, not RDS.

How to eliminate wrong answers

Option A is wrong because CloudWatch alarms and Lambda can automate responses to metrics but do not provide database-level replication or DNS-based failover for HANA. Option B is wrong because Auto Scaling groups and Elastic Load Balancer are designed for stateless web/application tiers, not for stateful database replication or HANA-specific failover. Option D is wrong because Amazon RDS Multi-AZ is a managed database service that does not support SAP HANA; SAP HANA must be deployed on EC2 with its own replication mechanisms.

Practice this question →