Knowledge + Practice

AWS Certified SAP on AWS Specialty PAS-C01 (PAS-C01) — Questions 1501–1575

1616 questions total · 22pages · All types, answers revealed

Take a mock exam Exam hub

Page 21 of 22

1501

MCQmedium

A company is running SAP on AWS and wants to automate the installation of SAP applications using infrastructure as code. Which AWS service should be used to define the infrastructure?

A.AWS OpsWorks

B.AWS CodeDeploy

C.AWS Elastic Beanstalk

D.AWS CloudFormation

AnswerD

CloudFormation allows you to define AWS infrastructure as code.

Why this answer

AWS CloudFormation allows defining infrastructure as code. Option A is wrong because OpsWorks is for Chef/Puppet. Option B is wrong because CodeDeploy is for application deployment, not infrastructure.

Option C is wrong because Elastic Beanstalk is for web applications, not infrastructure.

Full explanation →

1502

MCQhard

An SAP system on AWS is experiencing slow performance. The SAP team suspects that the Amazon EBS volumes used for the database are not providing sufficient IOPS. Which step should be taken to identify the bottleneck?

A.Monitor the EBS volume metrics in CloudWatch

B.Use AWS Trusted Advisor to check performance

C.Enable VPC Flow Logs to analyze network traffic

D.Review the AWS Config rules for EBS

AnswerA

CloudWatch metrics like VolumeQueueLength indicate IOPS saturation.

Why this answer

Amazon CloudWatch provides detailed metrics for EBS volumes, including `VolumeReadOps`, `VolumeWriteOps`, `VolumeQueueLength`, and `VolumeThroughputPercentage`. By monitoring these metrics, you can directly determine whether the EBS volume is reaching its provisioned IOPS limit or experiencing queue buildup, which would confirm an IOPS bottleneck. This is the most direct and actionable step to diagnose insufficient IOPS for the SAP database.

Exam trap

The trap here is that candidates may confuse high-level advisory tools (Trusted Advisor) or network-focused logs (VPC Flow Logs) with the precise storage performance metrics needed to diagnose an IOPS bottleneck, overlooking CloudWatch as the definitive source for EBS performance data.

How to eliminate wrong answers

Option B is wrong because AWS Trusted Advisor provides high-level best-practice checks (e.g., idle resources, security groups) but does not offer real-time, granular EBS performance metrics like IOPS or queue depth; it cannot pinpoint an IOPS bottleneck. Option C is wrong because VPC Flow Logs capture network traffic metadata (IP addresses, ports, packet counts) but do not measure EBS volume IOPS or latency; they are irrelevant for storage-level performance issues. Option D is wrong because AWS Config rules evaluate resource compliance against desired configurations (e.g., encryption, tagging) and do not monitor runtime performance metrics such as IOPS or throughput.

Full explanation →

1503

Multi-Selecteasy

A company is planning to migrate an SAP HANA database to AWS. Which THREE factors should the company consider when selecting an EC2 instance type for the SAP HANA database?

Select 3 answers

A.The instance type must support burstable performance

B.The instance must be EBS-optimized

C.The instance must be based on the AWS Nitro System

D.The instance type must be memory-optimized (e.g., r5, r6i, x1e)

E.The instance type must be listed in the SAP Certified Instance Types for SAP HANA

AnswersB, D, E

Correct. EBS-optimized instances are required for dedicated EBS bandwidth to ensure consistent I/O performance for HANA data volumes.

Why this answer

For SAP HANA on AWS, EC2 instance types must be memory-optimized (e.g., r5, r6i, x1e) and listed in the SAP Certified Instance Types for SAP HANA. Additionally, instances must be EBS-optimized to provide dedicated bandwidth to EBS volumes. Burstable performance (option A) is not suitable for SAP HANA's consistent performance requirements.

While the Nitro System (option C) is recommended, it is not a strict requirement.

Exam trap

Avoid choosing 'burstable performance' or 'Nitro System' as strict requirements. The key mandatory factors are EBS-optimized, memory-optimized, and SAP-certified.

Full explanation →

1504

MCQeasy

A company is migrating a SAP system to AWS and wants to use the same SAP system ID (SID) as on-premises. What is a prerequisite for this migration?

A.The SID must be changed to a new value for the migration.

B.The SID must be at least 5 characters long.

C.The SID must be registered with AWS.

D.The SID must be unique within the AWS account and region.

AnswerD

Duplicate SIDs are not allowed.

Why this answer

SAP requires that the System ID (SID) be unique within an AWS account and region to avoid conflicts with existing SAP systems. During migration, the same SID can be reused as long as no other SAP system with that SID exists in the same account and region, ensuring proper system identification and integration with AWS services like Amazon EFS or Amazon FSx for SAP.

Exam trap

The trap here is that candidates may assume the SID must be changed or registered with AWS, but the actual prerequisite is uniqueness within the AWS account and region, not a global or external registration.

How to eliminate wrong answers

Option A is wrong because the SID does not need to be changed; it can remain the same as on-premises, provided it is unique in the target AWS account and region. Option B is wrong because SAP SIDs are always exactly 3 characters long, not at least 5; this is a fixed length defined by SAP standards. Option C is wrong because there is no requirement to register the SID with AWS; AWS does not maintain a registry of SAP SIDs, and the uniqueness constraint is managed within the customer's account.

Full explanation →

1505

MCQhard

Refer to the exhibit. An IAM policy is attached to an IAM role used by an SAP automation script. The script is failing to start an EC2 instance. What is the most likely cause?

A.The policy does not grant permission to start instances.

B.The policy does not allow ec2:DescribeInstances.

C.The script does not have access to the S3 bucket.

D.The script is not using HTTPS, so the Deny statement blocks all actions.

AnswerD

The Deny statement with aws:SecureTransport: false blocks all actions if not using HTTPS.

Why this answer

The Deny statement in the policy blocks all actions unless the request uses HTTPS. Since the SAP automation script is failing to start an EC2 instance, the most likely cause is that the script is making HTTP requests instead of HTTPS, triggering the Deny and preventing any action, including ec2:StartInstances. This is a common security control to enforce encryption in transit.

Exam trap

AWS often tests the nuance that a Deny statement with a condition (like aws:SecureTransport) can override all Allow statements, leading candidates to overlook the condition and incorrectly focus on missing permissions.

How to eliminate wrong answers

Option A is wrong because the policy includes an Allow for ec2:StartInstances, so permission to start instances is explicitly granted. Option B is wrong because ec2:DescribeInstances is not required to start an instance; the failure is due to the Deny statement, not a missing Describe permission. Option C is wrong because the policy does not reference any S3 bucket, and the script's failure to start an EC2 instance is unrelated to S3 access.

Full explanation →

1506

MCQeasy

A company is migrating its SAP BusinessObjects to AWS. They want to use a managed service to reduce operational overhead. Which AWS service is most suitable?

A.Amazon QuickSight

B.Amazon EMR

C.Amazon Redshift

D.Amazon RDS

AnswerA

Amazon QuickSight is a managed BI service suitable for replacing SAP BusinessObjects.

Why this answer

Amazon QuickSight is a fully managed business analytics service that can replace SAP BusinessObjects for reporting and dashboards, reducing operational overhead. Option A (QuickSight) is correct. Option B (EMR) is for big data processing.

Option C (Redshift) is a data warehouse. Option D (RDS) is a relational database service.

Full explanation →

1507

MCQmedium

A company is using this CloudFormation template to provision infrastructure for an SAP HANA migration. When the stack is created, the RDS instance fails to launch. What is the most likely reason?

A.The InstanceType parameter is not properly referenced.

B.The DBInstanceClass db.x1e.2xlarge is not valid.

C.The AMI ID is invalid.

D.Amazon RDS does not support the SAP HANA engine.

AnswerD

SAP HANA is not available as an RDS engine; it must be deployed on EC2.

Why this answer

Amazon RDS does not support SAP HANA as a database engine. SAP HANA must be installed on EC2 instances or on bare metal. Option A is incorrect because the template references the InstanceType parameter correctly using the Ref function.

Option B is incorrect because while db.x1e.2xlarge is a valid RDS instance class for some engines (e.g., SQL Server), it is not valid for a non-existent RDS engine; but the primary issue is that SAP HANA is not supported on RDS at all. Option C is incorrect because the AMI ID is not relevant; RDS does not use AMIs; the stack would fail before checking AMI.

Full explanation →

1508

MCQeasy

A company wants to ensure that its SAP systems on AWS are compliant with internal security policies. Which AWS service can be used to continuously monitor and evaluate resource configurations?

A.Amazon Inspector

B.AWS Config

C.AWS CloudTrail

D.Amazon GuardDuty

AnswerB

Config evaluates resource configurations against rules.

Why this answer

AWS Config is the correct service because it continuously monitors and evaluates the configurations of AWS resources against desired policies, such as internal security policies for SAP systems. It provides detailed configuration snapshots, compliance history, and automated remediation via AWS Config Rules, which can be custom or managed, to ensure ongoing compliance.

Exam trap

The trap here is that candidates often confuse AWS Config with AWS CloudTrail, thinking both are for auditing, but CloudTrail tracks who did what and when (API activity), while Config tracks what the resource looks like (configuration state) over time.

How to eliminate wrong answers

Option A is wrong because Amazon Inspector is a vulnerability management service that scans for software vulnerabilities and unintended network exposure, not for evaluating resource configurations against internal policies. Option C is wrong because AWS CloudTrail records API activity and provides audit logs of actions taken on AWS resources, but it does not monitor or evaluate the state or configuration of those resources over time. Option D is wrong because Amazon GuardDuty is a threat detection service that analyzes continuous streams of metadata (e.g., DNS logs, VPC Flow Logs) for malicious activity, not for configuration compliance assessment.

Full explanation →

1509

MCQmedium

A company is migrating SAP applications to AWS and needs to replicate data from on-premises Active Directory to AWS Managed Microsoft AD for authentication. Which AWS service should be used?

A.AWS Transit Gateway

