Knowledge + Practice

CCNA Design of SAP Workloads on AWS Questions

75 of 462 questions · Page 5/7 · Design of SAP Workloads on AWS · Answers revealed

Practice these questions Domain overview All questions

301

Multi-Selectmedium

Which TWO statements are true regarding Amazon EBS volume types for SAP HANA data volumes?

Select 2 answers

A.io1 volumes are the recommended choice for SAP HANA

B.io2 Block Express volumes provide up to 256,000 IOPS

C.gp3 volumes can be provisioned with up to 16,000 IOPS

D.st1 volumes are suitable for SAP HANA log volumes

E.sc1 volumes are cost-effective for SAP HANA data volumes

AnswersB, C

io2 Block Express offers high IOPS and durability for critical workloads.

Why this answer

Option A is correct because gp3 volumes provide baseline IOPS of 3000 and can be provisioned up to 16,000 IOPS. Option C is correct because io2 Block Express volumes offer up to 256,000 IOPS and 99.999% durability. Option B is wrong because io1 volumes are legacy and io2 Block Express is recommended.

Option D is wrong because st1 volumes are throughput-optimized HDD, not suitable for SAP HANA. Option E is wrong because sc1 volumes are cold HDD, not for database workloads.

Practice this question →

302

MCQhard

During a migration of an SAP system to AWS, the administrator notices that the SAP application servers are experiencing high network latency when communicating with the SAP HANA database. The application and database servers are in different VPCs connected via VPC peering. Which design change would most effectively reduce the latency?

A.Set up an AWS Direct Connect connection.

B.Enable Enhanced Networking on the EC2 instances.

C.Increase the bandwidth of the VPC peering connection.

D.Place the application and database servers in the same subnet.

AnswerD

Same subnet eliminates network hops, reducing latency.

Why this answer

Placing the SAP application servers and the SAP HANA database in the same subnet eliminates the need for traffic to traverse a VPC peering connection, which introduces additional network hops and potential latency. In a single subnet, all traffic stays within the same VPC and uses the local network infrastructure, providing the lowest possible latency for SAP HANA communication, which is critical for performance.

Exam trap

The trap here is that candidates assume VPC peering is a low-latency solution and overlook that any inter-VPC traffic introduces additional network hops, while the simplest and most effective fix is to co-locate the servers in the same subnet to avoid the peering overhead entirely.

How to eliminate wrong answers

Option A is wrong because AWS Direct Connect is a hybrid connectivity service that connects an on-premises data center to AWS, not a solution for reducing latency between two VPCs within the same AWS region; it would not address the inter-VPC latency issue. Option B is wrong because Enhanced Networking uses the SR-IOV (Single Root I/O Virtualization) driver to provide higher packet-per-second performance and lower jitter, but it does not reduce the physical network distance or the number of hops introduced by VPC peering. Option C is wrong because VPC peering connections do not have a configurable bandwidth limit; bandwidth is determined by the instance type and network performance, and increasing it is not a valid operation—the latency issue stems from the additional network hops, not bandwidth constraints.

Practice this question →

303

MCQmedium

A company runs SAP NetWeaver on AWS and needs to ensure that the SAP application server instances are evenly distributed across two Availability Zones. Which AWS service should be used to distribute traffic?

A.AWS Global Accelerator

B.Application Load Balancer

C.Amazon CloudFront

D.Amazon Route 53 weighted routing

AnswerB

ALB can distribute incoming traffic across multiple AZs and instances.

Why this answer

Option D is correct. An Application Load Balancer (ALB) can distribute traffic across multiple EC2 instances in different Availability Zones. Option A is wrong because Route 53 is for DNS, not for load balancing traffic.

Option B is wrong because AWS Global Accelerator provides static IPs and traffic management, but not application-level load balancing. Option C is wrong because Amazon CloudFront is a CDN.

Practice this question →

304

MCQhard

An SAP administrator configures SAP HANA backup using Backint as shown in the exhibit. The backup job fails with an error indicating that the bucket 'sap-hana-backup-prod' does not exist. The administrator confirms that the bucket name is correct. What is the most likely cause of the failure?

A.The IAM role used by the instance does not have s3:PutObject permission.

B.The chunk size is too large for the bucket.

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

D.The bucket has a bucket policy that denies access.

AnswerC

Backint by default uses the region of the instance; if bucket is in different region, need to specify region.

Why this answer

The SAP HANA Backint agent communicates with Amazon S3 using the AWS SDK, which resolves the bucket endpoint based on the region configured in the agent or the instance metadata. If the bucket 'sap-hana-backup-prod' exists in a different AWS region than the EC2 instance, the Backint agent will attempt to access the bucket using the wrong regional endpoint, resulting in a 'bucket does not exist' error. This is a common misconfiguration when the Backint parameter file does not explicitly set the correct region or when the instance's default region differs from the bucket's region.

Exam trap

The trap here is that candidates often assume the error message 'bucket does not exist' always means the bucket name is incorrect or the bucket was deleted, overlooking the region mismatch issue that causes the S3 API to return a 404 when the bucket is in a different region.

How to eliminate wrong answers

Option A is wrong because the error message specifically states the bucket does not exist, not a permissions issue; an s3:PutObject permission failure would produce an 'Access Denied' or '403 Forbidden' error. Option B is wrong because the chunk size parameter in SAP HANA Backint controls the size of data segments sent to S3, and an oversized chunk would cause a 'Request entity too large' error, not a 'bucket does not exist' error. Option D is wrong because a bucket policy that denies access would result in an 'Access Denied' or '403 Forbidden' error, not a 'bucket does not exist' error.

