Courseiva

CCNA Sap Workload Design Questions

75 of 462 questions · Page 6/7 · Sap Workload Design topic · Answers revealed

Practice these questionsExam hubAll questions
376
MCQmedium

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

A.Use AWS S3 Cross-Region Replication to copy database backups every 15 minutes.
B.Configure SAP HANA System Replication (HSR) to an EC2 instance in us-west-2 with log replication in sync mode.
C.Take EBS snapshots of the HANA data volume every hour and copy them to us-west-2.
D.Use AWS Database Migration Service (DMS) to continuously replicate changes to a HANA instance in us-west-2.
AnswerB

HSR provides near real-time replication, meeting RPO.

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
377
MCQmedium

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

A.General Purpose SSD (gp3) volumes
B.Provisioned IOPS SSD (io2) volumes
C.Instance Store volumes
D.Throughput Optimized HDD (st1) volumes
AnswerB

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
378
MCQhard

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

A.Verify that EBS optimization is enabled
B.Increase the SWAP space on the instance
C.Upgrade to a compute-optimized instance like c5.24xlarge
D.Check the Elastic Network Adapter (ENA) settings and consider tuning the ring buffer size
AnswerD

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

Why this answer

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

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
379
MCQeasy

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

A.Internet Gateway
B.NAT Gateway
C.VPC Endpoint (Gateway)
D.AWS Site-to-Site VPN
AnswerC

Gateway VPC Endpoint provides private connectivity to S3 without internet.

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
380
MCQeasy

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

A.Migrate from gp2 to io2 EBS volumes with the same size.
B.Modify the volume to use Provisioned IOPS (io1) with a higher IOPS value.
C.Add an additional EBS volume and stripe the volumes using LVM.
D.Increase the size of the existing EBS gp2 volume to a larger size.
AnswerD

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
381
MCQmedium

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

A.Replace gp2 volumes with io2 Block Express volumes to provide consistent IOPS performance.
B.Move the database to an i3en.24xlarge instance to increase network and EBS bandwidth.
C.Enable EBS optimization on the existing instance to improve throughput.
D.Add two additional gp2 volumes to the RAID 0 stripe to increase throughput.
AnswerA

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
382
Multi-Selectmedium

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

Select 2 answers
A.Enable encryption at rest for EBS volumes and RDS databases
B.Use the AWS account root user for daily administration
C.Place SAP application servers in a public subnet with direct internet access
D.Store SAP transport files in a public S3 bucket
E.Use security groups to control traffic to SAP instances
AnswersA, E

Encryption protects data at rest.

Why this answer

Option B is correct because security groups act as virtual firewalls for EC2 instances. Option C is correct because encryption at rest is a security best practice. Option A is wrong because direct internet access is not recommended.

Option D is wrong because public S3 buckets are insecure. Option E is wrong because using the root user is not a best practice.

Practice this question →
383
MCQeasy

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

A.Multi-AZ with HANA System Replication in sync mode and automatic failover.
B.Single AZ with HANA System Replication to a standby in the same AZ.
C.Single AZ with daily backups to Amazon S3.
D.Multi-AZ with HANA System Replication in async mode and manual failover.
AnswerA

Provides automatic failover across AZs.

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
384
MCQmedium

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

A.Use Amazon FSx for Lustre as primary persistent storage for HANA data.
B.Use Provisioned IOPS SSD (io1 or io2) EBS volumes for the data volume.
C.Use General Purpose SSD (gp2) EBS volumes for the data volume.
D.Use Throughput Optimized HDD (st1) EBS volumes for the data volume.
AnswerB

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

Why this answer

Option B is correct because SAP HANA on AWS requires high-performance storage for the data volume, and AWS recommends using Provisioned IOPS SSD (io1 or io2) EBS volumes for HANA data to ensure consistent low latency and high throughput. Option A is incorrect because General Purpose SSD (gp2) does not provide sufficient IOPS for production HANA workloads. Option C is incorrect because Throughput Optimized HDD (st1) is not suitable for database workloads due to variable performance.

Option D is incorrect because Amazon FSx for Lustre is optimized for high-performance computing, not for persistent database storage.

Practice this question →
385
MCQhard

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

A.Increase the EBS read throughput
B.Use a larger instance type like r6i.32xlarge
C.Increase the GP3 volume IOPS
D.Switch to io2 Block Express volumes with higher IOPS
AnswerD

io2 provides consistent high IOPS for write-heavy workloads.

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
386
MCQmedium

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

A.The EBS volumes are not providing enough IOPS for the workload.
B.The HANA parameter 'max_concurrency' is set too low.
C.There are SQL statement contention and locking issues in the HANA database.
D.The EC2 instance type is undersized for the HANA workload.
AnswerC

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
387
MCQhard

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

A.Change the volume type to gp3 and adjust the IOPS and throughput settings.
B.Increase the size of the gp2 volumes to increase the baseline IOPS.
C.Move the data to instance store volumes for better performance.
D.Change the volume type to io1 and provision high IOPS.
AnswerA

gp3 provides baseline performance without burst credits.

Why this answer

Option C is correct because changing the volume type to gp3 provides baseline performance without burst credits, eliminating burst bucket depletion. Option A is wrong because gp2 volumes still use burst credits. Option B is wrong because Provisioned IOPS is more expensive and may not be needed.

Option D is wrong because instance store volumes are ephemeral and not suitable for persistent data.

Practice this question →
388
MCQmedium

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

A.AWS Systems Manager Automation to run DR scripts.
B.AWS CloudFormation StackSets to deploy the environment in the DR region.
C.Amazon S3 Cross-Region Replication to replicate SAP application data.
D.AWS Elastic Disaster Recovery (DRS) to replicate and orchestrate failover.
AnswerD

Elastic Disaster Recovery provides automated replication and orchestrated failover.

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
389
Matchingmedium

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

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

Concepts
Matches

Single small instance, no HA

Medium instances, minimal redundancy

Medium instances, some HA

Large instances, multi-AZ, HA and DR

Why these pairings

SAP landscape tiers have different size and availability requirements.

Practice this question →
390
Multi-Selecteasy

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

Select 2 answers
A.Use T2 or T3 burstable instances for cost savings.
B.Deploy SAP ASCS and PAS instances in separate Availability Zones.
C.Use EBS Multi-Attach volumes for the SAP application data.
D.Configure multiple Application Load Balancers in a failover configuration.
E.Use an Elastic Load Balancer to distribute traffic to multiple Web Dispatchers.
AnswersB, E

Multiple AZs provide failover if one AZ becomes unavailable.

Why this answer

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

Exam trap

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

Practice this question →
391
MCQmedium

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

A.Set up an automated process to copy the EC2 instance AMI to the DR Region every hour.
B.Use Amazon S3 Cross-Region Replication to replicate the HANA data directory to the DR Region.
C.Perform periodic HANA database backups to S3 and restore in the DR Region when needed.
D.Configure SAP HANA System Replication to a secondary instance in the DR Region and use automated EBS snapshots for cross-Region replication.
AnswerD

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

Why this answer

Option D is correct because SAP HANA System Replication with HANA Backup/Restore using cross-Region EBS snapshots can achieve RPO of 1 hour and RTO of 15 minutes if automated. Option A is wrong because copying AMIs every hour may not achieve RPO consistently and RTO may be longer. Option B is wrong because S3 versioning does not provide database-level replication.

Option C is wrong because manual restore from backup cannot achieve 15-minute RTO.

Practice this question →
392
MCQeasy

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

A.Use AWS Backup with a backup plan for the EC2 instance.
B.Use Amazon EBS snapshots of the database volume.
C.Configure SAP HANA Backup & Recovery using Backint agent to Amazon S3.
D.Use AWS Database Migration Service (DMS) for continuous replication.
AnswerC

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
393
Multi-Selecthard

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

Select 3 answers
A.Configure an Amazon SNS topic to send email or SMS notifications when the alarm state is reached.
B.Create a CloudWatch alarm that triggers when CPU utilization exceeds 90% for 5 consecutive minutes.
C.Create a CloudWatch metric filter on the HANA host's CPU utilization.
D.Enable CloudWatch Logs for the SAP application logs to detect performance issues.
E.Install the SAP Host Agent on the HANA instance and configure it to send metrics to SAP Solution Manager.
AnswersA, B, C

SNS delivers the alert to the operations team.

Why this answer

Option A is correct because Amazon SNS is the standard AWS service for distributing notifications from CloudWatch alarms. By configuring an SNS topic to send email or SMS, the operations team receives alerts when the CPU utilization alarm triggers, enabling timely response to performance issues.

Exam trap

The trap here is that candidates may confuse log-based monitoring (CloudWatch Logs) with metric-based monitoring (CloudWatch Metrics), or assume SAP-specific tools like SAP Host Agent are required for basic AWS monitoring, when in fact CloudWatch and SNS provide the native, simpler solution for CPU utilization alerting.

Practice this question →
394
MCQeasy

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

A.Amazon EFS
B.Amazon EBS io2 Block Express volumes
C.Amazon S3
D.Amazon EBS st1 volumes
AnswerB

io2 Block Express offers high IOPS and low latency for 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 are the only EBS volume type certified by SAP for production HANA databases on AWS, meeting the high IOPS and low latency requirements.

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
395
Multi-Selectmedium

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

Select 2 answers
A.Use IAM roles to grant EC2 instances access to AWS services.
B.Use security groups to control traffic to SAP application servers.
C.Disable encryption in transit between application and database tiers.
D.Allow SSH access from the internet for administration.
E.Store SAP backup files in a public S3 bucket for easy access.
AnswersA, B

