Courseiva

AWS Certified SAP on AWS Specialty PAS-C01 (PAS-C01) — Questions 1201–1275

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

Take a mock examExam hub
Page 16

Page 17 of 22

Page 18
1201
MCQhard

During an SAP migration to AWS, the migration team faces a challenge with the Transport Management System (TMS). The SAP system landscape includes development, quality assurance, and production systems running on separate EC2 instances. The TMS is configured with transport routes between these systems. After migration, transports fail with errors related to missing files on the transport directory. What should the team do to ensure the TMS works correctly?

A.Create an EBS volume for each SAP system and copy transport files manually.
B.Set up an Amazon EFS file system and mount it as the transport directory on all SAP instances.
C.Store the transport directory in an S3 bucket and mount it using S3FS.
D.Use AWS Storage Gateway with SMB file share to host the transport directory.
AnswerB

Amazon EFS provides a fully managed NFS file system that can be mounted on multiple EC2 instances, making it the ideal shared transport directory for TMS.

Why this answer

The Transport Management System (TMS) requires a shared transport directory accessible by all SAP instances (DEV, QAS, PRD). Option B is correct because Amazon EFS provides a scalable NFS file system that can be mounted on multiple EC2 instances simultaneously, satisfying the shared storage requirement. Option A is incorrect because EBS volumes are block storage that can only be attached to a single instance; manual file copying is not feasible for ongoing TMS operations.

Option C is incorrect because mounting an S3 bucket via S3FS introduces performance and consistency issues; S3 is object storage not designed for low-latency file sharing required by TMS. Option D is incorrect because AWS Storage Gateway with SMB file share adds unnecessary complexity; EFS with NFS is the standard and simpler solution for shared transport directories in SAP on AWS.

Full explanation →
1202
MCQhard

An SAP administrator attaches this IAM policy to a user. The user is unable to start an EC2 instance with ID i-0abcdef1234567890. What is the most likely cause?

A.The IAM policy does not include the ec2:RebootInstances action.
B.The IAM policy is applied to a user who is working in a different AWS region than the one specified in the resource ARN.
C.The IAM policy does not include the ec2:DescribeInstances action.
D.The IAM policy does not include the ec2:StartInstances action.
AnswerB

Correct. The resource ARN in the policy specifies a particular region, but the user is operating in a different region, so the policy does not apply.

Why this answer

The IAM policy likely includes a resource ARN that specifies a region (e.g., us-east-1). IAM policies with resource ARNs that include a region only apply to resources in that region. If the user is attempting to start the EC2 instance in a different region (e.g., eu-west-1), the policy does not grant permission, even though it includes ec2:StartInstances.

Option B correctly identifies this region mismatch as the most likely cause. Options A, C, and D are incorrect because the policy does include the necessary actions for starting an instance.

Full explanation →
1203
Multi-Selecteasy

Which THREE metrics should be monitored to ensure the health of an SAP NetWeaver application server? (Choose three.)

Select 3 answers
A.Memory utilization
B.Database connection count
C.CPU utilization
D.Work process utilization
E.Network packet loss
AnswersA, C, D

Memory pressure can cause swapping and performance degradation.

Why this answer

Options A, C, and D are correct. Memory utilization, CPU utilization, and work process utilization are key indicators of SAP NetWeaver application server health. Option B is wrong because database connection count is a database-level metric, not directly indicative of application server health.

Option E is wrong because network packet loss is an infrastructure metric that affects connectivity but is not a specific application server health metric.

Full explanation →
1204
Multi-Selecteasy

Which TWO AWS services can be used to monitor SAP HANA database performance metrics? (Choose TWO.)

Select 1 answer
A.SAP HANA Studio / SAP HANA Cockpit
B.AWS CloudTrail
C.AWS Config
D.Amazon CloudWatch
E.AWS X-Ray
AnswersD

Amazon CloudWatch can collect custom metrics from SAP HANA via monitoring integrations, making it a valid AWS service for monitoring performance metrics.

Why this answer

Amazon CloudWatch is the only AWS service listed that can monitor SAP HANA database performance metrics. SAP HANA Studio and SAP HANA Cockpit are native SAP tools, not AWS services. AWS CloudTrail, AWS Config, and AWS X-Ray are not used for monitoring database performance metrics.

Full explanation →
1205
MCQmedium

During the migration of an SAP HANA database to AWS, the migration team encounters high latency on the database connections. The team is using AWS Direct Connect. Which configuration change can help reduce latency?

A.Enable jumbo frames on the Direct Connect interface
B.Switch from Direct Connect to a VPN connection
C.Increase the bandwidth of the Direct Connect connection
D.Place the EC2 instances in the same Availability Zone
AnswerA

Enabling jumbo frames allows larger packets, reducing the number of packets and overhead, which can reduce latency for large transfers like SAP HANA.

Why this answer

Enabling jumbo frames reduces overhead by allowing larger packets, which can improve latency for large data transfers. Option B is incorrect because a VPN connection adds encapsulation overhead and can increase latency. Option C is incorrect because increasing bandwidth increases throughput but does not reduce latency; latency is affected by packet size and network path.

Option D is incorrect because placing EC2 instances in the same Availability Zone reduces physical distance but does not guarantee reduced latency if the network path is not optimized.

Full explanation →
1206
MCQhard

A company is running SAP ERP on AWS and using a shared file system for the SAP transport directory. The file system must be accessible from multiple EC2 instances in different Availability Zones. Which AWS storage solution should be used?

A.Amazon FSx for Windows File Server
B.Amazon EFS
C.Amazon S3
D.Amazon EBS
AnswerB

EFS provides a shared NFS file system accessible from multiple AZs.

Why this answer

Amazon EFS provides a scalable, shared file system that can be mounted from multiple EC2 instances across Availability Zones. Amazon S3 is object storage, not a file system. Amazon FSx for Windows File Server is for Windows-based environments.

Amazon EBS cannot be shared across instances.

Full explanation →
1207
MCQeasy

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

A.VPC Peering connection between subnets.
B.Internet Gateway
C.Network ACL with inbound rules for the database subnet.
D.Security Group rules allowing traffic between the security groups.
AnswerD

Security Groups allow stateful traffic between instances.

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Full explanation →
1208
MCQmedium

An SAP on AWS environment uses a shared file system with Amazon EFS. The operations team reports slow performance during peak hours. Which configuration change would most likely improve throughput?

A.Enable encryption at rest
B.Increase provisioned throughput
C.Enable Bursting Throughput
D.Change the performance mode to Max I/O
AnswerB

Increasing provisioned throughput directly raises the throughput limit, providing consistent performance during peak hours.

Why this answer

Increasing provisioned throughput on Amazon EFS is a direct configuration change that raises the throughput limit, which most reliably improves performance during peak hours. Bursting throughput is the default mode and cannot be 'enabled' as a change; it automatically allows bursting based on stored data, but during sustained peak usage, provisioned throughput is needed to guarantee higher throughput. Option A (encryption at rest) does not affect performance.

Option C (Enable Bursting Throughput) is misleading because bursting is already enabled by default and cannot be turned on as a new configuration; it also does not provide sustained throughput improvement. Option D (Max I/O performance mode) optimizes for high I/O operations but does not directly increase throughput.

Full explanation →
1209
MCQmedium

An SAP system running on AWS experiences high latency when accessing data in Amazon S3. The operations team suspects network bandwidth limitations. Which AWS service can be used to monitor the network throughput between the EC2 instances and S3?

A.Amazon CloudWatch S3 metrics
B.AWS Trusted Advisor
C.AWS Config
D.VPC Flow Logs
AnswerD

Correct. VPC Flow Logs capture IP traffic metadata (e.g., source/destination, packet/byte counts) which can be used to analyze network throughput between EC2 instances and S3.

Why this answer

(VPC Flow Logs) is correct because VPC Flow Logs capture IP traffic information and can help analyze network throughput between EC2 instances and S3. Option A is incorrect because CloudWatch S3 metrics are request-level, not network-level. Option B is incorrect because Trusted Advisor provides best practice checks, not real-time monitoring.

Option C is incorrect because AWS Config records resource changes, not network performance.

Full explanation →
1210
MCQmedium

A company is running an SAP HANA database on an EC2 instance with a single EBS volume for /hana/data. The performance team reports high write latency during peak hours. Which change would most effectively reduce write latency without compromising data durability?

A.Switch the EBS volume type to Provisioned IOPS SSD (io1) with high IOPS
B.Increase the size of the EBS volume to gain more baseline IOPS
C.Move the /hana/data directory to a General Purpose SSD (gp2) volume
D.Configure multiple EBS volumes in a striped RAID 0 array for the /hana/data directory
AnswerD

Striping across multiple EBS volumes distributes I/O and reduces latency.

Why this answer

Configuring multiple EBS volumes in a striped RAID 0 array is the most effective way to reduce write latency for SAP HANA's /hana/data directory because it distributes I/O across multiple volumes, increasing throughput and reducing latency. This approach is recommended by AWS for high-performance SAP HANA workloads. Option A (switching to io1 with high IOPS) could improve performance but is more expensive and may not provide the same level of throughput as striping.

Option B (increasing volume size) only increases baseline IOPS for gp2/gp3 volumes but does not guarantee latency reduction. Option C (moving to gp2) is a downgrade from the current volume type (likely gp3 or io1) and would likely increase latency.

Full explanation →
1211
Multi-Selectmedium