Practice this question →

305

Multi-Selecthard

A company is migrating its SAP ERP system to AWS. The system includes an SAP Central Services (ASCS) instance and an SAP application server. Which TWO of the following are required for high availability? (Choose TWO.)

Select 2 answers

A.Use an EBS Multi-Attach volume for shared /sapmnt

B.Enqueue replication server (ERS) must be set up for the ASCS cluster

C.Configure an Elastic Load Balancer for ASCS

D.Set up a cluster for ASCS using AWS cluster management tools

E.Deploy at least two application servers in different Availability Zones

AnswersB, D

ERS is required for enqueue replication in HA.

Why this answer

Options A and D are required for HA. Option B is optional. Option C is for networking, not HA.

Option E is for redundancy of application servers, but not a requirement for HA per se.

Practice this question →

306

MCQmedium

A company is migrating its SAP ERP system to AWS. They need to ensure high availability for the SAP Central Services (ASCS) instance. Which AWS architecture should they implement?

A.Configure a two-node cluster with a virtual IP (VIP) using AWS Route 53 health checks and failover

B.Run ASCS on Amazon RDS for SAP with Multi-AZ

C.Deploy ASCS on a single large EC2 instance

D.Use an Auto Scaling group with a minimum of 2 instances

AnswerA

Cluster with VIP provides HA for ASCS.

Why this answer

ASCS high availability requires a cluster with a virtual IP address managed by a load balancer or route table update. Option A is wrong because a single instance is not HA. Option B is wrong because Auto Scaling does not handle ASCS failover properly.

Option D is wrong because Multi-AZ RDS is for databases, not ASCS.

Practice this question →

307

MCQmedium

A company is deploying SAP Business Suite on AWS and wants to minimize network latency between the SAP application servers and the database server. Which placement strategy is best?

A.Place the servers in the same placement group within a single Availability Zone.

B.Place the servers in different VPCs connected via VPC Peering.

C.Place the application and database servers in different Availability Zones within the same region.

D.Place the servers in different AWS Regions.

AnswerA

Placement groups ensure low-latency, high-bandwidth connectivity.

Why this answer

Placement groups in AWS allow you to influence the placement of a group of interdependent instances to meet the needs of your workload. For SAP Business Suite, which is sensitive to network latency between application and database servers, using a cluster placement group within a single Availability Zone ensures the lowest possible latency and maximum throughput, as instances are placed in close proximity to each other, often within the same rack, enabling high-bandwidth, low-latency networking.

Exam trap

The trap here is that candidates often assume that distributing servers across multiple Availability Zones provides high availability, but for latency-sensitive SAP workloads, the question specifically asks for minimizing latency, not maximizing fault tolerance, so the single-AZ placement group is the correct answer.

How to eliminate wrong answers

Option B is wrong because placing servers in different VPCs connected via VPC Peering introduces additional network hops and latency, as traffic must traverse the VPC peering connection and potentially transit gateways, which is counterproductive for minimizing latency. Option C is wrong because placing servers in different Availability Zones within the same region introduces inter-AZ latency, typically 1-2 milliseconds, which is significantly higher than the sub-millisecond latency achievable within a single AZ using a placement group. Option D is wrong because placing servers in different AWS Regions introduces inter-region latency, often tens of milliseconds, which is unacceptable for the tight latency requirements of SAP Business Suite's application-to-database communication.

Practice this question →

308

Multi-Selectmedium

An architect is designing a disaster recovery plan for an SAP system using SAP HANA. The primary site is in us-east-1 and the DR site is in us-west-2. The RPO is 15 minutes and RTO is 1 hour. Which TWO AWS services or features should the architect use to meet these requirements? (Choose TWO.)

Select 2 answers

A.AWS Transit Gateway with VPC peering

B.AWS Elastic Disaster Recovery (AWS DRS)

C.Amazon S3 Cross-Region Replication

D.SAP HANA System Replication

E.AWS CloudEndure Disaster Recovery

AnswersB, D

AWS DRS automates failover and recovery, meeting RTO.

Why this answer

SAP HANA System Replication (option D) is the native SAP mechanism for replicating HANA databases synchronously or asynchronously, supporting an RPO of 15 minutes with asynchronous replication. AWS Elastic Disaster Recovery (option B) provides continuous block-level replication for the entire SAP system (including OS and application volumes) and enables automated failover within the 1-hour RTO. Together, they ensure both database consistency and full infrastructure recovery.

Exam trap

Cisco often tests the distinction between native SAP replication (HANA System Replication) and AWS infrastructure-level DR services (AWS DRS), and the trap here is that candidates may think CloudEndure (option E) is a separate valid service, but it is simply the previous branding of AWS DRS, making it a duplicate and incorrect choice.

Practice this question →

309

MCQmedium

A company is planning to migrate SAP S/4HANA to AWS. The system has a high transaction rate and requires low network latency between SAP application servers and the database. Which AWS infrastructure design minimizes network latency between the SAP application tier and the database tier?

A.Place the database server in one Availability Zone and application servers in another to improve fault tolerance.

B.Use a cluster placement group for the application servers and a separate placement group for the database.

C.Use a mix of instance types optimized for compute and memory across different Availability Zones.

D.Place all SAP application servers and the database server in the same Availability Zone.

AnswerD

Same AZ ensures minimal network hops and lowest latency.

Why this answer