B.AWS Directory Service for Microsoft Active Directory

C.AWS Resource Access Manager (RAM)

D.AWS AD Connector

AnswerB

AWS Directory Service for Microsoft Active Directory is a managed service that can be set up with a trust relationship to on-premises AD, allowing replication of directory objects, meeting the requirement.

Why this answer

AWS Directory Service for Microsoft Active Directory is the correct service because it provides a managed Active Directory in AWS that can be configured with a forest trust to on-premises Active Directory, enabling replication of directory data. This allows authentication using on-premises credentials in AWS. Option A (AWS Transit Gateway) is for network connectivity, not directory replication.

Option C (AWS Resource Access Manager) is used for sharing resources across accounts. Option D (AWS AD Connector) only proxies authentication requests and does not replicate data. Therefore, the best answer is AWS Directory Service for Microsoft Active Directory.

Full explanation →

1510

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 is the correct choice because it is part of AWS's bare metal 'u' instance family, specifically designed for large in-memory databases like SAP HANA, offering up to 12 TB of RAM. This instance type provides the highest memory capacity among AWS instances, making it suitable for scaling up SAP HANA when high memory utilization is observed.

Exam trap

The trap here is that candidates might choose x1e.32xlarge (3,904 GB) thinking it offers the highest memory, but the u-12tb1.112xlarge provides significantly more RAM (12 TB) and is specifically designed for large SAP HANA workloads.

How to eliminate wrong answers

Option A (r5.24xlarge) is wrong because it provides only 768 GB of RAM, which is insufficient for a large SAP HANA database requiring high memory capacity. Option C (x1e.32xlarge) is wrong because it offers 3,904 GB of RAM, which is less than the 12 TB provided by the u-12tb1.112xlarge and is not the highest memory capacity available. Option D (m5.24xlarge) is wrong because it provides only 384 GB of RAM, which is far too low for scaling up a large SAP HANA database and is optimized for general-purpose workloads, not memory-intensive databases.

Full explanation →

1511

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

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.

Full explanation →

1512

MCQhard

An administrator is migrating an on-premises application to AWS. The application stores persistent data on a separate disk. The administrator launched an EC2 instance as a test and attached an additional EBS volume for the persistent data. The above exhibit shows the block device mapping for the test instance. Later, the administrator terminates the test instance, but the persistent data must be retained. However, after termination, the persistent data volume is also deleted. What is the most likely cause?

A.The instance was stopped instead of terminated, and the persistent data volume was detached during the stop.

B.The persistent data volume (vol-0f1e2d3c4b5a67890) had DeleteOnTermination set to false, but the administrator inadvertently changed it before termination.

C.The administrator mistakenly stored the persistent data on the root volume (vol-0a1b2c3d4e5f67890), which has DeleteOnTermination set to true.

D.The persistent data volume was not properly attached to the instance before termination.

AnswerC

If the persistent data was on the root volume, it would be deleted when the instance is terminated because DeleteOnTermination is true.

Why this answer

The exhibit shows the root volume (vol-0a1b2c3d4e5f67890) as the only volume with DeleteOnTermination set to true. The administrator intended to store persistent data on a separate EBS volume, but the data was actually stored on the root volume. When the instance was terminated, the root volume was deleted due to its DeleteOnTermination flag being true, causing the loss of the persistent data.

Exam trap

The trap here is that candidates may assume the persistent data volume is the one with a different volume ID (vol-0f1e2d3c4b5a67890) and overlook the possibility that the data was actually stored on the root volume, which has DeleteOnTermination set to true by default.

How to eliminate wrong answers

Option A is wrong because stopping an instance does not delete any attached EBS volumes; it only halts the instance, and volumes remain attached unless explicitly detached. Option B is wrong because if the persistent data volume (vol-0f1e2d3c4b5a67890) had DeleteOnTermination set to false, it would not be deleted upon termination; changing it to true would require a deliberate action, and the question states the administrator did not intend to delete it. Option D is wrong because if the volume was not properly attached, the instance would not have been able to access the persistent data during the test, and the volume would not have been deleted upon termination—it would simply remain unattached.

Full explanation →

1513

MCQmedium

An SAP system running on AWS is experiencing high latency for database writes. The database is running on an RDS instance with General Purpose (gp2) storage. What change will PROVIDE the most immediate performance improvement?

A.Change the storage type to Provisioned IOPS (io1 or io2).

B.Add a read replica to offload read traffic.

C.Increase the allocated storage size to increase baseline IOPS.

D.Enable Multi-AZ deployment.

AnswerA

Provides consistent low latency for writes.

Why this answer

The SAP system is experiencing high latency for database writes, which is a latency-sensitive workload. General Purpose (gp2) storage provides a baseline of 3 IOPS per GB, but its burst model can lead to performance degradation under sustained high write loads. Changing to Provisioned IOPS (io1 or io2) guarantees consistent, low-latency I/O performance by allowing you to provision a specific number of IOPS independently of storage size, providing the most immediate performance improvement for write-heavy operations.

Exam trap

The trap here is that candidates often assume increasing storage size (Option C) will immediately boost IOPS, but they overlook the gp2 burst credit mechanism and the fact that Provisioned IOPS provides a guaranteed, immediate performance floor without relying on credits or size-dependent baselines.

How to eliminate wrong answers

Option B is wrong because adding a read replica offloads read traffic, but it does not improve write latency on the primary database instance; writes still go to the primary, and the replica does not affect write performance. Option C is wrong because increasing allocated storage size on gp2 increases baseline IOPS (3 IOPS per GB), but this is a gradual improvement and may not provide immediate relief for high latency, especially if the current burst balance is depleted; it also does not guarantee consistent performance for write-heavy SAP workloads. Option D is wrong because enabling Multi-AZ deployment provides high availability and automatic failover, but it does not improve write latency; in fact, synchronous replication to a standby instance can slightly increase write latency due to the additional replication overhead.

Full explanation →

1514

Drag & Dropmedium

Drag and drop the steps to automate the installation of SAP HANA on AWS using AWS CloudFormation into the correct order.

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

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

Why this order

CloudFormation automation involves template creation, upload, stack launch, provisioning, and verification.

Full explanation →

1515

MCQeasy

A company wants to ensure that its SAP system backups are stored in a different AWS Region to comply with disaster recovery requirements. Which AWS service should be used to copy EBS snapshots to another Region?

A.AWS Backup

B.Amazon Data Lifecycle Manager

C.Amazon S3 Cross-Region Replication

D.AWS CloudFormation StackSets

AnswerA

AWS Backup can copy backups across Regions.

Why this answer

AWS Backup is the correct answer because it provides a centralized backup service that can copy EBS snapshots across AWS Regions as part of backup plans. Amazon Data Lifecycle Manager (DLM) can automate snapshot creation and retention, but its cross-Region copy capabilities are limited compared to AWS Backup's comprehensive backup policies. Option C, S3 Cross-Region Replication, applies to S3 objects, not EBS snapshots.

Option D, CloudFormation StackSets, is used for infrastructure provisioning across accounts/regions, not for backup.

Full explanation →

1516

MCQeasy

A company is planning to run SAP S/4HANA on AWS and needs to ensure that the SAP system is backed up according to best practices. Which backup strategy is recommended?

A.Use EBS snapshots after quiescing the SAP system, combined with database backups to S3.

B.Use EBS snapshots of the data volumes without quiescing the application.

C.Store backup files on instance store volumes for quick recovery.

D.Use AWS Backup to take snapshots of the EC2 instance only.

AnswerA

Application-consistent snapshots plus database backups to S3 follow AWS best practices.

Why this answer

For SAP S/4HANA on AWS, the recommended backup strategy combines EBS snapshots taken after quiescing the SAP system (to ensure file system consistency) with database backups to Amazon S3. Quiescing the application ensures that all pending I/O operations are flushed and the file system is in a consistent state, preventing data corruption. Database backups to S3 provide a separate, application-consistent recovery point that can be used for point-in-time recovery, which is critical for SAP systems.

Exam trap

The trap here is that candidates may assume EBS snapshots alone are sufficient for SAP backups, overlooking the need for application quiescing and separate database backups to ensure both file system and database consistency.

How to eliminate wrong answers

Option B is wrong because taking EBS snapshots without quiescing the application risks creating an inconsistent file system state, which can lead to data corruption or an unrecoverable SAP system. Option C is wrong because instance store volumes are ephemeral and provide no data durability; they cannot be used for reliable backups as data is lost if the instance stops or fails. Option D is wrong because AWS Backup snapshots of only the EC2 instance do not capture the database state or ensure application consistency, and they lack the granularity needed for SAP database recovery.

Full explanation →

1517

Multi-Selecthard

A company is migrating a 10 TB SQL Server database to Amazon RDS for SQL Server using AWS DMS. The migration is taking longer than expected. Which TWO actions can improve the migration speed? (Choose two.)

Select 2 answers

A.Use a single DMS task with full LOB mode

B.Enable parallel loading by splitting tables into multiple tasks

C.Use S3 multipart upload for the data

D.Increase the DMS replication instance size

E.Disable transaction logging on the source

AnswersB, D

Parallel tasks utilize more resources and speed up data transfer.

Why this answer

Splitting tables into multiple DMS tasks enables parallel loading, which significantly reduces migration time by processing multiple tables concurrently. Option D is correct because increasing the DMS replication instance size provides more CPU and memory resources, allowing the instance to handle larger data volumes and higher throughput more efficiently.

Exam trap

The trap here is that candidates may think full LOB mode or disabling transaction logs speeds up migration, but these actions either add overhead or break DMS's ability to capture changes, while the correct answers focus on parallelism and resource scaling.

Full explanation →

1518

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

SAP HANA, NetWeaver, S/4HANA, and BusinessObjects are core SAP components. HANA runs on EC2 with certified instances; NetWeaver and BusinessObjects also run on EC2; S/4HANA requires HANA. Common confusions: Amazon RDS does not support HANA, and NetWeaver is not a database.

Full explanation →

1519

Multi-Selecthard