IAM roles are secure and avoid storing credentials.

Why this answer

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

Exam trap

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

Practice this question →
396
MCQhard

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

A.4500 IOPS
B.16,000 IOPS
C.3000 IOPS
D.1500 IOPS
AnswerC

Baseline IOPS = 3 * 1000 = 3000.

Why this answer

Option C is correct because gp2 baseline IOPS is 3 IOPS per GiB for volumes up to 533 GiB, then 16,000 IOPS maximum. For 1000 GiB, baseline IOPS = min(1000 * 3, 16000) = 3000 IOPS. Option A is wrong because 1500 is the previous IOPS.

Option B is wrong because 16000 is the max, not baseline. Option D is wrong because 4500 is incorrect calculation.

Practice this question →
397
MCQmedium

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

A.Enable the Max I/O performance mode on the EFS file system.
B.Change the performance mode from Max I/O to General Purpose.
C.Migrate the /sapmnt directory to an Amazon EBS volume.
D.Increase the provisioned throughput of the EFS file system.
AnswerA

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

Why this answer

Option D is correct because enabling EFS Max I/O performance mode allows higher throughput for large workloads. Option A is wrong because Provisioned Throughput increases cost but may not address latency. Option B is wrong because changing to General Purpose mode is the default and may not help.

Option C is wrong because EBS is not shared across multiple instances like EFS.

Practice this question →
398
MCQeasy

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

A.Use AWS Backup with the SAP HANA plugin
B.Use SAP HANA Backint integration to back up to S3
C.Create EBS snapshots of the database volumes
D.Configure S3 Lifecycle policies to move logs
AnswerB

Backint agent sends data directly to S3 with low overhead.

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
399
Multi-Selecthard

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

Select 3 answers
A.EBS snapshots taken every 15 minutes
B.SAP HANA System Replication in async mode
C.AWS CloudEndure Disaster Recovery
D.Amazon Route 53 DNS failover
E.Pre-built AMIs for SAP application servers
AnswersB, D, E

Async replication can achieve RPO of minutes.

Why this answer

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

Exam trap

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

Practice this question →
400
MCQhard

An SAP administrator is troubleshooting a performance issue on an SAP HANA instance running on an EC2 instance. The instance type is r5.8xlarge with 256 GB of RAM. The administrator notices that the instance's CPU credit balance is depleting rapidly. What is the most likely cause?

A.The instance is using EBS-optimized with insufficient bandwidth
B.The SAP application is using too much memory
C.The instance has a high network throughput causing CPU overhead
D.The instance is a burstable performance instance (e.g., T3) not an r5
AnswerD

Burstable instances earn CPU credits; r5 instances do not have CPU credits.

Why this answer

Option A is correct because r5 instances are not burstable performance instances; they have dedicated vCPUs and do not use CPU credits. The depletion indicates the instance is not an r5 but possibly a T3 instance. Option B and D are not related to CPU credits.

Option C is a misunderstanding.

Practice this question →
401
Multi-Selecthard

A company runs SAP HANA on AWS and wants to encrypt the database at rest. Which THREE options are available to achieve this?

Select 3 answers
A.Use Amazon RDS encryption for the SAP HANA database.
B.Use AWS KMS with a custom key store to manage encryption keys.
C.Enable SAP HANA native encryption for the database.
D.Use Amazon S3 server-side encryption for database files.
E.Enable Amazon EBS encryption on all volumes attached to the HANA instance.
AnswersB, C, E

KMS can manage keys for EBS and HANA encryption.

Why this answer

AWS KMS with a custom key store (option B) is a valid encryption option for SAP HANA on AWS because it allows you to use a customer-managed key store backed by AWS CloudHSM, giving you control over the encryption keys used to protect data at rest. This integrates with Amazon EBS encryption and other AWS services to encrypt the underlying storage volumes, ensuring compliance with key management requirements.

Exam trap

The trap here is that candidates may confuse Amazon RDS encryption with EC2-based database encryption, not realizing that SAP HANA is self-managed on EC2 and does not use the RDS service, making option A technically inapplicable.

Practice this question →
402
MCQmedium

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

A.Use an Application Load Balancer to distribute traffic across AZs.
B.Deploy ASCS with a cluster across two AZs, and use HANA System Replication across two AZs.
C.Place all components in a single AZ to avoid cross-AZ latency.
D.Use Amazon RDS Multi-AZ for the database and a single ASCS instance.
AnswerB

This provides HA for both ASCS and database across AZs.

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
403
MCQeasy

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

A.Check the security group associated with the instance
B.Check the network ACLs
C.Check the IAM policy attached to the instance profile
D.Check the S3 bucket policy
AnswerC

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

Why this answer

Checking the IAM policy attached to the instance profile ensures the correct permissions are granted. Option B is wrong because security groups control network traffic, not S3 access. Option C is wrong because S3 bucket policies are separate from IAM.

Option D is wrong because NACLs are for subnet traffic.

Practice this question →
404
MCQmedium

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

A.AWS CloudWatch alarms and AWS Lambda
B.Auto Scaling groups and Elastic Load Balancer
C.SAP HANA System Replication and Amazon Route 53
D.Amazon RDS Multi-AZ and Route 53
AnswerC

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
405
Multi-Selectmedium

An SAP administrator is designing a backup strategy for SAP HANA on AWS. Which THREE practices should be implemented to ensure reliable backups?

Select 3 answers
A.Store backups in Amazon S3 One Zone-IA
B.Disable encryption on backup targets to reduce latency
C.Take consistent EBS snapshots of HANA volumes after quiescing the database
D.Enable S3 Versioning on the backup bucket
E.Automate backups using AWS Backup with a backup plan
AnswersC, D, E

Consistent snapshots ensure data integrity.

Why this answer

Options A, B, and D are correct. Using AWS Backup for automation (A), EBS snapshots for consistency (B), and storing backups in S3 with versioning (D) are best practices. Option C is wrong because S3 One Zone-IA lacks durability.

Option E is wrong because encryption should be enabled, not disabled.

Practice this question →
406
MCQmedium

An SAP administrator is deploying an SAP ASCS instance using CloudFormation. The deployment fails because the instance cannot be reached from other SAP components. Based on the exhibit, what is the most likely cause?

A.The instance type m5.large is not certified for SAP ASCS.
B.The security group does not allow inbound traffic on the required SAP ports.
C.The instance lacks an IAM role to join the SAP domain.
D.The root volume is too small and uses gp2, which is not supported for SAP.
AnswerB

The template does not specify inbound rules; without proper security group rules, other components cannot connect.

Why this answer

The SAP ASCS instance must be reachable by other SAP components (e.g., PAS, AAS) on specific ports for services like the SAP Message Server (port 36xx/TCP) and SAP Enqueue Server (port 32xx/TCP). The exhibit shows the security group lacks inbound rules for these ports, so traffic from other components is blocked, causing the deployment to fail. Without proper inbound access, the ASCS instance cannot participate in the SAP system's communication, leading to the unreachability error.

Exam trap

The trap here is that candidates often focus on instance certification or storage requirements, overlooking the fundamental network connectivity issue caused by missing security group inbound rules for SAP-specific ports.

How to eliminate wrong answers

Option A is wrong because the m5.large instance type is certified for SAP ASCS on AWS, provided it meets the SAPS and memory requirements for the workload. Option C is wrong because SAP ASCS does not require an IAM role to join an SAP domain; IAM roles are used for AWS API access, not for SAP domain membership (which uses SAP-specific authentication). Option D is wrong because the root volume size and gp2 type are supported for SAP on AWS; gp2 is a valid EBS volume type for SAP, and the root volume size (e.g., 20 GiB) is typically sufficient for the OS and SAP binaries, though additional volumes are used for data.

Practice this question →
407
MCQeasy

A company is planning to run SAP applications on AWS. The security team requires that all data transmitted between the SAP application servers and the SAP HANA database be encrypted in transit. The SAP HANA database is on an EC2 instance in the same VPC. The application servers are also in the same VPC. Which configuration should the company implement to meet the encryption requirement with minimal impact on performance?

A.Use AWS PrivateLink to connect the application to the database
B.Enable SAP HANA TLS/SSL encryption for the database connections
C.Use VPC peering between the application and database subnets
D.Set up a VPN connection between the application and database servers
AnswerB

TLS/SSL encryption secures data in transit between SAP application and database servers.

Why this answer

Option B is correct because enabling SAP HANA TLS/SSL encryption encrypts data in transit between application and database servers without network overhead. Option A is wrong because VPC peering is for cross-VPC communication. Option C is wrong because VPN adds overhead.

Option D is wrong because AWS PrivateLink is for access to services, not for encryption within a VPC.

Practice this question →
408
Multi-Selecthard

Which THREE factors must be considered when choosing an EC2 instance type for SAP HANA production workloads?

Select 3 answers
A.Burstable CPU performance (T3 instances)
B.GPU compute capability
C.EBS-optimized support for consistent I/O
D.SAP certification of the instance type
E.Memory (RAM) size required by SAP HANA
AnswersC, D, E

Necessary for HANA performance.

Why this answer

Option C is correct because SAP HANA is an in-memory database that requires consistent, low-latency I/O for data persistence and log writes. EBS-optimized instances dedicate network bandwidth to EBS traffic, eliminating contention with other network traffic and ensuring predictable I/O performance, which is critical for production SAP HANA workloads.

Exam trap

The trap here is that candidates may assume burstable instances (T3) are suitable for any workload due to their cost-effectiveness, but SAP HANA requires sustained performance and SAP certification, which T3 instances lack.