Option D is correct because placing all SAP application servers and the database server in the same Availability Zone (AZ) minimizes network latency by keeping traffic within a single, high-bandwidth, low-latency AWS data center. SAP S/4HANA with a high transaction rate is sensitive to inter-AZ latency (typically 1-2 ms), which can degrade performance for synchronous database calls. Co-locating all tiers in one AZ ensures the lowest possible round-trip time for SAP's dialog work processes and database commits.

Exam trap

The trap here is that candidates often confuse high availability with performance, assuming that spreading resources across AZs improves both, but for SAP S/4HANA with high transaction rates, the primary design goal for latency is co-location in a single AZ, not fault tolerance.

How to eliminate wrong answers

Option A is wrong because placing the database and application servers in different Availability Zones introduces inter-AZ latency (typically 1-2 ms), which increases response time for SAP's synchronous database calls and can degrade transaction throughput. Option B is wrong because using separate placement groups for application and database servers does not guarantee they are in the same AZ or same rack; cluster placement groups are designed for low-latency within a single group, not across groups, and splitting them can still result in cross-AZ or cross-rack latency. Option C is wrong because mixing instance types across different Availability Zones does not address latency; it may actually increase network distance and variability, and SAP workloads require consistent low latency between tiers, not just optimized compute or memory.

Practice this question →

310

MCQeasy

A company is running SAP S/4HANA on AWS and needs to ensure high availability for the database layer. Which AWS service should be used to replicate the database to a standby instance in a different Availability Zone?

A.EC2 Auto Scaling

B.Amazon S3

C.Amazon RDS Multi-AZ

D.AWS Database Migration Service (DMS)

AnswerD

AWS DMS can perform ongoing replication to a standby HANA database.

Why this answer

AWS Database Migration Service (DMS) supports ongoing replication from an SAP HANA source database to a standby instance in a different Availability Zone using change data capture (CDC). This allows continuous data synchronization without requiring native SAP HANA replication features, making it suitable for high-availability setups where the database layer must be replicated across AZs.

Exam trap

The trap here is that candidates often confuse Amazon RDS Multi-AZ with a generic high-availability solution, but RDS Multi-AZ does not support SAP HANA, making DMS the correct choice for replicating SAP S/4HANA databases across Availability Zones.

How to eliminate wrong answers

Option A is wrong because EC2 Auto Scaling is designed to automatically adjust compute capacity based on demand, not to replicate databases or provide database-level high availability across AZs. Option B is wrong because Amazon S3 is an object storage service and cannot be used for real-time database replication or as a standby database instance. Option C is wrong because Amazon RDS Multi-AZ is a managed database service that provides automatic failover for supported database engines, but it does not support SAP HANA as a database engine, which is required for SAP S/4HANA workloads.

Practice this question →

311

Multi-Selecthard

A company is designing a disaster recovery (DR) strategy for SAP HANA on AWS. Which TWO of the following are valid DR approaches? (Choose two.)

Select 2 answers

A.Configure HANA System Replication to a secondary Region.

B.Use S3 cross-Region replication (CRR) to copy HANA backups.

C.Copy EBS snapshots to another Region using cross-Region snapshot copy.

D.Use AWS Backup with cross-Region copy.

E.Use Amazon RDS cross-Region read replicas for HANA.

AnswersA, C

HANA System Replication provides near real-time replication.

Why this answer

Options A and D are correct. A is correct because HANA System Replication can replicate data to another Region. D is correct because cross-Region EBS snapshots can be used for DR.

B is incorrect because RDS is not used for SAP HANA (HANA runs on EC2). C is incorrect because S3 cross-Region replication is for S3 objects, not HANA data. E is incorrect because AWS Backup with cross-Region copy can be used, but it is not a DR approach on its own; it backs up EBS snapshots.

Practice this question →

312

MCQhard

A company runs SAP NetWeaver on AWS. The system uses a shared file system for transport files via Amazon EFS. Recently, the transport directory performance has degraded. Which configuration change is most likely to improve the I/O performance for the transport directory?

A.Enable EFS performance mode with Max I/O.

B.Migrate the transport directory to an Amazon EBS volume.

C.Use Amazon S3 with a mount point.

D.Use EFS with Bursting Throughput mode.

AnswerA

Max I/O mode optimizes for high throughput and large file operations.

Why this answer

The correct answer is A because enabling EFS Max I/O performance mode provides higher throughput and IOPS for workloads with high I/O demands, such as SAP transport directories. Max I/O mode scales horizontally by distributing file data across multiple servers, which improves performance for parallel access patterns common in SAP transport operations.

Exam trap

The trap here is that candidates often assume Bursting Throughput mode (Option D) is sufficient for all EFS workloads, but they overlook that SAP transport directories require sustained high I/O that can exhaust burst credits, making Max I/O mode the better choice for consistent performance.

How to eliminate wrong answers

Option B is wrong because migrating to an EBS volume would require re-architecting the shared file system, as EBS is a block-level storage attached to a single EC2 instance, not suitable for shared access across multiple SAP instances. Option C is wrong because Amazon S3 with a mount point (e.g., using S3FS or similar FUSE-based solutions) introduces significant latency and lacks POSIX compliance, making it unsuitable for SAP transport directories that require low-latency file locking and consistency. Option D is wrong because EFS Bursting Throughput mode relies on burst credits and may not sustain high I/O performance for continuous workloads like SAP transport, leading to throttling once credits are exhausted.

Practice this question →

313

MCQhard

