PAS-C01 Mock Exam 95 — 25 Questions

Question 1

A company is running SAP S/4HANA on AWS with a high-availability setup using SAP HANA System Replication and a Pacemaker cluster. The cluster consists of two EC2 instances in different Availability Zones, each with an EBS volume for HANA data. The cluster uses a virtual IP address (VIP) managed by the AWS Route 53 health check and failover mechanism. During a recent failover test, the secondary node took over as primary, but the application was unable to connect to the database for several minutes. The investigation reveals that the VIP did not update correctly. The company wants to ensure fast and reliable VIP failover. What should the team do to improve the failover time?

Accepted Answer

Place the SAP HANA database behind an internal Network Load Balancer (NLB) and use the NLB's TCP health checks to route traffic to the active instance.. Option C is correct. Using an internal Network Load Balancer (NLB) as a database endpoint provides a static IP that can be redirected to the active HANA node. The NLB health check can quickly detect the failure and reroute traffic to the healthy secondary instance. Option A is incorrect because Route 53 health checks have a default interval of 30 seconds and DNS TTL can cause delays. Option B is incorrect because EIP reassignment requires API calls and may take longer. Option D is incorrect because increasing the TTL would make failover slower, not faster.

Answer

Increase the DNS TTL to 300 seconds to reduce lookups and rely on the Pacemaker VIP update.

Answer

Assign an Elastic IP address to the active node and use a script to reassign it during failover.

Answer

Reduce the Route 53 health check interval to 10 seconds and lower the DNS TTL to 60 seconds.

Question 2

A company runs its SAP Business Suite on AWS with an Oracle database on an EC2 instance. The database is stored on multiple EBS volumes configured as a RAID 0 array. The company wants to migrate the database to SAP HANA on a new EC2 instance. The SAP HANA instance will use EBS volumes for data and log storage. The current Oracle database size is 500 GB. The company needs to minimize downtime during the migration. Which migration strategy should they use?

Accepted Answer

Use SAP HANA System Replication to replicate data from the source Oracle database to the target HANA database.. Option A is correct: Using SAP HANA System Replication with initial load from backup is the standard low-downtime method. Option B is wrong because DMS does not support SAP HANA as a target for homogeneous migration. Option C is wrong because AWS Application Migration Service is for server migration, not database. Option D is wrong because a manual export/import requires significant downtime.

Answer

Use AWS Application Migration Service to migrate the entire EC2 instance.

Answer

Export the Oracle database to a flat file and import into SAP HANA.

Answer

Use AWS Database Migration Service (DMS) to migrate from Oracle to SAP HANA.

Question 3

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

Accepted Answer

Set the 'Delete on Termination' attribute to 'True' on all EBS volumes attached to the instance when it is launched by LaMa.. Option A is correct. When launching an instance, enabling the 'Delete on Termination' flag for the root volume ensures that the volume is deleted upon instance termination. For additional volumes, this flag must also be set. LaMa will then terminate the instance, and the volumes will be automatically deleted. Option B is incorrect because Lambda functions can be used but are more complex and may not be triggered by termination if the instance is the event source. Option C is incorrect because Lifecycle Manager is for scheduled snapshots, not for deletion on termination. Option D is incorrect because CloudTrail logs events but does not automatically delete volumes; it would require additional automation.

Answer

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

Answer

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

Answer

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

Question 4

A company has deployed SAP S/4HANA on AWS using a single EC2 instance for the HANA database. The database volume is an EBS io1 volume with 5,000 provisioned IOPS. The company wants to implement a high availability (HA) solution for the database using SAP HANA System Replication (HSR) with automatic failover. They plan to use a second EC2 instance in a different Availability Zone. The database administrator is concerned about data consistency during replication. Which additional AWS service should be used to ensure data consistency and minimize data loss during failover?

Accepted Answer

Amazon Route53 with health checks to automatically redirect traffic to the standby instance.. Option C is correct because Elastic Load Balancing with a TCP listener can be used to front the HSR traffic and provide a floating IP. Alternatively, Amazon Route53 with health checks can redirect clients. Option A (EBS snapshots) are for backup, not replication. Option B (AWS Backup) is not for replication. Option D (DMS) is for migration.

Answer

AWS Backup to schedule backups of the HANA database.

Answer

AWS Database Migration Service (DMS) to continuously replicate data.

Answer