Practice this question →
409
MCQhard

A company runs SAP S/4HANA on AWS and notices high latency in database transactions. The database is hosted on an r5.24xlarge instance with 768 GB of EBS gp3 storage. The SAP application servers are in the same VPC but different subnets. What should be changed to reduce latency?

A.Use a smaller instance type to reduce network hops.
B.Place the database instance in a cluster placement group with the application servers.
C.Enable EBS optimization on the database instance and ensure the instance type supports dedicated EBS bandwidth.
D.Change the EBS volume type to io2 Block Express with maximum IOPS.
AnswerC

EBS optimization provides dedicated network for EBS, reducing latency.

Why this answer

Option C is correct because EBS optimization ensures dedicated network bandwidth for EBS traffic, preventing contention with other network traffic. The r5.24xlarge instance supports dedicated EBS bandwidth, and enabling this feature reduces latency for database transactions by providing consistent, high-throughput access to the EBS gp3 volume.

Exam trap

The trap here is that candidates often assume high latency in database transactions is always a network or placement issue, leading them to choose cluster placement groups or instance size changes, when the actual root cause is EBS bandwidth contention that is resolved by enabling EBS optimization.

How to eliminate wrong answers

Option A is wrong because using a smaller instance type would reduce available compute and network resources, likely increasing latency rather than reducing it, and network hops are determined by subnet routing, not instance size. Option B is wrong because a cluster placement group provides low-latency network connectivity between instances, but the application servers and database are already in the same VPC; the latency issue is related to EBS storage performance, not inter-instance network latency. Option D is wrong because while io2 Block Express offers higher IOPS and lower latency, the gp3 volume already provides up to 16,000 IOPS and 1,000 MB/s throughput, and the primary bottleneck is likely EBS bandwidth contention, not volume type; changing to io2 Block Express would increase cost without addressing the root cause if EBS optimization is not enabled.

Practice this question →
410
MCQeasy

A company is deploying SAP S/4HANA on AWS and needs to back up the HANA database to Amazon S3. The database is 1 TB and changes frequently. The backup must be completed within 4 hours. What is the most efficient backup method?

A.Take EBS snapshots of the HANA data volumes and copy them to S3.
B.Export the HANA database to a file and manually upload to S3 using AWS CLI.
C.Use AWS Backup to schedule HANA database backups to S3.
D.Configure SAP HANA Backint agent to stream backups directly to Amazon S3.
AnswerD

Backint provides efficient, integrated streaming backups to S3.

Why this answer

Using SAP HANA Backup to Amazon S3 via the Backint agent is the most efficient and recommended method for HANA backups to S3. Option A (EBS snapshots) requires additional steps and may not be integrated. Option B (AWS Backup) supports HANA but is less integrated than Backint.

Option D (manual copy) is not efficient. Option C is correct.

Practice this question →
411
Multi-Selecthard

A company is deploying a mission-critical SAP S/4HANA system on AWS. They need to ensure the highest level of availability and minimize data loss. Which TWO strategies should they implement? (Choose two.)

Select 2 answers
A.Use EC2 Spot Instances for the primary application server
B.Configure automated EBS snapshots every 5 minutes
C.Use Amazon RDS Multi-AZ for the HANA database
D.Set up HANA System Replication in synchronous mode across two Availability Zones
E.Deploy the ASCS and PAS instances in a cluster with Pacemaker across AZs
AnswersD, E

Synchronous replication ensures no data loss and automatic failover.

Why this answer

Option D is correct because HANA System Replication in synchronous mode ensures that every committed transaction is written to the primary and replicated to a secondary HANA instance before the commit is acknowledged. This provides near-zero data loss (RPO=0) and, combined with automatic failover, supports high availability across Availability Zones.

Exam trap

The trap here is that candidates often confuse Amazon RDS Multi-AZ with SAP HANA database replication, but SAP HANA is not supported on RDS and must be managed directly on EC2 with HANA System Replication.

Practice this question →
412
Multi-Selecthard

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

Select 3 answers
A.Encrypt EBS volumes using AWS KMS.
B.Use security groups to restrict traffic between SAP application and database tiers.
C.Use IAM roles for EC2 instances to access AWS services.
D.Place all SAP instances in public subnets for easier access.
E.Store AWS credentials in the SAP application code for API access.
AnswersA, B, C

Encryption protects data at rest.

Why this answer

Options A, B, and D are correct. A: Using AWS KMS to encrypt EBS volumes ensures data at rest is encrypted. B: Security groups are stateful firewalls that control traffic between instances.

D: IAM roles provide temporary credentials for EC2 instances to access AWS services securely. Option C is incorrect because public subnets expose instances to the internet, which is not a security best practice. Option E is incorrect because root user credentials should not be used for daily operations; IAM users are preferred.

Practice this question →
413
MCQhard

A company runs SAP S/4HANA on AWS in a single region with a multi-AZ setup. The SAP HANA database uses HANA System Replication (HSR) for high availability. The primary HANA instance is in us-east-1a and the secondary is in us-east-1b. The application servers are split across both AZs. Recently, during a maintenance window, the primary HANA instance failed unexpectedly. The secondary automatically took over. However, after the failover, the application servers in us-east-1a are experiencing higher latency when connecting to the database, while application servers in us-east-1b have normal latency. The network team confirms that the inter-AZ latency is within normal limits. Which of the following is the MOST likely cause of the increased latency?

A.The secondary HANA instance is using a different instance type with a single Elastic Network Interface (ENI), which limits throughput.
B.The placement group that includes the application servers and the database is now split across AZs, reducing performance.
C.The application servers in us-east-1a are now connecting to the HANA database in us-east-1b, which adds inter-AZ latency.
D.The EBS volumes attached to the old primary instance are still being replicated to the secondary, causing network congestion.
AnswerC

Previously, all connections were within the same AZ; after failover, half the servers must connect across AZs.

Why this answer

Option C is correct because after the failover, the secondary HANA instance in us-east-1b became the active database. Application servers in us-east-1a must now connect across AZs to reach the database in us-east-1b, incurring inter-AZ latency. Although the network team confirms normal inter-AZ latency, the additional network hop and physical distance between AZs still introduce higher latency compared to same-AZ connections, which explains the observed increase.

Exam trap

The trap here is that candidates may assume inter-AZ latency is negligible or that the network team's confirmation of 'normal limits' means latency is not the issue, but in SAP HANA workloads, even 1-2 ms of additional latency can cause noticeable performance degradation for cross-AZ database connections.

How to eliminate wrong answers

Option A is wrong because the instance type and number of ENIs affect network throughput, not latency; a single ENI does not inherently cause higher latency, and HSR failover does not change the instance type of the secondary. Option B is wrong because placement groups are not used for SAP HANA multi-AZ setups; they are designed for low-latency within a single AZ, and splitting a placement group across AZs would not be configured in this architecture. Option D is wrong because EBS volume replication is not part of HSR; HSR uses log-based replication over the network, and EBS volumes are not replicated between instances; the old primary's volumes are irrelevant after failover.

Practice this question →
414
MCQhard

A company is deploying SAP S/4HANA on AWS and needs to ensure that the system can survive a single Availability Zone failure. Which architecture meets this requirement?

A.Store the database files on Amazon S3 and mount them to the EC2 instance
B.Deploy an active-passive setup with the primary in one AZ and a standby in another AZ, using replication
C.Use Amazon RDS Multi-AZ for the SAP HANA database
D.Deploy a single EC2 instance in one Availability Zone with EBS snapshots
AnswerB

Active-passive with cross-AZ standby ensures availability if one AZ fails.

Why this answer

Option B is correct because an active-passive SAP HANA setup with the primary in one Availability Zone (AZ) and a standby in another AZ, using HANA System Replication (HSR) in synchronous mode, ensures zero data loss and automatic failover if a single AZ fails. This architecture meets the SAP S/4HANA requirement for high availability (HA) across AZs, as HSR replicates data at the database level, and the standby can take over within minutes.

Exam trap

The trap here is that candidates often confuse Amazon RDS Multi-AZ with SAP HANA HA, but RDS Multi-AZ is a managed service for non-SAP databases and does not support SAP HANA, which requires self-managed HSR on EC2 for cross-AZ failover.

How to eliminate wrong answers

Option A is wrong because Amazon S3 is an object storage service that cannot be mounted as a file system to an EC2 instance for SAP HANA database files; SAP HANA requires block storage (e.g., Amazon EBS) with low latency and consistent I/O, and S3 lacks the necessary POSIX file system semantics and performance characteristics. Option C is wrong because Amazon RDS Multi-AZ does not support SAP HANA as a database engine; RDS supports MySQL, PostgreSQL, Oracle, SQL Server, and MariaDB, but SAP HANA must be deployed on EC2 instances with HSR for HA. Option D is wrong because a single EC2 instance with EBS snapshots provides backup and point-in-time recovery, but it cannot survive an AZ failure since there is no standby instance in another AZ; recovery from snapshots takes minutes to hours and involves data loss, not automatic failover.

Practice this question →
415
MCQeasy

A company wants to use an SAP-certified AMI for a non-production SAP system to reduce deployment time. Which AWS service provides access to SAP-certified AMIs?

A.EC2 Image Builder
B.AWS Systems Manager
C.AWS Marketplace
D.AWS Service Catalog
AnswerC

Marketplace provides SAP-certified AMIs for quick deployment.

Why this answer

AWS Marketplace is the correct service because it provides access to SAP-certified AMIs that have been pre-configured and validated by SAP for running SAP workloads on AWS. These AMIs are published by AWS and SAP partners, ensuring compliance with SAP's certification requirements and reducing deployment time for non-production systems.