A company is designing a disaster recovery (DR) solution for SAP HANA on AWS. The primary site is in us-east-1, and the DR site is in us-west-2. The RPO is 5 minutes, and the RTO is 1 hour. The company wants to use SAP HANA System Replication (HSR). Which configuration meets these requirements?

A.Use asynchronous HSR with multiple secondary instances (multi-target) in us-west-2.

B.Use synchronous HSR between us-east-1 and us-west-2.

C.Use asynchronous HSR with a single secondary instance in us-west-2.

D.Use EBS snapshots every 5 minutes and copy them to us-west-2.

AnswerA

Multi-target async replication provides better RPO by replicating to multiple targets.

Why this answer

Option A is correct because multi-target asynchronous HSR allows SAP HANA to replicate data to multiple secondary instances simultaneously, meeting the 5-minute RPO with asynchronous replication while providing the flexibility to fail over to a secondary instance in us-west-2 within the 1-hour RTO. Asynchronous replication is necessary over such a long distance (us-east-1 to us-west-2) to avoid latency impacting primary site performance, and multi-target enables multiple DR targets without additional primary-side overhead.

Exam trap

The trap here is that candidates often assume synchronous replication is always better for low RPO, but over long distances it introduces unacceptable latency, making asynchronous the only viable option for cross-region DR.

How to eliminate wrong answers

Option B is wrong because synchronous HSR over a cross-region distance (us-east-1 to us-west-2) would introduce significant network latency, causing transaction commit delays and potentially exceeding the RTO due to performance degradation or replication timeouts. Option C is wrong because a single secondary instance in us-west-2 does not provide the required high availability for DR; if that single instance fails or becomes unreachable, replication stops and the RPO/RTO cannot be guaranteed. Option D is wrong because EBS snapshots every 5 minutes cannot achieve a 5-minute RPO due to snapshot creation and copying latency, and restoring from snapshots typically takes longer than 1 hour, failing the RTO.

Practice this question →

314

MCQeasy

A company is migrating its SAP ERP system to AWS and needs to choose a storage option for the SAP HANA database. Which AWS storage service is most suitable for SAP HANA data volumes?

A.Amazon S3

B.Amazon EBS io2 Block Express volumes

C.Amazon EBS gp3 volumes

D.Amazon EFS

AnswerB

io2 Block Express volumes provide high throughput and low latency, suitable for SAP HANA.

Why this answer

Option B is correct because Amazon EBS io2 Block Express volumes are designed for high-performance, low-latency workloads like SAP HANA. Option A is wrong because EBS gp3 is general purpose and may not meet HANA performance requirements. Option C is wrong because EFS is file storage, not block storage.

Option D is wrong because S3 is object storage.

Practice this question →

315

MCQeasy

A company needs to back up its SAP HANA database running on AWS. The backup must be stored in a durable and cost-effective manner. Which AWS service should the company use for long-term backup storage?

A.Amazon EBS snapshots

B.Amazon Glacier

C.AWS Backup

D.Amazon S3

AnswerD

S3 is ideal for durable and cost-effective backup storage.

Why this answer

Option A is correct because Amazon S3 is durable, cost-effective, and suitable for long-term backup storage. Option B is wrong because Amazon Glacier is for archival, not regular backups. Option C is wrong because Amazon EBS snapshots are stored in S3 but are not directly accessible as files.

Option D is wrong because AWS Backup can orchestrate backups but uses S3 as the storage target.

Practice this question →

316

MCQeasy

A company is planning to run SAP S/4HANA on AWS. They need to ensure that the SAP system can be restored within 4 hours in the event of a disaster. Which AWS service should be used to achieve this recovery time objective (RTO)?

A.AWS Elastic Disaster Recovery

B.EBS snapshots copied to another region

C.AWS CloudEndure Disaster Recovery

D.Amazon S3 cross-region replication

AnswerA

DRS provides fast recovery for SAP systems.

Why this answer

AWS Elastic Disaster Recovery (AWS DRS) is the correct service because it provides continuous replication of SAP S/4HANA workloads with sub-second RPO and supports automated recovery orchestration, enabling restoration within the 4-hour RTO. It is the direct successor to CloudEndure Disaster Recovery and is purpose-built for enterprise applications like SAP, offering non-disruptive testing and fast failover to a secondary AWS Region or Availability Zone.

Exam trap

The trap here is that candidates confuse AWS Elastic Disaster Recovery with its predecessor name 'CloudEndure Disaster Recovery' (Option C), which is the same service but the exam expects the current AWS branding, or they mistakenly think periodic EBS snapshots (Option B) can achieve a 4-hour RTO for SAP without considering the recovery time for snapshot restoration and database consistency.

How to eliminate wrong answers

Option B is wrong because EBS snapshots copied to another region provide only periodic, point-in-time backups (typically every 1-24 hours), which cannot guarantee the sub-minute RPO needed for SAP S/4HANA and may require manual steps to restore, exceeding the 4-hour RTO. Option C is wrong because AWS CloudEndure Disaster Recovery is the previous name for AWS Elastic Disaster Recovery; it is the same service, but the current AWS service name is 'AWS Elastic Disaster Recovery' (the exam uses the updated name), so selecting this option indicates a misunderstanding of the service naming. Option D is wrong because Amazon S3 cross-region replication is an object-level replication service for S3 buckets, not a block-level replication solution for EC2 instances or SAP databases, and it cannot replicate the entire SAP system state (OS, database, application) required for disaster recovery.

Practice this question →

317

Multi-Selecthard

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

Select 3 answers