Amazon EBS snapshots to capture point-in-time copies of the data volume.

Question 5

A company runs its SAP HANA database on an EC2 instance (r5.8xlarge) with 8 EBS gp2 volumes (1 TB each) in a RAID 0 stripe. The database is critical and requires high availability. The current architecture uses a single EC2 instance in one Availability Zone. The company wants to implement a disaster recovery solution with a Recovery Point Objective (RPO) of 15 minutes and a Recovery Time Objective (RTO) of 4 hours. The DR site must be in a different AWS Region. The SAP HANA database size is 4 TB. The company has a 1 Gbps Direct Connect connection between the primary and DR Regions. The database workload is write-intensive with an average write throughput of 200 MB/s. Which solution meets the RPO and RTO requirements?

Accepted Answer

Set up HANA System Replication (HSR) in asynchronous mode from the primary to a secondary EC2 instance in the DR Region. Use the same instance type and EBS configuration. In case of failure, perform a HSR takeover.. Option B is correct. HANA System Replication (HSR) in async mode can replicate data with sub-minute RPO. Using the same instance type and RAID configuration ensures performance. The 1 Gbps connection can handle the replication traffic (200 MB/s = 1.6 Gbps, but compression reduces it). Option A is incorrect because EBS snapshots cannot be taken every 15 minutes and restoring 4 TB from snapshots takes more than 4 hours. Option C is incorrect because DMS is for database migration, not HANA replication. Option D is incorrect because backing up to S3 and restoring takes longer than 4 hours.

Answer

Take EBS snapshots of the RAID array every 15 minutes and replicate them to the DR Region using EBS snapshot copy. In the DR Region, restore the snapshots to new volumes and attach them to a new EC2 instance.

Answer

Back up the HANA database to Amazon S3 every 15 minutes using the HANA backup tool, and set up cross-Region replication for the S3 bucket. In the DR Region, restore the latest backup to a new EC2 instance.

Answer

Use AWS Database Migration Service (DMS) to continuously replicate changes to a target HANA database in the DR Region.

Question 6

A company runs its SAP ERP system on AWS with an SAP HANA database on an EC2 instance. The database is configured with multiple EBS io1 volumes striped in a RAID 0. Recently, the company implemented a new backup process using AWS Backup with the Backint agent. However, during the backup window, the database performance degrades significantly, causing application timeouts. The database administrator checks CloudWatch metrics and sees that the EBS write latency spikes to over 50 ms during backups. The backup target is an S3 bucket in the same region. The EC2 instance type is r5.4xlarge with EBS-optimized enabled. What is the MOST likely cause of the performance degradation?

Accepted Answer

The Backint agent is consuming CPU and I/O resources, causing contention.. Option D is correct because Backint backups can consume significant CPU and I/O, impacting database performance. Option A (EBS volume limit) is unlikely with RAID 0. Option B (matching instance type) is not needed. Option C (S3 performance) is not the bottleneck.

Answer

The EBS volumes have reached the provisioned IOPS limit of 20,000 IOPS.

Answer

The S3 bucket is in a different region, causing network latency.

Answer

The EC2 instance type does not match the requirements for Backint.

Question 7

You are an SAP Basis consultant for a company running SAP ECC on Oracle on AWS. The system is hosted on a single EC2 instance (r5.8xlarge) with a separate EC2 instance for the database (Oracle on RDS). Recently, users have reported that the system becomes unresponsive for a few minutes every day at 10:00 AM. You check CloudWatch metrics and see a spike in CPU utilization on the application server at that time, but the database metrics are normal. The application server is running SAP instance and also a custom batch job that runs daily at 10:00 AM. The batch job is using a significant amount of CPU. You need to resolve the issue without losing the functionality of the batch job. Which action should you take?

Accepted Answer

Move the custom batch job to a separate EC2 instance dedicated to running batch processes.. Option A is correct because moving the batch job to a separate EC2 instance isolates the CPU-intensive process from the main SAP application, preventing it from affecting user sessions. Option B (increase instance size) is expensive and may not be necessary if the batch job can be separated. Option C (reschedule the job) might avoid peak hours but does not address the root cause of resource contention. Option D (RDS read replica) does not help with application server CPU issues.

Answer

Reschedule the batch job to run at a different time, such as 2:00 AM.

Answer

Upgrade the application server instance to a larger size, such as r5.16xlarge.