Exam trap

The trap here is that candidates may confuse AWS Marketplace with EC2 Image Builder or AWS Service Catalog, assuming that any AMI management or catalog service can provide certified images, but only AWS Marketplace hosts the official SAP-certified AMIs.

How to eliminate wrong answers

Option A is wrong because EC2 Image Builder is used to create and maintain custom AMIs, but it does not provide access to pre-existing SAP-certified AMIs. Option B is wrong because AWS Systems Manager is a management service for operational tasks like patching and automation, not a repository for certified AMIs. Option D is wrong because AWS Service Catalog allows organizations to create and manage a catalog of approved IT services, but it does not host SAP-certified AMIs directly; it can only reference AMIs from sources like AWS Marketplace.

Practice this question →
416
MCQhard

An architect is designing a disaster recovery (DR) solution for an SAP ERP system on AWS. The primary site is in us-east-1 and the DR site is in us-west-2. The SAP application uses an Oracle database. The RTO is 4 hours and RPO is 1 hour. Which solution meets these requirements with the least operational overhead?

A.Set up Oracle Active Data Guard between the primary and DR regions
B.Take daily EBS snapshots of the database volumes and copy them to us-west-2, then restore using the snapshots
C.Use AWS Backup to copy EC2 AMIs and RDS snapshots to us-west-2 every hour
D.Configure AWS Database Migration Service (DMS) with ongoing replication from the primary Oracle database to a standby in us-west-2
AnswerD

DMS provides continuous replication, meeting RPO of 1 hour, and can be automated for failover.

Why this answer

AWS Database Migration Service (DMS) with ongoing replication provides continuous change data capture (CDC) from the primary Oracle database to a standby in us-west-2, meeting the 1-hour RPO and 4-hour RTO with minimal operational overhead. DMS handles schema conversion, replication, and failover without requiring manual intervention or complex Oracle licensing, making it the most efficient choice for cross-region DR.

Exam trap

AWS often tests the misconception that native Oracle replication tools like Data Guard are always the best choice for DR, but the question emphasizes 'least operational overhead,' and DMS avoids the licensing and management burden of Active Data Guard while still meeting the RPO/RTO.

How to eliminate wrong answers

Option A is wrong because Oracle Active Data Guard requires Oracle Database Enterprise Edition with the Active Data Guard option, which adds significant licensing costs and operational complexity for managing Data Guard brokers, log transport, and failover scripts on EC2. Option B is wrong because daily EBS snapshots cannot achieve a 1-hour RPO, as snapshots are taken only once per day and the restore process from snapshots takes hours, exceeding the 4-hour RTO. Option C is wrong because AWS Backup copying EC2 AMIs and RDS snapshots every hour still results in a maximum RPO of 1 hour only if snapshots are taken exactly on the hour, but restoring from AMIs or RDS snapshots typically takes longer than 4 hours due to volume initialization and database recovery, and this approach does not support ongoing replication for near-zero data loss.

Practice this question →
417
Multi-Selecthard

An SAP administrator is setting up a disaster recovery (DR) site for SAP S/4HANA in a different AWS Region. To minimize data loss, which THREE strategies should be implemented? (Choose THREE.)

Select 3 answers
A.Set up automated EBS snapshots of HANA volumes and copy them to the DR region.
B.Implement cross-Region replication for Amazon EFS file systems used for SAP transport.
C.Configure SAP HANA system replication using asynchronous mode across regions.
D.Use EBS Multi-Attach volumes to share disks between regions.
E.Use Amazon CloudFront to cache HANA data in the DR region.
AnswersA, B, C

Snapshots provide recoverable point-in-time copies in the DR region.

Why this answer

Automated EBS snapshots of HANA volumes can be copied to the DR region using AWS Backup or custom scripts, providing point-in-time recovery with minimal data loss. This strategy ensures that persistent data is asynchronously replicated across regions, which is a standard approach for SAP disaster recovery.

Exam trap

The trap here is that candidates may confuse EBS Multi-Attach (a single-AZ feature) with cross-region replication, or assume CloudFront can serve as a database cache, when in fact it is only for HTTP/HTTPS content delivery and cannot handle SAP HANA data.

Practice this question →
418
MCQmedium

A company runs SAP on AWS with a shared storage solution for transport files. They need a highly available, scalable, and POSIX-compliant file system. Which AWS storage service should they use?

A.Amazon Elastic File System (EFS)
B.Amazon S3
C.Amazon FSx for NetApp ONTAP
D.Amazon Elastic Block Store (EBS) with Multi-Attach enabled
AnswerC

FSx for NetApp ONTAP provides POSIX-compliant, highly available, and scalable file storage ideal for SAP transport files.

Why this answer

Amazon FSx for NetApp ONTAP provides a fully managed, POSIX-compliant shared file system that supports the NFS, SMB, and iSCSI protocols required by SAP transport directories. It offers high availability across multiple Availability Zones, automatic failover, and scalable throughput, making it the correct choice for SAP transport files on AWS.

Exam trap

The trap here is that candidates often assume Amazon EFS is the default POSIX-compliant file system for all Linux workloads, but they overlook that SAP transport files specifically require the advanced NetApp ONTAP features (like iSCSI support and enterprise storage replication) that FSx for ONTAP provides, which EFS cannot offer.

How to eliminate wrong answers

Option A is wrong because Amazon EFS is POSIX-compliant but does not support the iSCSI protocol or the advanced NetApp ONTAP features (e.g., SnapMirror, FlexClone) that SAP transport management often requires; it also lacks the ability to serve as a direct target for SAP's transport directory in many enterprise SAP architectures. Option B is wrong because Amazon S3 is not POSIX-compliant and uses a flat key-value store with eventual consistency for some operations, which cannot meet the strict file-locking and hierarchical namespace requirements of SAP transport files. Option D is wrong because Amazon EBS with Multi-Attach enabled supports only a limited number of Nitro-based EC2 instances (up to 16) and does not provide a fully managed, scalable, POSIX-compliant file system; it also lacks the native NFS/iSCSI protocol support needed for SAP transport directories.

Practice this question →
419
MCQhard

An SAP system on AWS uses a shared file system via Amazon EFS for transport directory (/usr/sap/trans). The system experiences slow batch jobs. Monitoring shows high read latency on EFS. Which action would most likely reduce latency?

A.Use a larger EC2 instance for the application server
B.Migrate the transport directory to Amazon S3
C.Use EFS Max I/O performance mode or Provisioned Throughput
D.Move the transport directory to instance store volumes
AnswerC

Max I/O increases IOPS; Provisioned Throughput increases throughput.

Why this answer

EFS Max I/O performance mode is designed to scale to higher levels of aggregate throughput and IOPS with lower latencies for workloads like SAP transport directories that experience high concurrency and throughput demands. Provisioned Throughput allows you to specify a higher throughput level independent of the amount of data stored, directly addressing the high read latency issue. This is the most effective action because it optimizes the file system's performance characteristics for the SAP batch job workload.

Exam trap

The trap here is that candidates often confuse EFS performance modes with storage tiers (e.g., Standard vs. Infrequent Access) or assume that increasing compute power (Option A) will fix storage latency, when in fact the bottleneck is the file system's throughput ceiling, not the application server's CPU or memory.

How to eliminate wrong answers

Option A is wrong because increasing the EC2 instance size does not reduce EFS read latency; EFS performance is independent of the compute instance's size and is governed by the file system's throughput and IOPS limits. Option B is wrong because Amazon S3 is an object store, not a POSIX-compliant shared file system, and cannot serve as a drop-in replacement for the SAP transport directory (/usr/sap/trans) which requires NFSv4 semantics, file locking, and low-latency random access. Option D is wrong because instance store volumes are ephemeral and tied to the lifecycle of the EC2 instance; they cannot provide the persistent, shared access required for the transport directory across multiple SAP application servers.

Practice this question →
420
Multi-Selecthard

A company runs SAP S/4HANA on AWS in a multi-AZ deployment. The SAP HANA database is 2 TB and uses EBS gp3 volumes. During a monthly patching cycle, the primary database fails over to the secondary, but the secondary takes over 30 minutes to come online. Which TWO changes would most likely reduce the failover time? (Choose two.)

Select 2 answers
A.Increase the provisioned IOPS and throughput on the EBS log volumes.
B.Place the primary and secondary HANA servers in a cluster placement group.
C.Use different EC2 instance types for primary and secondary to balance cost.
D.Deploy all HANA nodes in the same Availability Zone to reduce network latency.
E.Enable EBS optimization on the secondary instance's EBS volumes.
AnswersA, B

Higher log volume performance improves replication throughput.

Why this answer

HANA system replication in a multi-AZ setup can be optimized by using AWS placement groups for low latency, and increasing the log volume size to handle higher I/O during replication. Option A (single AZ) defeats HA. Option B (increasing log volume) helps sustain replication throughput.

Option C (using different instance types) is not recommended. Option D (placement group) reduces network latency. Option E (EBS optimization) is already enabled by default on modern instances.

Practice this question →
421
MCQeasy

An architect is designing a network topology for an SAP system on AWS. The SAP application servers must be placed in private subnets, and the web dispatchers must be accessible from the internet. Which configuration should the architect use to meet these requirements?

A.Place all SAP servers in public subnets and use security groups to restrict access
B.Place the web dispatchers in private subnets and use a NAT Gateway for internet access
C.Place all servers in private subnets and use an Application Load Balancer for internet access
D.Place the web dispatchers in public subnets, the application servers in private subnets, and use a Network Load Balancer in front of the web dispatchers
AnswerD