A.The instance must have enough memory to fit the HANA database.

B.The instance must support high network throughput for data replication.

C.The instance should have GPU accelerators for faster query processing.

D.The instance must have local instance store volumes for data persistence.

E.The instance type must be listed in the SAP HANA hardware directory for AWS.

AnswersA, B, E

HANA is memory-optimized.

Why this answer

Option A is correct because SAP HANA is an in-memory database that loads the entire dataset into RAM for processing. The EC2 instance must have sufficient memory to accommodate the HANA database size, including overhead for system tables and temporary data, as specified in the SAP HANA memory sizing guidelines.

Exam trap

The trap here is that candidates may mistakenly think GPU accelerators are needed for SAP HANA's analytical queries or that local instance store volumes provide persistent storage, when in fact SAP HANA requires certified instance types and persistent storage like EBS.

Practice this question →

318

MCQmedium

An SAP system on AWS uses a multi-AZ deployment with an Application Load Balancer (ALB) to distribute traffic across application servers. The ALB health checks are failing intermittently. What is the most likely cause?

A.The security group for the ALB is blocking health check traffic.

B.The target group is not associated with the ALB.

C.The health check path is not configured correctly for the SAP application.

D.The application servers are running on burstable instance types.

AnswerC

Incorrect health check path can cause intermittent failures if the application occasionally returns non-200 status.

Why this answer

Option B is correct because ALB health checks require a specific path (e.g., /health) and may fail if the path is incorrect or the application is not responding. Option A is wrong because security groups are static and would cause consistent failures. Option C is wrong because ALB health checks are independent of instance types.

Option D is wrong because health checks are configured at the ALB level, not the target group.

Practice this question →

319

MCQmedium

An administrator is troubleshooting an SAP system where the application server cannot connect to the database server. Both servers are in the same VPC but different subnets. Security groups allow traffic on the database port. What is the next step to diagnose the issue?

A.Check the DB Subnet Group configuration

B.Verify route tables for the subnets

C.Review VPC Flow Logs for rejected traffic

D.Check the Network ACLs for both subnets to ensure inbound/outbound rules allow the database port

AnswerD

NACLs are stateless and must allow both inbound and outbound traffic.

Why this answer

Network ACLs (NACLs) are stateless, meaning they require explicit inbound and outbound rules for traffic to flow in both directions. Even if security groups allow the database port, a missing or misconfigured NACL rule on either subnet can silently drop traffic. Since the servers are in different subnets, checking NACLs is the next logical step after confirming security groups are correct.

Exam trap

The trap here is that candidates assume security groups are the only firewall layer, forgetting that NACLs are stateless and must be explicitly configured for both inbound and outbound traffic on each subnet.

How to eliminate wrong answers

Option A is wrong because DB Subnet Group configuration only determines which subnets an RDS instance can be placed in, not the network connectivity between an application server and a database server. Option B is wrong because route tables control traffic between subnets and other networks, but within the same VPC, subnets are implicitly connected via the VPC's main route table, so missing routes are unlikely to cause a connectivity issue between two subnets. Option C is wrong because VPC Flow Logs are a diagnostic tool for analyzing traffic after a problem is suspected, not the next step in a systematic troubleshooting process; they would be useful if NACLs and security groups appear correct but traffic is still failing.

Practice this question →

320

MCQhard

A company runs its SAP S/4HANA production workload on AWS using an 8xlarge instance with 2,000 GB of gp3 storage for /usr/sap and 6,000 GB of io2 Block Express with 64,000 IOPS for /hana/data and /hana/log. The system experiences intermittent performance degradation during peak hours, particularly for batch jobs that heavily write to the database. The SAP team reports that the database response time spikes from under 5 milliseconds to over 200 milliseconds during these periods. The AWS account has a default EBS IOPS limit of 80,000 per region. The current io2 volume is attached as a single volume. Which combination of actions would resolve the performance issue?

A.Replace the io2 volumes with larger gp3 volumes and increase the volume size to 8,000 GB to benefit from gp3 baseline performance.

B.Split the /hana/data volume into multiple io2 volumes, configure them as a RAID 0 stripe, and attach each to a separate EBS-optimized connection. Increase total provisioned IOPS to 80,000 distributed across volumes.

C.Migrate to a larger instance type with higher EBS-optimized bandwidth and increase the volume IOPS to 80,000.

D.Increase the provisioned IOPS on the existing io2 volume to 80,000 IOPS to stay within the default limit.

AnswerB

RAID 0 across multiple volumes increases aggregate IOPS and throughput, leveraging multiple EBS connections and avoiding single-volume limits.

Why this answer

Option B is correct because splitting the /hana/data volume into multiple io2 volumes and configuring them as a RAID 0 stripe distributes I/O across multiple EBS-optimized connections, effectively increasing the available throughput and IOPS beyond the limits of a single volume attachment. This approach also allows the total provisioned IOPS to reach 80,000, which is the regional default limit, while each individual volume stays within its own IOPS ceiling, thus resolving the database response time spikes during peak batch write operations.

Exam trap

The trap here is that candidates assume increasing IOPS on a single volume or moving to a larger instance alone will solve the performance issue, ignoring the fundamental single-volume throughput and IOPS ceiling that requires striping across multiple volumes to scale.

How to eliminate wrong answers