Answer

Create an RDS read replica and offload the batch job's database queries to it.

Question 8

A company runs SAP BusinessObjects on AWS using multiple EC2 instances. The system uses a shared file system (EFS) for the repository and output files. Recently, users have reported that generating large reports takes much longer than usual. The SAP administrator checks the EFS metrics in CloudWatch and sees that the BurstCreditBalance is consistently near zero. The EFS file system is in General Purpose mode with default throughput settings. The current size of the file system is 500 GB. What should the administrator do to improve performance?

Accepted Answer

Enable Max I/O throughput mode on the EFS file system.. Option B is correct because enabling Max I/O throughput mode increases the throughput baseline for larger file systems, providing more consistent performance. Option A is wrong because increasing EFS size does not directly improve burst credits; the burst model depends on size. Option C is wrong because using Provisioned Throughput would incur costs but may be appropriate; however, Max I/O is a better first step for a system that has exhausted burst credits. Option D is wrong because transitioning to EFS One Zone does not improve throughput performance.

Answer

Migrate the EFS file system to EFS One Zone for better performance.

Answer

Switch to Provisioned Throughput mode and set a higher value.

Answer

Increase the size of the EFS file system by adding more data to it.

Question 9

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

Accepted Answer

Configure EFS mount targets in each AZ and use an EFS access point with a consistent mount path.. Option D is correct because the EFS mount target is in a specific subnet, and after failover, the application servers might be trying to connect to the wrong mount target or the DNS might not resolve correctly. Using an EFS access point with a consistent path and ensuring proper DNS resolution across AZs can resolve this. Option A (increase EFS throughput) does not address connectivity. Option B (use FSx for ONTAP) could be an alternative but is not the immediate cause. Option C (HSR setup issue) is not the cause if the database fails over correctly.

Answer

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

Answer

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

Answer

Reconfigure SAP HANA System Replication to use synchronous replication.

Question 10

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?

Accepted Answer

The network ACL for the public subnet does not allow inbound ephemeral ports from the private subnet.. Option B is correct because security groups are stateful; if the application security group allows inbound HTTPS from the web security group, the return traffic is automatically allowed. However, network ACLs are stateless, so the private subnet NACL must allow inbound traffic from the public subnet, which it does, but it must also allow outbound return traffic from the application servers to the web dispatchers. The outbound rule in the private NACL allows all traffic, so that is not the issue. Actually, the problem is likely that the web dispatchers are in a public subnet with a NACL that allows inbound HTTPS from the internet, but the application servers are in a private subnet and need to send return traffic. Since NACLs are stateless, the private subnet NACL must allow inbound HTTPS from the web dispatchers, which is configured, but also outbound traffic from the application servers. The outbound rule allows all, so that's fine. The real issue could be that the web dispatchers' security group does not allow inbound traffic from the application servers for the return traffic? But security groups are stateful, so no. Let's re-evaluate: The web dispatchers initiate connection to application servers on port 443. The application servers respond. The web dispatchers' security group must allow outbound HTTPS to the application servers, which it does. The application servers' security group must allow inbound HTTPS from the web dispatchers, which it does. Since security groups are stateful, the return traffic is allowed. So the issue might be with routing? But all in same VPC. Perhaps the web dispatchers are in a public subnet without a route to the private subnet? Actually, by default, VPC has local route. So routing is fine. The most common issue is that the network ACL for the private subnet must allow inbound ephemeral ports for the response traffic. Since NACLs are stateless, the outgoing response from application servers uses ephemeral ports, and the private subnet NACL must allow outbound traffic on those ports. The outbound rule allows all, so that's fine. But the public subnet NACL must allow inbound ephemeral ports for the response traffic coming back to the web dispatchers. The public subnet NACL allows inbound HTTPS from the internet, but not necessarily ephemeral ports from the private subnet. So the issue is that the public subnet NACL does not allow inbound traffic on ephemeral ports from the private subnet. Option A is incorrect because security groups are fine. Option C is incorrect because security groups are stateful. Option D is incorrect because routing should work.

Answer

The security group for the application servers does not allow inbound HTTPS from the web dispatchers.

Answer

The security group for the web dispatchers does not allow outbound HTTPS to the application security group.

Answer

The VPC does not have a route between the public and private subnets.

Question 11

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?

Accepted Answer