This design provides internet access to web dispatchers via a public-facing NLB while keeping application servers private.

Why this answer

Option D is correct because web dispatchers need direct internet accessibility, which is achieved by placing them in public subnets with an Internet Gateway route. The SAP application servers must remain in private subnets for security, and a Network Load Balancer (NLB) in front of the web dispatchers provides layer 4 load balancing and health checks without exposing the dispatchers' IPs directly, while preserving client IP for logging and security.

Exam trap

The trap here is that candidates often assume an Application Load Balancer (ALB) is always the best choice for internet-facing web traffic, but for SAP Web Dispatchers, a Network Load Balancer (NLB) is required because ALBs cannot handle non-HTTP protocols like DIAG and RFC, and they modify headers in ways that break SAP session persistence.

How to eliminate wrong answers

Option A is wrong because placing all SAP servers in public subnets exposes the application servers to the internet, violating the requirement for private subnets and increasing the attack surface; security groups alone do not prevent direct internet routing. Option B is wrong because placing web dispatchers in private subnets with a NAT Gateway allows outbound internet access only, not inbound internet traffic from users, so the web dispatchers would not be accessible from the internet. Option C is wrong because placing all servers in private subnets and using an Application Load Balancer (ALB) for internet access would require the ALB to be in public subnets, but the ALB operates at layer 7 and is not designed to front-end web dispatchers that handle SAP-specific protocols (e.g., DIAG, RFC) which require layer 4 load balancing; additionally, the ALB would terminate TLS and modify headers, which can break SAP Web Dispatcher functionality.

Practice this question →
422
Multi-Selecthard

A company runs SAP S/4HANA on AWS with a large HANA database (10 TB). The database uses EBS gp3 volumes. The system experiences performance degradation due to high disk I/O. The architect decides to migrate to EBS io2 Block Express volumes. Which THREE factors should the architect consider when planning the migration?

Select 3 answers
A.The maximum IOPS per volume supported by io2 Block Express is 256,000.
B.SAP HANA supports RAID 0 across multiple io2 volumes without additional software.
C.io2 Block Express volumes can be attached to multiple EC2 instances simultaneously using EBS Multi-Attach.
D.To achieve the required throughput, multiple io2 volumes should be striped using LVM.
E.The cost of io2 Block Express volumes is higher than gp3 volumes on a per-GB basis.
AnswersA, D, E

High IOPS per volume is a key benefit for large HANA systems.

Why this answer

Option A is correct because io2 Block Express volumes support a maximum IOPS of 256,000 per volume, which is significantly higher than the 16,000 IOPS limit of gp3. This high IOPS capability is critical for large SAP HANA databases (10 TB) that experience performance degradation due to high disk I/O, as it allows the database to handle bursty workloads without throttling.

Exam trap

The trap here is that candidates may confuse io2 Block Express with standard io2 volumes, assuming Multi-Attach is supported, or incorrectly believe SAP HANA natively supports RAID 0 without additional volume management tools.

Practice this question →
423
MCQmedium

An SAP system on AWS is experiencing performance degradation. The SAP administrator wants to monitor the EC2 instance's CPU utilization and memory usage. Which AWS service should be used to collect memory metrics?

A.Amazon CloudWatch (default metrics)
B.AWS Systems Manager Inventory
C.AWS Trusted Advisor
D.Amazon CloudWatch Agent
AnswerD

The CloudWatch Agent can collect memory and disk metrics from EC2 instances.

Why this answer

Option B is correct because CloudWatch Agent can collect memory metrics from EC2 instances. Option A is wrong because CloudWatch by default only collects CPU, disk, and network metrics. Option C is wrong because AWS Systems Manager Inventory collects software inventory, not memory metrics.

Option D is wrong because AWS Trusted Advisor provides recommendations, not metrics.

Practice this question →
424
Multi-Selecteasy

Which TWO AWS services can be used to monitor SAP system performance and send alerts? (Choose two.)

Select 2 answers
A.Amazon Simple Notification Service (SNS)
B.Amazon Inspector
C.Amazon CloudWatch
D.AWS Config
E.AWS Trusted Advisor
AnswersA, C

SNS can send notifications from CloudWatch alarms.

Why this answer

Amazon CloudWatch is the primary AWS monitoring service that can collect metrics from SAP systems (e.g., via SAP Cloud Connector or custom scripts) and trigger alarms based on thresholds. Amazon SNS is the notification service that CloudWatch alarms use to send alerts via email, SMS, or HTTP endpoints. Together, they form the standard monitoring and alerting pipeline for SAP workloads on AWS.

Exam trap

The trap here is that candidates often confuse AWS Config or Trusted Advisor as monitoring services, but they are configuration auditing and advisory tools, not real-time performance monitoring and alerting services like CloudWatch and SNS.

Practice this question →
425
MCQmedium

An SAP administrator is configuring the /hana/data volume for SAP HANA on an EC2 instance. The exhibit shows the /etc/fstab entry. What is the purpose of the 'noatime' mount option?

A.To enable swap space on the volume.
B.To enable disk quotas.
C.To mount the volume as read-only.
D.To disable updating the access time on files, improving performance.
AnswerD

noatime reduces write operations.

Why this answer

The 'noatime' mount option disables the update of inode access timestamps (atime) on every file read. For SAP HANA, which performs high-frequency I/O operations on the /hana/data volume, this eliminates unnecessary metadata writes, reducing disk I/O overhead and improving overall filesystem performance.

Exam trap

The trap here is that candidates may confuse 'noatime' with other mount options like 'ro' (read-only) or 'sw' (swap), or assume it is related to performance tuning for swap or quotas, when in fact it specifically targets access time updates to reduce I/O overhead.

How to eliminate wrong answers

Option A is wrong because swap space is configured via a swap partition or a swap file, not by the 'noatime' mount option; 'noatime' does not enable swap. Option B is wrong because disk quotas are enabled using the 'usrquota' or 'grpquota' mount options, not 'noatime'. Option C is wrong because mounting a volume as read-only is achieved with the 'ro' mount option, while 'noatime' only affects access time updates and does not restrict write operations.

Practice this question →
426
MCQmedium

A company is migrating an SAP system to AWS and needs to ensure that the SAP license is compliant. The current license is based on the number of users. Which AWS pricing model is most appropriate for this scenario?

A.Spot Instances
B.Reserved Instances
C.Dedicated Hosts
D.On-Demand instances
AnswerD

On-Demand allows scaling based on demand without affecting user-based licensing.

Why this answer

Option B is correct because On-Demand instances provide flexibility to scale without upfront commitment, and SAP licensing is user-based, not tied to instance size. Option A is wrong because Reserved Instances lock in a specific instance type. Option C is wrong because Dedicated Hosts may be needed for some SAP licenses but not for user-based licensing.

Option D is wrong because Spot Instances are not suitable for production SAP systems.

Practice this question →
427
Drag & Dropmedium

Drag and drop the steps to perform a backup and restore of an SAP HANA database using AWS Backup into the correct order.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps
Order

Why this order

AWS Backup requires a plan, resource assignment, backup execution, selection of backup, and restore.

Practice this question →
428
Multi-Selecthard

An SAP administrator is troubleshooting a performance issue on an SAP NetWeaver system running on AWS. The system uses an Oracle database. The CPU utilization of the database server is consistently below 30%, but application response times are slow. Which THREE checks should the administrator perform to identify the bottleneck?

Select 3 answers
A.Use Amazon CloudWatch metrics to check network throughput and latency between the application and database servers.
B.Check the EBS volume queue length and I/O wait times on the database server.
C.Examine Oracle database wait events for enqueue and latch contention.
D.Increase the number of CPU cores on the database server.
E.Enable Amazon EBS Elastic Volumes to increase volume size dynamically.
AnswersA, B, C

Network latency can cause slow responses.

Why this answer

Option A is correct because high network latency or insufficient throughput between the application and database servers can cause slow response times even when CPU utilization is low. Amazon CloudWatch metrics such as NetworkIn, NetworkOut, and NetworkPacketsIn/Out can reveal congestion or bandwidth saturation, which is a common bottleneck in SAP NetWeaver deployments on AWS.

Exam trap

The trap here is that candidates often assume low CPU utilization means the system is not busy, overlooking that I/O wait, network latency, or database contention can cause slow responses without consuming CPU cycles.

Practice this question →
429
MCQmedium

A company is migrating its SAP ERP system to AWS and needs to minimize network latency between the SAP application servers and the database. Which AWS service or feature should be used to meet this requirement?

A.Use AWS Global Accelerator for the application servers.
B.Place the application and database servers in the same placement group.
C.Set up VPC peering between the application and database VPCs.
D.Use an Elastic Load Balancer in front of the application servers.
AnswerB

Placement groups provide low-latency, high-throughput networking between EC2 instances.

Why this answer

Placement groups in AWS, specifically cluster placement groups, provide low-latency network performance by ensuring that EC2 instances are placed in close physical proximity within a single Availability Zone. This minimizes network latency between SAP application servers and the database, meeting the requirement for high-throughput, low-latency communication critical for SAP ERP workloads.

Exam trap

The trap here is that candidates often confuse network-level services like Global Accelerator or load balancers with physical proximity optimizations, mistakenly thinking they reduce inter-instance latency when they actually add network hops or are designed for external traffic optimization.

How to eliminate wrong answers