Option A is wrong because gp3 volumes, even at 8,000 GB, have a baseline IOPS of only 16,000 (with a maximum of 16,000 IOPS without additional cost), which is far below the required 64,000 IOPS and cannot match the low-latency performance of io2 Block Express for SAP HANA workloads. Option C is wrong because simply migrating to a larger instance type with higher EBS-optimized bandwidth does not address the single-volume bottleneck; the existing single io2 volume still cannot exceed its maximum IOPS limit (64,000) and the throughput limitation of a single EBS attachment, so performance degradation would persist. Option D is wrong because increasing the provisioned IOPS on the existing single io2 volume to 80,000 exceeds the volume-level IOPS limit for io2 (which is 64,000 IOPS for volumes up to 16 TB) and also does not resolve the throughput bottleneck of a single EBS-optimized connection.

Practice this question →

321

MCQmedium

An SAP system administrator is designing the storage layout for an SAP HANA database on AWS. The HANA data volume requires 5000 IOPS and 250 MB/s throughput. Which EBS volume type and configuration should be used to meet these requirements cost-effectively?

A.Use a single gp3 volume with 5000 IOPS and 250 MB/s throughput

B.Use a single sc1 volume with 5000 IOPS and 250 MB/s throughput

C.Use a single st1 volume with 5000 IOPS and 250 MB/s throughput

D.Use a single io1 volume with 5000 provisioned IOPS and 250 MB/s throughput

AnswerD

io1 supports up to 64,000 IOPS and 1000 MB/s per volume.

Why this answer

Option B is correct because a single io1 volume can be provisioned with 5000 IOPS and 250 MB/s throughput. Option A is wrong because gp3 can provide up to 3000 IOPS and 125 MB/s. Option C is wrong because st1 is throughput-optimized but not for database workloads.

Option D is wrong because sc1 is cold storage.

Practice this question →

322

MCQmedium

A company running SAP on AWS wants to automate the start and stop of non-production instances to save costs. Which AWS service is best suited for scheduling instance state changes?

A.AWS Instance Scheduler

B.Amazon CloudWatch Events (EventBridge)

C.AWS Auto Scaling

D.AWS Lambda with custom code

AnswerA

Specifically designed for scheduling EC2 start/stop.

Why this answer

AWS Instance Scheduler is a purpose-built solution that uses AWS CloudFormation to deploy a scheduler that automatically starts and stops EC2 instances based on defined schedules. It is the recommended approach for SAP non-production instances because it natively supports tagging, time zones, and periodic schedules without requiring custom code, making it the most cost-effective and maintainable option for this use case.

Exam trap

The trap here is that candidates often choose AWS Lambda with custom code (Option D) because they think it gives more control, but the exam expects the purpose-built AWS Instance Scheduler as the best practice for scheduling instance state changes, as it is a managed solution that requires no custom development.

How to eliminate wrong answers

Option B is wrong because Amazon CloudWatch Events (EventBridge) is a service for routing events to targets, not a scheduler itself; while it can invoke a Lambda function on a schedule, it lacks built-in instance management logic and would require additional custom code to handle start/stop operations. Option C is wrong because AWS Auto Scaling is designed to automatically adjust capacity based on demand or health checks, not to schedule instance state changes at specific times; it cannot start or stop instances on a fixed schedule. Option D is wrong because AWS Lambda with custom code is a valid approach but is not the best suited service for this task; it requires writing and maintaining custom scheduling logic, error handling, and state management, whereas AWS Instance Scheduler provides a ready-to-use, managed solution that reduces operational overhead.

Practice this question →

323

MCQmedium

An SAP administrator is designing a disaster recovery plan for SAP NetWeaver on AWS. They want to minimize RTO and RPO while keeping costs low. Which strategy should they use?

A.Use AWS Elastic Disaster Recovery (DRS) with SAP HANA system replication

B.Use AWS EC2 Image Builder to create daily AMIs

C.Take manual EBS snapshots every 12 hours

D.Replicate SAP application data to an S3 bucket in another region

AnswerA

DRS provides continuous replication, minimizing RTO and RPO.

Why this answer

Using AWS Elastic Disaster Recovery (DRS) with SAP HANA replication provides low RTO/RPO and cost-effective DR. Option A is wrong because EC2 Image Builder is for AMI creation, not DR. Option B is wrong because manual snapshots have higher RPO.

Option D is wrong because S3 replication does not replicate running instances.

Practice this question →

324

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

Option A and D are correct. Option B is wrong because Systems Manager is for management, not deployment. Option C is wrong because CloudWatch is for monitoring.

Option E is wrong because WorkSpaces is a VDI service.

Practice this question →

325

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 →

326

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 →

327

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

Options A and C are correct. Amazon CloudWatch can monitor SAP metrics, and SAP Solution Manager can be integrated with AWS for comprehensive monitoring. Option B is wrong because AWS Config is for configuration auditing.

Option D is wrong because AWS Trusted Advisor provides best-practice checks, not real-time monitoring. Option E is wrong because Amazon Inspector is for security assessment.

Practice this question →

328

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

Option D is correct because CPU ready time indicates the VM is waiting for physical CPU cycles from the hypervisor. Moving to a dedicated host or dedicated instance reduces competition for CPU resources. Option A is wrong because increasing vCPUs may increase contention.

Option B is wrong because memory is not the issue. Option C is wrong because changing tenancy to default does not help.

Practice this question →

329

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

The correct answer is C because if DeleteOnTermination is false, the EBS volume will persist after instance termination. This is important for data volumes like HANA data. Option A is incorrect because the volume remains in the account.

Option B is incorrect because it will not be deleted. Option D is incorrect because the volume is attached.

Practice this question →