Enable HANA system replication and configure ASCS with enqueue replication across the two AZs.. Option D is correct because cross-AZ failover for both database and SAP central services requires proper configuration of HANA system replication and enqueue replication. Option A is wrong because Route53 routing is not sufficient for automatic failover of SAP services; it only handles DNS. Option B is wrong because a single ELB does not provide cross-AZ failover for the database. Option C is wrong because increasing instance size does not improve availability.

Answer

Configure Amazon Route53 with a failover routing policy for the SAP application URLs.

Answer

Place an Application Load Balancer in front of the database instances.

Answer

Use larger instance types for all SAP instances to handle the load.

Question 12

A retail company is migrating its SAP ERP system from on-premises to AWS. The system includes an SAP HANA database (2 TB) and an SAP NetWeaver application server. The migration strategy is to use SAP HANA System Replication (HSR) to replicate the database to an EC2 instance running SAP HANA, then perform a takeover. The application server will be migrated using AWS Application Migration Service (MGN). The network connection is AWS Direct Connect with 1 Gbps bandwidth. During a test migration, the HSR replication is working, but the application server replication through MGN is taking much longer than expected. The MGN console shows that the data replication progress is stuck at 45% for several hours. The source server is a physical server with a 500 GB disk, 75% utilized. Which action is most likely to resolve the issue?

Accepted Answer

Increase the disk queue depth on the source server or add additional disks to improve I/O performance.. MGN replication stalls often due to disk queue depth issues on the source. Option A is correct because increasing disk throughput can help. Option B is wrong because MGN uses block-level replication, not file-based. Option C is wrong because the network bandwidth is 1 Gbps, which is adequate. Option D is wrong because MGN does not have a staging area that can be increased; the staging area is on the source.

Answer

Convert the source disks to dynamic disks to improve replication speed.

Answer

Increase the staging area size in the MGN replication settings.

Answer

Increase the Direct Connect bandwidth to 10 Gbps.

Question 13

A healthcare company is migrating its SAP Business Suite system to AWS. The system includes an SAP HANA database (1.5 TB) and an SAP NetWeaver application server. They plan to use SAP HANA System Replication (HSR) for the database and AWS Application Migration Service (MGN) for the application server. The network connection is AWS Direct Connect with 500 Mbps bandwidth. During a test migration, the HSR replication is working, but the MGN replication for the application server is extremely slow. The MGN console shows that the replication is progressing at only 10 Mbps. The source application server is a physical machine with a 300 GB disk, 60% utilized. The administrator has verified that there are no other applications consuming significant network bandwidth. Which action is most likely to improve the MGN replication speed?

Accepted Answer

Increase the bandwidth limit setting in the MGN agent configuration on the source server.. MGN uses a replication server in AWS. The source server may be throttled by the MGN agent's default bandwidth limit. Option A is correct because increasing the agent's bandwidth limit can improve speed. Option B is wrong because changing the staging area disk type on the source does not affect replication speed. Option C is wrong because the network bandwidth is 500 Mbps, higher than 10 Mbps, so network is not the bottleneck. Option D is wrong because changing the target instance type does not affect data transfer.

Answer

Change the target EC2 instance type to a larger size.

Answer

Request an increase in the Direct Connect bandwidth to 1 Gbps.

Answer

Change the staging area disk on the source server from HDD to SSD.

Question 14

A company is migrating its SAP Business Suite system from on-premises to AWS. The system uses a Sybase ASE database. The migration team has limited Sybase expertise. They want to minimize the operational overhead after migration. Which database migration approach should they choose?

Accepted Answer

Use SAP Software Update Manager (SUM) with Database Migration Option (DMO) to migrate the system to SAP HANA on EC2.. SAP supports Sybase ASE to SAP HANA migration as part of SAP Business Suite on HANA. Migrating to SAP HANA on AWS is a strategic move and reduces complexity. Using DMS for Sybase to RDS for Sybase is possible but Sybase ASE on RDS is not a managed service; it's an EC2-based deployment. Option C is correct because moving to HANA is a common SAP migration path and reduces overhead. Option A is wrong because DMS cannot migrate to Sybase on RDS (RDS supports Sybase? Actually RDS does not support Sybase; only EC2). Option B is wrong because using AWS MGN for the database server retains Sybase on EC2, not reducing overhead. Option D is wrong because DataSync is not for database replication.