A company is migrating an SAP system from on-premises to AWS. The current system uses a dual-stack (IPv4 and IPv6) network. The company wants to ensure that the SAP system on AWS supports both IP versions. Which THREE actions should the company take? (Choose 3.)

Select 3 answers

A.Update security group rules to allow both IPv4 and IPv6 traffic

B.Assign both IPv4 and IPv6 addresses to the EC2 instances

C.Create an Egress-Only Internet Gateway

D.Configure the VPC to support dual-stack mode

E.Set up a NAT Gateway for IPv6 traffic

AnswersA, B, D

Correct: Security group rules must allow both IPv4 and IPv6 traffic for dual-stack support.

Why this answer

To support dual-stack (IPv4 and IPv6) on AWS, the VPC must be configured for dual-stack, EC2 instances must have both IPv4 and IPv6 addresses assigned, and security group rules must allow both IPv4 and IPv6 traffic. Option A (Update security group rules to allow both IPv4 and IPv6 traffic) is correct. Option B (Assign both IPv4 and IPv6 addresses to the EC2 instances) is correct.

Option D (Configure the VPC to support dual-stack mode) is correct. Option C (Create an Egress-Only Internet Gateway) is not required for dual-stack support; it's used for outbound-only IPv6 traffic. Option E (Set up a NAT Gateway for IPv6 traffic) is incorrect because NAT Gateways are for IPv4, not IPv6.

Full explanation →

1520

MCQhard

A company is using SAP Landscape Management (LaMa) to automate the provisioning and decommissioning of SAP application servers in an AWS environment. The SAP systems are deployed on EC2 instances using Amazon EBS volumes. The operations team has observed that when LaMa triggers a scale-in operation to remove an application server, the instance is terminated, but the associated EBS volumes (including the root volume) are not deleted, resulting in orphaned volumes and increasing storage costs. The team wants to ensure that EBS volumes are automatically deleted when an instance is terminated, especially during LaMa-driven operations. Which solution should the team implement?

A.Configure an Amazon Data Lifecycle Manager (DLM) policy to delete volumes that are not attached to a running instance.

B.Set the 'Delete on Termination' attribute to 'True' on all EBS volumes attached to the instance when it is launched by LaMa.

C.Create an AWS Lambda function that is triggered by EC2 instance termination events to delete unattached EBS volumes.

D.Use AWS CloudTrail to monitor TerminateInstances events and trigger an AWS Step Function workflow to delete the volumes.

AnswerB

With DeleteOnTermination enabled, when LaMa terminates the instance, the volumes are automatically deleted, preventing orphaned volumes.

Why this answer

The correct solution is to set the 'Delete on Termination' attribute to 'True' on all EBS volumes attached to the instance when it is launched by LaMa. This ensures that when the instance is terminated (e.g., during a LaMa scale-in operation), the EBS volumes are automatically deleted, preventing orphaned volumes. Option A is incorrect because Amazon Data Lifecycle Manager (DLM) is used for managing snapshot schedules, not for immediate deletion on termination.

Option C is incorrect because while a Lambda function could delete volumes after termination, it adds complexity and may have timing issues; the simpler and more reliable method is to set the flag at launch. Option D is incorrect because CloudTrail logs API calls but does not directly perform actions; setting up Step Functions for this purpose is overly complex compared to the native 'Delete on Termination' attribute.

Full explanation →

1521

MCQeasy

An SAP system administrator needs to automate the patching of Amazon RDS for SAP ASE databases. Which AWS service can be used to schedule and apply database patches automatically?

A.AWS OpsWorks

B.Amazon RDS maintenance window

C.AWS Systems Manager Maintenance Windows

D.AWS Systems Manager Patch Manager

AnswerB

Amazon RDS maintenance window is the correct feature because it allows you to define a schedule for automatic patching of RDS databases.

Why this answer

Amazon RDS maintenance window is a built-in feature that allows you to schedule automatic patching for RDS databases, including SAP ASE. It is the appropriate mechanism for automating patching. Options A (AWS OpsWorks) is for configuration management.

Option C (AWS Systems Manager Maintenance Windows) can orchestrate tasks but cannot directly apply RDS patches; RDS manages patching internally. Option D (AWS Systems Manager Patch Manager) is designed for EC2 instances, not RDS.

Full explanation →

1522

Multi-Selectmedium

A company is designing a disaster recovery plan for a critical application running on EC2 instances in an Auto Scaling group behind an Application Load Balancer (ALB). The application uses an RDS Multi-AZ database. Which TWO actions should the operations team take to minimize recovery time and data loss?

Select 2 answers

A.Configure automated EBS snapshots for EC2 instances and copy them to a secondary region.

B.Enable cross-region read replicas for the RDS database and promote to master if needed.

C.Create an AMI from a running instance and share it with the secondary region.

D.Use Route53 health checks to automatically failover traffic to a standby environment.

AnswersA, B

Snapshots can be used to restore volumes in another region.

Why this answer

Automated EBS snapshots, when copied to a secondary region, provide a mechanism to restore EC2 instances and their data in the event of a regional failure. This minimizes recovery time by having the snapshots available in the DR region, and minimizes data loss by ensuring point-in-time backups are replicated off-site. The snapshots can be used to launch new instances or create AMIs in the secondary region, supporting the recovery of the Auto Scaling group.

Exam trap

The trap here is that candidates may assume creating an AMI from a running instance (Option C) is sufficient for DR, but they overlook that it does not provide ongoing incremental replication, leading to significant data loss compared to automated EBS snapshots copied to a secondary region.

Full explanation →

1523

MCQhard

A company is migrating a 5 TB Oracle data warehouse to Amazon Redshift. They need to minimize downtime and ensure data consistency. Which migration approach should they use?

A.Export data using Oracle UNLOAD and COPY into Redshift

B.Use AWS DMS with ongoing replication and perform a cutover

C.Stream data using Amazon Kinesis and then load into Redshift

D.Use AWS SCT to convert schema and then manually copy data

AnswerB

DMS can replicate continuously and then apply final changes.

Why this answer

Using AWS DMS with ongoing replication and performing a cutover ensures data consistency and minimizes downtime during the migration. DMS replicates changes in real-time, allowing a final cutover with zero data loss. Option A (Oracle UNLOAD and COPY) requires significant downtime for export/import.

Option C (Amazon Kinesis) is for streaming, not bulk migration. Option D (AWS SCT for schema conversion) only handles schema, not data transfer.

Full explanation →

1524

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

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.

Full explanation →

1525

MCQmedium

A company is planning to migrate its SAP ERP system from an on-premises data center to AWS. The system uses SAP HANA as the database. The current on-premises HANA database size is 1 TB. The company wants to minimize downtime during the migration. The network connection between on-premises and AWS has a bandwidth of 1 Gbps. The company has already set up a Direct Connect connection. They plan to use SAP HANA system replication to replicate the database to an EC2 instance in AWS. However, the initial data transfer will take too long due to the large dataset. What should they do to reduce the initial replication time?

A.Order an additional Direct Connect circuit to increase bandwidth.

B.Enable compression on the HANA system replication.

C.Set up a VPN connection over the internet for faster transfer.

D.Use AWS Snowball Edge to physically transfer the initial HANA backup.

AnswerD

Snowball provides high-speed physical transfer.

Why this answer

Using AWS Snowball Edge to physically transfer the initial HANA backup is much faster than transferring over the network, even with Direct Connect. Option A is wrong because ordering an additional Direct Connect circuit is costly and does not address the time limitation of the 1 Gbps link. Option B is wrong because enabling compression on HANA system replication may help but is still constrained by the available bandwidth.

Option C is wrong because setting up a VPN over the internet is typically slower and less reliable than the existing Direct Connect connection.

Full explanation →

1526

MCQeasy

A company is migrating its on-premises Oracle database to Amazon RDS for Oracle. They need to minimize downtime and ensure data consistency. Which AWS service should they use for the initial data load and ongoing replication?

A.AWS Snowball Edge

B.AWS Database Migration Service (DMS)

C.AWS DataSync

D.AWS Schema Conversion Tool (SCT)

AnswerB

Correct because DMS can perform full load and ongoing replication (CDC) to minimize downtime.

Why this answer

**Option A (AWS Snowball Edge):** Incorrect because Snowball Edge is designed for offline data transfer, not for ongoing replication with minimal downtime. It could be used for initial data load but does not support continuous replication.

**Option B (AWS DMS):** Correct. AWS Database Migration Service can perform a full load of the source Oracle database to Amazon RDS for Oracle and then continuously replicate changes using Change Data Capture (CDC) to minimize downtime and ensure consistency.

**Option C (AWS DataSync):** Incorrect because DataSync is used for file-based data transfers (e.g., NFS/SMB shares), not for database replication.

**Option D (AWS SCT):** Incorrect because the Schema Conversion Tool only converts database schemas and code; it does not handle data migration or replication.

Full explanation →

1527

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.

Full explanation →

1528

MCQhard

An SAP system is deployed across multiple Availability Zones using an Application Load Balancer (ALB) for the SAP Web Dispatcher. Users report that sessions are frequently dropped during peak hours. Which configuration change should resolve this?

A.Disable cross-zone load balancing on the ALB.

B.Increase the number of Web Dispatcher instances in each Availability Zone.

C.Enable deletion protection on the ALB.

D.Enable sticky sessions (session affinity) on the ALB target group.

AnswerD

Sticky sessions ensure requests from a user go to the same instance.

Why this answer

Enabling sticky sessions (session affinity) on the ALB target group ensures that all requests from a user session are routed to the same Web Dispatcher instance. Without session affinity, the ALB distributes requests across multiple Web Dispatcher instances, and if the session state is stored locally on each instance, subsequent requests may land on a different instance that does not have the session data, causing the session to be dropped. This is a common issue during peak hours when the load balancer distributes traffic more aggressively.

Exam trap

The trap here is that candidates may confuse horizontal scaling (Option B) with solving session persistence issues, not realizing that adding more instances without sticky sessions actually worsens the problem by increasing the chance of a request landing on an instance without the session context.