A company is deploying a multi-tier web application on AWS. The application consists of an Application Load Balancer (ALB), a fleet of EC2 instances in an Auto Scaling group, and an Amazon RDS MySQL Multi-AZ DB instance. The security team requires that all traffic between the ALB and EC2 instances is encrypted, and that the EC2 instances can only be accessed by the ALB. Which TWO steps should be taken to meet these requirements? (Choose TWO.)

Select 2 answers
A.In the EC2 security group, allow inbound HTTPS traffic from 0.0.0.0/0.
B.Enable encryption at rest on the EC2 instances using EBS encryption.
C.In the EC2 security group, allow inbound traffic on port 443 from the ALB's security group.
D.Configure the target group of the ALB to use HTTPS protocol.
E.Configure the ALB with an HTTPS listener and upload the SSL/TLS certificate.
AnswersC, D

This restricts access to only the ALB, meeting the requirement.

Why this answer

Referencing the ALB's security group in the inbound rule of the EC2 security group ensures that only traffic originating from the ALB is allowed, meeting the requirement that EC2 instances can only be accessed by the ALB. Option D is correct because configuring the target group to use HTTPS protocol ensures that traffic between the ALB and EC2 instances is encrypted using TLS, satisfying the encryption requirement.

Exam trap

The trap here is that candidates often confuse the ALB listener protocol (which encrypts client-to-ALB traffic) with the target group protocol (which encrypts ALB-to-instance traffic), leading them to select Option E instead of Option D.

Full explanation →
1212
Multi-Selecthard

A company runs SAP S/4HANA on AWS. They want to ensure high availability for the central services (ASCS) and enqueue replication. Which TWO components should be deployed to meet this requirement?

Select 2 answers
A.Secondary ASCS instance in a different Availability Zone
B.Primary ASCS instance in one Availability Zone
C.Third ASCS instance in a third Availability Zone
D.Enqueue Replication Server (ERS) in a different Availability Zone
E.SAP HANA database replication
AnswersB, D

Primary ASCS runs the enqueue service.

Why this answer

For HA, deploy the ASCS instance in a primary node and an enqueue replication server (ERS) in a secondary node, typically in different AZs.

Full explanation →
1213
MCQhard

An SAP administrator created the IAM policy shown for a backup script. The script fails when trying to upload a backup to S3. What is the likely cause?

A.The resource for S3 should include the bucket itself (arn:aws:s3:::sap-backup-bucket).
B.The ec2:Describe* action is not required and causes a conflict.
C.The s3:* action is too broad and is denied by an S3 bucket policy.
D.The KMS key ARN is malformed; it contains extra characters.
AnswerD

The key ARN has a typo with 'a123b4cd56ef' instead of proper format.

Why this answer

The KMS key ARN in the IAM policy is malformed (contains extra characters). When the backup script attempts to upload to S3 with server-side encryption using KMS (SSE-KMS), S3 needs to decrypt the object using the KMS key. If the key ARN is invalid, the kms:Decrypt permission cannot be evaluated, causing the upload to fail.