Answer

Use AWS MGN to replicate the entire Sybase server to EC2, then perform a system upgrade to SAP HANA.

Answer

Use AWS DataSync to copy the Sybase data files to EBS and attach to an EC2 instance running Sybase.

Answer

Use AWS DMS to migrate the Sybase database to Amazon RDS for Sybase.

Question 15

A retail company is migrating its SAP ERP system to AWS. The system includes an SAP HANA database (1 TB) and an SAP NetWeaver application server. The migration strategy is to use AWS Database Migration Service (DMS) for the database and then manually install the application server on an EC2 instance. The network connection is AWS Direct Connect with 1 Gbps bandwidth. During the migration, the DMS task for the database completes successfully, but the application server installation fails because the SAP installation media is not accessible. The installation media is stored on an on-premises file server. The EC2 instance for the application server is in a private subnet with no direct internet access. The administrator has created a VPC endpoint for S3 to access the media, but the media is not in S3. Which step should the administrator take to make the installation media available?

Accepted Answer

Add a route in the VPC route table to direct traffic to the on-premises network via Direct Connect.. Since the media is on-premises, the EC2 instance needs access to the on-premises file server. Option A is correct because using Direct Connect, the private subnet can route to on-premises via the VPC route table. Option B is wrong because the media is not in S3. Option C is wrong because the media is not on the internet. Option D is wrong because the media is not in S3.

Answer

Copy the installation media to an S3 bucket and use the VPC endpoint to access it.

Answer

Attach an internet gateway to the VPC and assign a public IP to the EC2 instance.

Answer

Use AWS Storage Gateway to cache the media in S3.

Question 16

A company is migrating a large SAP S/4HANA system (8 TB total data, high I/O) from on-premises to AWS. The SAP system runs on HANA database and uses a three-tier architecture with application servers and database servers. The migration plan must minimize downtime and ensure data consistency. The company has a 10 Gbps direct connection to AWS. They have considered using AWS DMS, but the database is SAP HANA, which is not supported as a source by DMS. The migration team needs to transfer the HANA database and also the application files. They also need to replicate ongoing changes to minimize downtime. Which combination of AWS services should the migration team use? (Choose the best answer.)

Accepted Answer

Use AWS Application Migration Service (MGN) for the application servers. Use HANA Backint agent to back up the database to S3 and perform incremental backups for ongoing replication.. AWS DataSync can transfer large files efficiently over Direct Connect. HANA database backup to S3 using Backint allows incremental backups and can be used with S3 for ongoing replication. AWS HANA replication is not a service; SAP HANA system replication is a feature. AWS MGN can replicate the entire server including OS and application. The best combination is to use MGN for the application servers and Backint to S3 for HANA database backup and recovery. Option C is correct. Option A is not suitable because DMS cannot migrate HANA. Option B is not efficient for ongoing replication. Option D includes AWS DMS which is not supported.

Answer

Use AWS DataSync to copy the entire HANA database files (data and log volumes) and application files to AWS. Then restore from the copied files.

Answer

Use AWS Database Migration Service (DMS) with SAP HANA as a source by installing a custom connector. Use AWS DataSync for application files.

Answer

Use AWS DMS for the HANA database using a homogeneous migration. Use AWS MGN for the application servers.

Question 17

A technology company is migrating its SAP Business Warehouse (BW) system to AWS. The system includes an SAP HANA database (2 TB) and multiple application servers. The migration plan is to use SAP HANA System Replication (HSR) for the database and AWS Application Migration Service (MGN) for the application servers. The network connection is AWS Direct Connect with 1 Gbps bandwidth. During a test migration, the HSR replication is working, but the MGN replication for one of the application servers is failing with an error: "The agent cannot communicate with the MGN service endpoint." The source server is a Windows Server 2016 machine. The administrator has verified that the source server has internet connectivity. Which action is most likely to resolve the issue?

Accepted Answer

Create a VPC endpoint for AWS Application Migration Service in the source VPC.. MGN agent communicates with the MGN service endpoint over internet or via VPC endpoint. Option A is correct because setting up a VPC endpoint for MGN in the source VPC allows private connectivity. Option B is wrong because the agent is already installed. Option C is wrong because HTTP proxy may help but is not the most likely issue. Option D is wrong because the source server is Windows, not Linux.

Answer

Reinstall the MGN agent on the source server.