330

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 →

331

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

Option B is correct because 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 →

332

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 →

333

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 correct answer is D because the MinSize is set to 1, and the DesiredCapacity is 2, but the MaxSize is 5. However, if the MinSize is 1, the Auto Scaling group cannot scale down below that, but it should be able to scale up to DesiredCapacity. The real issue is that the DesiredCapacity might be overridden by MinSize? Actually, MinSize is 1, DesiredCapacity is 2, so it should launch 2 instances.

But the question says only one instance is launched. The most likely reason is that there is a capacity issue in the specified Availability Zones. Option A is incorrect because the template has MinSize 1, MaxSize 5.

Option B is incorrect because DesiredCapacity is 2. Option C is incorrect because M5 is Nitro-based but that does not affect number of instances.

Practice this question →

334

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

Option D is correct because 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 →

335

MCQmedium

An SAP administrator is designing a high-availability (HA) setup for SAP HANA in a multi-AZ deployment on AWS. Which combination of AWS services and configurations is required for a fully automated HA solution?

A.Classic Load Balancer, AWS CloudTrail, and Amazon Inspector

B.Amazon Route 53, Application Load Balancer, and AWS CloudFormation

C.NAT Gateway, EBS snapshots, and AWS Lambda

D.EC2 Auto Scaling, Amazon RDS, and AWS Backup

AnswerB

Route 53 provides DNS failover, ALB health checks, and CloudFormation automates resource creation for HA.

Why this answer

Option D is correct. AWS uses Route 53 for DNS failover, Application Load Balancer (ALB) for health checks and traffic distribution, and AWS CloudFormation for automated infrastructure deployment. Option A is wrong because NAT Gateway is not used for HA.

Option B is wrong because EC2 Auto Scaling is not suitable for HANA scale-up. Option C is wrong because ELB Classic is not recommended and CloudTrail is for auditing.

Practice this question →

336

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 →

337

MCQeasy

A company is planning to run SAP Business Suite on AWS. They want to minimize downtime during a failover scenario. Which AWS feature should they use to achieve automatic failover of the SAP Central Services (ASCS) instance?

A.AWS Auto Scaling

B.Amazon CloudWatch with alarms

C.Elastic Load Balancer

D.Amazon Route 53 with health checks and failover routing

AnswerD

Route 53 can perform DNS failover to the standby ASCS when the primary fails.

Why this answer

Amazon Route 53 with health checks and failover routing is the correct choice because SAP Central Services (ASCS) requires a DNS-level failover mechanism to redirect clients to the standby instance without relying on IP-level changes. Route 53 monitors the health of the primary ASCS instance via health checks and automatically updates DNS records to point to the secondary instance when a failure is detected, enabling automatic failover with minimal downtime.

Exam trap

The trap here is that candidates often confuse load balancing (ELB) with failover routing, but SAP ASCS requires a DNS-based active/passive failover mechanism rather than a load balancer distributing traffic to multiple active instances.

How to eliminate wrong answers

Option A is wrong because AWS Auto Scaling is designed to automatically adjust the number of EC2 instances based on demand, not to handle failover of SAP Central Services, which requires a static, stateful pair of instances (primary and standby) and cannot be replaced by scaling out. Option B is wrong because Amazon CloudWatch with alarms can monitor metrics and trigger notifications or actions via Lambda or Auto Scaling, but it does not provide a native DNS-level failover mechanism for ASCS; it would require custom scripting and additional services to achieve failover, adding complexity and potential delay. Option C is wrong because Elastic Load Balancer distributes incoming traffic across multiple targets, but SAP ASCS is a stateful service that requires a single active instance at a time; an ELB cannot manage the active/passive failover logic needed for ASCS and would introduce session affinity issues.

Practice this question →

338

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 metrics map to AWS resource characteristics.

Practice this question →

339

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

Option B is correct because 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 →

340

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 →

341

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 →

342

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 →

343

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

Option C is correct because converting gp2 volumes to gp3 provides higher baseline IOPS and throughput without additional cost for provisioned IOPS. Option A is wrong because disabling HANA's delta merge increases fragmentation, worsening performance. Option B is wrong because increasing EBS snapshot frequency does not affect I/O performance.

Option D is wrong because using a larger instance type addresses compute, not disk I/O.

Practice this question →

344

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 →

345

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 correct answer is B because the x1e.32xlarge instance is part of the X1e family, which is optimized for memory-intensive workloads like SAP HANA. Option A is incorrect because t3 instances are burstable and not suitable for production HANA. Option C is incorrect because c5 instances are compute-optimized.

Option D is incorrect because r5 instances are memory-optimized but not specifically designed for SAP HANA as X1e is.

Practice this question →

346

MCQhard

An SAP HANA system on AWS is experiencing performance degradation. The administrator suspects that the EBS volumes are not providing consistent IOPS. Which AWS tool can be used to monitor the performance of EBS volumes at the volume level?

A.AWS X-Ray

B.Amazon CloudWatch

C.Amazon Inspector

D.AWS Trusted Advisor

AnswerB

CloudWatch provides detailed EBS metrics such as IOPS and throughput.

Why this answer

Option B is correct. Amazon CloudWatch provides metrics like VolumeReadBytes, VolumeWriteBytes, VolumeQueueLength for EBS volumes. Option A is wrong because AWS Trusted Advisor gives recommendations, not performance metrics.

Option C is wrong because Amazon Inspector is for security assessment. Option D is wrong because AWS X-Ray is for tracing application requests.

Practice this question →