Option A is wrong because AWS Global Accelerator improves global traffic routing and reduces internet latency via the AWS edge network, but it does not reduce network latency between instances within the same AWS region or Availability Zone; it is designed for external user traffic, not inter-instance communication. Option C is wrong because VPC peering connects separate VPCs for IP routing but does not influence the physical placement or network distance between instances; it does not inherently reduce latency compared to instances in the same VPC or placement group. Option D is wrong because an Elastic Load Balancer distributes incoming traffic across multiple application servers for high availability and scaling, but it adds network hop latency and does not reduce the latency between application servers and the database; it is not a solution for inter-instance latency optimization.

Practice this question →
430
MCQmedium

A company is migrating an SAP ERP system to AWS and wants to use SAP HANA as the database. The current on-premises database is 4 TB. Which EC2 instance type is optimized for SAP HANA workloads and provides sufficient memory?

A.x1e.32xlarge
B.r5.24xlarge
C.m5.24xlarge
D.c5.18xlarge
AnswerA

x1e.32xlarge offers 4 TB of memory, SAP HANA certified.

Why this answer

The x1e.32xlarge instance is specifically optimized for SAP HANA workloads, offering 3,904 GiB of memory, which is sufficient for a 4 TB SAP HANA database when considering the 1:5 memory-to-data ratio required by SAP (4 TB data requires approximately 800 GB memory, but the x1e.32xlarge provides ample headroom for growth and workload peaks). It also supports SAP HANA certified instance types and provides high network and EBS throughput essential for HANA's performance demands.

Exam trap

The trap here is that candidates often choose the r5.24xlarge because it is memory-optimized and has a high memory-to-vCPU ratio, but they overlook that it is not SAP HANA certified for production workloads and its 768 GiB memory is insufficient for a 4 TB database, as SAP requires a minimum memory-to-data ratio of 1:5 (and often 1:2 for production).

How to eliminate wrong answers

Option B (r5.24xlarge) is wrong because while it is memory-optimized, it only provides 768 GiB of memory, which is insufficient for a 4 TB SAP HANA database that typically requires at least 800 GB to 1 TB of memory for the data and working memory, and it is not listed as a certified SAP HANA instance type for production workloads. Option C (m5.24xlarge) is wrong because it is a general-purpose instance with only 384 GiB of memory, far below the memory requirements for a 4 TB HANA database, and it lacks the dedicated HANA certification. Option D (c5.18xlarge) is wrong because it is compute-optimized with only 144 GiB of memory, completely inadequate for SAP HANA's memory-intensive in-memory database operations, and it is not certified for SAP HANA.

Practice this question →
431
MCQhard

A company runs SAP Business Suite on AWS with a large SAP HANA database. They observe high memory utilization and need to scale up. Which instance type should they choose to provide the highest memory capacity for SAP HANA?

A.r5.24xlarge
B.u-12tb1.112xlarge
C.x1e.32xlarge
D.m5.24xlarge
AnswerB

u-12tb1.112xlarge offers 12 TB memory, designed for large SAP HANA.

Why this answer

The u-12tb1.112xlarge instance provides 12 TB of memory, which is the highest among the options. Option A is wrong because the x1e.32xlarge has 3.9 TB. Option B is wrong because the r5.24xlarge has 768 GB.

Option C is wrong because the m5.24xlarge has 384 GB.

Practice this question →
432
MCQhard

An SAP system on AWS is experiencing high latency for disk I/O. The system uses Amazon EBS gp2 volumes. The operations team notices that the volume queue depth is consistently high. Which change is most likely to reduce latency?

A.Increase the EC2 instance size to get more EBS bandwidth.
B.Migrate from gp2 to gp3 volumes and increase IOPS.
C.Configure RAID 0 across multiple EBS volumes.
D.Increase the block size of the file system.
AnswerB

gp3 provides higher baseline IOPS and consistent performance, reducing queue depth and latency.

Why this answer

The correct answer is B because gp3 volumes offer a baseline performance that is higher than gp2 for a given size, and they allow you to independently increase IOPS without needing to provision more storage. Since the volume queue depth is consistently high, the bottleneck is likely due to insufficient IOPS, and migrating to gp3 with increased IOPS directly addresses this by providing more I/O capacity, reducing latency.

Exam trap

The trap here is that candidates often assume increasing instance size (Option A) or using RAID 0 (Option C) will fix any performance issue, but the question specifically points to a high queue depth caused by IOPS limits, which is best addressed by migrating to a volume type that allows independent IOPS scaling.

How to eliminate wrong answers

Option A is wrong because increasing the EC2 instance size may provide more EBS bandwidth, but the queue depth issue is driven by IOPS limits of the gp2 volume, not by the instance's network bandwidth; the instance's EBS bandwidth is only a factor if it is saturated, which is not indicated here. Option C is wrong because configuring RAID 0 across multiple EBS volumes can increase throughput and IOPS, but it does not reduce latency for a single volume queue depth issue; it adds complexity and potential for increased latency due to striping overhead. Option D is wrong because increasing the block size of the file system can improve throughput for large sequential I/O, but it does not reduce latency for the high queue depth caused by insufficient IOPS; it may even increase latency for small random I/O.

Practice this question →
433
Matchingmedium

Match the SAP system component to its AWS service or concept.

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

Concepts
Matches

Amazon EC2 with HANA optimized instances

Application server layer

Next-generation ERP suite

Business intelligence platform

Why these pairings

These are core SAP components and their typical AWS deployment context.

Practice this question →
434
Multi-Selectmedium

A company is designing an SAP HANA database on AWS. The database requires high throughput and low latency for data volumes. Which TWO AWS features should be used to meet these requirements? (Choose two.)

Select 2 answers
A.Use EBS gp3 volumes for the HANA data volume.
B.Use EC2 instance store volumes for the HANA data volume.
C.Store HANA data on Amazon S3 with S3 Express One Zone.
D.Enable EBS optimization on the EC2 instance.
E.Use EBS io2 Block Express volumes for the HANA data volume.
AnswersD, E

EBS optimization provides dedicated network throughput for EBS traffic.

Why this answer

Option D is correct because enabling EBS optimization on an EC2 instance dedicates network bandwidth to EBS I/O, eliminating contention between network and storage traffic, which is critical for SAP HANA's high-throughput, low-latency requirements. Option E is correct because EBS io2 Block Express volumes provide up to 256,000 IOPS per volume with sub-millisecond latency, meeting the demanding performance needs of SAP HANA data volumes.

Exam trap

The trap here is that candidates often confuse 'high throughput' with 'high IOPS' and choose gp3 volumes (Option A) for their cost-effectiveness, failing to recognize that SAP HANA's performance requirements exceed gp3's maximum capabilities, while io2 Block Express is the only EBS volume type designed for such demanding workloads.

Practice this question →
435
MCQmedium

A company is planning to migrate its SAP S/4HANA system to AWS. The system requires high availability with an RTO of less than 30 minutes and RPO of less than 15 minutes. The SAP application layer runs on Linux. Which architecture should a solutions architect recommend to meet these requirements?

A.Deploy the SAP application on a single EC2 instance and use S3 for database backups with cross-region replication.
B.Deploy a single EC2 instance for the SAP application and database in one Availability Zone, and take hourly snapshots of the EBS volumes.
C.Use two EC2 instances in an Auto Scaling group with instance store volumes for the database, and store application files on S3.
D.Deploy the SAP application on two EC2 instances in different AZs with a shared EFS file system, and use a multi-AZ RDS for SAP HANA with synchronous replication.
AnswerD

Multi-AZ deployment with synchronous replication meets RPO; EFS provides shared storage for quick failover.

Why this answer

Option D is correct because it meets the RTO of <30 minutes and RPO of <15 minutes by deploying the SAP application on two EC2 instances across different Availability Zones with a shared EFS file system for stateless application files, and using a multi-AZ RDS for SAP HANA with synchronous replication. Synchronous replication ensures zero data loss (RPO=0) and automatic failover to the standby in a different AZ achieves RTO well under 30 minutes. The Linux SAP application layer is stateless, so EFS provides a shared, highly available file system that allows either instance to serve traffic seamlessly after a failover.

Exam trap

The trap here is that candidates often confuse high availability with disaster recovery, assuming that backups or snapshots (Options A and B) can meet low RPO/RTO targets, when in fact only synchronous replication with automatic failover (Option D) can achieve sub-15-minute RPO and sub-30-minute RTO for SAP HANA.

How to eliminate wrong answers

Option A is wrong because a single EC2 instance provides no high availability; if the instance or AZ fails, the RTO and RPO targets cannot be met, and S3 cross-region replication for backups does not provide automatic failover or synchronous replication. Option B is wrong because a single EC2 instance and single-AZ database with hourly EBS snapshots cannot achieve an RPO of less than 15 minutes (hourly snapshots mean up to 60 minutes of data loss) and provides no automatic failover for high availability. Option C is wrong because instance store volumes are ephemeral and data is lost if the instance stops or fails, making it impossible to meet the RPO requirement; Auto Scaling groups do not provide synchronous replication or automatic database failover, and instance stores are not suitable for persistent SAP HANA data.

Practice this question →
436
MCQmedium

An SAP administrator needs to implement a backup strategy for an SAP HANA database on AWS that provides point-in-time recovery (PITR) with minimal RPO. Which combination of AWS services should be used?

A.HANA backup to NFS on Amazon EFS
B.Amazon EBS snapshots of the HANA data volumes
C.Amazon S3 lifecycle policies
D.AWS Backup with Backint agent for SAP HANA
AnswerD

This provides integrated, automated backups with PITR capability.

Why this answer