How to eliminate wrong answers

Option A is wrong because disabling cross-zone load balancing would restrict traffic to Web Dispatcher instances only within the same Availability Zone as the client, which could lead to uneven load distribution and increased session drops, not resolve them. Option B is wrong because increasing the number of Web Dispatcher instances does not address the root cause of session drops; it only adds capacity, but if sessions are not pinned to a specific instance, new instances will still cause session routing issues. Option C is wrong because enabling deletion protection on the ALB prevents accidental deletion of the load balancer but has no effect on session persistence or traffic routing behavior.

Full explanation →

1529

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

SAP HANA is an in-memory database that requires large amounts of RAM and high memory bandwidth to keep all data in memory for real-time processing. The X1e instance family is specifically designed for high-memory workloads like SAP HANA, offering up to 4 TB of memory and high-frequency Intel Xeon processors, making it the only instance family among the options that meets SAP's certified memory and CPU requirements.

Exam trap

The trap here is that candidates often confuse general-purpose or compute-optimized instances (like M5 or C5) as suitable for SAP HANA because they focus on CPU performance alone, ignoring the critical requirement for massive memory capacity and SAP certification that only the X1e family provides.

How to eliminate wrong answers

Option A is wrong because T3 instances are burstable general-purpose instances with limited baseline CPU performance and small memory sizes, which cannot sustain the consistent high CPU and memory demands of SAP HANA. Option B is wrong because M5 instances are general-purpose instances with a balanced ratio of CPU to memory, but they lack the high memory capacity (max 384 GB) required for SAP HANA production workloads. Option C is wrong because C5 instances are compute-optimized with a high CPU-to-memory ratio, designed for compute-intensive tasks like batch processing, not for memory-intensive in-memory databases like SAP HANA.

Full explanation →

1530

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

Increasing provisioned IOPS on the io1 volume from 10,000 to 20,000 doubles the throughput from 250 MB/s to 500 MB/s, directly resolving the write latency issue.

Why this answer

The bottleneck is write throughput at 250 MB/s, which is the maximum throughput achievable with 10,000 provisioned IOPS on an io1 volume (assuming 256 KB I/O size). By increasing the provisioned IOPS to 20,000, the throughput doubles to 500 MB/s, directly reducing write latency. Option A is incorrect because EBS Multi-Attach is designed for shared volumes in multi-node clusters, not for a single-node HANA database.

Option C is incorrect because EBS-optimized instances are already enabled by default on current-generation EC2 instances; additional configuration would not increase throughput. Option D is incorrect because changing to gp3 would require a volume type conversion and might not achieve the same IOPS performance; gp3 has a maximum of 16,000 IOPS and 1,000 MB/s throughput, but the simplest and most direct fix is to increase IOPS on the existing io1 volume.

Full explanation →

1531

MCQhard

An organization is migrating an SAP ECC system to AWS using SAP Software Provisioning Manager (SWPM) and a homogeneous system copy. They have already exported the source system and are now importing to the target. The import fails with an error indicating that the target database tablespace is full. What should the administrator do to resolve the issue?

A.Increase the allocated storage for the target database tablespace.

B.Reduce the size of the source export by excluding some data.

C.Restart the import with a smaller package size.

D.Use SAP DMO instead of SWPM for the migration.

AnswerA

This provides the necessary space to complete the import.

Why this answer

The correct solution is to increase the size of the database tablespace on the target RDS instance or EC2-based database. Restarting the import without fixing the space issue will fail again. Reducing source export size is not appropriate as it would lose data.

Using a different migration method is unnecessary.

Full explanation →

1532

MCQeasy

An organization is migrating its SAP ERP system to AWS. The system uses SAP NetWeaver and a third-party backup tool that requires direct access to the database files. Which AWS storage option should be used for the database to ensure compatibility?

A.Amazon EFS

B.Amazon FSx for Windows File Server

C.Amazon EBS

D.Amazon S3

AnswerC

EBS provides block-level storage that can be accessed as a raw device.

Why this answer

(Amazon EBS) is correct because EBS provides block-level storage that can be mounted as a raw device, allowing backup tools to directly access database files. Option A (Amazon EFS) is wrong because EFS is a file storage service, not block-level. Option B (Amazon FSx for Windows File Server) is wrong because FSx for Windows is file storage for Windows workloads, not block-level.

Option D (Amazon S3) is wrong because S3 is object storage, not block-level.

Full explanation →

1533

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

AWS LaMa uses AWS CloudFormation to orchestrate the provisioning and teardown of infrastructure resources during SAP system cloning, refresh, or migration operations. Without cloudformation:CreateStack and cloudformation:DeleteStack, LaMa cannot create the temporary stacks needed for tasks like host replacement or storage snapshot-based cloning.

Exam trap

The trap here is that candidates often assume LaMa directly manages EC2 or RDS resources via their respective APIs, when in fact LaMa delegates all infrastructure provisioning to CloudFormation stacks to maintain consistency and support rollback.

How to eliminate wrong answers

Option A is wrong because LaMa does not directly invoke Lambda functions for its core automation; Lambda is used for custom extensions or post-processing, not for the primary orchestration of SAP landscape operations. Option C is wrong because LaMa manages SAP databases on RDS through CloudFormation stacks, not by directly calling rds:CreateDBInstance or rds:DeleteDBInstance; direct RDS API calls would bypass LaMa's state management and rollback capabilities. Option D is wrong because while LaMa may use S3 for storing backups or logs, the missing action for its typical automation tasks is not S3 object operations but the CloudFormation stack lifecycle actions that drive infrastructure provisioning.

Full explanation →

1534

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

Enabling jumbo frames (MTU 9001) on the VPC for the SAP application tier reduces CPU overhead and improves network throughput by allowing larger payloads per packet. This is particularly beneficial for SAP's high-volume data transfers between application and database servers, as it reduces the number of packets processed and lowers latency.

Exam trap

A common misconception in AWS is that simplifying network design by using a single subnet or placing the database tier in a public subnet is acceptable, but in reality, SAP on AWS demands strict network segmentation and security isolation to meet both operational and compliance requirements.

Full explanation →

1535

MCQmedium

A company is running SAP on EC2 instances with EBS volumes. They need to take daily snapshots of the EBS volumes and retain them for 90 days. Which approach is most cost-effective?

A.Use Amazon Data Lifecycle Manager (DLM) to automate snapshots and set a retention policy of 90 days.

B.Use S3 Lifecycle policies to transition snapshots to Glacier after 90 days.

C.Create a script that takes snapshots daily and stores them indefinitely.

D.Use AWS Backup to schedule backups and set retention to 90 days.

AnswerA

DLM automates and manages lifecycle, costing only for storage.

Why this answer

Amazon Data Lifecycle Manager (DLM) automates the creation and deletion of EBS snapshots, allowing you to set a retention policy of 90 days. This is cost-effective as old snapshots are automatically deleted. Option B is incorrect because S3 Lifecycle policies manage objects in S3, not EBS snapshots; snapshots are stored in S3 but are managed by DLM or AWS Backup.

Option C is incorrect because storing snapshots indefinitely would incur unnecessary costs. Option D, AWS Backup, is a managed service that can be used but may have additional costs compared to DLM, and DLM is specifically designed for cost-effective snapshot management.

Full explanation →

1536

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

The high CPU utilization with moderate memory usage indicates a compute-bound workload, not a memory-bound one. Changing from an r5.8xlarge (32 vCPUs, 256 GiB memory) to a c5.9xlarge (36 vCPUs, 72 GiB memory) provides more vCPUs and a better compute-to-memory ratio, directly addressing the CPU bottleneck. This aligns with SAP's recommendation to match instance types to workload characteristics, where compute-optimized instances are suitable for CPU-intensive SAP applications.

Exam trap

The trap here is that candidates assume high CPU utilization always requires a larger instance (Option A) or a storage fix (Options B and C), but the PAS-C01 exam tests the ability to match instance families to workload characteristics, specifically that compute-optimized instances (c5) are the correct choice for CPU-bound SAP applications, not memory-optimized ones.

How to eliminate wrong answers

Option A is wrong because increasing memory (r5.12xlarge) does not resolve high CPU utilization; it only adds more RAM, which is already underutilized, and does not increase vCPU count proportionally (r5.12xlarge has 48 vCPUs, but the bottleneck is CPU, not memory). Option B is wrong because increasing the EBS root volume size does not improve CPU performance; it only provides more storage capacity, which does not affect compute throughput or CPU utilization. Option C is wrong because adding Provisioned IOPS to EBS volumes improves disk I/O performance, but the issue is high CPU utilization, not disk latency or IOPS limits; CloudWatch metrics show moderate memory usage, not disk queue depth or I/O wait.

Full explanation →

1537

MCQhard

An operations team is troubleshooting a performance issue in an SAP environment where the database server's memory usage is consistently high. The team suspects that the SAP buffer cache is not sized optimally. Which CloudWatch metric should be monitored to confirm this?

A.`ReadIOPS` for the RDS instance

B.`DatabaseConnections` for the RDS instance

C.`FreeableMemory` for the RDS instance

D.`SwapUsage` for the RDS instance

AnswerC

Low freeable memory indicates the database is using most of the available memory, which could be due to a large buffer cache.

Why this answer

The `DatabaseMemoryUsedPercent` metric for Amazon RDS provides the percentage of memory used by the database engine, including buffer cache. A consistently high value may indicate an oversized buffer cache relative to available memory, but the question asks for a metric to confirm. However, the correct metric for RDS memory is `FreeableMemory`.

The buffer cache size can be inferred from `FreeableMemory`. Alternatively, for EC2-based SAP, the OS metrics are needed. Given the options, `FreeableMemory` is the best indicator.

Full explanation →

1538

MCQeasy

A company is migrating its SAP environment to AWS and wants to automate the installation of SAP software on EC2 instances. Which AWS service is best suited for this purpose?

A.AWS CloudFormation

B.AWS Elastic Beanstalk

C.Amazon EC2 Launch Templates