347

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 →

348

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 →

349

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

Option A is correct because using AWS Instance Scheduler automates starting and stopping instances on a schedule. Option B is wrong because Reserved Instances are for steady state, not for intermittent use. Option C is wrong because Savings Plans are also for consistent usage.

Option D is wrong because On-Demand with no scheduling does not reduce cost.

Practice this question →

350

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

Option B is correct because Security Groups act as a virtual firewall for EC2 instances, and adding a rule to the database security group that allows inbound traffic from the application server security group is the recommended way to control traffic between instances. Option A is incorrect because an Internet Gateway is for internet access. Option C is incorrect because a Network ACL is stateless and more complex to manage.

Option D is incorrect because VPC Peering is for connecting different VPCs.

Practice this question →

351

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

The correct answer is C because 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 →

352

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 →

353

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

Option B is correct because 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 →

354

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 →

355

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 →

356

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

Option D is correct because r5.8xlarge is a fixed instance size. To increase CPU capacity, the company can move to a larger instance in the same family (r5.12xlarge or r5.24xlarge) using instance resizing (stop the instance, change instance type, start). Option A is incorrect because adding EBS volumes does not increase CPU.

Option B is incorrect because launching additional instances would require a distributed HANA setup which may not be cost-effective. Option C is incorrect because auto scaling is not applicable for a single HANA instance.

Practice this question →

357

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

Option B is correct because SAP HANA System Replication with HANA replication over AWS Direct Connect or VPN to a different region can achieve an RPO of seconds and RTO of minutes, meeting the requirements. Option A is incorrect because Amazon EBS Snapshots are not real-time and cannot achieve 15-minute RPO. Option C is incorrect because S3 Cross-Region Replication is for S3 objects, not for HANA database files.

Option D is incorrect because AWS Database Migration Service is for one-time migrations, not continuous replication.

Practice this question →

358

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

Option C is correct because 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 →

359

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 →

360

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

Option A is correct because 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 →

361

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 →

362

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

Option B is correct because 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 →

363

Multi-Selectmedium

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

Select 2 answers

A.Install HANA on a separate EBS volume mounted under /hana/data

B.Configure swap space on the instance to handle memory pressure

C.Enable multi-attach on EBS volumes for HANA shared storage in scale-out

D.Use EBS io2 Block Express volumes for HANA data and log

E.Change the hostname after the HANA installation to match the DNS name

AnswersC, D

Multi-attach allows multiple nodes to access the same EBS volume for shared /hana/shared.

Why this answer

Option C is correct because SAP HANA scale-out configurations require shared storage for /hana/shared, and EBS multi-attach allows multiple EC2 instances to concurrently access the same EBS volume, which is necessary for the shared file system. Option D is correct because EBS io2 Block Express volumes provide the high IOPS, low latency, and consistent performance required for SAP HANA data and log volumes, meeting SAP's storage performance recommendations.

Exam trap

Cisco often tests the misconception that general Linux administration practices (like configuring swap or changing hostnames post-installation) apply to SAP HANA, when in fact SAP HANA has strict, specific requirements that override these defaults.

Practice this question →

364

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 →

365

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

Option C is correct because 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 →

366

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

Option B is correct because 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 →

367

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

Option D is correct because the aws:SecureTransport condition enforces HTTPS for S3 API requests. Options A, B, and C are not conditions that enforce encryption in transit.

Practice this question →

368

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

SAP HANA supports system replication, and using a cluster manager like Pacemaker on Amazon EC2 with EBS multi-attach enables automatic failover. AWS does not offer a managed SAP HANA HA service.

Practice this question →

369

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

Options A, C, and E are correct. Using Reserved Instances for predictable workloads reduces cost. Rightsizing instances ensures you are not over-provisioned.

Automating start/stop for non-production instances saves costs. Option B is wrong because gp2 is less expensive than io2 but may not meet performance requirements. Option D is wrong because Dedicated Hosts are more expensive.

Practice this question →

370

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

Option B is correct because 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 →

371

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

Options A and C are correct. A: SAP NetWeaver can use a multi-AZ deployment with Amazon EFS as a shared file system for the SAP transport directory, and a cluster manager (e.g., Pacemaker) to handle failover. C: SAP NW HA can also be achieved using a Windows Server Failover Cluster with shared storage (e.g., Amazon FSx for Windows File Server).

Option B is incorrect because Amazon RDS does not support SAP NetWeaver. Option D is incorrect because a single EC2 instance does not provide HA. Option E is incorrect because S3 is not a file system suitable for SAP transport directory.

Practice this question →

372

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

AnswersA, B, E

Multi-Attach enables shared storage for HA scenarios like SAP enqueue replication.

Why this answer

Option A is correct because EBS Multi-Attach allows a single Provisioned IOPS (io1/io2) EBS volume to be attached to multiple EC2 instances in the same Availability Zone, enabling shared storage for SAP workloads that require active-active or active-passive clustering. This is critical for SAP ASCS/ERS and SAP HANA scale-out configurations where multiple instances need concurrent read/write access to the same data volume without relying on network file systems.

Exam trap

The trap here is that candidates confuse high availability design (which requires redundancy across instances and AZs) with backup strategies (S3), leading them to select Option D instead of recognizing that backup storage is a data protection concern, not an HA architecture component.

Practice this question →

373

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

Option D is correct because 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 →

374

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 →

375

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 →

← PreviousPage 5 of 7 · 462 questions totalNext →

Ready to test yourself?

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

Start 20-question session