AWS Backup with the Backint agent for SAP HANA is the correct choice because it integrates directly with SAP HANA's native backup interface (Backint), enabling log backups and full/differential backups to Amazon S3. This combination supports point-in-time recovery (PITR) with minimal RPO by continuously backing up transaction logs, which is essential for meeting strict recovery objectives.

Exam trap

AWS often tests the misconception that EBS snapshots alone provide application-consistent backups for SAP HANA, but they fail to capture transaction logs needed for PITR, leading candidates to incorrectly choose Option B.

How to eliminate wrong answers

Option A is wrong because backing up HANA to NFS on Amazon EFS does not support the Backint interface for log backups, making PITR with minimal RPO impractical due to lack of native log backup integration and potential performance issues. Option B is wrong because Amazon EBS snapshots of HANA data volumes are crash-consistent but not application-consistent; they cannot capture HANA transaction logs for PITR, and restoring from an EBS snapshot alone does not guarantee database consistency without additional log replay. Option C is wrong because Amazon S3 lifecycle policies manage object transitions and deletions, not backup creation; they are a storage management feature, not a backup service, and cannot initiate or orchestrate HANA backups.

Practice this question →
437
MCQeasy

A company is planning to run SAP HANA on AWS and needs to ensure that the database meets the required memory and CPU performance. Which instance family should the company choose for the SAP HANA database?

A.T3 instances
B.M5 instances
C.C5 instances
D.X1e instances
AnswerD

X1e instances are SAP HANA certified.

Why this answer

Option B is correct because SAP HANA is certified on X1, X1e, and newer high-memory instances like u-6tb1. Option A is wrong because M5 instances are general-purpose and not certified for SAP HANA. Option C is wrong because C5 instances are compute-optimized.

Option D is wrong because T3 instances are burstable and not suitable.

Practice this question →
438
MCQhard

A company runs a large SAP ERP system on AWS. The SAP application servers are deployed across multiple Availability Zones using an Auto Scaling group behind an Application Load Balancer. The SAP HANA database is a single-node instance on a large EC2 instance with EBS io1 volumes. The database experiences high write latency during peak hours. The administrator investigates and finds that the EBS volume write throughput is consistently at the maximum limit of 250 MB/s. The volume is 4 TB with 10,000 provisioned IOPS. The application servers are idle during the peak hour due to database slowness. The company needs a solution to reduce write latency without changing the application. Which solution should the administrator implement?

A.Enable EBS Multi-Attach and add additional EC2 instances to share the volume
B.Increase the provisioned IOPS on the io1 volume to 20,000
C.Enable EBS-optimized on the EC2 instance
D.Change the volume type to gp3 and increase throughput to 500 MB/s
AnswerB

Doubling IOPS doubles the throughput to 500 MB/s, which should reduce write latency.

Why this answer