D.AWS OpsWorks

AnswerA

CloudFormation can automate the entire SAP deployment using custom resources.

Why this answer

(AWS CloudFormation) is correct because CloudFormation allows infrastructure as code and can use custom resource providers for SAP installation. Option B (AWS Elastic Beanstalk) is for web applications, not SAP. Option C (Amazon EC2 Launch Templates) only configures EC2 instances at launch, not full SAP installation.

Option D (AWS OpsWorks) is for Chef/Puppet automation but not SAP-specific.

Full explanation →

1539

MCQeasy

The exhibit shows an IAM policy for an SAP backup process that uploads backups to S3. An administrator wants to ensure that all uploads are encrypted using SSE-S3. What does this policy enforce?

A.The backup process must encrypt the files before uploading them.

B.The backup process must use AWS KMS to encrypt the objects.

C.Any PutObject request that does not include the encryption header will be denied.

D.The bucket automatically encrypts objects with SSE-S3 even if the request does not specify it.

AnswerC

The condition requires the encryption header; without it, the request fails.

Why this answer

The policy uses a `Deny` effect with a `StringNotEquals` condition on the `s3:x-amz-server-side-encryption` header, requiring it to be `AES256`. This enforces that any `PutObject` request must include the `x-amz-server-side-encryption: AES256` header; otherwise, the request is denied. Option C correctly states that requests without the encryption header will be denied.

Exam trap

The trap here is that candidates often confuse the `StringNotEquals` condition with a requirement for client-side encryption or KMS, or assume that bucket default encryption would automatically satisfy the policy, when in fact the policy explicitly denies requests that do not include the correct header.

How to eliminate wrong answers

Option A is wrong because the policy does not require client-side encryption before upload; it enforces server-side encryption (SSE-S3) by mandating the encryption header on the request. Option B is wrong because the policy specifies `AES256`, which corresponds to SSE-S3, not AWS KMS (which uses `aws:kms` as the header value). Option D is wrong because the policy does not enable default bucket encryption; it uses an explicit Deny to reject requests that lack the required header, rather than relying on automatic encryption.

Full explanation →

1540

MCQeasy

A company is migrating an SAP system to AWS and needs to ensure that the SAP application can communicate with the database over a low-latency, high-bandwidth connection. What is the best practice for network architecture?

A.Place the SAP application on-premises and the database on AWS.

B.Place the SAP application and database in the same VPC and same Availability Zone.

C.Place the SAP application and database in separate Availability Zones within the same region.

D.Place the SAP application in a different AWS Region than the database.

AnswerB

Same AZ ensures low-latency communication.

Why this answer

Placing the SAP application and database in the same VPC and Availability Zone minimizes latency. Separate AZs increase latency. Different regions introduce significant latency.

On-premises connection defeats purpose of migration.

Full explanation →

1541

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 in asynchronous mode across regions meets the RPO of less than 15 minutes because it continuously replicates log data with minimal latency, and the RTO of less than 2 hours is achievable by taking over the replicated HANA database in the DR region. EBS snapshots every 15 minutes provide an additional layer for persistent storage consistency, but the primary mechanism for meeting the RPO is the asynchronous log replication, which typically achieves sub-minute RPO.

Exam trap

The trap here is that candidates often assume synchronous replication is always better for low RPO, but in cross-region scenarios, synchronous mode is impractical due to latency, and asynchronous mode with log shipping easily achieves sub-15-minute RPO while avoiding performance impact on the primary system.

How to eliminate wrong answers

Option B is wrong because EBS snapshots replicated to the DR region via S3 cross-region replication cannot achieve an RPO of less than 15 minutes due to the snapshot creation interval (minimum 5-10 minutes) and replication latency, and the RTO would exceed 2 hours because you must restore volumes and reattach them before starting SAP. Option C is wrong because AWS Backup with continuous backups supports RPO of up to 1 minute for EBS volumes but does not provide native SAP HANA database-consistent recovery; it only captures block-level changes, not HANA transaction log consistency, and the RTO for restoring a full HANA system from backups typically exceeds 2 hours. Option D is wrong because SAP HANA System Replication in synchronous mode across regions introduces significant network latency that can impact primary system performance and is not recommended for cross-region deployments due to the high latency and potential for transaction blocking; it also does not inherently provide a faster RTO than asynchronous mode.

Full explanation →

1542

MCQeasy

A company is running an SAP HANA database on an EC2 instance with an EBS gp3 volume. The workload is write-intensive and latency-sensitive. Which configuration change would provide the most consistent I/O performance?

A.Switch to an EBS st1 (throughput-optimized HDD) volume

B.Enable EBS Multi-Attach for the gp3 volume

C.Increase the size of the existing gp3 volume to increase baseline throughput

D.Use an EBS io2 Block Express volume with provisioned IOPS

AnswerD

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

Why this answer

An SAP HANA database is extremely sensitive to I/O latency and requires consistent, high IOPS for write-intensive workloads. EBS io2 Block Express volumes provide up to 256,000 provisioned IOPS with 99.999% durability, delivering the predictable low-latency performance that gp3 volumes cannot guarantee under sustained write pressure. This makes D the correct choice for consistent I/O performance.

Exam trap

The trap here is that candidates often assume increasing volume size (Option C) will solve performance issues, but gp3's performance scales linearly with size only for throughput, not for IOPS consistency under sustained write loads, which is the key requirement for SAP HANA.

How to eliminate wrong answers

Option A is wrong because st1 (throughput-optimized HDD) volumes are designed for large, sequential workloads like big data and log processing, not for latency-sensitive, write-intensive databases like SAP HANA; they have a baseline throughput of only 40 MB/s per TB and cannot deliver the sub-millisecond latency required. Option B is wrong because EBS Multi-Attach allows a single volume to be attached to multiple EC2 instances, but it does not improve I/O performance or consistency for a single-instance workload; it is intended for clustered applications like WSFC, not for reducing latency or increasing IOPS. Option C is wrong because increasing the size of a gp3 volume increases its baseline throughput (e.g., from 125 MB/s at 1 GB to higher values), but gp3 volumes have a burst model and can experience performance throttling under sustained high write loads, whereas SAP HANA requires consistent, provisioned IOPS without reliance on burst credits.

Full explanation →

1543

MCQmedium

An SAP system administrator notices that the SAP HANA database backup job to Amazon S3 is failing intermittently. The backup script uses the AWS CLI. Which step should be taken to diagnose the issue?

A.Enable S3 Transfer Acceleration on the bucket

B.Check AWS CloudTrail logs for S3 API call errors

C.Configure S3 Lifecycle policy to expire incomplete multipart uploads

D.Modify the backup script to use the AWS SDK instead of CLI

AnswerB

CloudTrail logs show failed API calls and error codes.

Why this answer

AWS CloudTrail logs record API calls made to Amazon S3, including errors, which can help diagnose why the backup job is failing. Option A is wrong because S3 Transfer Acceleration only improves upload speed, not reliability. Option C is wrong because S3 Lifecycle policies manage object expiration and are unrelated to diagnosing backup failures.

Option D is wrong because switching from AWS CLI to SDK does not address the root cause; diagnostics should focus on API call errors, permissions, or network issues.

Full explanation →

1544

MCQeasy

A company is planning to migrate its SAP landscape to AWS. The SAP systems include a production system, a QA system, and a development system. All systems use the same SAP S/4HANA version. Which strategy is MOST cost-effective for the DR (disaster recovery) setup?

A.Set up warm standby in a second Region with a standby application server and database.

B.Use cross-Region replication with AWS reserved instances for the DR systems.

C.Use a pilot light strategy with AWS DMS ongoing replication.

D.Deploy active-active SAP systems in two AWS Regions with Elastic Load Balancing.

AnswerC

Correct. Pilot light with AWS DMS ongoing replication uses minimal resources (e.g., a small database instance) to keep data synchronized, while application servers and other components are not running. Only during a failover are additional resources provisioned, leading to the lowest possible cost for DR.

Why this answer

For SAP systems where all environments use the same S/4HANA version, the most cost-effective DR approach is a pilot light strategy using AWS DMS ongoing replication. This minimizes costs by replicating only the data (e.g., via DMS) and keeping only essential infrastructure running (e.g., a small standby database) while leaving additional compute resources (application servers, etc.) off until failover. In contrast, cross-Region replication with reserved instances (Option B) incurs significant ongoing costs because reserved instances must be paid for upfront or over time even when not running, and the DR systems would need to be sized for peak capacity, leading to waste.

Warm standby (Option A) and active-active (Option D) are more expensive due to the need for continuously running infrastructure or load balancing across regions. Therefore, pilot light with DMS is the most cost-effective for this scenario.

Exam trap

Candidates often assume that cross-Region replication with reserved instances is cost-effective because of the discounts, but they forget that reserved instances represent a long-term financial commitment. For DR workloads that are not continuously active, a pilot light approach that avoids paying for idle compute is actually cheaper.

How to eliminate wrong answers

Option A is wrong because a warm standby setup in a second Region with a standby application server and database incurs higher costs due to running additional EC2 instances and database instances continuously, which is not the most cost-effective strategy for DR. Option C is wrong because a pilot light strategy with AWS DMS ongoing replication is typically used for database migration or minimal DR setups, but it does not leverage reserved instances for cost savings and may not provide the same cost efficiency as cross-Region replication with reserved instances for SAP systems. Option D is wrong because deploying active-active SAP systems in two AWS Regions with Elastic Load Balancing is overkill and extremely expensive, as it requires running full production workloads in both Regions simultaneously, which is unnecessary for DR and not cost-effective.

Full explanation →

1545

MCQhard

An SAP system on AWS is experiencing high latency between the SAP application servers and the HANA database. The application servers are in a different Availability Zone than the database. Which change should a migration specialist recommend to reduce latency without increasing costs significantly?

A.Enable Enhanced Networking on all instances

B.Create a VPC Peering connection between the application and database subnets

C.Use larger instance types for the application servers

D.Deploy SAP application servers in the same placement group and Availability Zone as the HANA database