Answer

Configure an HTTP proxy on the source server to route traffic through the corporate proxy.

Answer

Change the source server's OS to Linux.

Question 18

A manufacturing company is migrating its SAP ECC system to AWS. The system includes an SAP HANA database (1 TB) and an SAP NetWeaver application server. They plan to use AWS Database Migration Service (DMS) for the database and AWS Application Migration Service (MGN) for the application server. The network connection is AWS Direct Connect with 1 Gbps bandwidth. During a test migration, the DMS task for the database fails with a connection error. The source database is on an on-premises server that is behind a firewall. The administrator has already opened the necessary ports in the firewall. The DMS replication instance is in a VPC with a public subnet. Which step should the administrator take to resolve the connection issue?

Accepted Answer

Create a private subnet for the DMS replication instance and attach a NAT gateway to allow outbound traffic to the on-premises database.. DMS replication instance needs network connectivity to the source database. If the source is behind a firewall, the DMS instance may need to be in a private subnet with a NAT gateway or VPC peering. Option A is correct because creating a private subnet and enabling NAT gateway allows outbound connectivity. Option B is wrong because DMS endpoint is for configuring source/target, not for network connectivity. Option C is wrong because the firewall is already open. Option D is wrong because modifying the source database configuration is not needed.

Answer

Modify the DMS source endpoint to use a different port.

Answer

Configure the source database to allow connections from the DMS replication instance IP.

Answer

Open additional ports in the on-premises firewall.

Question 19

A large enterprise is migrating its SAP S/4HANA system to AWS. The system includes a production SAP HANA database (4 TB) and a development SAP HANA database (1 TB). The migration strategy is to use SAP HANA System Replication (HSR) for both databases to EC2 instances in the same AWS region. The company has a compliance requirement that the production database must be in a different AWS account than the development database. The network between on-premises and AWS uses AWS Direct Connect with 10 Gbps bandwidth. During the test migration, the HSR replication for the development database works, but the production database fails to establish replication. The error log shows: "HSR connection timed out." The security groups and network ACLs for the production target EC2 instance allow inbound traffic on port 30101 from the on-premises source IP. What is the most likely cause of the failure?

Accepted Answer

The production target EC2 instance is in a different AWS account, and there is no VPC peering or Transit Gateway between the accounts to allow connectivity.. HSR requires communication between the source and target HANA instances. If the target is in a different account, VPC peering or Transit Gateway is needed for cross-account connectivity. Option A is correct because cross-account communication requires VPC peering or Transit Gateway. Option B is wrong because the port is correct. Option C is wrong because HSR does not use port 443. Option D is wrong because the source is on-premises, not in another AWS account.

Answer

The production source HANA instance is not configured to replicate to a different AWS account.

Answer

The production target EC2 instance is using the wrong port for HSR.

Answer

The security group on the production target EC2 instance does not allow inbound traffic on port 443.

Question 20

A company is migrating a 3 TB SAP ERP system running on Oracle on AIX to SAP HANA on AWS. The system has a complex landscape with multiple application servers and a central Oracle database. The migration must be completed within a 4-day window with minimal downtime. The company has a 1 Gbps AWS Direct Connect connection. The SAP system is heavily customized with many ABAP programs and custom database objects. The migration team plans to use SAP Software Update Manager (SUM) with the Database Migration Option (DMO). During the migration rehearsal, the SUM DMO process fails during the database migration phase with an error indicating that the source database character set is not supported by the target SAP HANA. The source Oracle database uses the WE8ISO8859P1 character set. The team needs to resolve this issue before the final migration. Which course of action should the team take?

Accepted Answer

Convert the source Oracle database character set to UTF-8 (AL32UTF8) before starting the SUM DMO migration.. SAP HANA supports only UTF-8. Therefore, the source database must be converted to UTF-8 before migration. Option A is wrong because SAP HANA does not support WE8ISO8859P1 directly. Option B is wrong because HANA Studio migration tools also require UTF-8. Option D is wrong because AWS DMS does not support SAP HANA as a target for character set conversion.

Answer

Use SAP HANA Studio migration tools to convert the character set during migration without changing the source.

Answer

Use AWS Database Migration Service (AWS DMS) to migrate the data and automatically convert the character set.

Answer

Change the target SAP HANA database to use the WE8ISO8859P1 character set by modifying the HANA database parameters.