Option C is correct because increasing the volume size increases the throughput limit (baseline throughput for io1 is 0.5 MB/s per GB, so 4 TB gives 2048 MB/s, but maximum throughput per volume is 500 MB/s; however, the current limit is 250 MB/s due to IOPS limit. Actually, io1 throughput = (provisioned IOPS) * (I/O size). At 10,000 IOPS and 256 KB I/O size, throughput is 250 MB/s.

Increasing IOPS to 20,000 would double throughput to 500 MB/s. Option A is wrong because gp3 has lower throughput per GB. Option B is wrong because EBS-optimized instances are already enabled.

Option D is wrong because enabling EBS Multi-Attach is not for single-node and adds complexity.

Practice this question →
439
MCQmedium

An SAP administrator is creating an IAM policy for the AWS SAP Landscape Management (LaMa) connector. The policy includes the actions shown. Which additional action is missing for LaMa to perform its typical automation tasks?

A.lambda:InvokeFunction
B.cloudformation:CreateStack and cloudformation:DeleteStack
C.rds:CreateDBInstance and rds:DeleteDBInstance
D.s3:PutObject and s3:GetObject
AnswerB

LaMa uses CloudFormation to provision infrastructure.

Why this answer

Option D is correct. LaMa often uses CloudFormation to create and manage stacks. The policy lacks CloudFormation actions.

Option A is wrong because S3 actions are not typically required. Option B is wrong because RDS is not used for SAP HANA. Option C is wrong because Lambda is not essential for LaMa automation.

Practice this question →
440
Multi-Selectmedium

Which TWO of the following are valid considerations when designing the network for SAP workloads on AWS? (Select TWO.)

Select 2 answers
A.Enable jumbo frames on the VPC for SAP application tier
B.Use a single subnet for all SAP tiers to simplify routing
C.Use a public subnet for the SAP database tier
D.Deploy SAP application servers in a cluster placement group
E.Disable VPC Flow Logs to save costs
AnswersA, D

Jumbo frames reduce overhead and improve throughput.

Why this answer

SAP systems require jumbo frames to improve network performance, and placement groups can reduce latency. NACLs are stateless and can be used for security, but the question asks for design considerations.

Practice this question →
441
MCQmedium

An SAP Basis administrator notices that the SAP application is running slowly during peak hours. The system is deployed on a single r5.8xlarge instance with 256 GiB of memory. CloudWatch metrics show high CPU utilization but moderate memory usage. Which action should the architect take to improve performance?

A.Increase the instance memory by selecting r5.12xlarge
B.Increase the size of the EBS root volume
C.Add Provisioned IOPS to the EBS volumes
D.Change the instance type to c5.9xlarge
AnswerD

c5.9xlarge provides more vCPUs (36) compared to r5.8xlarge (32) and is compute-optimized.

Why this answer

Switching to a compute-optimized instance like c5.9xlarge provides more CPU resources for the same memory footprint, addressing high CPU utilization. Option B is wrong because adding memory won't help if CPU is the bottleneck. Option C is wrong because increasing EBS volume size does not improve CPU.

Option D is wrong because Provisioned IOPS addresses disk performance, not CPU.

Practice this question →
442
MCQmedium

A company is running SAP Business Suite on AWS and wants to implement a disaster recovery (DR) strategy with a Recovery Time Objective (RTO) of less than 2 hours and a Recovery Point Objective (RPO) of less than 15 minutes. The primary and DR sites are in different AWS regions. Which solution meets these requirements?

A.Use SAP HANA System Replication in asynchronous mode across regions with EBS snapshots every 15 minutes
B.Use EBS snapshots replicated to the DR region with S3 cross-region replication
C.Use AWS Backup with continuous backups
D.Use SAP HANA System Replication in synchronous mode across regions
AnswerA

Asynchronous replication with frequent snapshots can meet RPO < 15 minutes and RTO < 2 hours.

Why this answer

SAP HANA System Replication with synchronous mode in the same region can achieve RPO < 15 minutes, but across regions asynchronous replication is needed. Option A is wrong because cross-region synchronous replication is not possible due to latency. Option B is wrong because EBS snapshots alone may not meet RPO.

Option C is wrong because S3 cross-region replication is for objects, not SAP data.

Practice this question →
443
MCQmedium

An SAP NetWeaver system on AWS needs to be highly available across two Availability Zones. Which AWS service should be used to manage the floating IP address used by the SAP application servers?

A.VPC Peering
B.AWS Global Accelerator
C.Elastic IP address
D.Amazon Route 53 with failover routing
AnswerD

Route 53 can route traffic to healthy endpoints in different AZs.

Why this answer

Amazon Route 53 with failover routing is the correct choice because it can manage a floating IP address by using DNS health checks to automatically route traffic to the healthy SAP application server in the active Availability Zone. When the primary server fails, Route 53 updates DNS resolution to point to the secondary server's IP, effectively providing a floating IP mechanism without requiring a static IP reassignment.

Exam trap

The trap here is that candidates often confuse Elastic IP addresses with floating IPs, not realizing that Elastic IPs require manual remapping and lack automatic health-based failover, whereas Route 53 failover routing provides the automated DNS-level failover needed for SAP high availability.

How to eliminate wrong answers

Option A is wrong because VPC Peering is a network connectivity service that connects two VPCs, not a mechanism to manage floating IP addresses for SAP application servers. Option B is wrong because AWS Global Accelerator uses anycast IP addresses and static IPs to route traffic to optimal endpoints, but it does not manage a floating IP address that moves between SAP application servers across Availability Zones; it is designed for global traffic optimization, not local HA failover. Option C is wrong because an Elastic IP address is a static public IPv4 address that can be remapped to another instance, but it is not suitable for managing a floating IP in a highly available SAP architecture across Availability Zones because it requires manual intervention or scripting to reassign, and it does not provide automatic health-based failover.

Practice this question →
444
Multi-Selectmedium

A company is migrating its SAP NetWeaver system to AWS and wants to implement a high-availability architecture for the SAP Central Services (ASCS) and Enqueue Replication Server (ERS). Which TWO of the following are required components in a recommended AWS HA setup for ASCS and ERS?

Select 2 answers
A.A shared file system (e.g., Amazon EFS) to store the SAP transport directory and global profile.
B.An Application Load Balancer to distribute traffic between ASCS and ERS instances.
C.A floating IP address (using Elastic IP or Route 53 health checks) to manage the ASCS virtual hostname.
D.A read replica of the SAP HANA database to offload application traffic.
E.A secondary Windows Server Failover Cluster in a different Availability Zone.
AnswersA, C

ASCS and ERS require shared storage for transport directory.

Why this answer

Option A is correct because in an SAP NetWeaver high-availability architecture on AWS, a shared file system such as Amazon EFS is required to store the SAP transport directory and global profile. This ensures that both the ASCS and ERS instances can access consistent configuration and transport files, which is essential for failover and cluster operations. Without a shared file system, the instances would have divergent configurations, breaking the HA setup.

Exam trap

The trap here is that candidates often confuse the need for a load balancer (Option B) with the floating IP mechanism, not realizing that SAP ASCS/ERS uses a virtual IP for active/passive failover rather than distributing traffic across multiple active instances.

Practice this question →
445
MCQeasy

A company is running SAP HANA on AWS. They want to ensure that the database is backed up automatically and the backups are stored securely and durably. Which AWS service should be used to store the backup files?

A.Amazon EBS Snapshots
B.Amazon RDS
C.Amazon Elastic File System
D.Amazon S3
AnswerD

S3 is ideal for storing backup files with high durability.

Why this answer

Amazon S3 is the correct service for storing SAP HANA backup files because it provides a highly durable (99.999999999% durability), scalable, and secure object storage platform. SAP HANA supports backing up directly to S3 using the Backint agent or via third-party backup tools, and S3 offers features like server-side encryption (SSE-S3 or SSE-KMS) and lifecycle policies for cost-effective long-term retention.

Exam trap

The trap here is that candidates may confuse Amazon EBS Snapshots (Option A) as the default backup mechanism for SAP HANA on AWS, but EBS Snapshots are not suitable for SAP HANA database-level backups because they capture the entire volume state and do not integrate with SAP HANA's backup catalog or support point-in-time recovery of the database itself.

How to eliminate wrong answers

Option A is wrong because Amazon EBS Snapshots are block-level backups tied to a specific Availability Zone and are not designed for direct SAP HANA database file backups; they capture entire volumes, not individual database files, and lack the granularity and portability needed for SAP HANA backup strategies. Option B is wrong because Amazon RDS is a managed relational database service, not a storage service for backup files; it cannot be used to store SAP HANA backup files as SAP HANA is not an RDS engine. Option C is wrong because Amazon Elastic File System (EFS) is a file-level NFS storage service that is not optimized for high-throughput backup workloads and does not provide the same durability, cost-efficiency, or direct integration with SAP HANA backup tools as S3.

Practice this question →
446
MCQmedium

An organization has a production SAP ERP system on AWS with a multi-node SAP HANA scale-out configuration. The system uses a cluster placement group for low latency. During a maintenance window, the administrator needs to stop and start all instances. After restart, the HANA nodes cannot communicate with each other. The cluster placement group is still intact, but the private IP addresses have changed. The HANA topology relies on hostnames resolved via /etc/hosts. What is the MOST likely cause and solution?

A.The private IP addresses changed, but /etc/hosts still has the old IPs. Update /etc/hosts with the new IPs or use Elastic IPs.
B.The EBS volumes were detached during stop. Reattach the volumes.
C.The security group rules were reset. Reapply the security group rules.
D.The cluster placement group was removed during stop/start. Recreate the placement group.
AnswerA

Stop/start can change private IPs; using Elastic IPs or updating /etc/hosts resolves this.

Why this answer

When EC2 instances in a cluster placement group are stopped and started, the private IP addresses can change unless they are configured with a primary Elastic Network Interface (ENI) or Elastic IP. Since the SAP HANA scale-out topology relies on hostnames resolved via /etc/hosts, the old IPs in that file become stale after the restart, breaking inter-node communication. Updating /etc/hosts with the new private IPs or assigning Elastic IPs to preserve the addresses resolves the issue.

Exam trap

The trap here is that candidates assume stopping and starting instances preserves all network configurations, but AWS explicitly changes private IPs by default unless Elastic IPs or static ENIs are used, which is a key nuance for SAP HANA multi-node setups.

How to eliminate wrong answers

Option B is wrong because stopping and starting an EC2 instance does not detach EBS volumes; volumes persist and are reattached automatically on start. Option C is wrong because security group rules are not reset during a stop/start cycle; they remain intact as they are associated with the ENI, not the instance state. Option D is wrong because a cluster placement group is not removed when instances are stopped and started; it persists as a logical grouping and only enforces placement during launch.

Practice this question →
447
MCQmedium

An SAP system on AWS experiences intermittent performance issues. CloudWatch metrics show high CPU credit usage on the t3.large EC2 instance hosting the SAP application. The instance is configured as a 'standard' placement group. What is the MOST likely cause and recommended action?

A.The instance size is too small. Move to a larger t3 instance.
B.The burstable instance is exhausting its CPU credits. Change to a non-burstable instance.
C.The placement group is causing network bottlenecks. Move to a cluster placement group.
D.The EBS volume is not provisioned with enough IOPS. Increase the volume size.
AnswerB

T3 instances use CPU credits; sustained high usage depletes them, causing throttling.

Why this answer

The t3.large is a burstable instance that earns CPU credits when idle and spends them when active. SAP applications often have sustained CPU demands that can exhaust the credit balance, causing performance throttling. Switching to a non-burstable instance (e.g., m5.large) provides consistent baseline CPU performance without credit-based limitations.

Exam trap

The trap here is that candidates may assume a larger burstable instance (Option A) solves the problem, but the PAS-C01 exam tests understanding that burstable instances are fundamentally inappropriate for sustained SAP workloads, regardless of size.

How to eliminate wrong answers

Option A is wrong because simply moving to a larger t3 instance (e.g., t3.xlarge) still uses CPU credits and can still exhaust them under sustained load; the root cause is the burstable nature, not the size. Option C is wrong because a standard placement group does not cause network bottlenecks; cluster placement groups offer lower latency but do not address CPU credit exhaustion. Option D is wrong because the issue is high CPU credit usage, not EBS IOPS; CloudWatch metrics for CPU credits are unrelated to EBS volume performance.

Practice this question →
448
MCQhard

An SAP system on AWS experiences intermittent connectivity issues between the SAP Central Services (SCS) instance and the application servers. The SCS instance is in a private subnet in us-east-1a, and the application servers are spread across us-east-1a and us-east-1b. Security groups allow traffic on all required ports. What is the MOST likely cause of the intermittent connectivity?

A.The route tables do not have a route for the SCS subnet.
B.The network ACLs are blocking the traffic.
C.The Internet Gateway is misconfigured.
D.The VPC peering connection is not established correctly.
AnswerB

Network ACLs are stateless and can cause intermittent issues if inbound rules allow but outbound rules deny return traffic.

Why this answer

Network ACLs are stateless and must explicitly allow both inbound and outbound traffic on ephemeral ports. If the outbound rules for the SCS subnet's NACL do not allow return traffic on high ports (e.g., 1024–65535), or if the application servers' subnet NACL blocks inbound traffic from the SCS instance, connections will intermittently fail. Security groups are stateful and automatically allow return traffic, but NACLs are not, making them the likely culprit for intermittent connectivity across different Availability Zones.

Exam trap

The trap here is that candidates assume security groups are the only firewall layer and forget that network ACLs are stateless and require explicit rules for return traffic, especially when instances span multiple Availability Zones where subnet-level ACLs differ.

How to eliminate wrong answers

Option A is wrong because route tables control traffic flow between subnets and the internet, but the SCS and application servers are in the same VPC; as long as the local route (10.0.0.0/16) exists, which it does by default, no additional route is needed for intra-VPC communication. Option C is wrong because the Internet Gateway is only involved in traffic destined for the internet; the SCS instance is in a private subnet and does not use an IGW for internal VPC traffic. Option D is wrong because VPC peering is used for communication between different VPCs; all instances in this scenario are within the same VPC, so no peering connection is involved.

Practice this question →
449
MCQhard

A company runs SAP Business Suite on AWS. They plan to use the SAP Landscape Management (LaMa) connector to automate system copy and relocation. What is a prerequisite for using the AWS LaMa connector?

A.An EC2 Auto Scaling group configured for the SAP application tier
B.AWS Systems Manager managed instances for all SAP servers
C.An IAM role with permissions for EC2, EBS, and CloudFormation actions
D.SSH keys for all SAP instances to allow LaMa to connect
AnswerC

LaMa needs IAM permissions to provision EC2, attach EBS, and use CloudFormation for automation.

Why this answer

Option C is correct. The AWS LaMa connector requires an IAM role with specific permissions for LaMa to manage EC2 instances and storage. Option A is wrong because LaMa does not require EC2 Auto Scaling.

Option B is wrong because LaMa uses AWS APIs, not SSH keys. Option D is wrong because LaMa does not use AWS Systems Manager for this purpose.

Practice this question →
450
MCQmedium

An SAP administrator is migrating an SAP Business Suite system from on-premises to AWS. The system uses an Oracle database that is 2 TB in size. The bandwidth between the on-premises data center and AWS is limited to 100 Mbps. The migration must be completed within a weekend (48 hours). The administrator decides to use AWS DMS for ongoing replication after an initial full load. However, the initial full load takes too long. What should the administrator do to accelerate the initial full load?

A.Disable encryption on the database backup to reduce transfer overhead.
B.Increase the size of the DMS replication instance to the largest available.
C.Use Amazon S3 Transfer Acceleration to speed up the upload.
D.Use AWS Snowball Edge to physically transfer the database backup to AWS, then restore and use DMS for ongoing replication.
AnswerD

Snowball bypasses network limitations.

Why this answer

Option A is correct because using AWS Snowball Edge to transfer the database backup to AWS bypasses the network bottleneck. Option B is wrong because increasing instance size does not improve network speed. Option C is wrong because disabling encryption does not significantly speed up transfer.

Option D is wrong because S3 Transfer Acceleration improves speed but may still be limited by 100 Mbps.

Practice this question →
← PreviousPage 6 of 7 · 462 questions totalNext →

Ready to test yourself?

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

Start 20-question session