AnswerD

Same placement group and AZ minimizes network hops and latency.

Why this answer

Deploying SAP application servers in the same placement group and Availability Zone as the HANA database minimizes network distance and reduces latency without additional cost. Option A is incorrect: Enhanced Networking improves throughput and reduces packet loss but does not eliminate cross-AZ latency. Option B is incorrect: VPC Peering is used for inter-VPC connectivity, not for reducing latency within the same VPC.

Option C is incorrect: using larger instance types does not necessarily reduce network latency and would increase costs.

Full explanation →

1546

MCQhard

A company is migrating a 10 TB SAP HANA database to AWS. They have a limited time window and need to minimize migration time. The database is running on a physical server with 1 Gbps network link to AWS. Which migration strategy is MOST suitable?

A.Use AWS Direct Connect to increase bandwidth before migration

B.Use AWS Snowball Edge to transfer the database files offline

C.Use AWS SCT to convert the database and then use DMS

D.Use AWS DMS over the existing network link

AnswerB

Snowball Edge can transfer 10 TB quickly via physical shipment.

Why this answer

AWS Snowball Edge provides a high-capacity physical device for offline data transfer, avoiding network bandwidth limitations. Option A is wrong because AWS Direct Connect requires setup time and still is limited by 1 Gbps bandwidth, which would still result in long transfer times for 10 TB. Option C is wrong because AWS SCT is for schema conversion, not data transfer.

Option D is wrong because AWS DMS over a 1 Gbps link would take too long for 10 TB of data.

Full explanation →

1547

Multi-Selecteasy

A company wants to automatically recover an SAP HANA database EC2 instance if it becomes impaired due to underlying hardware issues. Which THREE components are required for this automatic recovery?

Select 3 answers

A.A CloudWatch alarm that monitors the StatusCheckFailed metric.

B.An instance that is configured for EC2 Auto Recovery.

C.A single Availability Zone deployment.

D.Multiple Availability Zones for the instance.

E.An Elastic IP address associated with the instance.

AnswersA, B, C

The alarm triggers the recovery action.

Why this answer

A CloudWatch alarm monitoring the StatusCheckFailed metric triggers the EC2 Auto Recovery process when the instance becomes impaired. Option B is correct because the instance must be explicitly configured for EC2 Auto Recovery; this is a prerequisite for automatic recovery. Option C is correct because EC2 Auto Recovery operates within a single Availability Zone; the instance is recovered in the same AZ.

Option D is incorrect because multiple Availability Zones are not used—this feature does not support multi-AZ recovery. Option E is incorrect because an Elastic IP address is not required for automatic recovery; if an Elastic IP is associated, it will be remapped automatically, but it is not a component of the recovery configuration.

Full explanation →

1548

Multi-Selectmedium

An SAP system is deployed on EC2 with a Multi-AZ RDS for SAP ASE database. The operations team needs to ensure that database backups are stored in a separate AWS account for compliance. Which TWO actions should they take?

Select 2 answers

A.Share the snapshots publicly and then copy them to the target account.

B.Configure S3 cross-region replication for the automated backups.

C.Use AWS KMS with cross-account permissions to allow the target account to decrypt and copy the snapshots.

D.Use AWS Backup with a cross-account backup policy to copy snapshots to the target account.

E.Enable automatic cross-account backup in the RDS console.

AnswersC, D

Cross-account KMS keys enable secure sharing of encrypted snapshots.

Why this answer

The correct answers are C and D. Option C: Using AWS KMS with cross-account permissions allows the target account to decrypt and copy encrypted snapshots, enabling secure cross-account backup. Option D: AWS Backup with a cross-account backup policy can automatically copy RDS snapshots to another account, meeting compliance requirements.

Option A is wrong because sharing snapshots publicly is a severe security risk. Option B is wrong because S3 cross-region replication is for S3 objects, not RDS snapshots. Option E is wrong because the RDS console does not have an automatic cross-account backup feature; this requires AWS Backup or manual snapshot sharing with KMS.

Full explanation →

1549

MCQeasy

An SAP system on AWS uses Amazon RDS for its database. The operations team needs to perform a point-in-time recovery (PITR) to restore the database to a specific timestamp. Which AWS feature enables PITR for RDS?

A.Manual DB snapshots

B.Read Replicas

C.Automated backups

D.Multi-AZ deployment

AnswerC

Automated backups enable point-in-time recovery to any second within the retention period.

Why this answer

Automated backups (option C) enable point-in-time recovery (PITR) for Amazon RDS. They provide continuous backups that allow restoring the database to any point within the retention period. Option A (Manual DB snapshots) are user-initiated and not used for PITR.

Option B (Read Replicas) are for read scaling, not recovery. Option D (Multi-AZ deployment) provides high availability, not PITR.

Full explanation →

1550

MCQhard

A company is migrating a legacy SAP ERP system to AWS. The system uses a custom kernel and has strict latency requirements. The SAP application servers must be placed in the same AWS region as the database. Which migration strategy should be used?

A.Replatform

B.Refactor

C.Repurchase

D.Rehost

AnswerD

Minimal changes, suitable for custom kernels.

Why this answer

Rehost (lift-and-shift) is appropriate when moving SAP systems with custom kernels, as it minimizes changes. Option A (Replatform) involves changes to the platform. Option B (Refactor) involves re-architecting.

Option C (Repurchase) involves replacing the software.

Full explanation →

1551

Multi-Selecthard

A company is running SAP HANA on EC2 instances with EBS volumes. They need to ensure data durability and backup. Which THREE actions should be taken?

Select 3 answers

A.Disable automated backups to reduce costs.

B.Use instance store volumes for HANA data.

C.Enable SAP HANA System Replication to a secondary instance.

D.Configure SAP HANA backup to Amazon S3 using Backint.

E.Take regular EBS snapshots of the HANA data volumes.

AnswersC, D, E

Replication provides high availability and disaster recovery.

Why this answer

SAP HANA System Replication provides synchronous or asynchronous data replication to a secondary EC2 instance, ensuring high availability and data durability by maintaining a real-time copy of the HANA database. This is a native SAP feature that protects against instance failure and supports automatic failover, which is critical for production HANA workloads.

Exam trap

The trap here is that candidates may confuse instance store volumes with EBS volumes, assuming they provide similar durability, or mistakenly think disabling backups is a cost-saving measure without considering the critical need for recoverability in SAP HANA environments.

Full explanation →

1552

MCQmedium

A company runs SAP on AWS and uses a central syslog server to collect logs from all SAP instances. The operations team wants to use a managed AWS service to centralize log storage and enable real-time analysis. Which service should they use?

A.Amazon Athena

B.Amazon CloudWatch Logs

C.Amazon Kinesis Data Firehose

D.Amazon S3

AnswerB

Amazon CloudWatch Logs is a managed service that centralizes logs from multiple sources, enabling real-time monitoring and analysis with CloudWatch Logs Insights. It is the best fit for this requirement.

Why this answer

Amazon CloudWatch Logs is a managed service that can aggregate logs from multiple Amazon EC2 instances and other sources, providing centralized storage and real-time monitoring and analysis. It is the most appropriate choice for this use case because it offers built-in log aggregation, real-time analysis with CloudWatch Logs Insights, and integration with AWS services. Amazon Athena (Option A) is an interactive query service for analyzing data in Amazon S3, not designed for real-time log ingestion from multiple sources.

Amazon Kinesis Data Firehose (Option C) is a streaming data delivery service that can capture and load data into destinations like S3 or Redshift, but it requires additional setup for real-time analysis and is more complex for simple log centralization. Amazon S3 (Option D) is an object storage service that can store logs but does not natively provide real-time analysis capabilities.

Full explanation →

1553

Multi-Selectmedium

Which TWO actions should be taken to ensure high availability for an SAP NetWeaver system on AWS? (Choose TWO.)

Select 2 answers

A.Assign Elastic IP addresses to the instances for failover

B.Place all EC2 instances in a single Availability Zone

C.Use Amazon EC2 Spot Instances for cost savings

D.Deploy the ASCS instance in an Auto Scaling group

E.Use Amazon RDS Multi-AZ for the database

AnswersA, E

Elastic IPs can be remapped to standby instances during failover.

Why this answer

To ensure high availability for an SAP NetWeaver system on AWS, two key actions are: A) Assign Elastic IP addresses to the instances for failover, which allows rapid IP remapping to a standby instance in case of failure; and E) Use Amazon RDS Multi-AZ for the database, which provides automatic failover to a standby replica in a different Availability Zone. Option B (placing instances in a single AZ) reduces availability. Option C (using Spot Instances) risks interruption and is not suitable for production SAP systems.

Option D (deploying ASCS in an Auto Scaling group) is not recommended because ASCS is stateful and cannot scale horizontally.

Full explanation →

1554

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

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.

Full explanation →

1555

MCQmedium

A company has an SAP environment with a recovery time objective (RTO) of 2 hours and a recovery point objective (RPO) of 15 minutes. Which backup strategy meets these requirements?

A.Daily full backups to Amazon S3 and log backups every 30 minutes.

B.Weekly full backups and daily differential backups.

C.Incremental backups every 15 minutes and log backups every 5 minutes.

D.Hourly EBS snapshots and continuous log shipping to S3.

AnswerC

Frequent incremental and log backups can achieve 15-minute RPO and 2-hour RTO.

Why this answer

Incremental backups (every 15 minutes) combined with log backups (every 5 minutes) allow for a recovery point objective (RPO) of 15 minutes and can meet the 2-hour recovery time objective (RTO) if the database is appropriately sized and restore procedures are optimized. Option A is incorrect because log backups every 30 minutes result in a potential data loss of up to 30 minutes, exceeding the required 15-minute RPO. Option B is incorrect because weekly full and daily differential backups provide an RPO of up to 24 hours.

Option D is incorrect because hourly EBS snapshots do not provide the granularity needed for a 15-minute RPO and restoring from snapshots can be slower than from SAP HANA-native backups.

Full explanation →

1556