Option A is incorrect because for PutObject, the resource must be the object ARN (arn:aws:s3:::sap-backup-bucket/*), not the bucket itself. Option B is incorrect because ec2:Describe* actions do not interfere with S3 operations. Option C is incorrect because the s3:* action, while broad, is permitted on the specified objects, and there is no indication of a restrictive bucket policy.

Full explanation →
1214
MCQeasy

A company is deploying a new SAP S/4HANA system on AWS. The system will be used by 500 concurrent users. The SAP application server and the HANA database will run on separate EC2 instances. The company needs to ensure that the database instance has enough memory for the HANA database, which requires 512 GB of RAM. The application server requires 32 vCPUs and 128 GB of RAM. The company wants to minimize costs while meeting these requirements. Which combination of EC2 instance types should the company choose?

A.Use an r5.12xlarge for the database and an m5.4xlarge for the application server.
B.Use an x1e.8xlarge for the database and an r5.8xlarge for the application server.
C.Use an x1e.32xlarge for the database and an m5.8xlarge for the application server.
D.Use an r5.24xlarge for the database and an r5.8xlarge for the application server.
AnswerD

r5.24xlarge has 768 GB, sufficient; r5.8xlarge has 32 vCPU and 256 GB, sufficient.

Why this answer

The HANA database requires 512 GB of RAM. The r5.24xlarge provides 768 GB of RAM and 96 vCPUs, which is sufficient and cost-effective for the database. The r5.8xlarge provides 32 vCPUs and 256 GB of RAM, meeting the application server's requirements of 32 vCPUs and 128 GB.

Option A uses an r5.12xlarge (384 GB RAM) for the database, which is insufficient for 512 GB. Option B uses an x1e.8xlarge (244 GB RAM) for the database, also insufficient. Option C uses an x1e.32xlarge (976 GB RAM) for the database, which is overkill and more expensive, and the m5.8xlarge (32 vCPUs, 128 GB RAM) for the application is adequate but the database choice increases cost unnecessarily.

Therefore, D minimizes cost while meeting requirements.

Full explanation →
1215
MCQmedium

A company runs a critical SAP application on an SAP HANA database on AWS. The database is backed up daily to Amazon S3. The company needs to ensure that the database can be restored to a point in time within the last 24 hours with minimal data loss. Which AWS service should be used to achieve this requirement?

A.Enable S3 Object Versioning on the backup bucket.
B.Configure Amazon Data Lifecycle Manager (DLM) for EBS snapshots.
C.Use AWS Backup with the SAP HANA backup plan.
D.Use Amazon RDS automated backups.
AnswerC

AWS Backup provides a managed backup service for SAP HANA databases, supporting automated backups and point-in-time recovery (PITR).

Why this answer

AWS Backup provides a managed backup service for SAP HANA databases, supporting automated backups and point-in-time recovery (PITR) within a specified retention period. Option A is incorrect because S3 Object Versioning protects against accidental deletion but does not provide database-level point-in-time recovery. Option B is incorrect because Amazon Data Lifecycle Manager (DLM) is designed for managing EBS snapshots, not for SAP HANA database backups.

Option D is incorrect because Amazon RDS is a managed relational database service and does not support SAP HANA.

Exam trap

Candidates often confuse DLM with AWS Backup. DLM is for EBS snapshots, not SAP HANA backups. AWS Backup is the correct service for SAP HANA because it offers application-consistent backup plans and supports point-in-time recovery.

Full explanation →
1216
MCQhard

An SAP administrator notices that the /hana/data filesystem on an SAP HANA database is approaching 95% utilization. The HANA instance uses EBS gp3 volumes. What is the MOST efficient way to increase storage without downtime?

A.Add a new EBS volume and extend the logical volume.
B.Migrate the database to a new instance with larger volumes.
C.Modify the existing EBS volume to increase its size.
D.Create a snapshot, create a larger volume, and restore.
AnswerC

EBS gp3 volumes support online resizing.

Why this answer

EBS gp3 volumes support online resizing without downtime. You can increase the volume size while the instance is running, and then extend the filesystem and logical volume (if using LVM) to utilize the additional space. This avoids any disruption to the SAP HANA database.

Exam trap

The trap here is that candidates may think adding a new volume (Option A) is simpler or that snapshot-based migration (Option D) is required, but AWS EBS gp3 volumes support online resizing, making Option C the most efficient and downtime-free approach.

How to eliminate wrong answers

Option A is wrong because adding a new EBS volume and extending the logical volume requires attaching the new volume, which may involve rescanning the SCSI bus and could introduce complexity, but more importantly, it is less efficient than simply resizing the existing volume since it adds management overhead and potential path issues. Option B is wrong because migrating the database to a new instance with larger volumes would require downtime for data transfer and reconfiguration, making it inefficient compared to a simple volume resize. Option D is wrong because creating a snapshot and restoring to a larger volume involves stopping the database or at least ensuring data consistency, which introduces downtime, and is unnecessary when gp3 volumes can be resized online.

Full explanation →
1217
Multi-Selecthard

An SAP system on AWS is running on a single Availability Zone. The operations team wants to improve high availability. Which THREE actions should they take?

Select 3 answers
A.Use an Application Load Balancer to distribute traffic across AZs.
B.Use EBS Multi-Attach to share volumes across AZs.
C.Assign Elastic IP addresses to instances for failover.
D.Deploy SAP application servers in an Auto Scaling group across multiple AZs.
E.Configure the SAP database for Multi-AZ deployment.
AnswersA, D, E

ALB can route traffic to healthy targets in multiple AZs.

Why this answer

A: Use an Application Load Balancer to distribute traffic across AZs. This helps distribute traffic across multiple AZs, improving availability. D: Deploy SAP application servers in an Auto Scaling group across multiple AZs.

This ensures that if one AZ fails, the application servers in other AZs continue to serve traffic. E: Configure the SAP database for Multi-AZ deployment. This provides a standby database in another AZ for automatic failover.

B is incorrect because EBS volumes are AZ-specific and cannot be attached across AZs. C is incorrect because Elastic IP addresses are static public IPs and do not provide high availability across AZs on their own; they are typically used for failover within a single AZ.

Full explanation →
1218
Multi-Selecthard

An SAP administrator is troubleshooting a performance issue on an SAP HANA database running on an EC2 instance. The instance type is r5.4xlarge with EBS-optimized enabled. CloudWatch metrics show high WriteIOPS but low throughput. Which THREE factors could be causing this behavior? (Choose three.)

Select 3 answers
A.The SAP HANA database is performing many small write operations.
B.The database is experiencing lock contention or thread contention.
C.The EBS volume's throughput limit is lower than the burst credit threshold.
D.The instance's EBS-optimized feature is not enabled.
E.The EBS volume is configured with a large block size.
AnswersA, B, C

Small writes increase IOPS but result in low throughput.

Why this answer

Options A, B, and C are correct. Small I/O operations cause high IOPS but low throughput (A). Lock contention or thread contention can reduce throughput by causing waiting times (B).

EBS volume throughput limits can cap the actual throughput even if IOPS are high (C). Option D is incorrect because EBS optimization is already enabled. Option E is incorrect because a large block size would increase throughput, not cause low throughput.

Full explanation →
1219
Drag & Dropmedium

Drag and drop the steps to migrate an on-premises SAP system to AWS using AWS Application Migration Service (MGN) 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

MGN migration involves installing agent, configuring replication, testing, cutover, and post-migration steps.

Full explanation →
1220
MCQhard

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

A.The instance type does not support EBS optimization. Switch to a network-optimized instance.
B.The EBS volume is not optimized for SAP. Use io1 with high provisioned IOPS.
C.The volume is too small for the workload. Increase the volume size to gain baseline IOPS.
D.The gp2 volume does not provide enough burst IOPS. Migrate to gp3.
AnswerC

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

Why this answer

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

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

Exam trap

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

How to eliminate wrong answers

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

Full explanation →
1221
MCQmedium

A company is migrating an SAP NetWeaver system to AWS. The system uses a shared file system for central transport directories and logs. Which AWS storage service should be used to provide a scalable, highly available, and shared file system that can be mounted by multiple EC2 instances across different Availability Zones?

A.Amazon EBS with Multi-Attach enabled
B.Amazon EFS
C.EC2 Instance Store
D.Amazon S3 with S3 File Gateway
AnswerB

Amazon EFS provides a fully managed, highly available, and scalable NFS file system that can be accessed from multiple EC2 instances across different AZs, ideal for SAP shared directories.

Why this answer

Amazon EFS (Option B) is correct because it provides a scalable, highly available, shared NFS file system that can be mounted by multiple EC2 instances across different Availability Zones, making it suitable for SAP shared file systems. Option A (EBS with Multi-Attach) is incorrect because Multi-Attach only works within a single AZ and has limited attach instances (up to 16), not across AZs. Option C (EC2 Instance Store) is incorrect because it is ephemeral and cannot be shared across instances.

Option D (Amazon S3 with S3 File Gateway) is incorrect because it is not a native shared file system; File Gateway provides NFS/SMB access to S3 but adds complexity and latency, and is not the recommended service for SAP shared directories.

Full explanation →
1222
MCQeasy

A company wants to automate the backup of SAP HANA databases running on EC2 instances. The backups must be stored in Amazon S3 for long-term retention. Which AWS service can be used to schedule and manage these backups?

A.AWS Storage Gateway
B.AWS Database Migration Service (DMS)
C.AWS Backup
D.Amazon S3 Lifecycle policies
AnswerC

AWS Backup can schedule and manage backups of SAP HANA databases on EC2, supporting application-consistent backups.

Why this answer

AWS Backup (Option C) is the correct service for automating backups of SAP HANA databases on EC2, supporting application-consistent backups via pre- and post-scripts and storing them in S3 for long-term retention. Option A (Storage Gateway) is for hybrid storage integration, not backup automation. Option B (DMS) is for database migration, not backup.

Option D (S3 Lifecycle policies) manage object lifecycle, not scheduling backups.

Full explanation →
1223
Multi-Selectmedium

A company is migrating a SAP HANA database to AWS. Which THREE factors should be considered when choosing the EC2 instance type for SAP HANA?

Select 3 answers
A.The instance must be listed in the SAP HANA certified instance list.
B.The instance must have enough memory (RAM) to hold the entire HANA database.
C.The instance must have a GPU for accelerated processing.
D.The instance must be EBS-optimized by default.
E.The instance must have high network bandwidth for SAP HANA system replication.
AnswersA, B, E

Only certified instances support HANA.

Why this answer

Correct options: A, B, E. SAP HANA requires AWS certified instance types (A), enough memory to hold the database in RAM (B), and high network bandwidth for system replication (E). GPU is not required (C).

EBS-optimized is not a selection factor; it is a feature that may be enabled on certain instance types but not a primary consideration for choosing the instance type (D).

Exam trap

A common trap is to think that EBS-optimized is a requirement, but it is not; what matters is the instance being certified and having sufficient memory and network bandwidth.

Full explanation →
1224
Multi-Selecthard

A company runs SAP on AWS and uses SAP HANA as its database. The system is experiencing high latency during peak hours. The SAP HANA administrator wants to identify performance bottlenecks at the CPU, memory, and disk I/O levels. Which TWO AWS services can be used together to monitor and correlate these metrics?

Select 2 answers
A.AWS Config
B.Amazon CloudWatch Logs
C.Amazon Inspector
D.Amazon CloudWatch
E.AWS X-Ray
AnswersB, D

CloudWatch Logs can ingest HANA traces for correlation.

Why this answer

Amazon CloudWatch (Option D) collects and stores CPU, memory, and disk I/O metrics from SAP HANA instances via the CloudWatch Agent or direct integration. Amazon CloudWatch Logs (Option B) ingests SAP HANA diagnostic logs, such as trace files and performance dumps, enabling correlation of log events with metric spikes. Together, they provide a unified view to pinpoint bottlenecks at the CPU, memory, and I/O levels during peak hours.

Exam trap

The trap here is that candidates often confuse AWS X-Ray (application tracing) with infrastructure-level monitoring, or assume AWS Config can track performance metrics, when in fact only CloudWatch and CloudWatch Logs together provide the necessary metric and log correlation for SAP HANA bottleneck analysis.

Full explanation →
1225
MCQeasy

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

A.Amazon Inspector
B.AWS Config
C.AWS Pricing Calculator
D.AWS Trusted Advisor
AnswerC

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Full explanation →
1226
MCQmedium

A company is deploying SAP NetWeaver on AWS and wants to use Amazon FSx for NetApp ONTAP as the shared file system for the SAP transport directory (/usr/sap/trans). The company needs to ensure that the transport directory is highly available and can be accessed from multiple SAP application servers across different Availability Zones. Which configuration should the SAP administrator use?

A.Use Amazon EFS with a mount target in each AZ.
B.Mount the transport directory from an Amazon EC2 instance running NFS in the same AZ.
C.Store the transport directory in Amazon S3 and use an S3 mount point.
D.Create an FSx for ONTAP file system with Multi-AZ configuration and mount the NFS share on all SAP servers.
AnswerD

FSx for ONTAP Multi-AZ provides HA and cross-AZ access.

Why this answer

Amazon FSx for NetApp ONTAP with Multi-AZ configuration provides a highly available NFS share that can be accessed from SAP application servers across multiple Availability Zones, meeting the requirements for the SAP transport directory. Option A is incorrect because Amazon EFS, while highly available, is not the specified service required by the scenario (FSx for ONTAP is explicitly mentioned). Option B is incorrect because mounting from a single EC2 instance is not highly available and introduces a single point of failure.

Option C is incorrect because Amazon S3 is not a POSIX-compliant file system and is not suitable for SAP transport directories.

Full explanation →
1227
Multi-Selecthard

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

Select 3 answers
A.Warm standby with a fully scaled-down environment that is manually scaled up during DR.
B.Pilot light environment with replicated data volumes that can be attached to EC2 instances in DR.
C.Regular backup of SAP systems to Amazon S3 and restore in another region.
D.SAP HANA System Replication across AWS Regions.
E.Multi-site active-active with real-time replication and automatic failover.
AnswersB, C, D

Pilot light uses replicated data that can be quickly activated.

Why this answer

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

Exam trap

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

Full explanation →
1228
Multi-Selectmedium

A company is designing an SAP HANA disaster recovery solution using SAP HANA System Replication. Which TWO AWS services are required to enable automatic failover across AWS Regions?

Select 2 answers
A.AWS Elastic Load Balancing (NLB)
B.AWS Direct Connect
C.AWS CloudFormation
D.AWS Route 53
E.AWS Shield
AnswersA, D

NLB can be used with a static IP and health checks to route traffic to the active HANA instance.

Why this answer

AWS Route 53 provides DNS-based failover routing to redirect traffic to the DR region. AWS Elastic Load Balancing (NLB) is used to distribute traffic to the HANA instances and can be used with a floating IP. AWS Direct Connect is not required.

AWS CloudFormation is not needed for automatic failover. AWS Shield is for DDoS protection.

Full explanation →
1229
Multi-Selectmedium

A company is running SAP ERP on AWS and wants to implement a disaster recovery (DR) strategy with a Recovery Point Objective (RPO) of 15 minutes and Recovery Time Objective (RTO) of 2 hours. The primary site is in us-east-1, and the DR site is in us-west-2. Which TWO AWS features should be combined to achieve this? (Choose TWO.)

Select 2 answers
A.Amazon RDS Multi-Region replication
B.Amazon S3 Cross-Region Replication for database backups
C.AWS CloudEndure Disaster Recovery
D.Amazon EBS Multi-AZ snapshots
E.EC2 AMI Copy to copy server images to the DR region
AnswersB, E

S3 CRR can replicate backups to the DR region with low RPO.

Why this answer

Amazon S3 Cross-Region Replication (CRR) for database backups ensures that backup files are automatically replicated to the DR region within minutes, supporting an RPO of 15 minutes. EC2 AMI Copy allows you to copy pre-configured server images (including OS and SAP application layers) to the DR region, enabling rapid recovery of EC2 instances within the 2-hour RTO. Together, these two features provide a cost-effective, fully automated DR solution for SAP on AWS without requiring third-party tools.

Exam trap

The trap here is that candidates often confuse AWS CloudEndure Disaster Recovery (a third-party tool) with a native AWS feature, or they mistakenly think Amazon RDS Multi-Region replication applies to SAP ERP databases, which are typically self-managed on EC2, not RDS.

Full explanation →
1230
MCQmedium

An SAP system running on AWS is experiencing performance degradation. The system uses a shared file system for /sapmnt and /usr/sap/trans. The file system is hosted on an Amazon EFS file system. Which configuration change is most likely to improve throughput for these file systems?

A.Change the EFS performance mode to Max I/O to support higher levels of aggregate throughput and operations per second.
B.Increase the Provisioned Throughput of the EFS file system.
C.Switch the EFS file system to General Purpose (Burstable) performance mode.
D.Enable burst credits on the EFS file system to handle peak loads.
AnswerA

Max I/O mode is designed for large-scale, parallel workloads like SAP shared directories.

Why this answer

Amazon EFS Max I/O performance mode is designed for workloads with high throughput and parallel operations, such as SAP shared file systems for /sapmnt and /usr/sap/trans. Option B (Provisioned Throughput) provides consistent throughput but is not specifically optimized for parallel access and may incur additional cost. Option C (General Purpose Burstable) is the default mode, which is suitable for lower throughput workloads and would not improve performance.

Option D (Enable burst credits) is not a configurable option; EFS automatically uses burst credits when in Burstable mode, so enabling them is not applicable.

Full explanation →
1231
Multi-Selectmedium

Which THREE factors should be considered when selecting an EC2 instance type for an SAP HANA production system?

Select 3 answers
A.Memory (RAM) size
B.SAP certification
C.Network bandwidth
D.Instance store volumes
E.GPU capabilities
AnswersA, B, C

HANA is an in-memory database; RAM size is primary.

Why this answer

The correct answers are A, B, and C. SAP HANA is an in-memory database, so memory size (RAM) is critical. The instance must be SAP-certified to ensure compatibility and performance.

Network bandwidth is important for HANA system replication and data transfer. Option D is incorrect because HANA uses EBS volumes for persistent storage, not instance store (which is ephemeral). Option E is incorrect because GPUs are not required for SAP HANA.

Full explanation →
1232
MCQeasy

A company runs SAP on AWS and needs to ensure that the SAP application logs are centrally collected and analyzed for security incidents. Which AWS service should be used to collect and store the logs from EC2 instances?

A.Amazon Kinesis Data Firehose
B.AWS CloudTrail
C.Amazon S3
D.Amazon CloudWatch Logs
AnswerD

CloudWatch Logs can collect and store application logs from EC2 instances.

Why this answer

Amazon CloudWatch Logs can collect and store application logs from EC2 instances using the unified CloudWatch agent. It provides centralized log management and can be used for security incident analysis. Option A (Amazon Kinesis Data Firehose) is for streaming data to destinations like S3 or Redshift, not primarily for log collection from instances.

Option B (AWS CloudTrail) records API activity, not application logs. Option C (Amazon S3) can store logs but does not directly collect them from EC2 instances without additional services like CloudWatch Logs or Kinesis. Therefore, Amazon CloudWatch Logs is the correct service for collecting and storing SAP application logs from EC2 instances.

Exam trap

Candidates often choose CloudTrail because it logs API calls, but it does not capture application-level logs. CloudWatch Logs is the correct service for collecting custom application logs from EC2 instances.

Full explanation →
1233
MCQmedium

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

A.Attach multiple Elastic Network Interfaces (ENIs) to the HANA instance
B.Configure the HANA database with Amazon RDS Multi-AZ
C.Set up HANA System Replication across two Availability Zones
D.Take EBS snapshots every hour and restore in another AZ
AnswerC

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Full explanation →
1234
MCQeasy

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

A.AWS Quick Start.
B.AWS Service Catalog.
C.AWS OpsWorks.
D.Amazon Elastic Kubernetes Service (EKS).
AnswerA

Quick Starts are reference deployments with CloudFormation templates.

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Full explanation →
1235
MCQhard

A company is migrating SAP HANA to AWS and needs to ensure high availability. The database must be replicated synchronously across two Availability Zones with automatic failover. Which AWS service should be used?

A.SAP HANA System Replication (HSR) with Pacemaker
B.Amazon EBS Multi-Attach volumes
C.AWS Database Migration Service (DMS)
D.Amazon RDS Multi-AZ deployment
AnswerA

HSR with Pacemaker provides synchronous replication and automatic failover.

Why this answer

SAP HANA System Replication (HSR) with Pacemaker provides synchronous replication and automatic failover, making it the appropriate solution for high availability across Availability Zones. Amazon EBS Multi-Attach is incorrect because it is limited to a single AZ and not designed for SAP HANA replication. AWS DMS is for database migration, not ongoing HA.

Amazon RDS Multi-AZ is for RDS databases and does not support SAP HANA.

Full explanation →
1236
MCQeasy

A company is migrating an on-premises Oracle database to Amazon RDS for Oracle. They want to minimize downtime and ensure data consistency. Which AWS service should be used for the migration?

A.AWS Schema Conversion Tool (SCT)
B.AWS Database Migration Service (DMS)
C.AWS Server Migration Service (SMS)
D.AWS DataSync
AnswerB

DMS performs live data migration with minimal downtime.

Why this answer

AWS Database Migration Service (DMS) is designed for minimal-downtime database migrations. Option B is correct. Option A (SCT) is used for schema conversion, not the migration itself.

Option C (Server Migration Service) is for server-level migrations. Option D (DataSync) is for file-based data transfer.

Full explanation →
1237
MCQhard

A company has deployed its SAP S/4HANA system on AWS in a single Availability Zone. The system consists of a primary application server (PAS), additional application servers (AAS), and a HANA database server, all running on EC2 instances. The company is experiencing occasional performance degradation during peak hours. The CloudWatch metrics show that the database server's CPU utilization spikes to 90% during these periods, while the application servers' CPU remains below 50%. The storage is configured with two EBS io1 volumes (each 1 TB, 10,000 IOPS) for HANA data and one io1 volume (500 GB, 5,000 IOPS) for log. The network throughput is not saturated. The company wants to resolve the performance issue without increasing costs significantly. Which course of action should the company take?

A.Implement SAP HANA System Replication with a secondary node in the same AZ to offload read operations.
B.Increase the Provisioned IOPS on the data volumes to 20,000 each.
C.Switch the EBS volumes from io1 to gp3 to reduce latency.
D.Upgrade the database instance to a larger type, such as r5.12xlarge.
AnswerA

HSR allows read workloads to be redirected to the secondary, reducing CPU on primary.

Why this answer

Implementing SAP HANA System Replication with a secondary node in the same Availability Zone allows read-only queries to be offloaded to the secondary node, reducing CPU load on the primary database server. This directly addresses the CPU spike during peak hours without significantly increasing costs. Option B is wrong because the performance issue is CPU-bound, not I/O-bound; increasing IOPS would add cost without resolving the CPU bottleneck.

Option C is wrong because switching from io1 to gp3 may reduce storage costs but does not improve CPU performance. Option D is wrong because upgrading to a larger instance is expensive and may not be necessary if HSR can distribute the load effectively.

Full explanation →
1238
MCQeasy

Solutions Architect needs to automate the patching of Amazon EC2 instances running Amazon Linux 2. The instances are in an Auto Scaling group and must be patched without downtime. Which approach is BEST?

A.Use Amazon Inspector to scan for vulnerabilities and automatically apply patches.
B.Terminate all instances and let the Auto Scaling group launch new instances from a patched AMI.
C.Use AWS Systems Manager Patch Manager with a maintenance window and update the Auto Scaling group launch configuration to use a patched AMI for new instances.
D.Create a custom AMI with latest patches and update the Auto Scaling group manually during a maintenance window.
AnswerC

Patch Manager applies patches and rolling updates minimize downtime.

Why this answer

AWS Systems Manager Patch Manager automates patching of existing EC2 instances without downtime by using a maintenance window to schedule patch installation, and updating the Auto Scaling group launch configuration ensures new instances launched by the group use a patched AMI, maintaining consistency. This approach avoids terminating all instances at once (which would cause downtime) and leverages AWS-native automation for ongoing compliance.

Exam trap

The trap here is that candidates may think Amazon Inspector can automatically patch instances (option A) because it integrates with Systems Manager, but Inspector only scans and reports vulnerabilities, not applying patches directly.

How to eliminate wrong answers

Option A is wrong because Amazon Inspector is a vulnerability assessment service that identifies security issues but does not automatically apply patches; it integrates with Systems Manager for remediation but cannot patch instances on its own. Option B is wrong because terminating all instances in an Auto Scaling group simultaneously would cause downtime, as the group would need to launch new instances from a patched AMI, which violates the 'no downtime' requirement. Option D is wrong because creating a custom AMI and manually updating the Auto Scaling group during a maintenance window is not automated and does not address patching of existing running instances, only new ones; it also requires manual intervention, which is less reliable and scalable than the automated approach in option C.

Full explanation →
1239
Multi-Selectmedium

Which TWO actions are required to set up automated failover for an SAP HANA database using AWS services? (Choose TWO.)

Select 2 answers
A.Create an AWS Lambda function to reassign an Elastic IP address to the standby instance
B.Configure a CloudWatch alarm to detect database failure
C.Use an Amazon RDS Multi-AZ deployment for the HANA database
D.Schedule a snapshot and restore on failure
E.Store HANA data on Amazon EFS and mount it on both instances
AnswersA, B

Lambda can automate the IP reassignment during failover.

Why this answer

Automated failover requires detecting failure and reassigning resources. CloudWatch alarms can detect database unavailability and trigger a Lambda to reassign the Elastic IP to the standby instance. Stopping the primary is unnecessary and might not be desired.

Multi-AZ RDS is for non-HANA databases. EFS is not typically used for HANA failover. Snapshot restore is too slow for automated failover.

Full explanation →
1240
MCQhard

A company runs SAP ERP on AWS with a two-tier architecture: application and database on the same EC2 instance. The instance is part of an Auto Scaling group with a minimum of 1 and maximum of 1, so it's effectively a single instance. The operations team wants to implement a patching strategy for the operating system that minimizes downtime. They need to apply security patches quarterly. Which approach should they take?

A.Use AWS Systems Manager Patch Manager to apply patches during a maintenance window.
B.Use AWS Systems Manager Automation to create a new AMI, launch a new instance, and update the DNS record.
C.Create a second instance in the Auto Scaling group and detach the original.
D.Apply patches in-place using yum update and reboot the instance.
AnswerB

This blue/green deployment minimizes downtime.

Why this answer

The best approach for minimizing downtime when patching a single-instance SAP ERP system on AWS. Using AWS Systems Manager Automation to create a new AMI, launch a new instance, and update the DNS record allows a controlled replacement with minimal downtime, as the new instance is fully prepared before switching traffic. Option A (Patch Manager) applies patches in-place, which still requires a reboot and thus downtime.

Option C (creating a second instance in the Auto Scaling group) is not feasible because the architecture is two-tier (application and database on same instance), and simply adding a second instance without proper data synchronization would cause data inconsistency. Option D (in-place yum update and reboot) also requires downtime and does not provide a rollback mechanism.

Full explanation →
1241
MCQhard

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

A.Add more EBS volumes with higher IOPS to offload CPU.
B.Launch additional r5.8xlarge instances and configure HANA scale-out.
C.Configure Auto Scaling to add instances during peak load.
D.Resize the instance to a larger instance type in the r5 family.
AnswerD

Larger instance type provides more CPU cores.

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Full explanation →
1242
MCQhard

A company runs SAP on AWS and uses a distributed deployment with multiple application servers in an Auto Scaling group. They want to ensure that when a new instance is launched, it is automatically registered with the SAP Central Services instance. Which approach should they use?

A.Configure the user data script to run the registration command on instance boot.
B.Use an AWS CloudFormation template to create the instance and include the registration in the template.
C.Use AWS Systems Manager Run Command to register the instance after it launches.
D.Use an Auto Scaling lifecycle hook that triggers a Lambda function to perform the registration when the instance enters the 'InService' state.
AnswerD

An Auto Scaling lifecycle hook pauses the instance in the 'InService' state and triggers a Lambda function to perform registration, ensuring the instance is registered before it receives traffic.

Why this answer

Auto Scaling lifecycle hooks allow you to pause an instance during launch and perform custom actions, such as invoking a Lambda function to register the instance with SAP Central Services, before the instance is placed in service. Option A is incorrect because user data runs at boot but does not integrate with the Auto Scaling lifecycle to ensure registration completes before the instance becomes healthy. Option B is incorrect because CloudFormation is used for infrastructure provisioning and not for per-instance registration triggered by scaling events.

Option C is incorrect because AWS Systems Manager Run Command is not automatically triggered during Auto Scaling launches; it requires manual or scheduled execution.

Exam trap

Candidates often confuse user data with lifecycle hooks. User data runs at boot but does not pause the instance lifecycle, so it cannot guarantee registration before the instance becomes healthy. A lifecycle hook with a Lambda function ensures registration completes before the instance is marked 'InService'.

Full explanation →
1243
Multi-Selecteasy

Which TWO AWS services can be used to automate the patching of SAP application servers?

Select 2 answers
A.AWS CloudFormation
B.AWS Systems Manager Patch Manager
C.Amazon EC2 Auto Scaling
D.AWS Lambda
E.AWS Elastic Beanstalk
AnswersB, D

Patch Manager automates patching.

Why this answer

AWS Systems Manager Patch Manager (Option B) is correct because it provides a fully managed service specifically designed to automate the process of patching operating systems and applications, including SAP application servers running on EC2 instances. It uses patch baselines to define approved patches and can schedule patching across multiple instances, ensuring SAP systems remain compliant without manual intervention.

Exam trap

The trap here is that candidates may confuse infrastructure automation (CloudFormation, Auto Scaling) with operational patching, or assume Elastic Beanstalk can manage SAP workloads, when in fact only Systems Manager Patch Manager and Lambda (for custom orchestration) are directly applicable for automating SAP patching.

Full explanation →
1244
MCQmedium

A company runs SAP on AWS and needs to patch the operating system of multiple EC2 instances on a schedule. The instances are part of an Auto Scaling group. Which AWS service can be used to apply patches without disrupting the Auto Scaling group's desired capacity?

A.AWS Systems Manager Patch Manager
B.Amazon EC2 Auto Scaling
C.AWS CloudFormation
D.AWS CodeDeploy
AnswerA

Patch Manager automates OS patching on a schedule.

Why this answer

AWS Systems Manager Patch Manager can be used to apply OS patches to EC2 instances on a schedule. It integrates with Auto Scaling groups to maintain desired capacity, for example by using instance refresh to roll out patches without disrupting the group's capacity. Option B (Amazon EC2 Auto Scaling) is incorrect because it manages scaling, not patching.

Option C (AWS CloudFormation) is incorrect because it is used for infrastructure provisioning, not patching. Option D (AWS CodeDeploy) is incorrect because it is for application deployments, not OS patching.

Full explanation →
1245
Multi-Selecteasy

Which TWO components are typically migrated as part of an SAP workload migration to AWS?

Select 2 answers
A.AWS KMS encryption keys.
B.SAP Central Services (ASCS/SCS).
C.AWS Direct Connect virtual interface.
D.IAM roles and policies.
E.SAP HANA database.
AnswersB, E

Application services are migrated.

Why this answer

When migrating an SAP workload to AWS, the key components that are typically migrated include SAP Central Services (ASCS/SCS) and the SAP HANA database. These are core parts of the SAP system. Option A is incorrect because AWS KMS encryption keys are infrastructure security components, not part of the workload itself.

Option C is incorrect because AWS Direct Connect is a network connectivity service, not migrated. Option D is incorrect because IAM roles and policies are AWS access control mechanisms, not workload components.

Full explanation →
1246
MCQeasy

A company is running SAP on AWS and wants to automatically recover an unhealthy EC2 instance that hosts their SAP application. Which AWS feature should they configure to automatically restart the instance in the same Availability Zone if it fails?

A.Cluster Placement Group
B.Auto Scaling group
C.EC2 Auto Recovery
D.Lifecycle Hook
AnswerC

Auto Recovery restarts the same instance in the same AZ.

Why this answer

(EC2 Auto Recovery) is correct because EC2 Auto Recovery automatically recovers an impaired EC2 instance in the same Availability Zone, which matches the requirement. Option A is wrong because a Cluster Placement Group is a logical grouping of instances within a single AZ to achieve low-latency network performance, not for automatic recovery. Option B is wrong because an Auto Scaling group is used for scaling and replacing instances based on demand, but it may launch instances in different AZs, not necessarily the same AZ.

Option D is wrong because a Lifecycle Hook is used to perform custom actions when instances are launched or terminated by Auto Scaling, not for automatic recovery of a single instance.

Full explanation →
1247
MCQmedium

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

A.AWS Database Migration Service with ongoing replication.
B.Amazon EBS Snapshots copied to us-west-2 every hour.
C.Amazon S3 Cross-Region Replication for HANA data files.
D.SAP HANA System Replication to an EC2 instance in us-west-2.
AnswerD

HANA System Replication provides near real-time replication.

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Full explanation →
1248
MCQhard

A company is migrating an SAP Business Suite system on Oracle to SAP S/4HANA on AWS. The migration involves a near-zero downtime requirement. The current system uses SAP Oracle on Linux. Which combination of tools should the company use?

A.Use AWS Schema Conversion Tool (AWS SCT) and AWS Database Migration Service (AWS DMS) with ongoing replication.
B.Use AWS Database Migration Service (AWS DMS) to migrate the Oracle database to Amazon RDS for SAP HANA.
C.Use SAP Landscape Transformation (SLT) to replicate data to SAP HANA, then switch applications.
D.Use SAP Software Update Manager (SUM) with the Database Migration Option (DMO) and the near-zero downtime option.
AnswerD

SUM DMO with NZDT is the SAP-recommended approach for near-zero downtime migration to S/4HANA.

Why this answer

For migrating an SAP Business Suite on Oracle to SAP S/4HANA with near-zero downtime, the recommended tool is SAP Software Update Manager (SUM) with the Database Migration Option (DMO) and the near-zero downtime (NZDT) option. This allows for a combined system upgrade and database migration with minimal downtime. Option A is incorrect because AWS SCT is not designed for SAP HANA migrations.

Option B is incorrect because AWS DMS does not support SAP HANA as a target. Option C is incorrect because SLT is used for data replication, not for system conversion or migration.

Full explanation →
1249
MCQeasy

An SAP system needs to send email notifications from the SAP application server running on EC2. Which AWS service should be used?

A.Amazon Simple Email Service (SES)
B.Amazon Pinpoint
C.Amazon Simple Queue Service (SQS)
D.Amazon Simple Notification Service (SNS)
AnswerA

SES is designed for sending email from applications.

Why this answer

Amazon Simple Email Service (SES) is the correct choice because it is a cloud-based email sending service designed specifically for sending transactional and notification emails from applications, including SAP systems running on EC2. SES supports SMTP and API-based integration, allowing the SAP application server to send outbound email notifications reliably without managing on-premises email infrastructure.

Exam trap

The trap here is that candidates often confuse SNS with SES because both can send email, but SNS is a pub/sub messaging service with limited email formatting and no SMTP support, whereas SES is the correct service for application-to-user transactional email.

How to eliminate wrong answers

Option B (Amazon Pinpoint) is wrong because Pinpoint is a marketing and engagement service focused on targeted campaigns, analytics, and multi-channel messaging (email, SMS, push), not a simple transactional email service for application notifications. Option C (Amazon Simple Queue Service) is wrong because SQS is a message queuing service for decoupling application components, not an email sending service. Option D (Amazon Simple Notification Service) is wrong because SNS is a pub/sub messaging service that can send notifications via SMS, email, or HTTP endpoints, but it is not designed for high-volume transactional email sending with SMTP integration; SES is the dedicated email service for such use cases.

Full explanation →
1250
MCQhard

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

A.Purchase Reserved Instances for the current usage to get a discount
B.Increase the instance size to improve performance and reduce runtime
C.Use EC2 Spot Instances for the application servers and configure them to be terminated gracefully
D.Use Dedicated Hosts to reduce licensing costs
AnswerC

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Full explanation →
1251
MCQeasy

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

A.AWS Database Migration Service (DMS)
B.Application Load Balancer (ALB)
C.Amazon RDS Multi-AZ
D.SAP HANA System Replication (HSR)
AnswerD

HSR provides synchronous replication and automatic failover for HANA.

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Full explanation →
1252
MCQeasy

Refer to the exhibit. An SAP administrator has created this CloudFormation snippet to create a Route 53 record for an SAP system. The record is intended to point to an Application Load Balancer. What is a potential issue with this configuration?

A.Using a CNAME record for the root domain (zone apex) is not allowed.
B.The TTL value of 60 seconds is too low for production use.
C.The RecordSet type should be A instead of CNAME for an ALB.
D.The ResourceRecords value should be an IP address, not a DNS name.
AnswerA

DNS standards prohibit CNAME at the zone apex; an Alias record should be used instead.

Why this answer

DNS standards prohibit using a CNAME record at the zone apex (root domain, e.g., example.com) because it would conflict with the SOA and NS records required for the zone. Route 53 does not allow CNAME records for the root domain. Option B is incorrect because a TTL of 60 seconds is acceptable for dynamic environments.

Option C is incorrect because an ALB endpoint is a DNS name, not an IP address, so an A record cannot be used; Route 53 supports alias records for ALBs, but the snippet uses a CNAME. Option D is incorrect because the ResourceRecords value for a CNAME record must be a DNS name, not an IP address.

Full explanation →
1253
MCQmedium

A company is migrating an SAP BW system to AWS. The source runs on Oracle. The target is SAP HANA. Which AWS service can help with the migration of custom ABAP code and stored procedures?

A.AWS Schema Conversion Tool (AWS SCT)
B.SAP HANA Studio
C.SAP DMO
D.AWS Database Migration Service (AWS DMS)
AnswerA

SCT can convert stored procedures and ABAP code to SQLScript.

Why this answer

AWS SCT can convert Oracle PL/SQL and ABAP code to SAP HANA SQLScript. SAP HANA Studio can manually rewrite but not automate. AWS DMS does not handle code.

SAP DMO is for system migration but may not convert custom code as efficiently as SCT.

Full explanation →
1254
MCQhard

An SAP system administrator notices that the SAP Central Services (ASCS) instance on an EC2 instance has failed. The instance is still running, but the ASCS service is unresponsive. What is the MOST efficient way to restore the ASCS service without affecting the SAP application?

A.Manually fail over the ASCS to the secondary node in the cluster.
B.Reboot the EC2 instance hosting the ASCS.
C.Restore the ASCS instance from the most recent AMI backup.
D.Restart the ASCS service using SAP MMC or sapcontrol.
AnswerD

Restarting the ASCS service using SAP MMC or sapcontrol directly targets the failed service, is quick, and minimizes impact on the SAP application.

Why this answer

The most efficient way to restore the ASCS service without affecting the SAP application is to restart the ASCS service using SAP MMC or sapcontrol (Option D). This action is quick and minimally disruptive, as it only restarts the service without impacting the underlying EC2 instance or requiring failover procedures.

Option A (fail over to secondary node) is less efficient because it requires a properly configured cluster environment and may take longer to orchestrate, and it may not be necessary if the primary node's service can be restarted.

Option B (reboot the EC2 instance) is inefficient and disruptive because it restarts the entire instance, affecting all services and potentially causing downtime for the SAP application.

Option C (restore from AMI backup) is the most time-consuming and resource-intensive approach, and is only appropriate if the instance or service is corrupt and cannot be recovered by restarting.

Full explanation →
1255
MCQhard

An SAP administrator is restoring an SAP HANA database from a backup stored in Amazon S3. The restore fails with an error indicating that the backup file is corrupt. The backup was created using the SAP HANA BACKUP command with the S3 backint agent. What could cause the backup file to be corrupt?

A.S3 Transfer Acceleration was used during backup.
B.The multipart upload of the backup file was interrupted and not completed.
C.The S3 bucket has versioning enabled.
D.The backup was replicated to another AWS Region using S3 Cross-Region Replication.
AnswerB

Incomplete multipart upload results in a corrupt object.

Why this answer

When using the SAP HANA backint agent to back up to S3, the backup file is uploaded via multipart upload. If this multipart upload is interrupted and not completed, the resulting object in S3 will be incomplete, causing it to appear corrupt when attempting to restore. Option A is incorrect because S3 Transfer Acceleration improves transfer speed but does not affect file integrity.

Option C is incorrect because S3 Versioning creates multiple versions of the same object but does not corrupt data. Option D is incorrect because S3 Cross-Region Replication creates identical copies of the object, so it would not introduce corruption.

Full explanation →
1256
MCQeasy

Refer to the exhibit. A CloudTrail log entry shows that the user 'sapadmin' stopped an instance. Which of the following is true based on the log?

A.The StopInstances API call failed.
B.The user 'sapadmin' started the instance.
C.The user 'sapadmin' stopped the instance i-0abcdef1234567890.
D.The event was related to an RDS instance.
AnswerC

The log shows the event name and user.

Why this answer

The eventName is StopInstances and the user is sapadmin, meaning the user successfully stopped instance i-0abcdef1234567890. Options A and B are incorrect: A is wrong because there is no error code, indicating the API call succeeded; B is wrong because the eventName is StopInstances, not StartInstances. Option D is wrong because the eventSource is ec2.amazonaws.com, indicating an EC2 instance, not an RDS instance.

Full explanation →
1257
MCQmedium

A company is migrating its SAP NetWeaver system to AWS. The system uses an Oracle database. The company wants to use the SAP Software Provisioning Manager (SWPM) to perform a system copy. The target database will be Amazon RDS for Oracle. Which of the following backup types can be used as the source for the SWPM system copy?

A.An Oracle Data Pump export
B.An AWS DMS snapshot of the Oracle database
C.An Oracle Export utility (exp) dump
D.An Oracle RMAN backup
AnswerD

SWPM accepts RMAN backups as source.

Why this answer

SAP Software Provisioning Manager (SWPM) supports using Oracle Recovery Manager (RMAN) backups as the source for a system copy to Amazon RDS for Oracle. Options A, B, and C are incorrect because SWPM does not support Oracle Data Pump exports, AWS DMS snapshots, or Oracle Export utility dumps as direct input for the system copy process.

Full explanation →
1258
MCQhard

An SAP system administrator notices that an SAP S/4HANA system on AWS is experiencing high network latency between the application server and the database server. Both servers are in the same VPC but in different Availability Zones. What is the most effective way to reduce latency?

A.Set up VPC peering between the two subnets.
B.Deploy AWS Global Accelerator to optimize the traffic path.
C.Add multiple Elastic Network Interfaces (ENIs) to the instances.
D.Launch both instances in the same placement group and enable EBS optimization.
AnswerD

Placement groups ensure low-latency network performance between instances, and EBS optimization dedicates bandwidth for storage traffic.

Why this answer

Launching both instances in the same placement group ensures they are in close physical proximity within the same Availability Zone, which minimizes network latency. Enabling EBS-optimized instances dedicates network bandwidth to EBS I/O, reducing contention and further improving database performance. This directly addresses the high latency caused by cross-AZ traffic between the SAP application and database servers.

Exam trap

The trap here is that candidates often assume cross-AZ latency can be solved by network optimizations like VPC peering or Global Accelerator, but the fundamental fix is to co-locate the instances in the same Availability Zone using a placement group.

How to eliminate wrong answers

Option A is wrong because VPC peering connects separate VPCs, not subnets within the same VPC, and does not reduce latency between instances already in the same VPC. Option B is wrong because AWS Global Accelerator improves latency by routing traffic over the AWS global network for internet-facing applications, but it does not optimize traffic within a single VPC between two EC2 instances. Option C is wrong because adding multiple ENIs increases network throughput and allows for separate traffic flows, but it does not reduce the physical distance or cross-AZ latency between instances.

Full explanation →
1259
MCQeasy

A company is running a critical SAP application on SAP HANA in an AWS Single-AZ deployment. The application has experienced downtime twice in the last month due to underlying hardware failures. What is the MOST cost-effective solution to minimize future downtime without compromising performance?

A.Move the SAP HANA instance to a larger instance type to improve hardware reliability.
B.Deploy the SAP HANA database in a Multi-AZ configuration using SAP HANA System Replication (HSR) across Availability Zones.
C.Use Dedicated Hosts to ensure physical isolation from other AWS customers.
D.Implement automated snapshots of the SAP HANA data volume and restore in case of failure.
AnswerB

Deploy the SAP HANA database in a Multi-AZ configuration using SAP HANA System Replication (HSR) across Availability Zones, providing automatic failover without downtime.

Why this answer

Deploying SAP HANA in a Multi-AZ configuration using SAP HANA System Replication (HSR) across Availability Zones provides synchronous replication and automatic failover in case of hardware failure. This minimizes downtime without requiring a larger instance or manual intervention, and maintains performance by using the same instance type and storage configuration as the primary.

Exam trap

The trap here is that candidates often confuse AWS RDS Multi-AZ with SAP HANA's HA approach. SAP HANA uses its own System Replication (HSR) across AZs, not a managed AWS service like Multi-AZ DB instance. The key is understanding that AWS provides infrastructure for HSR, but the replication is managed by SAP HANA itself.

How to eliminate wrong answers

Option A is wrong because moving to a larger instance type does not inherently improve hardware reliability; larger instances still run on a single physical host and are subject to the same failure risks, so this does not address the root cause of downtime. Option C is wrong because Dedicated Hosts provide physical isolation from other AWS customers but do not eliminate the risk of hardware failure on that single host; they do not offer automatic failover or redundancy across Availability Zones. Option D is wrong because automated snapshots are point-in-time backups that require manual restoration and significant recovery time (RTO), which does not minimize downtime as effectively as an active-passive Multi-AZ failover that occurs automatically within minutes.

Full explanation →
1260
Multi-Selecthard

Which TWO components are required to set up SAP HANA System Replication (HSR) on AWS for high availability? (Choose TWO.)

Select 2 answers
A.A dedicated replication network interface with low latency.
B.Two EC2 instances in different Availability Zones.
C.An Amazon S3 bucket for storing backup logs.
D.Shared storage (e.g., Amazon EFS) for log replication.
E.A Network Load Balancer to distribute database connections.
AnswersA, B

A dedicated replication network interface ensures low latency and high throughput for HSR traffic, and is a required component.

Why this answer

SAP HANA System Replication (HSR) on AWS requires two EC2 instances in different Availability Zones (B) to provide failure domain isolation, and a dedicated replication network interface with low latency (A) to handle replication traffic separately from client traffic. Shared storage like Amazon EFS (D) is not required because HSR uses direct log shipping from primary to secondary instance, not a shared file system. The replication is done over the network, making shared storage unnecessary.

Full explanation →
1261
MCQeasy

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

A.Install the AWS Systems Manager Agent (SSM Agent) on the HANA host.
B.Create a backup vault in AWS Backup.
C.Mount an Amazon EFS file system to the HANA host for backup storage.
D.Configure AWS Database Migration Service (DMS) to replicate data to S3.
AnswerA

SSM Agent is required to run the Backint installation document.

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Full explanation →
1262
Multi-Selecteasy

Which TWO AWS services can be used to automate the backup of SAP HANA databases? (Choose two.)

Select 2 answers
A.Amazon RDS
B.AWS Lambda
C.AWS Storage Gateway
D.AWS Backup
E.SAP HANA Backint agent for Amazon S3
AnswersD, E

AWS Backup can schedule and manage EBS snapshots for HANA volumes.

Why this answer

AWS Backup is a fully managed backup service that supports SAP HANA databases on Amazon EC2 through the AWS Backup Gateway and integration with the SAP HANA Backint agent. It provides centralized backup management, automated scheduling, and lifecycle policies, making it a correct choice for automating SAP HANA backups.

Exam trap

The trap here is that candidates may confuse AWS Lambda's ability to run custom backup scripts with being a native backup automation service, but AWS Backup is the intended managed service for SAP HANA backup automation, and the SAP HANA Backint agent for Amazon S3 is a direct integration tool for database-level backups.

Full explanation →
1263
Multi-Selecteasy

Which THREE actions should be taken to secure an SAP environment running on AWS?

Select 3 answers
A.Open all ports to allow any traffic for flexibility.
B.Disable AWS CloudTrail to reduce costs.
C.Enable encryption at rest for Amazon EBS volumes.
D.Use security groups to restrict inbound and outbound traffic to necessary ports.
E.Use AWS Identity and Access Management (IAM) roles to grant permissions to EC2 instances.
AnswersC, D, E

Encryption protects data stored on EBS.

Why this answer

Options C, D, and E are correct. Option C (Enable encryption at rest for Amazon EBS volumes) protects data. Option D (Use security groups to restrict inbound and outbound traffic to necessary ports) controls network access.

Option E (Use AWS Identity and Access Management (IAM) roles to grant permissions to EC2 instances) avoids long-term credentials. Option A (Open all ports) is insecure. Option B (Disable AWS CloudTrail) reduces auditability.

Full explanation →
1264
MCQeasy

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

A.VPC peering between the application and database subnets.
B.Placement groups for the application and database instances.
C.AWS Direct Connect to connect the application and database servers.
D.AWS Transit Gateway to connect the application and database subnets.
AnswerB

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Full explanation →
1265
MCQeasy

A company is migrating its SAP ERP system to AWS and wants to use SAP HANA as the database. Which AWS service can be used to automate the installation and configuration of SAP HANA?

A.AWS CodePipeline
B.AWS CloudFormation
C.AWS OpsWorks
D.AWS Systems Manager
AnswerD

Systems Manager automates tasks via runbooks and can install SAP HANA.

Why this answer

AWS Systems Manager provides the capability to automate the installation and configuration of SAP HANA through its Automation and Run Command features, which can execute custom scripts and workflows. Specifically, AWS offers pre-built Automation documents (e.g., AWS-ConfigureSAP) and integration with SAP Landscape Management to streamline SAP HANA deployment on EC2 instances. This makes Systems Manager the correct choice for automating SAP HANA setup in a migration context.

Exam trap

The trap here is that candidates often confuse AWS CloudFormation's ability to provision EC2 instances with the ability to install and configure SAP HANA, overlooking that CloudFormation alone cannot run the SAP HANA installer or apply OS-level tuning without additional automation like Systems Manager or custom scripts.

How to eliminate wrong answers

Option A is wrong because AWS CodePipeline is a continuous delivery service for building, testing, and deploying application code, not for automating OS-level or database installation tasks like SAP HANA. Option B is wrong because AWS CloudFormation is an Infrastructure as Code (IaC) service that provisions and manages AWS resources (e.g., EC2, VPC) but does not natively handle the installation or configuration of SAP HANA software on those resources without custom scripts or additional tools. Option C is wrong because AWS OpsWorks is a configuration management service based on Chef and Puppet, which is not designed or optimized for SAP HANA deployment; SAP HANA requires specific kernel parameters, file system layouts, and SAP-specific automation that Systems Manager handles more directly.

Full explanation →
1266
MCQhard

A company runs its SAP ERP system on AWS using SAP HANA as the database. The HANA database is deployed on an EC2 instance with 488 GiB of memory. The system has been running for months, but recently the application team reported that some queries are taking significantly longer than usual. The operations team checks the CloudWatch metrics and sees that the database instance's CPU utilization is consistently above 90% during peak hours. They also notice that the EBS volume used for HANA data files has a read latency of over 20 ms. The volume is a gp3 volume with 16,000 IOPS. The instance type is an x1e.8xlarge. The team suspects that the instance is not optimized for the workload. What should they do to resolve the performance issue?

A.Change the EBS volume type to gp2 with a larger size.
B.Increase the gp3 volume IOPS to 32,000 to reduce read latency.
C.Replace the instance with an x1e.16xlarge instance to increase CPU and memory capacity.
D.Enable EBS optimization on the EC2 instance.
AnswerC

Upgrading to x1e.16xlarge provides double the vCPUs and memory (976 GiB), directly addressing the CPU bottleneck and providing more memory for HANA, even though the stated 2 TB memory requirement cannot be met by any x1e instance. This is the best option among those provided.

Why this answer

The x1e.8xlarge instance provides 4 vCPUs and 488 GiB of memory, which are insufficient for the workload causing consistently high CPU utilization. Upgrading to an x1e.16xlarge instance increases vCPUs to 8 and memory to 976 GiB, directly addressing the CPU bottleneck and memory pressure. The high EBS read latency may be a secondary effect of the overloaded instance, and additional capacity can help alleviate storage performance issues.

Option A is incorrect because changing to gp2 with a larger size does not guarantee lower latency and does not address the CPU constraint. Option B is incorrect because increasing IOPS on the gp3 volume only addresses storage performance, not the compute bottleneck. Option D is incorrect because EBS optimization is enabled by default on x1e instances; there is no additional setting to toggle.

Full explanation →
1267
MCQhard

You are an AWS administrator for a company running SAP S/4HANA on AWS. The system uses a three-tier architecture: web dispatchers, application servers, and a HANA database. All components are in a single VPC. Security requirements demand that the web dispatchers are in a public subnet, application servers in private subnets, and the database in a private subnet. The web dispatchers need to communicate with the application servers on port 443, and application servers communicate with the database on port 31341. You have configured security groups accordingly. However, the web dispatchers cannot connect to the application servers. The network ACL for the public subnet allows inbound HTTPS from the internet and outbound all traffic. The private subnet NACL allows inbound HTTPS from the public subnet and outbound all traffic. The security group for the web dispatchers allows outbound HTTPS to the application security group. The application security group allows inbound HTTPS from the web security group. What is the issue?

A.The network ACL for the public subnet does not allow inbound ephemeral ports from the private subnet.
B.The security group for the application servers does not allow inbound HTTPS from the web dispatchers.
C.The security group for the web dispatchers does not allow outbound HTTPS to the application security group.
D.The VPC does not have a route between the public and private subnets.
AnswerA

The response traffic from the application servers uses ephemeral ports; the public NACL must allow inbound on those ports from the private subnet.

Why this answer

The issue is that network ACLs are stateless. The web dispatchers initiate outbound HTTPS connections to the application servers. The application servers respond using ephemeral ports.

The public subnet NACL allows inbound HTTPS from the internet, but it does not allow inbound traffic on ephemeral ports from the private subnet. This blocks the return traffic. Therefore, option A is correct.

Options B and C are incorrect because security groups are stateful and allow return traffic automatically. Option D is incorrect because the VPC's local route handles traffic between subnets.

Full explanation →
1268
MCQhard

A company is migrating SAP applications to AWS and needs to test the migration process without affecting the production environment. Which AWS service should be used to create an isolated test environment?

A.AWS CodePipeline
B.AWS Service Catalog
C.AWS OpsWorks
D.AWS CloudFormation
AnswerD

CloudFormation can create isolated stacks for testing.

Why this answer

AWS CloudFormation (option D) allows you to create an isolated test environment using infrastructure as code (IaC) templates, enabling you to replicate the production setup without affecting the live environment. Option A is wrong because AWS CodePipeline is a CI/CD service for automating build, test, and deploy pipelines, not for creating test environments. Option B is wrong because AWS Service Catalog is for creating and managing catalogs of IT services, not for provisioning isolated test environments.

Option C is wrong because AWS OpsWorks is a configuration management service using Chef and Puppet, not primarily for creating isolated test environments. Therefore, D is correct.

Full explanation →
1269
MCQmedium

A company is running SAP BusinessObjects on AWS. The application servers are behind an Application Load Balancer (ALB). The ALB is configured to use a single target group. The company wants to deploy a new version of the application with zero downtime. Which deployment strategy should be used?

A.Perform a rolling update by terminating one instance at a time and launching a new one.
B.Implement a blue/green deployment by creating a new target group and updating the ALB listener.
C.Create a new ALB and update the DNS record to point to the new ALB.
D.Use a canary release by routing 10% of traffic to the new version.
AnswerB

Blue/green allows instant traffic switch with no downtime.

Why this answer

A blue/green deployment allows you to create a completely new target group with the new application version, then update the ALB listener rule to route all traffic from the existing target group to the new one. This ensures zero downtime because the switch is instantaneous at the listener level, and the old environment remains intact for immediate rollback if needed.

Exam trap

The trap here is that candidates confuse a rolling update (which can cause brief downtime) with a blue/green deployment (which provides instant, zero-downtime cutover), especially when the question explicitly requires zero downtime and the ALB is already in place.

How to eliminate wrong answers

Option A is wrong because a rolling update terminates instances one at a time, which can cause brief periods of reduced capacity or failed health checks, leading to potential downtime for SAP BusinessObjects sessions. Option C is wrong because creating a new ALB and updating DNS introduces propagation delays (DNS TTL), which cannot guarantee zero downtime during the transition. Option D is wrong because a canary release routes only a portion of traffic (e.g., 10%) to the new version, which does not achieve full zero-downtime deployment for the entire application; it is a testing strategy, not a complete cutover.

Full explanation →
1270
Multi-Selectmedium

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

Select 2 answers
A.Implement daily snapshots of all SAP EBS volumes using AWS Backup.
B.Deploy the SAP ASCS instance in a Multi-AZ configuration using AWS services.
C.Configure SAP HANA System Replication with synchronous data replication and automatic takeover.
D.Use AWS Elastic Disaster Recovery to replicate the entire SAP environment to a different Region.
E.Use Amazon S3 cross-region replication for all SAP application files.
AnswersB, C

Multi-AZ provides automatic failover for the central services.

Why this answer

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

Exam trap

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

Full explanation →
1271
Multi-Selectmedium

Which TWO options are valid methods for encrypting data at rest in an SAP HANA database running on Amazon EBS? (Choose two.)

Select 2 answers
A.Use SSL/TLS connections to the database.
B.Enable SAP HANA native encryption for the database.
C.Use AWS KMS to encrypt the database schema.
D.Store database files in Amazon S3 with SSE-S3.
E.Enable EBS encryption when launching the EC2 instance.
AnswersB, E

HANA can encrypt data at rest.

Why this answer

SAP HANA provides native encryption capabilities that encrypt data at rest within the database itself, including data files, log files, and backups. This encryption is managed by SAP HANA's own key management system and operates independently of the underlying storage layer, making it a valid method for encrypting data at rest on Amazon EBS.

Exam trap

The trap here is that candidates often confuse encryption in transit (SSL/TLS) with encryption at rest, or incorrectly assume that AWS KMS can directly encrypt database schemas, when in fact KMS is a key management service that must be integrated with a specific encryption implementation like EBS encryption or SAP HANA native encryption.

Full explanation →
1272
MCQhard

A company runs SAP on AWS and wants to automate the failover of their SAP HANA database across Availability Zones using a multi-AZ setup. They are using Pacemaker and STONITH fencing. Which AWS resource is commonly used as a fencing device for SAP HANA multi-AZ clusters?

A.Amazon Simple Notification Service (SNS)
B.Amazon Simple Queue Service (SQS)
C.Amazon RDS
D.Amazon CloudWatch alarm and EC2 API
AnswerD

The AWS STONITH agent uses CloudWatch and EC2 API to stop an unresponsive node.

Why this answer

STONITH (Shoot The Other Node In The Head) fencing in a multi-AZ SAP HANA cluster on AWS requires a mechanism to forcibly isolate or terminate an unresponsive node. Amazon CloudWatch alarms combined with EC2 API calls (e.g., `aws ec2 stop-instances` or `aws ec2 terminate-instances`) serve as the fencing device by triggering an API action to shut down the faulty instance, ensuring data integrity and preventing split-brain scenarios.

Exam trap

The trap here is that candidates confuse high-level AWS services like SNS or SQS with the actual low-level EC2 API calls required for STONITH fencing, mistakenly thinking notification or queuing services can directly perform instance termination.

How to eliminate wrong answers

Option A is wrong because Amazon SNS is a pub/sub notification service used for sending alerts or triggering workflows, but it cannot directly execute EC2 instance termination or stop actions required for STONITH fencing. Option B is wrong because Amazon SQS is a message queue service for decoupling application components; it lacks the ability to perform EC2 API calls to fence a node. Option C is wrong because Amazon RDS is a managed database service and is not used as a fencing device for SAP HANA clusters running on EC2; SAP HANA multi-AZ clusters rely on Pacemaker and custom fencing scripts, not RDS.

Full explanation →
1273
MCQmedium

An SAP Basis administrator is deploying a new SAP S/4HANA system on AWS. The architecture uses a multi-AZ deployment for high availability: primary database in us-east-1a, standby in us-east-1b. The ASCS instance is in us-east-1a with a replicated enqueue server (ERS) in us-east-1b. For the application servers, two instances are in us-east-1a and two in us-east-1b. The administrator needs to ensure that the SAP system remains available if an entire Availability Zone fails. What is the MOST important configuration step to achieve this?

A.Configure Amazon Route53 with a failover routing policy for the SAP application URLs.
B.Place an Application Load Balancer in front of the database instances.
C.Enable HANA system replication and configure ASCS with enqueue replication across the two AZs.
D.Use larger instance types for all SAP instances to handle the load.
AnswerC

These are the standard SAP HA mechanisms for cross-AZ failover.

Why this answer

High availability across AZs requires both HANA system replication and enqueue replication. HANA system replication ensures the database can fail over to the standby in the other AZ. Enqueue replication (ERS) ensures that the lock table is replicated so that the ASCS can fail over without losing locks.

Option A is wrong because Route53 routing only handles DNS resolution, not automatic failover of SAP services. Option B is wrong because an Application Load Balancer does not provide database failover; it distributes traffic to application servers. Option D is wrong because larger instance sizes increase capacity but do not provide high availability in case of AZ failure.

Full explanation →
1274
MCQhard

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

A.Use an io2 Block Express volume with sufficient IOPS.
B.Migrate the data to an instance store volume.
C.Change the volume type to gp3 with increased IOPS.
D.Use a Throughput Optimized HDD (st1) volume.
AnswerA

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Full explanation →
1275
MCQmedium

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

A.Use S3 lifecycle policies to transition backups to Glacier.
B.Take manual EBS snapshots of the database volumes before each backup.
C.Use AWS Backup with pre and post scripts for application-consistent snapshots and enable continuous backup.
D.Use AWS Backup with EBS snapshots every hour.
AnswerC

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Full explanation →
Page 16

Page 17 of 22

Page 18

All pages

12345678910111213141516171819202122

Practice PAS-C01 by domain

Target a specific domain to shore up weak areas.

Design of SAP Workloads on AWSTechnologyMigrationOperations and Maintenance
See all domains with question counts →