Courseiva

CCNA Sap Workload Design Questions

75 of 428 questions · Page 3/6 · Sap Workload Design topic · Answers revealed

Practice these questionsExam hubAll questions
151
MCQmedium

An SAP system on AWS is using Amazon EBS volumes for the database. The company wants to take crash-consistent snapshots of the entire database volume set. Which approach is recommended?

A.Stop the instance, take snapshots, then restart
B.Use EBS Multi-Attach to attach volumes to a backup instance
C.Take snapshots of each volume individually at the same time
D.Use AWS Backup with pre- and post-scripts for volume groups
AnswerD

AWS Backup can create crash-consistent snapshots across volumes.

Why this answer

AWS Backup with pre- and post-scripts for volume groups is the recommended approach because it orchestrates crash-consistent snapshots across multiple EBS volumes by freezing the application (e.g., SAP HANA) and flushing I/O before the snapshot, then unfreezing after. This ensures all volumes are captured at the same point in time without downtime, which is critical for SAP databases requiring consistency across the entire volume set.

Exam trap

The trap here is that candidates assume taking snapshots simultaneously (Option C) guarantees crash consistency, but EBS snapshots are initiated asynchronously and do not capture a point-in-time across multiple volumes without application-level coordination.

How to eliminate wrong answers

Option A is wrong because stopping the instance causes downtime, which is unnecessary and disruptive for production SAP workloads; crash-consistent snapshots can be achieved without stopping the instance. Option B is wrong because EBS Multi-Attach is designed for shared volumes in clustered environments, not for taking consistent snapshots across a volume set, and attaching volumes to a backup instance does not guarantee crash consistency. Option C is wrong because taking snapshots of each volume individually at the same time does not guarantee crash consistency; EBS snapshots are asynchronous and may capture data at slightly different points, leading to inconsistencies across volumes.

Practice this question →
152
MCQeasy

A company is running SAP HANA on AWS and needs to ensure high availability for the database. Which AWS service should be used to automatically recover the HANA primary instance in case of an instance failure?

A.Amazon CloudWatch alarms
B.AWS CloudFormation custom resources
C.AWS Lambda functions
D.Amazon Route 53 health checks and failover routing
AnswerD

Route 53 health checks can trigger failover to a standby database.

Why this answer

Amazon Route 53 health checks and failover routing can automatically detect an instance failure and route traffic to a standby HANA primary instance. By configuring a Route 53 DNS failover record with health checks against the primary instance, DNS resolution is updated to point to the secondary instance when the primary becomes unhealthy, enabling automated recovery without manual intervention.

Exam trap

The trap here is that candidates often assume AWS services like CloudWatch or Lambda are sufficient for automatic recovery, but the question specifically asks for the service that automatically recovers the HANA primary instance via failover, which requires DNS-level rerouting provided by Route 53 health checks and failover routing.

How to eliminate wrong answers

Option A is wrong because Amazon CloudWatch alarms can trigger actions like sending notifications or invoking Lambda functions, but they cannot directly perform DNS failover or automatically recover a HANA primary instance without additional orchestration. Option B is wrong because AWS CloudFormation custom resources are used to execute custom logic during stack creation/update/deletion, not for real-time automated recovery of a running instance. Option C is wrong because AWS Lambda functions can be used as part of a recovery workflow, but they are not a native service for automatic failover; they require additional components (e.g., Route 53, CloudWatch) to detect failure and trigger recovery, making them an indirect solution rather than the primary service for automatic recovery.

Practice this question →
153
Multi-Selecthard

Which TWO are required considerations when sizing an SAP HANA instance on AWS for a production environment? (Choose two.)

Select 2 answers
A.Provision instance store volumes for HANA data and log areas.
B.Purchase Reserved Instances for the HANA server to reduce costs.
C.Ensure the instance has enough memory to hold the HANA data in memory (RAM:data ratio).
D.Provision EBS volumes with sufficient IOPS for the HANA workload.
E.Select an RDS instance type that supports SAP HANA.
AnswersC, D

HANA is in-memory; data must fit in RAM for performance.

Why this answer

SAP HANA is an in-memory database that requires all active data to reside in RAM. The RAM:data ratio must be carefully sized to ensure the instance has enough memory to hold the HANA data and log volumes in memory, typically with a 1:4 or 1:8 ratio depending on compression and workload. AWS provides specific instance types (e.g., x1e, u-6tb1) certified for SAP HANA that meet these memory requirements.

Exam trap

The trap here is that candidates confuse storage persistence requirements with instance store vs. EBS, or mistakenly think RDS can host SAP HANA, when in fact SAP HANA requires certified EC2 instances and specific EBS configurations for production workloads.

Practice this question →
154
MCQmedium

A company is running SAP on AWS and needs to design a disaster recovery (DR) solution with a Recovery Point Objective (RPO) of 15 minutes and a Recovery Time Objective (RTO) of 4 hours. The primary region is us-east-1 and the DR region is us-west-2. The SAP application uses an SAP HANA database with a size of 2 TB. Which combination of AWS services should be used to meet the DR requirements most cost-effectively?

A.Use AWS Database Migration Service (DMS) with continuous replication from the primary HANA database to a target in us-west-2.
B.Use AWS Backup with continuous backups and cross-region copy to achieve RPO of 15 minutes.
C.Use AWS Backup to take hourly backups of the HANA database and restore in us-west-2 during a disaster.
D.Configure HANA System Replication (HSR) across regions and use a standby HANA instance in us-west-2 with a smaller instance size.
AnswerD

HSR provides near-synchronous replication with RPO of seconds; a smaller standby reduces cost and can be scaled up during failover within RTO.

Why this answer

HANA System Replication (HSR) is the native SAP HANA replication technology that can achieve an RPO of 15 minutes or less by asynchronously replicating data across regions. By using a smaller standby instance in us-west-2, the solution meets the RTO of 4 hours (since the standby can be scaled up or promoted quickly) while minimizing ongoing DR costs. This approach is purpose-built for SAP HANA and avoids the overhead of third-party tools or backup-based restores.

Exam trap

The trap here is that candidates assume AWS Backup or DMS can handle SAP HANA replication, but neither supports the required continuous, low-RPO replication for HANA, and the native HSR is the only service that meets both the RPO and RTO cost-effectively.

How to eliminate wrong answers

Option A is wrong because AWS Database Migration Service (DMS) does not support SAP HANA as a continuous replication source for ongoing changes; DMS is designed for homogeneous/heterogeneous migrations, not for real-time HANA replication with sub-15-minute RPO. Option B is wrong because AWS Backup does not support continuous backups for SAP HANA; it can only take snapshot-based backups at scheduled intervals, and achieving a 15-minute RPO with hourly backups is impossible. Option C is wrong because hourly backups cannot guarantee a 15-minute RPO (the maximum data loss could be up to 1 hour), and restoring from backups in a DR region would likely exceed the 4-hour RTO due to the time required to restore a 2 TB HANA database.

Practice this question →
155
MCQmedium

An SAP administrator is creating an IAM policy for an EC2 instance that performs SAP database backups to S3 and creates EBS snapshots. The policy as shown fails to allow the EC2 instance to perform backup operations. What is the most likely reason?

A.The S3 resource ARN is incorrect; it should be 'arn:aws:s3:::sap-backup-bucket' without the '/*'.
B.The S3 actions are too permissive; they should be restricted to specific prefixes.
C.The ec2:CreateSnapshot action must be restricted to specific volume ARNs.
D.The policy does not include the 's3:ListBucket' action for the bucket itself.
AnswerD

Without 's3:ListBucket' on the bucket resource, the instance cannot list objects or verify bucket existence, causing failures.

Why this answer

The policy lacks the `s3:ListBucket` action for the bucket itself (ARN without `/*`). When an EC2 instance performs SAP database backups to S3, the AWS SDK or CLI first issues a `ListBucket` request to verify the bucket exists and to list objects before uploading. Without this permission, the backup operation fails at the initial listing step, even if `s3:PutObject` is allowed on the object ARN.

Exam trap

The trap here is that candidates focus on the EC2 snapshot permissions or S3 object ARN syntax, overlooking the prerequisite `s3:ListBucket` action required for any S3 upload workflow.

How to eliminate wrong answers

Option A is wrong because the S3 resource ARN `arn:aws:s3:::sap-backup-bucket/*` is correct for object-level actions like `s3:PutObject`; removing the `/*` would restrict access to the bucket itself, which is needed for `s3:ListBucket` but not for `s3:PutObject`. Option B is wrong because the S3 actions being too permissive is not the cause of failure; the issue is a missing action, not excessive permissions. Option C is wrong because `ec2:CreateSnapshot` does not require restriction to specific volume ARNs for the policy to work; the failure is due to missing S3 permissions, not EC2 snapshot permissions.

Practice this question →
156
MCQeasy

Which AWS service is used to automate the installation and configuration of SAP applications on AWS according to best practices?

A.AWS OpsWorks
B.AWS Launch Wizard for SAP
C.AWS CloudFormation
D.AWS Quick Starts
AnswerB

Launch Wizard provides guided, best-practice deployment for SAP.

Why this answer

AWS Launch Wizard for SAP is the correct service because it provides a guided, best-practice-based deployment experience specifically for SAP applications. It automatically provisions the necessary AWS infrastructure (EC2, EBS, VPC, etc.) and configures the SAP software according to AWS and SAP validated architectures, reducing manual effort and errors.

Exam trap

The trap here is that candidates confuse AWS Launch Wizard for SAP with AWS CloudFormation or Quick Starts, assuming any automation tool can handle SAP installation, but only Launch Wizard integrates the SAP-specific software installation and best-practice validation directly into the provisioning workflow.

How to eliminate wrong answers

Option A is wrong because AWS OpsWorks is a configuration management service that uses Chef and Puppet, but it is not purpose-built for SAP deployment and does not include SAP-specific best practices or automated SAP installation workflows. Option C is wrong because AWS CloudFormation is a general-purpose Infrastructure as Code (IaC) service that requires users to manually define all resources and SAP-specific configurations; it lacks the guided, automated SAP installation and validation logic that Launch Wizard provides. Option D is wrong because AWS Quick Starts are reference deployments that use CloudFormation templates, but they are not dynamically interactive or tailored to individual SAP system requirements (like SID, sizing, or HA) and do not automate the actual SAP software installation step.

Practice this question →
157
MCQhard

An SAP administrator notices that the SAP HANA database is running out of disk space on the /hana/data volume. The volume is an EBS gp3 volume with 2000 GB size. The administrator wants to increase the size without downtime. Which action should be taken?

A.Detach the volume, create a snapshot, create a larger volume from the snapshot, and attach it
B.Create a new larger volume and copy data using rsync
C.Increase the IOPS of the volume to improve performance
D.Use the modify-volume API to increase the size of the existing volume
AnswerD

EBS supports online modification of volume size.

Why this answer

AWS EBS gp3 volumes support online resizing via the modify-volume API without requiring downtime. The SAP HANA /hana/data volume can be increased in size while the instance remains running, as EBS volumes can be modified dynamically. After the modification, the administrator must extend the file system to recognize the new space, but no volume detachment or data migration is needed.

Exam trap

The trap here is that candidates may confuse the need to increase disk space with performance tuning (IOPS) or assume that volume modifications require downtime, leading them to choose snapshot-based or data-copy methods instead of the simpler online resize.

How to eliminate wrong answers

Option A is wrong because detaching the volume would cause downtime for the SAP HANA database, as the /hana/data volume must remain attached for the database to operate. Option B is wrong because creating a new volume and using rsync to copy data introduces unnecessary complexity and potential downtime, and it does not leverage EBS's native online resizing capability. Option C is wrong because increasing IOPS addresses performance, not disk space; the issue is running out of storage capacity, not throughput or latency.

Practice this question →
158
MCQmedium

A company runs SAP on AWS and wants to implement a high-availability (HA) solution for SAP Central Services (ASCS/ERS) using Amazon EC2 instances. Which AWS service is essential for managing the virtual IP address (VIP) required for the HA cluster?

A.AWS Global Accelerator
B.Amazon Route 53
C.AWS WAF
D.Application Load Balancer
AnswerB

Route 53 can provide failover routing with health checks to redirect traffic to the standby ASCS instance.

Why this answer

Amazon Route 53 is essential for managing the virtual IP address (VIP) required for the SAP Central Services (ASCS/ERS) HA cluster because it provides DNS-based failover. When the active ASCS instance fails, the HA cluster updates a Route 53 DNS record to point to the standby instance's IP address, effectively migrating the VIP. This allows clients to reconnect using the same DNS name without needing an elastic IP or a network-level VIP, which is not natively supported in AWS for this use case.

Exam trap

The trap here is that candidates often assume a traditional on-premises VIP (e.g., using a floating IP with ARP) is required, but AWS does not support that, so the correct answer is a DNS-based solution like Route 53, not a load balancer or accelerator.

How to eliminate wrong answers

Option A is wrong because AWS Global Accelerator provides static anycast IP addresses and traffic acceleration, but it does not support the dynamic, application-level VIP failover required for SAP ASCS/ERS HA clusters; it is designed for global traffic distribution, not for managing a single VIP that follows a cluster resource. Option C is wrong because AWS WAF is a web application firewall that protects against common web exploits, and it has no capability to manage or failover a virtual IP address for SAP Central Services. Option D is wrong because an Application Load Balancer distributes traffic across multiple targets at Layer 7, but it cannot be used to assign a single, floating VIP to an active-passive SAP ASCS/ERS cluster; the HA cluster requires a VIP that moves with the active node, which ALB does not support.

Practice this question →
159
MCQmedium

A company is experiencing performance issues with their SAP ERP system on AWS. The system is running on an r5.4xlarge EC2 instance with gp2 EBS volumes. The database is SAP HANA. CloudWatch metrics show high write latency on the data volume. Which change would most likely improve performance?

A.Increase the size of the gp2 volume to get more baseline IOPS
B.Move the database to a t3.large instance
C.Enable EBS optimization on the instance
D.Change the volume type to io2 Block Express
AnswerD

io2 Block Express offers consistent low latency and high IOPS for SAP HANA.

Why this answer

SAP HANA is highly sensitive to storage latency, and the high write latency on the data volume indicates that gp2's burst model is insufficient for sustained write workloads. io2 Block Express provides consistent, sub-millisecond latency with provisioned IOPS up to 256,000, which directly addresses the performance bottleneck. This change aligns with AWS best practices for SAP HANA production workloads, which recommend io2 volumes for data and log volumes.

Exam trap

The trap here is that candidates often assume increasing gp2 volume size (Option A) is a simple fix for IOPS, but they overlook that gp2's burst model cannot sustain the high-write, low-latency requirements of SAP HANA, and that AWS explicitly recommends io2 volumes for production HANA workloads.

How to eliminate wrong answers