MCQmedium

A company runs a critical web application on EC2 instances behind an Application Load Balancer (ALB). The application experiences intermittent high latency, and the operations team suspects that the load balancer is not distributing traffic evenly. Which configuration should the team check to confirm or rule out uneven traffic distribution?

A.Configure slow start on the target group

B.Increase the deregistration delay on the target group

C.Enable sticky sessions (session affinity) on the target group

D.Verify that cross-zone load balancing is enabled on the ALB

AnswerD

Cross-zone load balancing distributes traffic evenly across all instances in all enabled AZs. If disabled, each ALB node only sends traffic to instances in its own AZ, causing uneven distribution.

Why this answer

Uneven traffic distribution across EC2 instances behind an ALB is most commonly caused by cross-zone load balancing being disabled. By default, ALBs have cross-zone load balancing enabled, which distributes traffic evenly across all registered instances in all enabled Availability Zones. If it is disabled, each ALB node distributes traffic only to instances in its own Availability Zone, leading to imbalances when instance counts or capacities differ across zones.

Verifying this setting directly addresses the suspected uneven distribution.

Exam trap

The trap here is that candidates often confuse uneven distribution with session affinity (sticky sessions) or connection draining, but the root cause is typically the cross-zone load balancing setting, which directly controls whether traffic is balanced across all targets or confined to each Availability Zone.

How to eliminate wrong answers

Option A is wrong because slow start gradually ramps up traffic to new targets, which addresses cold-start latency but does not cause or resolve uneven distribution across healthy instances. Option B is wrong because increasing the deregistration delay keeps in-flight connections open during instance de-registration, which affects graceful shutdowns but has no impact on traffic distribution during normal operation. Option C is wrong because sticky sessions (session affinity) bind a client to a specific target, which can actually worsen uneven distribution by concentrating traffic on certain instances, not fix it.

Full explanation →

1557

MCQhard

A multinational corporation is migrating its SAP S/4HANA system to AWS. The system consists of a production database (3 TB), a development database (500 GB), and multiple application servers. The migration plan is to use AWS Database Migration Service (DMS) for the databases and AWS Application Migration Service (MGN) for the application servers. The company has set up a test environment in AWS and has performed a test migration. During the test, the production database migration via DMS completed successfully, but the development database migration failed with an error indicating that the source database version is not supported by DMS. The development database is SAP HANA 2.0 SPS 04, while the production database is SAP HANA 2.0 SPS 05. The target for both is Amazon RDS for SAP HANA. The DMS source endpoint was created using the same settings for both databases. Which step should the administrator take to resolve the development database migration failure?

A.Use SAP HANA System Replication to replicate the development database to RDS.

B.Upgrade the source development SAP HANA to a supported version (e.g., SPS 05).

C.Downgrade the production database to match the development version.

D.Use AWS Server Migration Service (SMS) for the development database.

AnswerB

DMS requires a supported source version.

Why this answer

DMS requires a supported SAP HANA version. The development database version (SPS 04) is not supported, so upgrading it to SPS 05 will allow the migration to proceed. Option A is incorrect because SAP HANA System Replication is not designed for migrating to RDS; it replicates between HANA instances.

Option C is incorrect because downgrading the production database is unnecessary and risky. Option D is incorrect because AWS SMS is for server migration, not database migration.

Full explanation →

1558

MCQeasy

A company is running an SAP HANA database on an Amazon EC2 instance. The storage is configured with multiple EBS volumes striped using LVM. The company wants to ensure the database performance is consistent and can detect potential bottlenecks. Which AWS service should be used to monitor the EBS volume metrics such as Average Queue Length and Throughput?

A.AWS Trusted Advisor

B.Amazon Inspector

C.Amazon CloudWatch

D.AWS CloudTrail

AnswerC

CloudWatch provides EBS performance metrics.

Why this answer

Amazon CloudWatch is the correct service because it provides detailed, granular monitoring of EBS volume metrics such as Average Queue Length (AverageQueueLength) and Throughput (VolumeReadBytes/VolumeWriteBytes). These metrics are collected at 1-minute intervals by default for EBS volumes attached to Nitro-based EC2 instances, enabling you to detect performance bottlenecks like high queue depths or throughput saturation. CloudWatch also allows you to set alarms and create dashboards for proactive monitoring of SAP HANA database storage performance.

Exam trap

The trap here is that candidates may confuse AWS Trusted Advisor's 'performance' checks (which only flag underutilized or overutilized resources at a high level) with the granular, real-time metrics that CloudWatch provides for EBS volumes, leading them to incorrectly select Trusted Advisor.

How to eliminate wrong answers

Option A is wrong because AWS Trusted Advisor provides high-level best-practice checks (e.g., idle resources, security groups, cost optimization) but does not expose real-time, per-volume metrics like Average Queue Length or Throughput. Option B is wrong because Amazon Inspector is a vulnerability management service that scans for software vulnerabilities and unintended network exposure, not a monitoring tool for EBS performance metrics. Option D is wrong because AWS CloudTrail records API activity and governance events (e.g., who created or deleted an EBS volume) but does not capture storage-level performance metrics such as queue depth or throughput.

Full explanation →

1559

MCQhard

You are managing an SAP S/4HANA system on AWS. The system uses a multi-AZ deployment with two application servers (one in us-east-1a, one in us-east-1b) and a HANA database in us-east-1a with a standby in us-east-1b using HSR. The /sapmnt and /usr/sap/trans are on an EFS file system. Recently, you noticed that during a failover test of the HANA database, the application servers lost connectivity to the database for several minutes, causing errors. You also observed that after the failover, the application servers could not reconnect until the EFS mount was remounted. What is the most likely cause and solution?

A.Increase the provisioned throughput on the EFS file system to handle the increased load during failover.

B.Migrate the shared file systems to Amazon FSx for NetApp ONTAP with multi-AZ deployment.

C.Configure EFS mount targets in each AZ and use an EFS access point with a consistent mount path.

D.Reconfigure SAP HANA System Replication to use synchronous replication.

AnswerC

This ensures that after failover, the application servers can mount the file system using the access point that resolves in the AZ.

Why this answer

The issue is that during a HANA database failover, the application servers lost connectivity and could not reconnect until the EFS mount was remounted. This indicates that the EFS mount targets are not properly configured for multi-AZ access. When the database fails over to the standby in us-east-1b, the application servers may be trying to access the EFS file system through a mount target that is only in us-east-1a, or the DNS resolution leads to a mount target in the wrong AZ, causing connectivity loss.

Option C is correct because configuring EFS mount targets in each AZ and using an EFS access point with a consistent mount path ensures that application servers in any AZ can reliably mount and access the shared file system without relying on cross-AZ connectivity. Option A (increase EFS throughput) does not address connectivity issues during failover. Option B (migrate to FSx for ONTAP) is not the immediate solution and may be unnecessary.

Option D (synchronous replication) does not fix the EFS connectivity problem.

Full explanation →

1560

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.

Full explanation →

1561

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.

Full explanation →

1562

MCQeasy

An SAP system administrator needs to automate the patching of SAP applications on EC2 instances. Which AWS service should they use?

A.Amazon Inspector

B.AWS Systems Manager Patch Manager

C.AWS OpsWorks

D.AWS Config

AnswerB

AWS Systems Manager Patch Manager automates OS and application patching across EC2 instances using a predefined patch baseline, directly satisfying the SAP administrator’s need to schedule and apply SAP application updates without manual intervention. Its integration with Systems Manager’s Run Command and maintenance windows enforces compliance against the specific constraint of automating patching on EC2, not just monitoring or deploying infrastructure.

Why this answer

AWS Systems Manager Patch Manager automates patching for managed instances, including SAP applications on EC2. Option A (Amazon Inspector) is for vulnerability assessment, not patching. Option C (AWS OpsWorks) is for configuration management with Chef/Puppet, not specifically for patching.

Option D (AWS Config) is for configuration compliance monitoring, not patching.

Full explanation →

1563

Multi-Selecteasy

Which TWO AWS services can be used to automate the start and stop of SAP EC2 instances based on a schedule? (Select TWO.)

Select 2 answers

A.AWS Lambda with CloudWatch Events

B.AWS Systems Manager Run Command

C.AWS Instance Scheduler

D.AWS Auto Scaling

E.AWS OpsWorks

AnswersA, C

Can schedule start/stop.

Why this answer

The correct answers are A (AWS Lambda with CloudWatch Events) and C (AWS Instance Scheduler). Option A allows you to run a custom Lambda function triggered by CloudWatch Events on a schedule (e.g., cron expression) to start or stop EC2 instances. Option C is a purpose-built AWS solution for scheduling instance start and stop times.

Options B (Systems Manager Run Command) is used for ad-hoc command execution, not for recurring scheduling. Option D (Auto Scaling) manages capacity based on scaling policies, not for scheduled start/stop of existing instances. Option E (AWS OpsWorks) is a configuration management service (Chef/Puppet) and not designed for scheduling instance power states.

Full explanation →

1564

MCQhard

An organization is migrating an SAP BusinessObjects system to AWS. The system uses a Sybase ASE database. They need to minimize downtime. Which migration strategy is most appropriate?

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

B.Perform an export/import of the database to AWS.

C.Use SAP Landscape Reorganization (LaMa) to automate the migration.

D.Set up HANA System Replication (HSR) to the AWS target.

AnswerC

LaMa supports Sybase ASE and can automate the cutover with minimal downtime.

Why this answer

The best approach is to use SAP Landscape Reorganization (LaMa) which supports Sybase ASE and can automate the migration with minimal downtime. DMS does not support Sybase ASE as a source. HSR is for SAP HANA, not Sybase.

Export/import is manual and leads to longer downtime.

Full explanation →

1565

MCQmedium

An operations team uses this IAM policy for a role assumed by SAP administrators. An administrator tries to stop a production SAP HANA instance in the us-west-2 region but receives an access denied error. What is the cause?

A.The Allow statement's resource ARN specifies us-east-1, but the instance is in us-west-2.

B.The Allow statement only permits stopping instances with the tag Environment=production, and the instance does not have that tag.

C.The Deny statement requires the resource to have a specific tag, which is missing.

D.The Deny statement with a condition on aws:RequestedRegion prevents actions outside us-east-1.

AnswerD

The condition denies all actions if the request is not in us-east-1.

Why this answer

The Deny statement includes a condition using aws:RequestedRegion that blocks any action unless the request is made in us-east-1. Since the administrator's request is in us-west-2, the condition fails and the Deny applies, causing the access denied error. Option A is incorrect because the Allow statement's resource ARN is for us-east-1, but the Deny overrides the Allow; the resource region is not the primary issue.

Option B is incorrect because even if the instance has the tag, the Deny still overrides. Option C is incorrect because the Deny does not require a tag; it checks the region.

Exam trap

Candidates often focus on the Allow statement's region-specific resource ARN and overlook the Deny statement's condition on aws:RequestedRegion, which explicitly blocks all actions outside us-east-1.

Full explanation →

1566

Multi-Selecteasy

Which TWO options are valid methods to back up an SAP HANA database on AWS? (Choose 2)

Select 2 answers

A.Use Amazon RDS automated backups

B.Use SAP HANA Backint with AWS Backup

C.Use AWS Database Migration Service (DMS)

D.Copy HANA data files to Amazon S3 using AWS CLI

E.Create application-consistent EBS snapshots using pre and post scripts

AnswersB, E

Backint integrates HANA backup with AWS.

Why this answer

Options B and E are correct. B: SAP HANA Backint integrated with AWS Backup provides a certified and native backup solution for HANA databases. E: Creating application-consistent EBS snapshots using pre and post scripts ensures data consistency and is a valid backup method.

Option A is incorrect because Amazon RDS automated backups are not applicable to SAP HANA running on EC2; RDS is a managed service for relational databases, not HANA. Option C is incorrect because AWS DMS is designed for database migration, not backup. Option D is incorrect because copying HANA data files to S3 using AWS CLI does not ensure consistency and is not a supported backup method for HANA.

Full explanation →

1567

MCQmedium

A company is migrating its SAP ERP system to AWS and needs to ensure that the SAP license is compliant. The company has a production license for SAP ERP. What should the company do for licensing on AWS?

A.Request a free SAP license for AWS from SAP.

B.Use a subscription-based SAP license from the AWS Marketplace.

C.Purchase a new SAP license for AWS.

D.Use the existing SAP license under the Bring Your Own License (BYOL) model.

AnswerD

BYOL allows using existing licenses on AWS.

Why this answer

AWS supports the Bring Your Own License (BYOL) model for SAP, allowing the company to use its existing SAP ERP license on AWS. Option A is incorrect because SAP does not offer a free license for AWS. Option B is incorrect because while subscription licenses are available, the company already has a production license, so BYOL is the appropriate choice.

Option C is incorrect because purchasing a new license is unnecessary when the existing license can be reused under BYOL.

Full explanation →

1568

MCQeasy

A company needs to migrate its SAP application server from on-premises to AWS. The server runs on Windows Server 2012 R2 and has a custom SAP kernel. Which AWS service should be used to migrate the server with minimal changes?

A.AWS CloudEndure Migration

B.AWS Database Migration Service (AWS DMS)

C.AWS Application Migration Service (AWS MGN)

D.AWS Server Migration Service (AWS SMS)

AnswerC

AWS Application Migration Service (MGN) automates lift-and-shift server migrations, supporting Windows and custom SAP kernels.

Why this answer

AWS Application Migration Service (AWS MGN) automates the lift-and-shift migration of servers from on-premises to AWS, supporting Windows Server and custom configurations such as SAP kernels. Option A (CloudEndure Migration) is wrong because CloudEndure has been superseded by AWS MGN and is no longer recommended for new migrations. Option B (AWS DMS) is wrong because it specializes in database migrations, not entire server instances.

Option D (AWS SMS) is wrong because it is an older, less flexible service that may not handle custom kernels as effectively as MGN.

Full explanation →

1569

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.

Full explanation →

1570

MCQhard

An IAM policy is attached to a user who manages SAP HANA volumes. The policy is shown in the exhibit. What is the effect of this policy?

A.The user can attach and detach any volume regardless of tags.

B.The user can delete any volume.

C.The user can attach and detach volumes that have the tag Environment=production, but cannot delete any volume.

D.The user can attach and detach any volume in the production environment.

AnswerC

Correct: The first statement allows AttachVolume and DetachVolume only when the volume has the tag Environment=production. The second statement denies DeleteVolume for all volumes. Thus, the user can attach/detach volumes with that tag but cannot delete any volume.

Why this answer

The first statement allows ec2:AttachVolume and ec2:DetachVolume only if the volume has tag Environment=production. The second statement denies ec2:DeleteVolume for all volumes. Therefore, the user can attach and detach volumes that have the tag Environment=production, but cannot delete any volume.

Option A is incorrect because attach/detach are allowed only with the condition. Option B is incorrect because delete is denied for all volumes. Option D is incorrect because the allow statement is conditional on the specific tag value, not just the production environment.

Full explanation →

1571

MCQmedium

An SAP system experiences an unplanned failover of the HANA database. The database administrator needs to investigate the root cause. Which AWS service should be used to analyze the timeline of events leading to the failover?

A.AWS CloudTrail

B.Amazon CloudWatch Logs

C.Amazon VPC Flow Logs

D.AWS Config

AnswerA

CloudTrail records API calls and events, enabling root cause analysis of failover.

Why this answer

AWS CloudTrail records API calls and events, which can help trace actions leading to failover. Option B (Amazon CloudWatch Logs) collects logs but not API activity. Option C (Amazon VPC Flow Logs) captures network traffic.

Option D (AWS Config) tracks configuration changes but not real-time events.

Full explanation →

1572

MCQeasy

An SAP system uses an NFS share from an EFS file system for transport files. Recently, the transport directory performance has degraded. Which change would most likely improve performance?

A.Increase the burst credit balance by creating more files.

B.Enable Provisioned Throughput on the EFS file system.

C.Migrate the transport directory to Amazon FSx for Lustre.

D.Use Amazon S3 with an NFS mount via AWS Storage Gateway.

AnswerB

Provisioned Throughput ensures consistent IOPS for NFS workloads.

Why this answer

Using Provisioned Throughput on EFS ensures consistent performance regardless of file system size. Option A is wrong because increasing burst credits only helps temporarily. Option C is wrong because FSx for Lustre is for high-performance computing, not general purpose NFS.

Option D is wrong because moving to S3 would require application changes.

Full explanation →

1573

MCQmedium

An SAP system administrator needs to monitor the CPU utilization of an EC2 instance running SAP NetWeaver and set an alarm when it exceeds 90% for 5 minutes. Which AWS service should they use?

A.AWS CloudTrail

B.Amazon CloudWatch

C.AWS Trusted Advisor

D.AWS Config

AnswerB

CloudWatch monitors EC2 metrics and can trigger SNS notifications when thresholds are breached.

Why this answer

Amazon CloudWatch is the correct service because it provides detailed monitoring of EC2 instances, including CPU utilization metrics, and allows you to set CloudWatch Alarms that trigger when a metric exceeds a specified threshold (e.g., 90%) for a given number of consecutive evaluation periods (e.g., 5 minutes). This is the native AWS service designed for performance monitoring and alerting.

Exam trap

The trap here is that candidates often confuse AWS CloudTrail (auditing) or AWS Config (compliance) with monitoring services, but only CloudWatch provides the metric collection and alarm functionality needed for real-time performance thresholds.

How to eliminate wrong answers

Option A is wrong because AWS CloudTrail records API activity and governance events, not system-level performance metrics like CPU utilization. Option C is wrong because AWS Trusted Advisor provides best-practice recommendations for cost, performance, security, and fault tolerance, but it does not offer real-time metric monitoring or alarm configuration. Option D is wrong because AWS Config tracks resource configuration changes and compliance, not operational metrics or threshold-based alarms.

Full explanation →

1574

MCQhard

An SAP administrator runs the AWS CLI command shown in the exhibit to check the status of a production HANA instance. The output shows the instance is running in us-east-1a. However, the SAP application team reports that the HANA database is not responding. What should the administrator check next to diagnose the issue?

A.The EBS volumes are detached from the instance

B.The instance state is 'running' so no issue with the instance

C.The HANA database service is not running on the instance

D.The security group does not allow inbound traffic to the database port

AnswerC

The administrator should verify the HANA process is running.

Why this answer

The AWS CLI command only checks the EC2 instance state (e.g., 'running'), not the status of the HANA database service itself. Even if the instance is running, the HANA database service (hdbnameserver, hdbindexserver, etc.) may have crashed, failed to start, or been stopped. The administrator should SSH into the instance and run commands like 'systemctl status hdbindexserver' or 'sapcontrol -nr <instance_number> -function GetProcessList' to verify the HANA service status.

Exam trap

The trap here is that candidates assume an EC2 instance state of 'running' guarantees all applications on it are functional, but AWS separates infrastructure health from guest OS/application health, and the exam tests this distinction by requiring you to check the database service separately.

How to eliminate wrong answers

Option A is wrong because if EBS volumes were detached, the instance would likely show a different state (e.g., 'stopped' or 'terminated') or the root volume would be missing, causing immediate boot failure; the CLI output shows the instance is running, so volumes are attached. Option B is wrong because an instance state of 'running' only indicates the OS is up, not that application-level services like HANA are operational; the database can be down while the instance is healthy. Option D is wrong because a security group blocking inbound traffic would prevent new connections but would not cause the database to be 'not responding' from the instance's perspective; the database service itself would still be running and could be checked locally via loopback; the issue is the service not running, not network access.

Full explanation →

1575

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.

Full explanation →

Page 21 of 22

All pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22

Practice PAS-C01 by domain

Target a specific domain to shore up weak areas.

Design of SAP Workloads on AWS Technology Migration Operations and Maintenance

See all domains with question counts →