Option A is wrong because increasing the size of a gp2 volume does increase baseline IOPS, but gp2's IOPS are tied to volume size and burst bucket performance; for SAP HANA's sustained high-write workloads, gp2 cannot guarantee consistent low latency, and the improvement from size increase is marginal compared to switching to a provisioned IOPS volume. Option B is wrong because moving to a t3.large instance would reduce CPU and memory resources significantly (t3.large has 2 vCPUs and 8 GiB RAM vs. r5.4xlarge's 16 vCPUs and 128 GiB RAM), which would severely degrade SAP HANA performance and is not a valid solution for write latency issues. Option C is wrong because EBS optimization is already enabled by default on all current-generation EC2 instances (including r5.4xlarge), so toggling it would have no effect; the issue is with the storage volume type, not the network/storage path.

Practice this question →
160
MCQmedium

An SAP administrator is creating an IAM policy to allow SAP basis users to manage their own SAP EC2 instances. The policy above is intended to allow users to start, stop, and reboot instances tagged with their username. However, users report that they cannot start instances. What is the MOST likely reason?

A.The condition references ${aws:username} which is not available in the context.
B.The condition key ec2:ResourceTag/SAPSystem is not valid.
C.The actions are not correct for managing instances.
D.The ec2:StartInstances action does not support resource-level permissions; it requires a separate condition or a wildcard resource.
AnswerD

StartInstances does not support resource-level permissions, so the condition doesn't apply.

Why this answer

The ec2:StartInstances action does not support resource-level permissions in IAM policies. This means that even if the policy specifies a condition based on tags, the condition is ignored for StartInstances, and the action will be denied unless the resource element is set to a wildcard ('*'). AWS documentation explicitly states that StartInstances, StopInstances, and RebootInstances require a wildcard resource or a separate condition to allow the action, making option D the correct answer.

Exam trap

The trap here is that candidates assume all EC2 actions support resource-level permissions and conditions, but AWS explicitly excludes certain actions like StartInstances, StopInstances, and RebootInstances from this support, requiring a wildcard resource or a separate condition to function correctly.

How to eliminate wrong answers

Option A is wrong because ${aws:username} is a valid IAM policy variable that resolves to the IAM user's username, and it is available in the request context for most AWS services, including EC2. Option B is wrong because ec2:ResourceTag/SAPSystem is a valid condition key that can be used to filter EC2 instances based on their tags, and there is no inherent issue with its syntax. Option C is wrong because the actions ec2:StartInstances, ec2:StopInstances, and ec2:RebootInstances are indeed the correct actions for starting, stopping, and rebooting EC2 instances, so the actions themselves are not the problem.

Practice this question →
161
MCQhard

An SAP administrator notices that the SAP application server is experiencing high latency when reading from the shared /sapmnt directory mounted from an Amazon EFS file system. The EFS file system is in General Purpose performance mode and uses Bursting throughput mode. The administrator checks CloudWatch metrics and sees that BurstCreditBalance is near zero. What is the most cost-effective solution to address the latency?

A.Increase the size of the EFS file system to increase the burst credit balance
B.Enable Provisioned Throughput mode on the EFS file system
C.Mount the /sapmnt directory from an Amazon EBS gp3 volume instead
D.Change the EFS performance mode to Max I/O
AnswerB

Provides consistent throughput without burst credits.

Why this answer

The BurstCreditBalance is near zero, indicating the file system has exhausted its burst credits under Bursting throughput mode. Enabling Provisioned Throughput mode allows you to specify a consistent throughput level independent of the file system's size, eliminating reliance on burst credits and resolving the latency for the /sapmnt directory. This is the most cost-effective solution as it avoids the need to increase storage size (Option A) or migrate to a different storage service.

Exam trap

The trap here is that candidates may assume increasing storage size (Option A) is the only way to increase throughput under Bursting mode, overlooking that Provisioned Throughput mode provides a direct, cost-effective alternative without requiring additional storage.

How to eliminate wrong answers

Option A is wrong because increasing the size of the EFS file system does increase the baseline throughput and burst credit accumulation rate, but it is not the most cost-effective solution; it would require significant additional storage capacity that may not be needed, and the latency issue is due to credit exhaustion, not insufficient size. Option C is wrong because mounting /sapmnt from an Amazon EBS gp3 volume would require re-architecting the shared filesystem for SAP, as EBS volumes are single-AZ and cannot be shared across multiple EC2 instances in different Availability Zones, which is critical for SAP application servers. Option D is wrong because changing the performance mode to Max I/O improves throughput for highly parallel workloads but does not address the underlying throughput credit exhaustion; Max I/O mode is designed for large-scale, concurrent access patterns and may not provide consistent low latency for the /sapmnt directory's metadata-heavy operations.

Practice this question →
162
MCQmedium

An SAP administrator needs to configure high availability for SAP NetWeaver AS ABAP. They plan to use AWS services. Which combination of services is required?

A.Amazon EFS and Pacemaker on EC2
B.AWS Global Accelerator and Auto Scaling
C.Elastic Load Balancing and Amazon Route 53
D.Amazon EBS Multi-Attach volumes
AnswerA

EFS provides shared storage; Pacemaker manages clustering.

Why this answer

SAP NetWeaver AS ABAP high availability on AWS requires shared storage for the /sapmnt and /usr/sap/trans directories, which Amazon EFS provides via NFSv4, and a cluster manager like Pacemaker on EC2 to orchestrate failover between the primary and secondary application servers. This combination ensures that the SAP central services (ASCS and ERS) can fail over seamlessly in the event of an instance or availability zone failure.

Exam trap

The trap here is that candidates often confuse general AWS HA services (like ELB or Auto Scaling) with the specific shared-storage and cluster-manager requirements of SAP NetWeaver AS ABAP, leading them to overlook the necessity of a cluster filesystem (EFS) and a cluster resource manager (Pacemaker).

How to eliminate wrong answers

Option B is wrong because AWS Global Accelerator and Auto Scaling are designed for improving network performance and scaling web/application tiers, not for orchestrating SAP application-level failover or providing the shared file system required by SAP NetWeaver AS ABAP. Option C is wrong because Elastic Load Balancing and Amazon Route 53 handle traffic distribution and DNS routing, but they do not provide the shared storage (e.g., /sapmnt) or the cluster fencing and resource management needed for SAP ASCS/ERS high availability. Option D is wrong because Amazon EBS Multi-Attach volumes support concurrent attachment to multiple EC2 instances only within a single Availability Zone, which violates the cross-AZ high availability requirement for SAP; additionally, SAP NetWeaver AS ABAP requires a distributed file system like NFS, not block-level shared storage.

Practice this question →
163
MCQeasy

An SAP administrator wants to monitor the CPU utilization of SAP application servers using Amazon CloudWatch. What is the minimum configuration required?

A.Install and configure the AWS CloudWatch Agent on each SAP application server.
B.Set up an AWS Lambda function to query EC2 metrics from the CloudWatch API.
C.Configure SAP Solution Manager to export metrics to CloudWatch.
D.Enable EC2 detailed monitoring from the AWS Management Console.
AnswerA

Agent collects OS-level metrics and sends to CloudWatch.

Why this answer

The AWS CloudWatch Agent must be installed and configured on each SAP application server to collect custom metrics like CPU utilization at the granularity and frequency required for SAP monitoring. CloudWatch by default only provides basic EC2 metrics (every 5 minutes) and cannot capture OS-level or application-level CPU utilization without the agent. The agent sends metrics via the CloudWatch PutMetricData API, enabling detailed monitoring of SAP-specific performance counters.

Exam trap

The trap here is that candidates often confuse enabling EC2 detailed monitoring (Option D) with collecting OS-level metrics, not realizing that detailed monitoring only increases the frequency of hypervisor-level metrics and does not provide the application-specific CPU data required for SAP monitoring.

How to eliminate wrong answers

Option B is wrong because AWS Lambda querying EC2 metrics from the CloudWatch API would only retrieve existing EC2-level metrics (e.g., CPUUtilization at 5-minute intervals) and cannot provide the OS-level or SAP-process-level CPU utilization needed; it adds no new data collection capability. Option C is wrong because SAP Solution Manager does not natively export metrics to CloudWatch; it uses its own monitoring infrastructure (e.g., CCMS, Wily Introscope) and would require a custom integration or adapter to forward data to CloudWatch. Option D is wrong because enabling EC2 detailed monitoring (1-minute intervals) only increases the frequency of hypervisor-level CPU metrics, not OS-level or application-specific CPU utilization, and still cannot capture SAP application server process metrics.

Practice this question →
164
Multi-Selecthard

An SAP system on AWS is using an SAP HANA database. The database administrator wants to monitor memory usage and receive alerts when memory consumption exceeds 90%. Which THREE services can be used together to achieve this?

Select 3 answers
A.Amazon Simple Notification Service (SNS)
B.Amazon CloudWatch custom metrics for SAP HANA
C.AWS Config
D.Amazon CloudWatch Alarms
E.Amazon Inspector
AnswersA, B, D

SNS can send notifications when alarms are triggered.

Why this answer

Amazon Simple Notification Service (SNS) is correct because it provides a fully managed pub/sub messaging service that can deliver alerts (e.g., via email, SMS, or HTTP endpoints) when triggered by an Amazon CloudWatch Alarm. In this scenario, once the CloudWatch Alarm detects that memory usage exceeds 90%, it publishes to an SNS topic, which then sends the notification to the database administrator. This enables real-time alerting without requiring custom polling or additional infrastructure.

Exam trap

The trap here is that candidates may confuse AWS Config (which audits configuration changes) with CloudWatch (which monitors performance metrics), or assume Amazon Inspector can monitor memory usage because it runs assessments on EC2 instances, but Inspector only checks for security vulnerabilities, not resource utilization.

Practice this question →
165
MCQmedium

A company is running SAP NetWeaver on AWS. The system uses an SAP HANA database. The operations team needs to monitor the database performance and receive alerts when specific metrics exceed thresholds. Which AWS service should be used to collect and analyze SAP HANA metrics?

A.Amazon CloudWatch
B.Amazon Inspector
C.AWS CloudTrail
D.AWS Config
AnswerA

CloudWatch can collect and alarm on custom metrics from HANA.

Why this answer

Amazon CloudWatch is the correct service because it can collect, monitor, and analyze SAP HANA database metrics using the AWS CloudWatch Agent or the SAP HANA CloudWatch integration. By configuring custom metrics or using the SAP HANA monitoring views, operations teams can set CloudWatch Alarms to trigger notifications when specific thresholds are exceeded, enabling proactive performance management.

Exam trap

The trap here is that candidates often confuse AWS CloudTrail (audit logging) or AWS Config (configuration compliance) with monitoring services, but only CloudWatch provides the metric collection, alarm, and notification capabilities required for real-time SAP HANA performance monitoring.

How to eliminate wrong answers

Option B is wrong because Amazon Inspector is a vulnerability management service that scans workloads for software vulnerabilities and unintended network exposure, not for collecting or analyzing database performance metrics. Option C is wrong because AWS CloudTrail records API activity and governance events for auditing, not real-time database performance monitoring or metric collection. Option D is wrong because AWS Config evaluates and records resource configuration changes for compliance and auditing, not for monitoring runtime database performance metrics like memory or CPU usage.

Practice this question →
166
MCQhard

An SAP workload on AWS uses an Auto Scaling group for the SAP Central Services (ASCS) and Enqueue Replication Server (ERS) instances. The instances are launched with a custom AMI that includes the SAP software. During a recent failover test, the ASCS instance failed to start after being terminated and re-launched by the Auto Scaling group. The error log indicates that the ASCS instance cannot find the quorum device. What is the most likely cause of this issue?

A.The quorum device (EBS volume) was not re-attached or was not available in the same Availability Zone as the new ASCS instance.
B.The instance type of the new ASCS instance is different from the original, causing incompatibility with the SAP kernel.
C.The ASCS instance does not have a public IP address, preventing communication with the quorum device.
D.The Security Group associated with the ASCS instance does not allow inbound traffic on the quorum port.
AnswerA

In a multi-AZ setup, the quorum device must be accessible to the new instance; if it's an EBS volume, it is tied to a specific AZ.

Why this answer

In an SAP on AWS high-availability setup, the ASCS and ERS instances rely on a shared quorum device (typically an EBS volume or an Amazon EFS file system) to maintain cluster state and prevent split-brain scenarios. When the Auto Scaling group terminates and re-launches the ASCS instance, the new instance must have the quorum device attached and be in the same Availability Zone as the EBS volume (since EBS volumes are AZ-specific). If the quorum device is not re-attached or is in a different AZ, the SAP cluster cannot find it, causing the ASCS instance to fail to start.

Exam trap

The trap here is that candidates may think the issue is related to network connectivity or security groups, but the real problem is the AZ-specific nature of EBS volumes and the requirement to re-attach the quorum device to the new instance.

How to eliminate wrong answers

Option B is wrong because the SAP kernel is not tied to a specific instance type; it runs on any supported instance type as long as the architecture (x86_64) and operating system match. Option C is wrong because the quorum device is accessed via block storage (EBS) or shared file system (EFS), not over the network using a public IP address; communication with the quorum device does not require a public IP. Option D is wrong because the quorum device is not accessed via a network port; it is a storage resource, so security group rules for inbound traffic are irrelevant to quorum device discovery.

Practice this question →
167
MCQeasy

A company is deploying SAP S/4HANA on AWS. They need to choose the appropriate storage for the database volume to meet high IOPS and low latency requirements. Which AWS storage service should they use?

A.Amazon EFS
B.Amazon S3
C.Amazon EBS io2 Block Express volumes
D.Amazon EBS gp3 volumes
AnswerC

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

Why this answer

Amazon EBS io2 Block Express volumes are designed for mission-critical SAP HANA workloads, offering up to 256,000 IOPS per volume and sub-millisecond latency. They provide 99.999% durability and meet the high-performance requirements for SAP S/4HANA database volumes on AWS.

Exam trap

The trap here is that candidates may choose gp3 volumes (Option D) because they are cost-effective and offer baseline performance, but they fail to recognize that SAP HANA requires the ultra-high IOPS and sub-millisecond latency that only io2 Block Express can guarantee for production workloads.

How to eliminate wrong answers

Option A is wrong because Amazon EFS is a file-level NFS storage service that does not provide the high IOPS or low latency required for SAP HANA database volumes, and it is not supported as a direct database storage option for SAP S/4HANA. Option B is wrong because Amazon S3 is an object storage service with higher latency and lower IOPS, unsuitable for transactional database workloads like SAP HANA that require block-level access. Option D is wrong because Amazon EBS gp3 volumes, while offering baseline performance and burst capability, cannot match the maximum IOPS (16,000 per volume) and consistent sub-millisecond latency of io2 Block Express, making them inadequate for high-performance SAP HANA requirements.

Practice this question →
168
MCQmedium

A company is migrating an SAP S/4HANA system to AWS. The system requires high availability across two Availability Zones. Which AWS service should be used to attach a block-level storage volume that can be concurrently accessed by two EC2 instances in active/passive mode?

A.Use Amazon FSx for NetApp ONTAP to provide a shared block storage volume accessible from both AZs.
B.Use Amazon FSx for Windows File Server with a multi-AZ file system.
C.Use Amazon S3 as a shared block storage device.
D.Use Amazon EBS Multi-Attach to attach a single EBS volume to both EC2 instances across AZs.
AnswerA

FSx for NetApp ONTAP supports shared block storage across AZs.

Why this answer

Amazon FSx for NetApp ONTAP provides a shared block-level storage volume that can be concurrently accessed by multiple EC2 instances across different Availability Zones using the iSCSI protocol. In an active/passive SAP S/4HANA setup, this allows the passive instance to mount the same storage volume and take over if the active instance fails, meeting the high-availability requirement across two AZs.

Exam trap

The trap here is that candidates often assume Amazon EBS Multi-Attach can work across Availability Zones, but it is strictly limited to instances within the same AZ, making it unsuitable for multi-AZ high availability in SAP workloads.

How to eliminate wrong answers

Option B is wrong because Amazon FSx for Windows File Server provides file-level (SMB) storage, not block-level storage, and is not designed for concurrent block-level access by EC2 instances in an active/passive SAP scenario. Option C is wrong because Amazon S3 is an object storage service, not a block-level storage device, and cannot be attached as a block volume to EC2 instances. Option D is wrong because Amazon EBS Multi-Attach only supports attaching a single EBS volume to multiple EC2 instances within the same Availability Zone, not across different AZs, and it does not support active/passive failover across AZs.

Practice this question →
169
MCQeasy

A company is running SAP ERP on AWS and wants to ensure that their SAP system is backed up according to SAP best practices. Which backup method should they use for the SAP HANA database?

A.AWS Backup service
B.EBS snapshots of the data volumes
C.SAP HANA Backint to Amazon S3
D.Amazon S3 replication
AnswerC

Backint provides integrated, consistent backups.

Why this answer

SAP HANA Backint to Amazon S3 is the correct backup method because it integrates directly with SAP HANA's native backup interface (Backint), allowing SAP to manage backup and restore operations natively. This approach supports SAP best practices for HANA database backups, including full, incremental, and differential backups, and leverages Amazon S3 for durable, scalable storage without requiring external scripting or manual snapshot coordination.

Exam trap

The trap here is that candidates often assume EBS snapshots are sufficient for database backups because they work for other databases, but SAP HANA requires application-consistent backups via Backint to maintain transactional integrity and support SAP's certified recovery procedures.

How to eliminate wrong answers

Option A is wrong because AWS Backup service does not natively support SAP HANA database backups via the Backint API; it can only back up EBS volumes or EC2 instances, which are not crash-consistent for HANA without application-level coordination. Option B is wrong because EBS snapshots of data volumes are not application-consistent for SAP HANA unless the database is frozen or stopped, which violates SAP best practices for online backups and can lead to data corruption or recovery failures. Option D is wrong because Amazon S3 replication is a storage-level feature for copying objects between S3 buckets, not a backup method for SAP HANA databases; it does not interact with HANA's backup interface or ensure transactional consistency.

Practice this question →
170
MCQmedium

A company is designing an SAP HANA disaster recovery (DR) solution on AWS. The primary site is in us-east-1, and the DR site is in us-west-2. The RPO is 15 minutes, and the RTO is 2 hours. Which AWS service should be used for replicating the SAP HANA database to the DR site?

A.SAP HANA System Replication with log shipping using Amazon S3 or direct VPN connection.
B.Amazon S3 Cross-Region Replication for database backup files.
C.Amazon EBS snapshots replicated to us-west-2 via Amazon Data Lifecycle Manager.
D.AWS Database Migration Service (DMS) with ongoing replication.
AnswerA

SAP HANA System Replication provides synchronous or asynchronous replication with low RPO.

Why this answer

SAP HANA System Replication (HSR) is the native, SAP-supported mechanism for real-time database replication, capable of achieving sub-minute RPOs by continuously shipping log entries to a secondary system. When combined with a direct VPN connection or Amazon S3 as a log shipping target, it meets the 15-minute RPO and 2-hour RTO requirements for disaster recovery across AWS regions. This is the only option that provides synchronous or near-synchronous replication of the HANA database itself, not just backups or snapshots.

Exam trap

The trap here is that candidates often confuse backup replication (S3 CRR or EBS snapshots) with live database replication, failing to recognize that SAP HANA System Replication is the only AWS-supported method that provides the required RPO by replicating transactional logs in near real-time.

How to eliminate wrong answers

Option B is wrong because Amazon S3 Cross-Region Replication replicates only static backup files (e.g., data or log backups) stored in S3, not the live database transactions, so it cannot achieve a 15-minute RPO for ongoing changes. Option C is wrong because Amazon EBS snapshots replicated via Data Lifecycle Manager capture point-in-time disk states, but they are not application-consistent for SAP HANA without additional scripting, and the snapshot frequency (typically every 1-24 hours) cannot meet a 15-minute RPO. Option D is wrong because AWS Database Migration Service (DMS) with ongoing replication is designed for heterogeneous database migrations and does not support SAP HANA as a source for continuous change data capture (CDC) replication.

Practice this question →
171
MCQmedium

A company is designing an SAP S/4HANA workload on AWS. The system must be highly available within a single AWS Region. Which architecture ensures automatic failover for the SAP Central Services (ASCS) instance?

A.Place an Application Load Balancer (ALB) in front of two ASCS instances in different Availability Zones.
B.Deploy ASCS on a single EC2 instance with multiple Elastic Network Interfaces (ENIs).
C.Use Amazon CloudFront to distribute traffic to multiple ASCS instances in different Availability Zones.
D.Configure Amazon Route 53 with health checks to failover to a secondary ASCS instance in a different Availability Zone.
AnswerD

Route 53 health checks can monitor the primary ASCS and automatically route traffic to a standby instance in another AZ.

Why this answer

Amazon Route 53 with health checks can monitor the primary ASCS instance and automatically fail over DNS resolution to a secondary ASCS instance in a different Availability Zone. This provides the necessary automatic failover for SAP Central Services (ASCS) without requiring a shared filesystem or cluster manager, as Route 53 health checks detect instance or service failure and update DNS records accordingly.

Exam trap

The trap here is that candidates often assume a load balancer (ALB) is required for high availability, but SAP ASCS uses proprietary protocols that ALB cannot inspect or health-check, making DNS-based failover with Route 53 the correct AWS-native approach.

How to eliminate wrong answers

Option A is wrong because an Application Load Balancer (ALB) operates at Layer 7 and cannot properly handle the proprietary SAP-specific protocols (e.g., Message Server and Enqueue Server) used by ASCS; ALB does not support the required health checks or session persistence for SAP Central Services. Option B is wrong because deploying ASCS on a single EC2 instance with multiple Elastic Network Interfaces (ENIs) does not provide any failover capability; it only adds network redundancy within the same instance, which is a single point of failure. Option C is wrong because Amazon CloudFront is a content delivery network (CDN) designed for static and dynamic web content distribution, not for routing SAP proprietary traffic to ASCS instances; it cannot perform health checks or failover for SAP services.

Practice this question →
172
MCQeasy

A company is running SAP Business Suite on AWS using an Oracle database. They need to migrate the Oracle database to SAP HANA as part of an SAP S/4HANA conversion. The current Oracle database size is 5 TB and runs on an r5.8xlarge instance. The target HANA database will run on an r5.24xlarge instance. The company wants to minimize downtime. What is the best approach to migrate the data?

A.Use AWS Database Migration Service (DMS) to continuously replicate data from Oracle to HANA, then switch over.
B.Use SAP Landscape Transformation (SLT) to replicate data in real-time from Oracle to HANA.
C.Use Oracle Data Pump to export the database and import into HANA using SAP HANA studio.
D.Use SAP Software Update Manager (SUM) with the Database Migration Option (DMO) to migrate and upgrade in one step.
AnswerD

SUM with DMO performs the migration and upgrade in a single process, minimizing downtime.

Why this answer

SAP provides the Software Update Manager (SUM) with DMO (Database Migration Option) to perform the migration and upgrade in one step, minimizing downtime. Option A (native Oracle export/import) is time-consuming. Option B (AWS DMS) is not fully supported for SAP HANA as target.

Option C (SAP Landscape Transformation) is for data replication but not for a one-step migration with upgrade. Option D is correct.

Practice this question →
173
MCQhard

An SAP administrator notices that the SAP HANA database is running out of memory frequently. The system is deployed on an EC2 instance with 512 GB of RAM. The HANA memory usage is peaking at 480 GB. What should the administrator do to resolve this issue?

A.Configure a swap file on the instance's root EBS volume
B.Enable HANA memory overcommit and set the memory limit to 90%
C.Migrate to an instance with more memory, such as x1e.32xlarge
D.Reduce the number of HANA table partitions
AnswerC

Correct. Migrating to a larger instance like x1e.32xlarge provides 976 GB of RAM, which comfortably accommodates the current peak of 480 GB and allows for growth. This is the most effective solution to resolve the out-of-memory issue.

Why this answer

The HANA database is peaking at 480 GB on a 512 GB instance, indicating that memory is nearly fully utilized. Enabling memory overcommit and setting the HANA memory limit to 90% (460.8 GB) would still be below the peak usage, potentially causing out-of-memory errors. The most straightforward and reliable solution is to migrate to a larger instance type, such as x1e.32xlarge, which offers 976 GB of RAM, providing sufficient headroom for current and future peak demands.

This aligns with AWS best practices for SAP HANA workloads.

Exam trap

The trap is that candidates might think enabling memory overcommit (Option B) is sufficient, but they overlook that the current peak usage exceeds the 90% limit of the existing instance. The correct approach is to upgrade to a larger instance to provide adequate memory headroom.

How to eliminate wrong answers

Option A is wrong because configuring a swap file on the root EBS volume is not recommended for SAP HANA; HANA is designed to run entirely in memory, and swap usage would cause severe performance degradation and potential data corruption, as HANA does not handle swapping gracefully. Option C is wrong because migrating to a larger instance like x1e.32xlarge (which has 3,904 GB of RAM) is an unnecessary and costly overprovisioning; the current instance has 512 GB and HANA peaks at 480 GB, so the issue is memory management, not capacity. Option D is wrong because reducing the number of HANA table partitions does not address the root cause of memory exhaustion; partitioning affects query performance and data distribution, not the overall memory limit or kernel memory management behavior.

Practice this question →
174
MCQeasy

An SAP Basis administrator is migrating an SAP NetWeaver system from on-premises to AWS. They want to minimize downtime during the migration of the database. Which AWS service is best suited for this?

A.AWS Server Migration Service (SMS)
B.AWS CloudEndure Migration
C.AWS Database Migration Service (DMS)
D.AWS Snowball Edge
AnswerC

DMS supports ongoing replication for minimal downtime.

Why this answer

AWS Database Migration Service (DMS) is best suited for migrating SAP NetWeaver databases with minimal downtime because it supports heterogeneous and homogeneous database migrations with ongoing replication. DMS can perform a full load of the database and then continuously replicate changes from the source to the target using change data capture (CDC), allowing the source database to remain operational until the cutover. This minimizes downtime to just the final switchover window, which is critical for SAP systems.

Exam trap

The trap here is that candidates confuse AWS DMS with server-level migration tools like SMS or CloudEndure, mistakenly thinking that replicating the entire server is equivalent to database replication, but DMS is the only service that provides native CDC for database-specific minimal downtime migrations.

How to eliminate wrong answers

Option A is wrong because AWS Server Migration Service (SMS) is designed for migrating entire virtual machines as images, not for database-level replication with minimal downtime; it would require taking the SAP database offline to create a consistent snapshot. Option B is wrong because AWS CloudEndure Migration is a block-level replication service for entire servers, not optimized for database-specific replication with CDC; it would replicate the entire OS and application stack, increasing complexity and potential downtime for an SAP database migration. Option D is wrong because AWS Snowball Edge is a physical data transfer device for large-scale offline data movement, not suitable for minimizing downtime as it requires stopping writes to the database, packaging data, and shipping the device, which introduces significant downtime.

Practice this question →
175
MCQhard

An SAP HANA administrator is troubleshooting a performance issue on an EC2 instance (r5.8xlarge) running SAP HANA. The instance has two EBS volumes attached. Based on the exhibit, which additional information is needed to determine if the instance is optimized for SAP HANA?

A.Whether the instance is EBS-optimized or has dedicated EBS bandwidth.
B.Whether the instance is in a placement group.
C.The volume type and IOPS of the attached EBS volumes.
D.Whether the AMI used is SAP-certified.
AnswerA

SAP HANA requires EBS optimization; the exhibit does not show this attribute (shown in describe-instances as 'EbsOptimized').

Why this answer

SAP HANA requires high and consistent network throughput for data replication and client access, and the instance must be EBS-optimized or have dedicated EBS bandwidth to ensure that EBS I/O does not contend with network I/O. Without this confirmation, the administrator cannot guarantee that the instance meets SAP's performance requirements for HANA workloads, as non-optimized instances share the same network interface for both EBS and data traffic, leading to potential bottlenecks.

Exam trap

The trap here is that candidates often focus on storage parameters like volume type and IOPS (Option C) because they are directly tied to SAP HANA's performance, but the question specifically asks about the instance's optimization, which is a network-level attribute that controls how EBS traffic is handled, not the storage configuration itself.

How to eliminate wrong answers

Option B is wrong because a placement group affects network latency and throughput between instances, but it does not directly impact the instance's ability to handle EBS I/O or its optimization for SAP HANA. Option C is wrong because while volume type and IOPS are important for storage performance, the question specifically asks about the instance's optimization for SAP HANA, which is determined by EBS-optimization or dedicated bandwidth, not the volume specifications themselves. Option D is wrong because the AMI certification ensures the operating system and SAP HANA software are compatible, but it does not address the underlying instance's network and EBS I/O architecture required for optimized performance.

Practice this question →
176
MCQmedium

A company is planning to migrate their SAP ECC system to AWS. They want to minimize downtime and use an automated approach. Which AWS service should be used for the migration?

A.AWS Application Discovery Service
B.AWS CloudFormation
C.AWS Launch Wizard
D.AWS Server Migration Service
AnswerC

Launch Wizard automates SAP deployment and migration with best practices.

Why this answer

AWS Launch Wizard for SAP is the correct choice because it provides a guided, automated deployment of SAP ECC on AWS, including infrastructure provisioning, OS configuration, and SAP installation. It minimizes downtime by automating the entire migration process, from sizing to deployment, using predefined best practices.

Exam trap

The trap here is that candidates often confuse AWS Server Migration Service (SMS) with a general-purpose migration tool, but SMS only handles VM-level replication and cannot automate the SAP-specific installation and configuration steps required for a production SAP ECC migration.

How to eliminate wrong answers

Option A is wrong because AWS Application Discovery Service is used for discovering on-premises application dependencies and usage patterns, not for automating the migration of SAP systems. Option B is wrong because AWS CloudFormation is an infrastructure-as-code service that can provision resources but lacks the SAP-specific automation, sizing, and installation logic required for a seamless SAP migration. Option D is wrong because AWS Server Migration Service (SMS) is designed for migrating virtual machines as images, not for handling the complex, multi-tier SAP ECC system with its database and application layers, and it does not automate SAP-specific configurations.

Practice this question →
177
MCQmedium

A company is deploying SAP Business Suite on AWS. They need to ensure that the SAP system can handle a sudden increase in user load without manual intervention. Which AWS service should be used to automatically scale the SAP application servers?

A.AWS Lambda
B.Amazon Elastic Container Service
C.Elastic Load Balancing
D.AWS Auto Scaling
AnswerD

Auto Scaling adjusts the number of EC2 instances automatically.

Why this answer

AWS Auto Scaling is the correct service because it automatically adjusts the number of SAP application server instances based on demand, using scaling policies tied to metrics like CPU utilization or memory. This ensures the SAP system can handle sudden user load spikes without manual intervention, which is a core requirement for elastic SAP deployments on AWS.

Exam trap

The trap here is that candidates often confuse Elastic Load Balancing with auto-scaling, thinking that load balancing alone provides elasticity, but ELB only distributes traffic and does not manage instance count.

How to eliminate wrong answers

Option A is wrong because AWS Lambda is a serverless compute service for event-driven code, not designed to run or scale SAP application servers, which require persistent, stateful operating system environments. Option B is wrong because Amazon Elastic Container Service (ECS) manages Docker containers, but SAP Business Suite is traditionally deployed on EC2 instances with specific OS and kernel requirements, not containerized. Option C is wrong because Elastic Load Balancing distributes incoming traffic across existing instances but does not automatically add or remove instances; it requires an external scaling mechanism like Auto Scaling to adjust capacity.

Practice this question →
178
Multi-Selectmedium

Which TWO Amazon CloudWatch metrics are most useful for monitoring SAP HANA database performance on EC2?

Select 2 answers
A.CPUCreditBalance
B.NetworkIn
C.DiskWriteOps
D.VolumeQueueLength
E.StatusCheckFailed
AnswersA, D

Important for T2/T3 instances to avoid throttling.

Why this answer

CPUCreditBalance (A) is critical for monitoring SAP HANA on EC2 because HANA is a memory- and CPU-intensive in-memory database that can burst CPU usage. If the instance runs on a T-series burstable instance, a low CPUCreditBalance indicates the instance may soon be throttled, causing severe performance degradation for HANA queries. VolumeQueueLength (D) is essential because SAP HANA relies on fast, low-latency storage (e.g., io1/io2 EBS volumes) for data persistence; a high queue length signals that I/O requests are backing up, directly impacting HANA's savepoint and log write performance.

Exam trap

The trap here is that candidates often confuse general EC2 health metrics (like StatusCheckFailed) or high-level throughput metrics (NetworkIn, DiskWriteOps) with the specific performance indicators that directly impact SAP HANA's in-memory and I/O-sensitive workload, leading them to overlook the burst credit and queue depth metrics that AWS explicitly documents for HANA monitoring.

Practice this question →
179
Multi-Selectmedium

A company is designing a disaster recovery (DR) strategy for its SAP landscape on AWS. The DR site must be in a different AWS Region. Which TWO options can be used to replicate the SAP HANA database to the DR Region? (Choose TWO.)

Select 2 answers
A.Amazon RDS Multi-Region replica
B.Amazon S3 Cross-Region Replication for HANA backup files
C.AWS Database Migration Service (DMS) with ongoing replication
D.SAP HANA System Replication across Regions
E.Amazon EBS snapshot copy to the DR Region
AnswersC, D

DMS can replicate HANA data to another region.

Why this answer

AWS DMS with ongoing replication can continuously replicate SAP HANA database changes to a target HANA instance in another Region using change data capture (CDC), enabling near-real-time synchronization for DR purposes. Option D is correct because SAP HANA System Replication can be configured across AWS Regions to replicate the HANA database synchronously or asynchronously, providing a native disaster recovery solution. Both methods are valid for replicating SAP HANA to a different AWS Region.

Exam trap

The trap here is that candidates may overlook that SAP HANA is not supported on Amazon RDS, leading them to incorrectly select Multi-Region replica, or they may assume EBS snapshot copy provides continuous replication when it only offers periodic, point-in-time copies.

Practice this question →
180
MCQmedium

A company runs SAP S/4HANA on AWS using a distributed architecture with separate instances for the database (DB) and application (ASCS, PAS, AAS). The application servers are in an Auto Scaling group. After a recent scaling event, users report that they cannot log in to the system. The SAP dispatcher logs show that the application servers cannot connect to the message server. What is the most likely cause?

A.The database connection string in the new application servers points to the wrong endpoint.
B.The new application servers are not registered in the SAP message server's configuration.
C.The SAP licenses are exhausted and need to be updated.
D.The security group of the application servers is not allowing outbound traffic to the DB server.
AnswerB

Auto Scaling instances must be registered in the SAP profile to communicate with the message server.

Why this answer

The most likely cause is that the new application servers launched by the Auto Scaling group are not registered in the SAP message server's configuration. In a distributed SAP system, each application server must be registered with the message server so that it can accept user logons and communicate with other components. If registration is missing, the dispatcher cannot connect to the message server, resulting in login failures.

Option A (database connection string) would cause database connectivity issues, not message server issues. Option C (licenses) would affect logons globally, not just after scaling. Option D (security group outbound) would block all traffic, not specifically message server traffic.

Practice this question →
181
MCQmedium

A company runs SAP on AWS and needs to implement a disaster recovery strategy for their SAP NetWeaver system. The primary site is in us-east-1, and the DR site is in us-west-2. They want to minimize data loss and recovery time. Which approach meets these requirements?

A.Use SAP HANA System Replication in asynchronous mode across regions.
B.Use SAP HANA System Replication in synchronous mode across regions.
C.Use AWS Backup to back up the SAP HANA database and restore in us-west-2.
D.Use Amazon S3 cross-region replication for SAP HANA data files.
AnswerA

Async replication provides low RPO and RTO for cross-region DR.

Why this answer

SAP HANA System Replication in asynchronous mode across regions is the correct approach because it provides near-zero recovery point objective (RPO) with minimal impact on primary system performance, while enabling rapid failover to the DR region in us-west-2. Asynchronous replication is suitable for cross-region scenarios where network latency would make synchronous mode impractical, and it meets the requirement to minimize both data loss and recovery time for SAP NetWeaver.

Exam trap

The trap here is that candidates often confuse synchronous mode as always better for data protection, but fail to recognize that cross-region latency makes synchronous replication impractical, leading to transaction timeouts or severe performance degradation, while asynchronous mode is the standard for multi-region DR in SAP on AWS.

How to eliminate wrong answers

Option B is wrong because synchronous mode across regions would introduce high latency and potential transaction blocking due to network round-trip times, making it unsuitable for cross-region DR and potentially causing application performance degradation. Option C is wrong because AWS Backup for SAP HANA provides point-in-time recovery but has a higher recovery time objective (RTO) due to the need to restore full database backups, and it does not support continuous replication for minimal data loss. Option D is wrong because Amazon S3 cross-region replication only replicates object-level data files and does not provide the transaction-consistent, log-based replication required for SAP HANA database recovery, nor does it support automated failover.

Practice this question →
182
MCQmedium

A company is migrating its SAP ERP system to AWS. The system has strict high availability requirements with a Recovery Point Objective (RPO) of 15 minutes and a Recovery Time Objective (RTO) of 2 hours. The SAP application and database (SAP HANA) must be in the same AWS Region but can be in different Availability Zones. Which architecture should the company use to meet these requirements?

A.Deploy SAP HANA in a single Availability Zone with asynchronous replication to a secondary instance in another AZ, and use manual failover.
B.Deploy SAP HANA in a Multi-AZ cluster using synchronous replication across two Availability Zones, with the SAP application servers in an Auto Scaling group across the same AZs.
C.Deploy SAP HANA on a single EC2 instance with EBS snapshots every 5 minutes, and use a secondary instance in another AZ with snapshots restored.
D.Deploy SAP HANA on a single EC2 instance with hourly backups to Amazon S3 and a script to restore the backup on a new instance in a different AZ.
AnswerB

Multi-AZ synchronous replication provides automatic failover and meets RPO and RTO.

Why this answer

It uses synchronous replication for SAP HANA across two Availability Zones, which ensures zero data loss and meets the RPO of 15 minutes. The Multi-AZ cluster with automatic failover achieves the RTO of 2 hours, while the SAP application servers in an Auto Scaling group across the same AZs provide high availability and load balancing. This architecture aligns with AWS best practices for SAP HANA HA, leveraging HANA System Replication (HSR) in sync mode.

Exam trap

The trap here is that candidates confuse asynchronous replication (which risks data loss) with synchronous replication (which ensures zero RPO), or they underestimate the recovery time of snapshot-based or backup-based approaches, assuming they can meet strict RTO/RPO targets.

How to eliminate wrong answers

Option A is wrong because asynchronous replication can result in data loss exceeding the 15-minute RPO, and manual failover increases RTO beyond 2 hours. Option C is wrong because EBS snapshots every 5 minutes cannot guarantee an RPO of 15 minutes due to snapshot consistency delays and restore times that exceed the 2-hour RTO. Option D is wrong because hourly backups to S3 provide an RPO of up to 60 minutes, failing the 15-minute requirement, and restoring from S3 takes longer than 2 hours, violating the RTO.

Practice this question →
183
MCQmedium

A company runs SAP S/4HANA on AWS and needs to back up the SAP HANA database to Amazon S3. They want to automate backups and ensure they are encrypted at rest. Which solution should they use?

A.Use AWS Backup to schedule backups to S3
B.Use an S3 lifecycle policy to transition backups to S3
C.Configure SAP HANA Backint agent to back up directly to S3 with SSE-S3 encryption
D.Use AWS KMS to encrypt backups and store them manually
AnswerC

Backint agent integrates with SAP HANA and supports encryption.

Why this answer

SAP HANA Backint is the native, certified method for integrating SAP HANA backups directly with Amazon S3. The Backint agent handles automated backup scheduling and, when configured with SSE-S3, ensures data is encrypted at rest using Amazon S3's server-side encryption, meeting both automation and encryption requirements without additional infrastructure.

Exam trap

The trap here is that candidates often assume AWS Backup can handle any database backup, but it lacks the specific SAP HANA Backint integration required for application-consistent, automated backups to S3.

How to eliminate wrong answers

Option A is wrong because AWS Backup does not natively support SAP HANA database backups; it can back up EC2 instances or EBS volumes but lacks the application-consistent integration required for SAP HANA's Backint interface. Option B is wrong because an S3 lifecycle policy manages object transitions and expiration after data is already in S3, not the backup process itself; it cannot initiate or automate SAP HANA backups. Option D is wrong because manually storing backups with AWS KMS encryption does not provide automation, and manual processes are error-prone and not suitable for production SAP HANA environments requiring scheduled, reliable backups.

Practice this question →
184
MCQeasy

A company wants to automate the deployment of SAP environments on AWS. Which AWS service should the company use to define the infrastructure as code?

A.AWS OpsWorks
B.AWS CodeDeploy
C.AWS Elastic Beanstalk
D.AWS CloudFormation
AnswerD

CloudFormation enables infrastructure as code.

Why this answer

AWS CloudFormation is the correct choice because it allows you to define your entire SAP infrastructure—including EC2 instances, VPCs, security groups, and storage—as code using JSON or YAML templates. This enables repeatable, version-controlled, and automated deployments of SAP environments, which is essential for infrastructure as code (IaC) practices.

Exam trap

The trap here is that candidates often confuse configuration management (OpsWorks) or application deployment (CodeDeploy) with infrastructure provisioning, leading them to select a service that manages servers or code rather than the underlying cloud resources.

How to eliminate wrong answers

Option A is wrong because AWS OpsWorks is a configuration management service that uses Chef and Puppet to manage server configurations, not to define infrastructure as code; it focuses on operating system and application configuration rather than provisioning cloud resources. Option B is wrong because AWS CodeDeploy is a deployment service that automates code deployments to running instances, not infrastructure provisioning; it handles application updates, not the underlying SAP infrastructure. Option C is wrong because AWS Elastic Beanstalk is a PaaS service for deploying web applications with automatic scaling and load balancing, but it does not support the complex, custom infrastructure requirements of SAP environments and lacks the granular control needed for SAP-specific configurations.

Practice this question →
185
MCQmedium

A company is running SAP S/4HANA on AWS. They are experiencing high read latency on their EBS volumes used for /usr/sap. Which of the following is the MOST effective way to improve read performance?

A.Use io2 Block Express volumes with provisioned IOPS.
B.Change the volume type to gp3 with higher throughput.
C.Move to a larger instance type with more network bandwidth.
D.Configure RAID 0 across multiple volumes.
AnswerA

io2 Block Express provides consistent low latency.

Why this answer

The io2 Block Express volume type provides the highest durability and consistent low-latency performance for SAP workloads, with up to 256,000 provisioned IOPS per volume. For /usr/sap, which is sensitive to read latency due to frequent binary and configuration file access, io2 Block Express ensures predictable sub-millisecond latency even under high I/O demand, directly addressing the high read latency issue.

Exam trap

The trap here is that candidates often confuse throughput improvements (gp3 or RAID 0) with latency reduction, but the question specifically targets read latency, which requires a volume type designed for consistent low-latency performance like io2 Block Express.

How to eliminate wrong answers

Option B is wrong because gp3 volumes, while offering baseline performance and burst capability, cannot match the ultra-low latency and consistent IOPS of io2 Block Express for latency-sensitive SAP /usr/sap directories. Option C is wrong because moving to a larger instance type with more network bandwidth improves network throughput, not EBS volume read latency, which is a storage-level performance characteristic. Option D is wrong because RAID 0 across multiple volumes increases throughput and IOPS but does not inherently reduce read latency per I/O operation, and it introduces complexity and risk of data loss without addressing the underlying volume performance.

Practice this question →
186
MCQeasy

A company is planning to migrate its SAP ERP system to AWS. The database is SAP HANA with a size of 3 TB. The company wants to minimize downtime during the migration. Which migration strategy should the company use?

A.Use HANA System Replication to replicate the database to an EC2 instance running HANA in the target AWS environment, then perform a takeover.
B.Export the HANA database to flat files using SAP HANA Studio, upload the files to Amazon S3, and import them into an EC2 HANA instance.
C.Use AWS Database Migration Service (DMS) with ongoing replication to migrate the database to Amazon RDS for SAP HANA.
D.Use AWS Backup to take a full backup of the on-premises HANA database and restore it to an EC2 instance in AWS.
AnswerA

HSR provides continuous replication with minimal downtime during the final switchover.

Why this answer

HANA System Replication (HSR) is the optimal strategy for minimizing downtime because it continuously replicates data from the on-premises HANA database to an EC2 instance running HANA in AWS. When the migration window opens, a simple takeover (failover) occurs, typically completing in minutes, which meets the requirement for minimal downtime. This approach avoids the lengthy export/import or backup/restore processes that would take hours for a 3 TB database.

Exam trap

The trap here is that candidates may assume AWS DMS or backup/restore services are suitable for SAP HANA migrations, but DMS does not support HANA as a target, and backup/restore methods cause significant downtime, whereas HANA System Replication is the only AWS-recommended approach for near-zero downtime migrations.

How to eliminate wrong answers

Option B is wrong because exporting a 3 TB HANA database to flat files via SAP HANA Studio and then importing from S3 would take many hours or days, causing significant downtime, and does not support ongoing replication to minimize the cutover window. Option C is wrong because AWS DMS does not support SAP HANA as a target for ongoing replication; Amazon RDS for SAP HANA is not a valid service (RDS supports only certain database engines like MySQL, PostgreSQL, Oracle, SQL Server, and MariaDB, not SAP HANA). Option D is wrong because using AWS Backup to take a full backup and restore it would require the database to be offline during the backup and restore process, leading to extended downtime, and AWS Backup does not natively support SAP HANA for ongoing replication or near-zero downtime migrations.

Practice this question →
187
Multi-Selectmedium

An SAP administrator is designing a backup strategy for an SAP HANA database on AWS. They want to use the Backint interface with Amazon S3. Which THREE components are required? (Choose three.)

Select 3 answers
A.EBS volumes for the backup catalog
B.IAM role with permissions to write to the S3 bucket
C.AWS Backint Agent for SAP HANA
D.S3 Transfer Acceleration enabled
E.An S3 bucket to store the backups
AnswersB, C, E

The EC2 instance needs an IAM role to access S3.

Why this answer

The Backint interface for SAP HANA on AWS requires an IAM role that grants the AWS Backint Agent permissions to write backup data to the designated S3 bucket. Without this IAM role, the agent cannot authenticate or perform PutObject operations against S3, making the backup fail.

Exam trap

The trap here is that candidates may assume EBS volumes are required for the backup catalog or that S3 Transfer Acceleration is mandatory for performance, but the Backint interface only needs the agent, an S3 bucket, and an IAM role with write permissions.

Practice this question →
188
MCQhard

An SAP administrator notices that the SAP HANA database backups to Amazon S3 are failing intermittently with timeout errors. The backup script uses the AWS CLI to copy files to an S3 bucket. What is the most likely cause and solution?

A.The S3 bucket policy is too restrictive, modify the policy
B.The S3 bucket has a lifecycle policy that deletes objects too quickly
C.The backup files are large and the CLI command does not use multipart upload; use multipart upload and increase timeout values
D.S3 Transfer Acceleration is not enabled, enable it
AnswerC

Large files need multipart upload and appropriate timeouts.

Why this answer

The intermittent timeout errors when copying large SAP HANA backup files to Amazon S3 via the AWS CLI are most likely caused by the CLI not using multipart upload for large files. The AWS CLI automatically uses multipart upload for files over a certain threshold (default 8 MB), but if the upload is timing out, the default timeout values may be insufficient for very large files. Enabling multipart upload and increasing the `--cli-read-timeout` and `--cli-connect-timeout` values resolves the issue by splitting the file into smaller parts and allowing more time for each part to complete.

Exam trap

The trap here is that candidates may assume S3 Transfer Acceleration is the solution for any slow or failing upload, but the question specifically mentions intermittent timeout errors with large files, which points to multipart upload and timeout configuration rather than acceleration.

How to eliminate wrong answers

Option A is wrong because a restrictive S3 bucket policy would cause consistent access denied errors, not intermittent timeout errors. Option B is wrong because a lifecycle policy that deletes objects too quickly would result in missing objects after upload, not timeout failures during the upload process. Option D is wrong because S3 Transfer Acceleration improves transfer speed over long distances but does not address timeout errors caused by large file uploads without multipart upload; it would not fix the underlying issue of the CLI timing out on a single large file transfer.

Practice this question →
189
MCQhard

An SAP Basis administrator notices that the SAP HANA database performance has degraded significantly after migrating to AWS. The database is running on an r5.8xlarge instance with 3.6 TB of Amazon EBS gp3 storage. The administrator checks Amazon CloudWatch metrics and finds that the Read/Write latency is consistently above 10 ms and the queue depth is averaging 32. What is the MOST likely cause of the performance degradation?

A.The EC2 instance type does not support enough EBS bandwidth for the workload.
B.The EC2 instance's EBS bandwidth is fully utilized, causing I/O queueing.
C.The gp3 volume burst credit balance is exhausted, causing throughput to drop to baseline.
D.The EBS gp3 volume size is too small, causing IOPS throttling.
AnswerB

High queue depth indicates I/O requests are waiting due to bandwidth saturation.

Why this answer

The r5.8xlarge instance provides a maximum EBS bandwidth of 4,750 Mbps and a maximum EBS IOPS of 60,000. With a queue depth averaging 32 and latency above 10 ms, the instance's EBS bandwidth is saturated, causing I/O requests to queue and wait. This is the classic symptom of hitting the instance-level EBS bandwidth limit, not a volume-level issue.

Exam trap

The trap here is that candidates confuse volume-level limits (gp3 baseline IOPS or gp2 burst credits) with instance-level EBS bandwidth limits, leading them to incorrectly select options C or D when the real bottleneck is the EC2 instance's aggregate EBS throughput capacity.

How to eliminate wrong answers

Option A is wrong because the r5.8xlarge instance type supports up to 4,750 Mbps of EBS bandwidth and 60,000 IOPS, which is more than sufficient for typical SAP HANA workloads; the problem is that this bandwidth is fully utilized, not that the instance type is insufficient. Option C is wrong because gp3 volumes do not use burst credits; they have a baseline performance of 3,000 IOPS and 125 MB/s throughput regardless of size, and burst credits are a feature of gp2, not gp3. Option D is wrong because gp3 volume IOPS are independent of volume size; you can provision up to 16,000 IOPS on any gp3 volume, and the 3.6 TB size is more than adequate to support the required IOPS without throttling.

Practice this question →
190
MCQhard

A company is running SAP ERP on AWS and notices performance degradation during peak hours. The application servers are in an Auto Scaling group behind an Application Load Balancer. Which configuration change would best handle the increased load?

A.Increase the minimum and maximum instance count in the Auto Scaling group
B.Configure a step scaling policy based on memory utilization
C.Replace the Application Load Balancer with a Network Load Balancer
D.Change the Auto Scaling policy to use a target tracking policy based on CPU utilization
AnswerD

CPU utilization is a more relevant metric for SAP application server load.

Why this answer

D is correct because SAP ERP workloads are typically CPU-bound during peak hours, and a target tracking policy based on CPU utilization automatically adjusts the Auto Scaling group to maintain a target CPU metric (e.g., 70%), ensuring the application servers scale out proactively to handle increased load without manual intervention. This approach aligns with SAP's recommended scaling strategy on AWS, as it directly addresses the performance degradation caused by high CPU demand.

Exam trap

The trap here is that candidates often assume increasing instance limits (Option A) or using memory-based scaling (Option B) is sufficient, but the exam tests understanding that SAP ERP is CPU-bound and requires a dynamic, metric-driven scaling policy like target tracking to effectively handle peak loads.

How to eliminate wrong answers

Option A is wrong because simply increasing the minimum and maximum instance count does not enable dynamic scaling; it only sets static boundaries, so the Auto Scaling group will not automatically add instances in response to peak load unless a scaling policy is also configured. Option B is wrong because memory utilization is not a reliable metric for SAP ERP scaling, as SAP workloads are primarily CPU-intensive and memory pressure is less indicative of performance degradation during peak hours; moreover, step scaling policies can be less responsive than target tracking due to their threshold-based nature. Option C is wrong because replacing the Application Load Balancer with a Network Load Balancer would not help handle increased load for SAP ERP application servers, as ALB operates at Layer 7 (HTTP/HTTPS) and is better suited for routing traffic to web-based SAP applications, while NLB operates at Layer 4 and lacks the application-level awareness needed for SAP's session management and health checks.

Practice this question →
191
MCQhard

A company is running SAP NetWeaver on AWS with a multi-ABAP application server setup. They want to implement a load balancing solution for HTTP traffic to the SAP Web Dispatcher. The solution must be highly available and support SSL termination. Which AWS service should be used?

A.Application Load Balancer (ALB)
B.Amazon CloudFront
C.Classic Load Balancer (CLB)
D.Network Load Balancer (NLB)
AnswerA

ALB supports HTTP/HTTPS, SSL termination, and health checks.

Why this answer

The Application Load Balancer (ALB) is the correct choice because it operates at Layer 7, can route HTTP/HTTPS traffic to SAP Web Dispatchers, supports SSL termination natively, and integrates with AWS Auto Scaling and health checks to provide high availability. SAP Web Dispatcher expects HTTP-based load balancing, and ALB’s content-based routing and stickiness features align with SAP’s recommended architecture for multi-ABAP application server setups.

Exam trap

The trap here is that candidates often confuse Network Load Balancer (NLB) as the default choice for high-performance SAP workloads, but the requirement for SSL termination and HTTP-level routing makes ALB the only correct option, as NLB cannot terminate SSL or inspect application-layer traffic.

How to eliminate wrong answers

Option B (Amazon CloudFront) is wrong because it is a global content delivery network (CDN) designed for caching static and dynamic content at edge locations, not for load balancing HTTP traffic to an internal SAP Web Dispatcher in a VPC; it lacks the ability to perform health checks on backend SAP instances and does not support direct TCP/HTTP load balancing to SAP application servers. Option C (Classic Load Balancer) is wrong because it is a legacy Layer 4/7 load balancer that does not support advanced HTTP routing rules, path-based routing, or native SSL termination with SNI, and it is not recommended for modern SAP deployments due to limited feature set and deprecation risk. Option D (Network Load Balancer) is wrong because it operates at Layer 4 (TCP/UDP) and cannot terminate SSL or inspect HTTP headers; while it can handle high-throughput traffic, it would require the SAP Web Dispatcher to handle SSL termination itself, defeating the requirement for SSL termination at the load balancer.

Practice this question →
192
MCQhard

A company is deploying SAP NetWeaver on AWS and needs to ensure that the SAP application servers can communicate with the SAP HANA database using the hostname. The environment uses a Windows Domain Controller for Active Directory. Which DNS resolution strategy should be used?

A.Use AWS Directory Service for Microsoft Active Directory with DNS
B.Configure DHCP option sets to use custom DNS
C.Install a DNS server on an Amazon Linux instance
D.Use Amazon Route 53 Resolver outbound endpoint
AnswerA

Provides DNS integrated with AD for hostname resolution.

Why this answer

AWS Directory Service for Microsoft Active Directory provides a managed DNS service that integrates with Active Directory. This allows SAP application servers to resolve the SAP HANA database hostname via DNS, which is essential for SAP NetWeaver's hostname-based communication. The managed service ensures automatic DNS record updates and supports Windows-native DNS resolution without requiring custom infrastructure.

Exam trap

The trap here is that candidates often assume any DNS solution (like Route 53 Resolver or a Linux DNS server) can handle Windows Active Directory hostname resolution, overlooking the need for native Windows DNS integration with dynamic updates and Kerberos authentication.

How to eliminate wrong answers

Option B is wrong because DHCP option sets can specify custom DNS servers, but they do not provide the Active Directory-integrated DNS resolution required for Windows Domain Controller environments; they only point to existing DNS servers. Option C is wrong because installing a DNS server on an Amazon Linux instance does not natively integrate with Active Directory for dynamic DNS updates and Windows authentication, leading to potential resolution failures for SAP hostnames. Option D is wrong because Amazon Route 53 Resolver outbound endpoints are used for hybrid DNS resolution between on-premises and AWS, not for providing Active Directory-integrated DNS within a VPC; they lack the Windows-specific features needed for SAP hostname resolution.

Practice this question →
193
MCQmedium

A company wants to implement a disaster recovery (DR) strategy for its SAP landscape on AWS. The primary site is in us-east-1, and the DR site is in us-west-2. They need to replicate SAP HANA database asynchronously with a Recovery Point Objective (RPO) of 15 minutes. Which AWS service should they use?

A.AWS Elastic Disaster Recovery (DRS)
B.SAP HANA System Replication
C.Amazon S3 cross-region replication for HANA backup files
D.AWS Database Migration Service (DMS) with ongoing replication
AnswerB

SAP HANA System Replication is the correct method for asynchronous replication.

Why this answer

SAP HANA System Replication (HSR) is the native, SAP-supported mechanism for asynchronous replication of HANA databases, capable of achieving an RPO of 15 minutes or less. It replicates at the database level using log shipping and is tightly integrated with HANA's recovery processes, making it the correct choice for this DR scenario.

Exam trap

The trap here is that candidates often confuse AWS-native DR services (like DRS or DMS) with SAP's own replication technology, forgetting that SAP HANA has a built-in, certified replication mechanism that is the only way to meet strict RPOs for HANA databases.

How to eliminate wrong answers

Option A is wrong because AWS Elastic Disaster Recovery (DRS) replicates entire servers at the block level, not the HANA database log level, and cannot guarantee the sub-15-minute RPO required for HANA's transactional consistency. Option C is wrong because S3 cross-region replication for HANA backup files only copies backup artifacts, not the live database state, resulting in an RPO measured in hours or days, not 15 minutes. Option D is wrong because AWS DMS with ongoing replication is designed for heterogeneous database migrations and does not support SAP HANA as a source for continuous log-based replication; it lacks the native HANA log replay capabilities needed for DR.

Practice this question →
194
Multi-Selecthard

Which ONE of the following is required to enable SAP HANA System Replication across two AWS Availability Zones?

Select 1 answer
A.The primary and secondary instances must be in the same AWS region
B.A Virtual Private Gateway must be attached to the VPC
C.The EBS volumes must be configured for multi-attach or use a shared file system
D.A cluster placement group must be used
E.An Application Load Balancer must be configured for the replication traffic
AnswersA

Correct. The primary and secondary instances must be in the same AWS region to meet latency requirements for SAP HANA System Replication.

Why this answer

SAP HANA System Replication requires primary and secondary instances to be in the same AWS region to ensure low-latency replication; cross-region replication is not supported for synchronous replication. Option A is correct. Option B is incorrect because a Virtual Private Gateway is not needed for replication within a VPC.

Option C is incorrect because SAP HANA System Replication operates at the database level and does not require shared storage or multi-attach EBS volumes. Option D is incorrect because a cluster placement group is not required for HANA System Replication; it is used for low-latency networking in scale-out scenarios. Option E is incorrect because an Application Load Balancer is not used for replication traffic; replication is handled directly between HANA instances.

Exam trap

The trap here is that candidates confuse SAP HANA System Replication (which requires same-region AZs) with SAP HANA scale-out or backup scenarios that might use shared storage or cross-region replication, leading them to select EBS multi-attach or cross-region options incorrectly.

Practice this question →
195
Multi-Selectmedium

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

Select 2 answers
A.Use Amazon EFS as the storage layer for HANA data files.
B.Use T3 instances for production to save costs.
C.Use Amazon RDS Multi-AZ for HANA database replication.
D.Use EBS Snapshots for backup of HANA data volumes.
E.Use EC2 instances from the SAP HANA certified instance list.
AnswersD, E

EBS Snapshots provide crash-consistent backups.

Why this answer

EBS Snapshots provide a consistent, crash-consistent backup mechanism for HANA data volumes when used with application-consistent procedures (e.g., pre-freeze/post-thaw scripts via AWS Backup or custom automation). Snapshots are block-level, incremental, and can be automated for point-in-time recovery, aligning with SAP HANA backup best practices on AWS.

Exam trap

The trap here is that candidates confuse general-purpose backup services (like EFS or RDS) with the specific storage and replication requirements of SAP HANA, leading them to select options that sound reasonable but are technically incompatible or uncertified.

Practice this question →
196
MCQeasy

A company wants to automate the deployment of SAP systems on AWS. Which AWS service is most appropriate for infrastructure as code (IaC) for SAP?

A.AWS OpsWorks
B.AWS Elastic Beanstalk
C.AWS CodeDeploy
D.AWS CloudFormation
AnswerD

CloudFormation is the standard IaC service on AWS.

Why this answer

AWS CloudFormation is the most appropriate service for infrastructure as code (IaC) for SAP because it allows you to define and provision AWS infrastructure declaratively using templates. This enables repeatable, version-controlled deployments of complex SAP landscapes, including EC2 instances, networking, storage, and security groups, which is critical for SAP's strict architectural requirements.

Exam trap

The trap here is that candidates often confuse AWS CodeDeploy or Elastic Beanstalk with IaC because they involve 'deployment,' but they are designed for application code or PaaS, not for provisioning the underlying SAP infrastructure, which requires full control over compute, storage, and networking.

How to eliminate wrong answers

Option A is wrong because AWS OpsWorks is a configuration management service based on Chef and Puppet, not a declarative IaC tool; it is designed for application configuration and lifecycle management, not for provisioning the underlying SAP infrastructure. Option B is wrong because AWS Elastic Beanstalk is a PaaS service that abstracts infrastructure management for web applications, but it does not support the custom, granular control required for SAP systems (e.g., specific instance types, HANA-specific storage, or high-availability setups). Option C is wrong because AWS CodeDeploy is a deployment automation service for application code updates, not for provisioning infrastructure; it cannot define or manage the underlying AWS resources needed for an SAP environment.

Practice this question →
197
MCQhard

An SAP administrator notices that the SAP HANA database on an EC2 instance is experiencing high I/O latency. The instance is using EBS gp2 volumes. Which change would most effectively reduce I/O latency for the SAP HANA data volume?

A.Use instance store SSDs for the SAP HANA data volume.
B.Switch to io2 Block Express EBS volumes for the data volume.
C.Increase the size of the EBS gp2 volume to increase baseline IOPS.
D.Configure RAID 0 across multiple gp2 volumes.
AnswerB

io2 Block Express provides sub-millisecond latency and high IOPS.

Why this answer

Io2 Block Express volumes provide consistent, high-performance IOPS with sub-millisecond latency, which is critical for SAP HANA data volumes. Unlike gp2, which relies on burst credits and has variable performance, io2 Block Express delivers predictable low latency and up to 256,000 IOPS per volume, directly addressing the high I/O latency issue.

Exam trap

The trap here is that candidates may assume increasing gp2 volume size or using RAID 0 will solve latency issues, but these approaches do not address the fundamental lack of consistent low-latency performance that io2 Block Express provides.

How to eliminate wrong answers

Option A is wrong because instance store SSDs are ephemeral and do not persist data across instance stops or terminations, making them unsuitable for SAP HANA data volumes that require durability and high availability. Option C is wrong because increasing the size of a gp2 volume only raises the baseline IOPS (at a rate of 3 IOPS per GB), but gp2 still suffers from burst bucket limitations and does not guarantee the sub-millisecond latency required for SAP HANA. Option D is wrong because RAID 0 across multiple gp2 volumes increases throughput and IOPS but does not reduce latency per I/O operation; it also introduces a single point of failure if any volume fails, which is unacceptable for SAP HANA data persistence.

Practice this question →
198
MCQeasy

A company is planning to run SAP S/4HANA on AWS. The architect needs to ensure that the EC2 instances are SAP certified for the specific SAP HANA version. Where should the architect verify the instance certification?

A.SAP Support Portal
B.AWS Management Console under EC2 instance types
C.SAP Certified and Supported SAP HANA Hardware Directory
D.AWS documentation for SAP on AWS
AnswerC

This directory is the official source for SAP HANA hardware certification.

Why this answer

The SAP Certified and Supported SAP HANA Hardware Directory is the authoritative source maintained by SAP that lists all certified hardware configurations, including specific AWS EC2 instance types and their supported SAP HANA versions. This directory is the only place where SAP officially validates that an EC2 instance meets the exact hardware and firmware requirements for a given SAP HANA release, ensuring compliance with SAP's certification standards.

Exam trap

The trap here is that candidates often assume AWS documentation or the AWS Management Console would contain SAP certification details, but only the SAP Hardware Directory provides the official, legally binding certification status for SAP HANA workloads.

How to eliminate wrong answers

Option A is wrong because the SAP Support Portal is used for managing support cases, downloading software, and accessing SAP notes, but it does not contain the certified hardware directory for EC2 instance types. Option B is wrong because the AWS Management Console under EC2 instance types only shows available instance families and their specifications, not SAP-specific certification status for a particular SAP HANA version. Option D is wrong because AWS documentation for SAP on AWS provides general guidance and best practices but does not replace the official SAP-certified hardware directory, which is the sole source for verifying instance certification.

Practice this question →
199
MCQmedium

A company is running SAP HANA on AWS and needs to back up the database to Amazon S3. Which approach provides the most efficient and cost-effective backup strategy?

A.Use AWS Storage Gateway with tapes.
B.Use SAP HANA Backint agent to back up directly to S3.
C.Take EBS snapshots of the HANA data volumes.
D.Copy HANA data files to EC2 instance store.
AnswerB

Backint integrates with SAP HANA for efficient backups.

Why this answer

The SAP HANA Backint agent is the native, certified integration for backing up SAP HANA directly to Amazon S3. It leverages the SAP HANA backup API to stream data directly to S3 without intermediate storage, providing the most efficient path with minimal overhead and cost, as you only pay for S3 storage and API calls.

Exam trap

The trap here is that candidates often confuse EBS snapshots as a valid backup method for SAP HANA, but they fail to account for the need for application-consistent snapshots and the fact that EBS snapshots are not integrated with SAP HANA's backup catalog, leading to potential data loss or corruption during recovery.

How to eliminate wrong answers

Option A is wrong because AWS Storage Gateway with tapes (VTL) introduces unnecessary complexity and cost for virtual tape storage, and is not optimized for SAP HANA's native backup protocols. Option C is wrong because EBS snapshots capture the entire volume, including unused space, and are not crash-consistent for SAP HANA without additional steps like pausing I/O, leading to higher storage costs and potential data inconsistency. Option D is wrong because EC2 instance store is ephemeral and provides no durability; data is lost if the instance stops or fails, making it unsuitable for backups.

Practice this question →
200
MCQmedium

A company runs its SAP ERP system on AWS. The database is SAP HANA on an EC2 instance. The system is critical and requires a recovery point objective (RPO) of less than 5 minutes and a recovery time objective (RTO) of less than 2 hours. Which solution meets these requirements with the LEAST operational overhead?

A.Use AWS Backup with the SAP HANA Backup and Restore feature (Backint integration) to perform continuous backups to S3.
B.Use EBS snapshots of the root and data volumes taken every 5 minutes.
C.Set up HANA system replication across two EC2 instances in different Availability Zones with manual failover.
D.Schedule manual HANA backups to S3 using cron scripts and hdbsql commands.
AnswerA

Continuous backups provide low RPO; automated restore meets RTO with low overhead.

Why this answer

AWS Backup with the SAP HANA Backup and Restore feature (Backint integration) provides continuous, incremental backups to Amazon S3, achieving an RPO of less than 5 minutes with automated, policy-driven backups. This solution minimizes operational overhead by eliminating manual scripting and infrastructure management, while supporting point-in-time recovery within the required RTO of under 2 hours.

Exam trap

The trap here is that candidates often overestimate the simplicity of EBS snapshots (Option B) for database workloads, not realizing that SAP HANA requires application-consistent backups and that frequent snapshots alone cannot achieve sub-5-minute RPO without significant custom orchestration.

How to eliminate wrong answers

Option B is wrong because EBS snapshots taken every 5 minutes cannot guarantee an RPO of less than 5 minutes due to snapshot initiation delays and the need to quiesce the HANA database, and they require manual or custom automation for consistency, increasing operational overhead. Option C is wrong because HANA system replication across Availability Zones with manual failover introduces significant operational overhead (manual intervention) and cannot meet the RTO of less than 2 hours reliably, as failover requires human action and coordination. Option D is wrong because scheduling manual HANA backups to S3 using cron scripts and hdbsql commands is error-prone, lacks automated monitoring, and requires custom scripting and maintenance, resulting in higher operational overhead and potential RPO/RTO gaps.

Practice this question →
201
MCQeasy

A company is designing a disaster recovery (DR) strategy for its SAP system on AWS. The primary site is in us-east-1 and the DR site in us-west-2. The RTO is 4 hours and RPO is 1 hour. Which AWS service should be used for cross-region replication of the SAP HANA database backups stored in Amazon S3?

A.AWS Backup with a cross-region backup plan.
B.Use AWS Storage Gateway to replicate backups.
C.Amazon S3 Cross-Region Replication (CRR).
D.Enable S3 Versioning on the source bucket.
AnswerC

S3 CRR automatically replicates new objects to another region, meeting RPO.

Why this answer

Amazon S3 Cross-Region Replication (CRR) is the correct choice because it automatically replicates objects (including SAP HANA database backups) from a source S3 bucket in us-east-1 to a destination bucket in us-west-2, meeting the 1-hour RPO by ensuring backups are available in the DR region within minutes of upload. CRR operates asynchronously at the object level, requires no additional infrastructure, and directly supports the stated requirement for cross-region replication of S3-stored backups without introducing extra latency or complexity.

Exam trap

The trap here is that candidates often confuse AWS Backup (which manages backup schedules and retention) with S3 CRR (which handles object-level replication), leading them to select AWS Backup despite it not being designed for cross-region replication of existing S3 objects.

How to eliminate wrong answers

Option A is wrong because AWS Backup with a cross-region backup plan is designed for scheduling and managing backups of AWS resources (e.g., EBS, RDS, DynamoDB) but does not natively replicate existing S3 objects; it would require creating separate backup copies, adding overhead and potentially missing the 1-hour RPO. Option B is wrong because AWS Storage Gateway is a hybrid storage service for on-premises to AWS connectivity (e.g., file, volume, or tape gateways) and is not designed for cross-region replication of S3 objects; it would introduce unnecessary complexity and latency. Option D is wrong because enabling S3 Versioning on the source bucket only preserves multiple versions of objects within the same bucket and region, providing protection against accidental deletion or overwrite, but does not replicate data to a different region, thus failing to meet the DR requirement for cross-region availability.

Practice this question →
202
MCQhard

An SAP system on AWS is experiencing performance degradation. The CloudWatch metrics show that the EBS volumes used for the HANA data files have an average queue length of 10 and average latency of 50 ms. What is the most likely cause?

A.EBS encryption is causing additional overhead.
B.EBS snapshots are being taken too frequently.
C.The EBS volume's provisioned IOPS are insufficient for the workload.
D.EBS optimization is not enabled on the instance.
AnswerC

Insufficient IOPS cause queuing and increased latency.

Why this answer

An average EBS queue length of 10 and average latency of 50 ms indicate that the volume is saturated with I/O requests. The queue length persistently exceeds the recommended threshold (typically <1 for optimal performance), and latency spikes above the 1–10 ms range for gp3 or io2 volumes. This directly points to insufficient provisioned IOPS for the SAP HANA workload, causing requests to queue up and wait for service.

Exam trap

The trap here is that candidates confuse high queue length with a snapshot or encryption issue, but AWS explicitly documents that queue length and latency are the primary indicators of IOPS exhaustion, not of background operations like snapshots or encryption.

How to eliminate wrong answers

Option A is wrong because EBS encryption uses AES-256 and is handled by the Nitro chip or instance hardware with negligible performance overhead; it does not cause queue buildup or latency spikes. Option B is wrong because EBS snapshots are incremental and taken from the control plane; they do not directly impact data-plane I/O latency or queue depth unless the volume is heavily utilized during a snapshot (which would still manifest as insufficient IOPS). Option D is wrong because EBS optimization is enabled by default on all current-generation instance types (e.g., m5, r5, x1e) and cannot be disabled; if it were missing on an older instance, it would cause a fixed bandwidth cap, not a queue-length symptom.

Practice this question →
203
MCQeasy

A company wants to use AWS Systems Manager to automate patching of SAP application servers. What is a prerequisite for Systems Manager to manage these EC2 instances?

A.Enable SSH access to the instances.
B.Assign a separate IAM role to each instance.
C.Install the SSM Agent on the EC2 instances.
D.Ensure the instances have public IP addresses.
AnswerC

SSM Agent is required for Systems Manager to communicate with instances.

Why this answer

AWS Systems Manager requires the SSM Agent to be installed and running on EC2 instances to enable communication with the Systems Manager service for patching and other management tasks. Without the agent, Systems Manager cannot send commands, initiate patching workflows, or gather inventory data from the instances. The SSM Agent is pre-installed on many Amazon Linux and Windows AMIs but must be manually installed on custom or imported images.

Exam trap

The trap here is that candidates often assume SSH or public IP addresses are required for remote management, but Systems Manager is designed to work without them, relying solely on the SSM Agent and IAM permissions over HTTPS.

How to eliminate wrong answers

Option A is wrong because SSH access is not required for Systems Manager; the service uses the SSM Agent over HTTPS (port 443) to communicate, not SSH. Option B is wrong because while an IAM role is necessary, a single IAM role can be shared across multiple instances; assigning a separate role to each instance is not a prerequisite. Option D is wrong because Systems Manager can manage instances in private subnets without public IP addresses, using VPC endpoints or Systems Manager managed instances with a NAT gateway.

Practice this question →
204
MCQhard

An SAP Basis administrator notices that the SAP application server on an EC2 instance is experiencing intermittent high latency when writing to the SAP HANA database. The HANA database is on a separate EC2 instance in the same VPC and Availability Zone. Which configuration change is most likely to resolve the issue?

A.Launch the instances in a cluster placement group
B.Enable EBS optimization on both instances
C.Change the Elastic Network Adapter (ENA) to SR-IOV
D.Enable Jumbo Frames on the network interfaces
AnswerD

Jumbo Frames reduce overhead for large packets, improving network throughput and reducing latency for HANA communication.

Why this answer

The intermittent high latency when writing to SAP HANA is likely caused by network packet fragmentation. Enabling Jumbo Frames (MTU 9001) on the network interfaces of both the SAP application server and the HANA database EC2 instances reduces the number of packets required for large data transfers, lowers CPU overhead for packet processing, and improves throughput. This is a standard recommendation for SAP on AWS to optimize network performance between application and database layers.

Exam trap

The trap here is that candidates often confuse network performance issues with compute or storage optimizations, leading them to choose EBS optimization or placement groups, when the real fix is a simple MTU adjustment to eliminate packet fragmentation overhead.

How to eliminate wrong answers

Option A is wrong because a cluster placement group is designed for low-latency, high-bandwidth communication between instances, but it does not address the underlying packet fragmentation issue; it would only help if the instances were in different AZs or needed enhanced network performance, which is not the case here. Option B is wrong because EBS optimization is a feature that dedicates bandwidth between the EC2 instance and EBS volumes, not between two EC2 instances; it would not resolve network latency between the SAP app server and HANA database. Option C is wrong because the Elastic Network Adapter (ENA) is already the default modern network interface for current-generation instances, and SR-IOV (Single Root I/O Virtualization) is an older technology (e.g., Intel 82599 VF) that is not applicable to ENA; changing to SR-IOV would not improve performance and could cause compatibility issues.

Practice this question →
205
Multi-Selectmedium

A company is running SAP HANA on AWS and needs to ensure high availability for the SAP Central Services (ASCS/ERS) instance. Which TWO actions should be taken to achieve this? (Choose two.)

Select 2 answers
A.Configure ASCS and ERS on separate EC2 instances in different Availability Zones.
B.Use an Application Load Balancer to distribute traffic between ASCS and ERS instances.
C.Use a Network Load Balancer with a floating IP address for the SAP virtual hostname.
D.Deploy both ASCS and ERS on the same EC2 instance to reduce latency.
E.Place both ASCS and ERS in the same Availability Zone to minimize network latency.
AnswersA, C

Separate instances in different AZs provide high availability.

Why this answer

SAP Central Services (ASCS/ERS) must run on separate EC2 instances to avoid a single point of failure. Placing them in different Availability Zones (AZs) ensures that if one AZ fails, the other instance can take over, providing high availability. This aligns with SAP's recommendation for a multi-AZ architecture for ASCS/ERS in an SAP HANA on AWS environment.

Exam trap

The trap here is that candidates often confuse the role of load balancers, assuming an ALB can handle SAP virtual hostname failover, when in fact only an NLB with a floating IP supports the required Layer 4 static IP behavior for SAP Central Services.

Practice this question →
206
MCQeasy

A company runs SAP on AWS and wants to back up its SAP HANA database to Amazon S3. The database is 2 TB in size. The backup must be encrypted at rest in S3 and must be cost-effective. Which approach should the company use?

A.Use AWS Backup to directly back up the SAP HANA database to S3 with SSE-S3
B.Configure a cron job to copy the SAP HANA backup files from EBS to S3 using AWS CLI
C.Install the SAP HANA Backint agent for Amazon S3 and configure it to use SSE-S3 encryption
D.Use SAP HANA Studio to export the database to a file on EBS and then manually upload to S3
AnswerC

Backint is the recommended method for backing up SAP HANA to S3 with encryption.

Why this answer

The SAP HANA Backint agent for Amazon S3 is the AWS-recommended, native integration for backing up SAP HANA databases directly to S3. It supports SSE-S3 encryption at rest, ensuring cost-effective storage without manual intervention or additional infrastructure, and is designed to handle large databases like the 2 TB workload efficiently.

Exam trap

The trap here is that candidates may confuse AWS Backup's general-purpose capabilities with SAP HANA-specific backup requirements, overlooking that only the Backint agent provides the native integration needed for consistent, encrypted, and automated backups to S3.

How to eliminate wrong answers

Option A is wrong because AWS Backup does not natively support SAP HANA database backups; it can back up EBS volumes or RDS instances but not the HANA database directly via Backint. Option B is wrong because using a cron job to copy backup files from EBS to S3 via AWS CLI is manual, error-prone, and does not integrate with HANA's backup lifecycle, risking data consistency and increasing operational overhead. Option D is wrong because exporting the database to a file on EBS via SAP HANA Studio and then manually uploading to S3 is not automated, lacks encryption at rest in S3 by default, and is inefficient for a 2 TB database, violating cost-effectiveness and reliability.

Practice this question →
207
MCQhard

A company runs SAP S/4HANA on AWS with a multi-tier landscape (DEV, QAS, PRD). The PRD system uses a clustered setup with two application servers behind an Application Load Balancer. The database is a single-node HANA on an r5.24xlarge instance. The administrator receives an alert that the PRD application is slow. CloudWatch metrics show high CPU utilization on the two application servers (average 95%) and high DB connection count. The ALB shows increased request latency. The database CPU is at 60%. The administrator suspects a SQL query performance issue. What should be the first step to identify the root cause?

A.Configure CloudWatch Logs to capture HANA trace logs and analyze them.
B.Enable detailed SQL trace in HANA to identify high-resource queries.
C.Add two more application servers to distribute the load.
D.Increase the size of the HANA database instance to reduce CPU pressure.
AnswerB

SQL trace identifies specific queries causing performance issues.

Why this answer

The symptoms (high CPU on app servers, high DB connections, increased ALB latency, DB CPU at 60%) strongly suggest a SQL query performance bottleneck, not a capacity issue. Enabling detailed SQL trace in HANA (option B) is the most direct first step to identify the specific high-resource queries causing the slowdown, as it captures execution plans, wait times, and resource consumption per query. This aligns with SAP's recommended troubleshooting methodology for HANA performance issues.

Exam trap

The trap here is that candidates may confuse high application server CPU with a scaling issue (option C) or assume high DB connections mean the database is underpowered (option D), rather than recognizing that a SQL performance problem can manifest as app-side symptoms while the DB CPU remains moderate.

How to eliminate wrong answers

Option A is wrong because CloudWatch Logs can capture HANA trace logs, but the first step should be to enable a targeted SQL trace to pinpoint problematic queries, not to passively collect general logs. Option C is wrong because adding application servers would not resolve a SQL query performance issue; it would only mask the symptom by distributing load, and the root cause (poor query) would remain. Option D is wrong because increasing the HANA database instance size would not fix a SQL query performance issue; the DB CPU is only at 60%, indicating the bottleneck is likely inefficient queries, not insufficient compute capacity.

Practice this question →
208
MCQhard

An SAP administrator created the IAM policy above for an EC2 instance role used by SAP HANA Backint agent. The backup to S3 fails with access denied. What is the likely cause?

A.The policy grants permissions on objects but not on the bucket itself. For s3:PutObject and s3:GetObject, a bucket-level permission is also required for some operations.
B.The policy does not allow s3:PutObject.
C.The policy does not allow ec2:CreateSnapshot.
D.The policy does not allow s3:ListBucket.
AnswerA

The resource ARN for S3 actions should include the bucket ARN for bucket-level operations.

Why this answer

The policy grants s3:PutObject and s3:GetObject on objects within the bucket (using the "arn:aws:s3:::bucket-name/*" resource), but does not include a bucket-level permission such as s3:PutObject or s3:GetObject on the bucket itself ("arn:aws:s3:::bucket-name"). For certain S3 operations, including multipart uploads and object writes that require bucket-level authorization checks, the IAM policy must explicitly allow the action on both the bucket and the object ARN. Without this, the SAP HANA Backint agent fails with access denied.

Exam trap

The trap here is that candidates assume s3:PutObject on the object ARN is sufficient, overlooking the requirement for bucket-level permissions on the same action for operations like multipart uploads or bucket-level condition checks.

How to eliminate wrong answers

Option B is wrong because the policy explicitly includes s3:PutObject on the object ARN, so the failure is not due to a missing s3:PutObject action. Option C is wrong because the question is about S3 backup failure, not EC2 snapshots; ec2:CreateSnapshot is irrelevant to the Backint agent's S3 access. Option D is wrong because s3:ListBucket is not required for the PutObject and GetObject operations used by the Backint agent; the error is caused by missing bucket-level permissions, not the ListBucket action.

Practice this question →
209
MCQeasy

An SAP system is running on AWS and needs to be accessible over the internet securely. Which AWS service should be used to provide secure remote access for administrators?

A.Set up an AWS Site-to-Site VPN connection from the corporate network
B.Use AWS Systems Manager Session Manager
C.Use Amazon WorkSpaces to provide a virtual desktop for administrators
D.Configure the EC2 instance in a public subnet with SSH access from the internet
AnswerB

Session Manager provides secure, audited shell access without opening inbound ports.

Why this answer

AWS Systems Manager Session Manager provides secure, auditable, browser-based or CLI-based remote access to EC2 instances without opening inbound ports, managing SSH keys, or using bastion hosts. It leverages the AWS SSM Agent and IAM policies to authenticate and authorize administrators, making it the most secure and operationally efficient option for SAP system administration on AWS.

Exam trap

The trap here is that candidates often assume a VPN or direct SSH access is required for secure remote administration, but AWS Systems Manager Session Manager provides a more secure and managed alternative that avoids exposing any network ports and eliminates the need for key management.

How to eliminate wrong answers

Option A is wrong because an AWS Site-to-Site VPN connection provides secure connectivity from a corporate network to the VPC, but it does not directly provide remote access for administrators to the SAP instance; it requires additional infrastructure like a bastion host or VPN client. Option C is wrong because Amazon WorkSpaces provides a virtual desktop for end users, not a secure remote access method for administrators to manage the SAP EC2 instance; it adds unnecessary complexity and cost. Option D is wrong because configuring the EC2 instance in a public subnet with SSH access from the internet exposes the management interface directly to the internet, violating security best practices and increasing the attack surface, especially for SAP workloads.

Practice this question →
210
MCQmedium

A company is migrating its SAP ERP system to AWS. The system requires high availability for the SAP central services (ASCS) and must support automatic failover. Which AWS architecture should the company use to meet these requirements?

A.Configure a Network Load Balancer in front of two ASCS instances in different Availability Zones.
B.Use Amazon RDS Multi-AZ to host the SAP central services.
C.Deploy ASCS on an EC2 instance in an Auto Scaling group with a lifecycle hook that triggers a Lambda function to reattach the ASCS cluster resources.
D.Run ASCS on a single EC2 instance in a single Availability Zone with an Elastic IP address.
AnswerC

This provides automated failover and high availability for ASCS.

Why this answer

It describes a pattern for achieving automatic failover of SAP ASCS using an Auto Scaling group with a lifecycle hook. When the ASCS instance fails, the Auto Scaling group launches a new instance, and the lifecycle hook triggers a Lambda function that reattaches the cluster resources (e.g., EIP, EBS volumes, or shared file systems) to the new instance, enabling the SAP ENSA2 or ENSA1 cluster to resume operations without manual intervention.

Exam trap

The trap here is that candidates often assume a Network Load Balancer (Option A) provides automatic failover for stateful SAP services, but NLB operates at Layer 4 and cannot handle the cluster state and shared storage requirements of SAP ASCS.

How to eliminate wrong answers

Option A is wrong because a Network Load Balancer (NLB) distributes traffic at the transport layer and cannot manage the stateful failover of SAP ASCS, which requires a cluster manager (e.g., Pacemaker) to handle shared resources and fencing. Option B is wrong because Amazon RDS Multi-AZ is designed for database workloads, not for SAP central services (ASCS), which are application-layer services that require shared file systems and cluster-aware failover. Option D is wrong because running ASCS on a single EC2 instance in a single Availability Zone provides no high availability or automatic failover, violating the requirement for automatic failover.

Practice this question →
211
MCQmedium

An organization runs SAP ERP on AWS with an SAP HANA database. The database is deployed on an EC2 instance with EBS storage. The company is planning to upgrade the HANA database from version 2.0 to 2.0 SPS 05. The upgrade process requires a system copy to a new instance. The company wants to minimize the downtime during the upgrade and ensure that the existing system remains available until the new system is ready. The current HANA instance has 1 TB of data. The company has a test environment that can be used for the upgrade. Which approach should the company take to minimize downtime?

A.Use SAP HANA Studio to export the production database to a file, import it into a new instance, and upgrade. Then redirect users to the new instance.
B.Perform the upgrade directly on the production HANA instance during a maintenance window.
C.Take a full backup of the production HANA database, restore it to a new instance, and perform the upgrade on the new instance. Then switch DNS to the new instance.
D.Set up SAP HANA System Replication from the production instance to a new instance. Perform the upgrade on the replica. Once upgraded, perform a takeover to make the new instance the primary.
AnswerD

Replication allows the production system to stay online; takeover is quick.

Why this answer

SAP HANA System Replication allows you to replicate data from the production instance to a new instance in near real-time. You can then perform the upgrade on the replica while the production system remains fully available. Once the upgrade is complete and validated, a takeover operation promotes the replica to primary, minimizing downtime to just the seconds required for the takeover and DNS switch.

Exam trap

The trap here is that candidates often choose Option C (backup and restore) because it seems straightforward, but they overlook that it does not keep the new instance synchronized with ongoing production changes, resulting in longer downtime than the replication-based approach.

How to eliminate wrong answers

Option A is wrong because exporting and importing 1 TB of data via SAP HANA Studio is a slow, manual process that would cause significant downtime, not minimize it. Option B is wrong because performing the upgrade directly on the production HANA instance would require taking the system offline for the entire upgrade duration, resulting in unacceptable downtime. Option C is wrong because taking a full backup and restoring it to a new instance is time-consuming for 1 TB of data, and the restore process does not keep the new instance synchronized with ongoing changes, so the switchover would still require a final outage to apply any delta.

Practice this question →
212
MCQeasy

A company is designing an SAP HANA disaster recovery (DR) solution on AWS. The primary site is in us-east-1, and the DR site is in us-west-2. The RPO must be less than 15 minutes, and the RTO must be less than 2 hours. Which replication strategy meets these requirements?

A.SAP HANA log shipping to an S3 bucket in the DR region.
B.S3 cross-region replication for HANA data files.
C.SAP HANA system replication with synchronous mode and pre-provisioned DR instances.
D.EBS snapshot replication to the DR region every 15 minutes.
AnswerC

Synchronous replication meets RPO; pre-provisioned instances reduce RTO.

Why this answer

SAP HANA system replication with synchronous mode ensures that every committed transaction is replicated to the DR site before acknowledgment, meeting the <15-minute RPO. Pre-provisioned DR instances in us-west-2 allow rapid failover, enabling the <2-hour RTO by eliminating the need to provision infrastructure during recovery.

Exam trap

The PAS-C01 exam often tests the misconception that any replication method with a 15-minute interval (like EBS snapshots or S3 replication) automatically meets a <15-minute RPO, ignoring the time required for snapshot finalization, transfer, and restoration, which pushes the actual RPO beyond the requirement.

How to eliminate wrong answers

Option A is wrong because SAP HANA log shipping to an S3 bucket in the DR region introduces significant latency and does not provide automatic failover, making it impossible to achieve a <15-minute RPO and <2-hour RTO. Option B is wrong because S3 cross-region replication for HANA data files only replicates static files, not the live transaction logs or in-memory state, so it cannot meet the RPO requirement and does not support database-level recovery. Option D is wrong because EBS snapshot replication to the DR region every 15 minutes can only achieve at best a 15-minute RPO (and often longer due to snapshot finalization), and restoring from snapshots requires manual steps that exceed the 2-hour RTO.

Practice this question →
213
MCQhard

An SAP administrator is setting up an S3 bucket to store SAP HANA backup files. The backups must be encrypted at rest using an AWS KMS customer managed key. Which bucket policy condition key should be used to enforce that only requests using KMS encryption with that specific key are allowed?

A.kms:EncryptionContext
B.s3:x-amz-server-side-encryption-aws-kms-key-id
C.s3:ServerSideEncryption
D.s3:x-amz-server-side-encryption
AnswerB

This condition key checks the specific KMS key ID used for encryption.

Why this answer

The `s3:x-amz-server-side-encryption-aws-kms-key-id` condition key allows you to enforce that only requests using a specific AWS KMS customer managed key for server-side encryption are permitted. This key is evaluated against the `x-amz-server-side-encryption-aws-kms-key-id` header in the request, ensuring that backups are encrypted with the exact KMS key ID specified in the bucket policy.

Exam trap

The trap here is that candidates confuse the condition key that checks for any KMS encryption (`s3:x-amz-server-side-encryption`) with the one that enforces a specific KMS key ID (`s3:x-amz-server-side-encryption-aws-kms-key-id`), leading them to select option D instead of B.

How to eliminate wrong answers

Option A is wrong because `kms:EncryptionContext` is a KMS condition key used to control access based on encryption context in KMS API calls, not to enforce the specific KMS key ID in S3 bucket policies. Option C is wrong because `s3:ServerSideEncryption` is not a valid AWS condition key; the correct prefix for S3 condition keys is `s3:x-amz-*`. Option D is wrong because `s3:x-amz-server-side-encryption` only checks whether server-side encryption is enabled (e.g., AES256 or aws:kms), but does not enforce the use of a specific KMS customer managed key ID.

Practice this question →
214
MCQeasy

An SAP administrator wants to attach the EBS volume shown above to two EC2 instances running SAP HANA in a scale-out configuration. What is the issue?

A.The volume is gp3 type, which does not support Multi-Attach.
B.The volume size is too small for HANA scale-out.
C.SAP HANA scale-out does not support shared volumes.
D.The volume IOPS is insufficient.
AnswerA

Multi-Attach is only available on io1 and io2 volumes.

Why this answer

The gp3 volume type does not support the Multi-Attach feature, which is required to attach a single EBS volume to multiple EC2 instances simultaneously. For SAP HANA scale-out configurations, shared storage is necessary for the /hana/shared file system, and Multi-Attach is only supported on io1 and io2 block express volumes. Therefore, using a gp3 volume prevents the multi-attach capability needed for this architecture.

Exam trap

The trap here is that candidates assume gp3 is a general-purpose volume that supports all features, but AWS explicitly restricts Multi-Attach to io1 and io2 block express only, making this a common pitfall in SAP workload design questions.

How to eliminate wrong answers

Option B is wrong because the volume size (e.g., 1 TiB) is actually sufficient for SAP HANA scale-out; the issue is not size but the volume type's lack of Multi-Attach support. Option C is wrong because SAP HANA scale-out does support shared volumes (specifically for /hana/shared), and this is a documented requirement for scale-out deployments on AWS. Option D is wrong because IOPS is not the limiting factor; gp3 volumes can provision adequate IOPS, but they still cannot be attached to multiple instances due to the absence of Multi-Attach.

Practice this question →
215
MCQmedium

An SAP administrator needs to monitor the disk I/O performance of EBS volumes attached to an SAP HANA instance. Which AWS service should be used to capture the average read latency and queue depth metrics?

A.AWS Config
B.AWS Health
C.Amazon CloudWatch
D.AWS CloudTrail
AnswerC

CloudWatch collects and provides metrics like AverageReadLatency and QueueDepth for EBS volumes.

Why this answer

Amazon CloudWatch provides the metrics necessary to monitor disk I/O performance, including `VolumeReadOps`, `VolumeQueueLength`, and `VolumeReadBytes` for EBS volumes. These metrics allow you to calculate average read latency (by dividing `VolumeReadBytes` by `VolumeReadOps`) and directly observe queue depth via `VolumeQueueLength`, making it the correct service for SAP HANA disk I/O monitoring.

Exam trap

The trap here is that candidates may confuse AWS CloudTrail (which logs API calls) with CloudWatch (which monitors performance metrics), or assume AWS Config or AWS Health provide operational performance data when they are designed for configuration auditing and service health notifications, respectively.

How to eliminate wrong answers

Option A is wrong because AWS Config is a service for evaluating, auditing, and recording configuration changes of AWS resources, not for capturing real-time performance metrics like disk latency or queue depth. Option B is wrong because AWS Health provides information about service health and events affecting your AWS infrastructure, but it does not expose granular EBS performance metrics. Option D is wrong because AWS CloudTrail records API activity and user actions for auditing and governance, not operational metrics such as I/O latency or queue depth.

Practice this question →
216
MCQmedium

A company is designing an SAP HANA multi-node scale-out deployment on AWS. The system requires high bandwidth and low latency between nodes. Which AWS networking feature should be used to meet these requirements?

A.Elastic Fabric Adapter (EFA)
B.AWS Direct Connect
C.Transit Gateway
D.VPC Peering
AnswerA

EFA provides low-latency, high-bandwidth inter-instance communication required for HANA scale-out.

Why this answer

Elastic Fabric Adapter (EFA) is correct because it provides OS-bypass capabilities using the Libfabric API, enabling direct memory access (DMA) between SAP HANA nodes. This eliminates kernel overhead, delivering the high bandwidth (up to 100 Gbps per adapter) and ultra-low latency (microsecond-level) required for SAP HANA multi-node scale-out workloads, where inter-node communication is critical for table partitioning and data replication.

Exam trap

The trap here is that candidates confuse EFA with standard Elastic Network Adapters (ENA) or assume that any high-bandwidth network feature (like Direct Connect or Transit Gateway) can solve inter-node latency, when only EFA provides the OS-bypass and RDMA semantics required for SAP HANA scale-out performance.

How to eliminate wrong answers

Option B (AWS Direct Connect) is wrong because it is a dedicated network connection from on-premises to AWS, not an inter-node networking feature within a VPC; it does not reduce latency or increase bandwidth between SAP HANA compute nodes. Option C (Transit Gateway) is wrong because it is a hub-and-spoke router for connecting multiple VPCs and on-premises networks, not a high-performance, low-latency interconnect for tightly coupled compute nodes within the same VPC. Option D (VPC Peering) is wrong because it is a simple layer-3 connection between VPCs that still traverses the standard AWS network stack with kernel overhead, lacking the OS-bypass and RDMA capabilities needed for SAP HANA scale-out performance.

Practice this question →
217
Multi-Selecteasy

An organization runs SAP BusinessObjects on AWS and wants to improve the performance of report generation. The current environment uses EBS gp2 volumes. Which TWO changes could potentially reduce report generation time?

Select 2 answers
A.Increase the size of the EBS root volume.
B.Enable EBS optimization on the instance.
C.Configure automated snapshots of the EBS volumes.
D.Switch to EBS io2 Block Express volumes with higher IOPS.
E.Add more SAP BusinessObjects application servers to distribute the workload.
AnswersD, E

Higher IOPS improves data access speed.

Why this answer

Switching to EBS io2 Block Express volumes provides higher IOPS and lower latency compared to gp2 volumes, which directly improves the I/O performance for SAP BusinessObjects report generation that often involves heavy database and file system reads. Option E is correct because adding more SAP BusinessObjects application servers distributes the report generation workload across multiple nodes, reducing the processing bottleneck on a single server and decreasing overall generation time.

Exam trap

The trap here is that candidates often confuse EBS optimization (a prerequisite for dedicated bandwidth) with a performance-tuning feature, or assume that increasing volume size (Option A) is a valid performance improvement method, when in fact switching to a higher-performance volume type like io2 Block Express is the correct storage-level optimization.

Practice this question →
218
MCQmedium

A company is deploying SAP on AWS and wants to ensure that the SAP system can automatically recover from an EC2 instance failure. Which AWS feature should be used?

A.Auto Scaling group with a scheduled scaling policy
B.Elastic Load Balancer health checks
C.EC2 Auto Recovery with CloudWatch alarms
D.Manual restart of the instance from the AWS Management Console
AnswerC

Auto Recovery automatically recovers the instance.

Why this answer

EC2 Auto Recovery, configured via a CloudWatch alarm based on the StatusCheckFailed metric, automatically recovers an EC2 instance by restarting it on a new host if the underlying hardware fails or becomes impaired. This is the correct AWS feature for automatic recovery from an EC2 instance failure, as it directly addresses instance-level hardware issues without requiring manual intervention or reconfiguration.

Exam trap

The trap here is that candidates often confuse Elastic Load Balancer health checks with instance recovery, but ELB only manages traffic distribution and does not perform any recovery action on the instance itself.

How to eliminate wrong answers

Option A is wrong because an Auto Scaling group with a scheduled scaling policy is designed for predictable scaling based on time, not for automatic recovery from an EC2 instance failure; it does not react to instance health status. Option B is wrong because Elastic Load Balancer health checks only detect and route traffic away from unhealthy instances, but they do not recover or restart the failed instance itself. Option D is wrong because a manual restart from the AWS Management Console requires human intervention and does not provide automatic recovery, which is the key requirement in the question.

Practice this question →
219
MCQmedium

An SAP administrator is setting up an SAP HANA system replication across two AWS Availability Zones (AZs). The primary and secondary instances use EBS volumes for data and log storage. What is the best practice for ensuring data consistency and minimizing data loss during a failover?

A.Take frequent EBS snapshots of the primary volume and restore them on the secondary.
B.Enable synchronous replication mode in SAP HANA.
C.Use asynchronous replication mode for better performance.
D.Configure the EBS volumes as Multi-Attach to allow both instances to access the same volume.
AnswerB

Synchronous replication ensures data consistency and minimal data loss.

Why this answer

SAP HANA synchronous replication mode ensures that a transaction is committed on both the primary and secondary instances before an acknowledgment is sent to the application. This guarantees zero data loss (RPO=0) during a failover, because the secondary always has an identical copy of the committed data. For cross-AZ deployments, this is the best practice to maintain data consistency while still providing high availability.

Exam trap

The trap here is that candidates often choose asynchronous replication (Option C) because they mistakenly prioritize performance over data consistency, failing to recognize that SAP HANA synchronous replication is the only mode that guarantees zero data loss across AZs in a system replication configuration.

How to eliminate wrong answers

Option A is wrong because EBS snapshots are point-in-time backups, not real-time replication; they introduce significant lag and cannot guarantee data consistency at the moment of failover, leading to potential data loss. Option C is wrong because asynchronous replication, while offering better performance, allows the secondary to lag behind the primary, which can result in data loss (RPO > 0) during a failover. Option D is wrong because EBS Multi-Attach does not support attaching a single volume to instances in different Availability Zones, and it does not provide the log-shipping or synchronization logic required for SAP HANA system replication.

Practice this question →
220
MCQeasy

A company plans to migrate its SAP ERP system to AWS. The system currently runs on IBM Db2 and uses a large amount of memory. The architect needs to choose an EC2 instance type that is SAP certified and provides high memory. Which instance family should the architect select?

A.c5.18xlarge
B.x1e.32xlarge
C.r5.24xlarge
D.i3.16xlarge
AnswerB

x1e instances are SAP-certified with up to 3,904 GiB of memory, suitable for large SAP systems.

Why this answer

The x1e.32xlarge instance is SAP-certified for high-memory workloads and is specifically designed for large in-memory databases like IBM Db2. It offers up to 3,904 GiB of memory, making it suitable for SAP ERP systems that require a large memory footprint. Other instance families like C5, R5, and I3 are not SAP-certified for high-memory SAP workloads or lack the necessary memory capacity.

Exam trap

The trap here is that candidates often confuse memory-optimized families (like R5) with SAP-certified high-memory families (like X1e), not realizing that SAP certification requires specific instance types that have passed SAP's validation for large memory configurations and database compatibility.

How to eliminate wrong answers

Option A is wrong because the C5 instance family is compute-optimized and not SAP-certified for high-memory workloads; it lacks the memory capacity required for large SAP ERP systems on Db2. Option C is wrong because the R5 instance family is memory-optimized but not SAP-certified for the high-memory requirements of this scenario; it offers less memory per vCPU compared to the X1e family and is not listed in the SAP AWS certified instances for large memory configurations. Option D is wrong because the I3 instance family is storage-optimized for high I/O workloads (e.g., NVMe SSD) and is not designed for high-memory SAP applications; it is not SAP-certified for memory-intensive ERP systems.

Practice this question →
221
MCQeasy

An SAP administrator is creating an IAM policy for an automation script that needs to start and stop a specific SAP HANA EC2 instance. The policy is shown in the exhibit. However, the script fails with an authorization error when trying to start the instance. What is the most likely cause?

A.The policy is missing an effect for the specific instance.
B.The policy does not include ec2:DescribeInstances action.
C.The ARN in the resource element does not match the actual instance ID.
D.The script does not have the correct region specified.
AnswerC

The instance ID in the policy is likely different from the actual instance.

Why this answer

The policy uses a resource ARN that specifies a particular instance ID. If the ARN does not match the actual instance ID of the SAP HANA EC2 instance, the `ec2:StartInstances` action will fail with an authorization error because IAM evaluates the resource ARN against the instance being started. AWS IAM policies require an exact match between the resource ARN in the policy and the instance ID for actions that operate on specific resources.

Exam trap

The trap here is that candidates often overlook the exact ARN matching requirement and assume the error is due to missing permissions or region misconfiguration, rather than a simple mismatch in the instance ID within the resource element.

How to eliminate wrong answers

Option A is wrong because the policy already includes an 'Allow' effect for the `ec2:StartInstances` and `ec2:StopInstances` actions, so adding another effect is unnecessary. Option B is wrong because `ec2:DescribeInstances` is a read-only action that is not required for starting or stopping instances; the `ec2:StartInstances` and `ec2:StopInstances` actions are sufficient for the automation script. Option D is wrong because the region is specified in the ARN (e.g., `us-east-1`) and the script's region configuration does not affect IAM policy evaluation; the error is due to the instance ID mismatch, not the region.

Practice this question →
222
Multi-Selectmedium

A company runs SAP HANA on AWS using an r5.8xlarge instance with 3.8 TB of EBS gp3 storage. The HANA data volume is 2 TB. The system is experiencing performance issues, and the database administrator suspects that the storage I/O is the bottleneck. Which TWO actions should be taken to improve I/O performance?

Select 2 answers
A.Increase the size of the log volume to improve write performance.
B.Change the data volume type from gp3 to io2 Block Express with higher IOPS.
C.Enable HANA delta merge operations to run more frequently.
D.Upgrade the instance to a larger size with higher network bandwidth.
E.Increase the provisioned IOPS on the HANA data volume.
AnswersB, E

io2 provides consistent low-latency performance.

Why this answer

Io2 Block Express provides up to 256,000 IOPS per volume with sub-millisecond latency, which is essential for SAP HANA's demanding I/O patterns. The current gp3 volume, while offering baseline performance, cannot match the consistent low-latency and high-IOPS capabilities required for HANA data volumes under heavy write workloads. Option E is also correct because increasing provisioned IOPS on the existing gp3 volume directly addresses the I/O bottleneck by raising the performance ceiling, though gp3 has a maximum of 16,000 IOPS per volume, which may still be insufficient for large HANA deployments.

Exam trap

The trap here is that candidates may confuse increasing volume size with improving performance, or assume that network bandwidth upgrades affect storage I/O, when in fact EBS performance is independent of instance network bandwidth and governed by volume type and IOPS provisioning.

Practice this question →
223
MCQeasy

A company plans to migrate its SAP ERP system from an on-premises environment to AWS. The system uses an Oracle database. Which AWS service provides the most cost-effective and high-performance storage for the Oracle data files?

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

Provides high performance for databases.

Why this answer

Amazon EBS io2 Block Express volumes provide the highest performance and durability for Oracle database workloads on AWS, offering up to 256,000 IOPS per volume and sub-millisecond latency. They are the most cost-effective choice for SAP ERP Oracle data files because they deliver consistent, high-throughput performance required for SAP's demanding I/O patterns, while allowing you to pay only for provisioned capacity without upfront costs. io2 volumes also support multi-attach and are designed for mission-critical databases, making them the optimal storage for Oracle data files in SAP on AWS.

Exam trap

The trap here is that candidates often confuse Amazon EFS or S3 as viable database storage options due to their scalability and durability, but they fail to recognize that Oracle databases require block-level storage with consistent low latency and high IOPS, which only EBS io2 Block Express provides for SAP workloads.

How to eliminate wrong answers

Option B (EC2 Instance Store) is wrong because instance store volumes are ephemeral and data is lost when the instance is stopped or terminated, making them unsuitable for persistent Oracle database storage. Option C (Amazon EFS) is wrong because it is a file-level NFS storage service that does not provide the block-level access or consistent low-latency performance required for Oracle database data files, and it is not optimized for high IOPS database workloads. Option D (Amazon S3) is wrong because it is an object storage service with higher latency and no direct block-level access, making it unsuitable for hosting live Oracle database files that require synchronous I/O operations.

Practice this question →
224
Multi-Selectmedium

A company is migrating its SAP ERP system to AWS and wants to minimize downtime during the migration. Which THREE strategies should be considered? (Choose three.)

Select 3 answers
A.Use Amazon S3 Transfer Acceleration to speed up data transfer.
B.Shut down the source system and perform a full database export to S3.
C.Perform a full export and import of the SAP system during a maintenance window.
D.Use SAP Landscape Transformation (SLT) to replicate data in real-time to the target system.
E.Set up AWS Database Migration Service (DMS) for ongoing replication after initial load.
AnswersA, D, E

S3 Transfer Acceleration speeds up data transfer, reducing migration window.

Why this answer

Amazon S3 Transfer Acceleration is correct because it uses AWS edge locations to accelerate uploads to S3 over long distances, leveraging optimized network paths and the TCP protocol to reduce latency and improve throughput. For large SAP database exports, this can significantly reduce the time required for the initial data transfer to AWS, thereby minimizing overall migration downtime.

Exam trap

The AWS SAP on AWS Specialty exam often tests the misconception that shutting down the source system or using a maintenance window is acceptable for minimizing downtime, when in fact these approaches increase downtime. The trap is that candidates confuse 'minimizing downtime' with 'scheduling downtime' and overlook real-time replication (SLT, DMS) and acceleration technologies (S3 Transfer Acceleration).

Practice this question →
225
MCQhard

An SAP system on AWS is experiencing high read latency from the SAP HANA database. The system uses Provisioned IOPS EBS volumes. Which action would most likely improve read latency?

A.Change the EBS volume type to gp2.
B.Disable write caching on the EBS volumes.
C.Move the HANA data to instance store volumes.
D.Increase the provisioned IOPS on the EBS volumes.
AnswerD

Increasing provisioned IOPS directly raises the I/O throughput limit, reducing read latency under load. This is the correct action.

Why this answer

Increasing the provisioned IOPS on the EBS volumes directly addresses high read latency by raising the I/O performance ceiling for the SAP HANA database. Since the system already uses Provisioned IOPS (io1/io2) volumes, higher IOPS reduces queue depth and read latency under heavy workloads. Other options are incorrect: changing to gp2 reduces IOPS, disabling write caching does not improve read latency, and instance store volumes are ephemeral and not recommended for HANA data persistence.

Exam trap

The trap here is that candidates may think increasing IOPS always helps, but the key nuance is that the system already uses Provisioned IOPS, so the correct action is to increase the provisioned IOPS value, not change volume types or rely on ephemeral storage.

How to eliminate wrong answers

Option A is wrong because changing to gp2 (general purpose SSD) would likely reduce performance, as gp2 offers lower and burstable IOPS compared to Provisioned IOPS volumes, worsening latency under sustained SAP HANA loads. Option B is wrong because disabling write caching on EBS volumes does not improve read latency; write caching affects write operations, and EBS volumes do not support configurable read caching at the volume level. Option C is wrong because instance store volumes are ephemeral and not suitable for SAP HANA data, which requires persistent, durable storage; moving data there would risk data loss on instance stop/termination and does not guarantee lower read latency.

Practice this question →
← PreviousPage 3 of 6 · 428 questions totalNext →

Ready to test yourself?

Try a timed practice session using only Sap Workload Design questions.

Start 20-question session