PAS-C01 Migration Practice Test 22 — 15 Questions

Question 1

A company is migrating its SAP ERP system to AWS. The SAP application requires low-latency access to the database and high network throughput between application and database tiers. Which AWS architecture should the company use?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

Use a placement group with enhanced networking for both application and database instances.. For SAP workloads on AWS, low-latency and high-throughput communication between application and database tiers is achieved by using a cluster placement group with enhanced networking (ENA) on both tiers. A cluster placement group packs instances close together in a single Availability Zone on the same high-bandwidth, low-latency network backbone, which is exactly what SAP's chatty app-to-DB traffic requires.

Answer

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

Answer

Use Amazon S3 as the database storage layer.

Answer

Place the SAP application servers in one Availability Zone and the database in another Availability Zone.

Question 2

A company is migrating its SAP BusinessObjects to AWS. The current on-premises deployment uses a Windows-based environment. Which AWS service should the company use to migrate the Windows servers?

Accepted Answer

AWS Application Migration Service (AWS MGN). AWS MGN is the recommended service for migrating Windows servers to AWS. Option A is wrong because AWS SCT is for schema conversion, not server migration. Option C is wrong because AWS DMS is for databases, not servers. Option D is wrong because AWS Server Migration Service (SMS) is deprecated.

Answer

AWS Schema Conversion Tool (AWS SCT)

Answer

AWS Database Migration Service (AWS DMS)

Answer

AWS Server Migration Service (AWS SMS)

Question 3

A company is migrating its SAP ERP system to AWS. The SAP application requires low-latency access to the database and high network throughput between application and database tiers. Which AWS architecture should the company use?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

Use the existing SAP license under the Bring Your Own License (BYOL) model.. SAP licensing on AWS follows the Bring Your Own License (BYOL) model, where the customer uses their existing SAP license on AWS infrastructure. Since the company already has a production license for SAP ERP, it can continue using that license on AWS under BYOL, provided the underlying infrastructure meets SAP's certification and sizing requirements. This avoids purchasing a new license or switching to a subscription model.

Answer

Request a free SAP license for AWS from SAP.

Answer

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

Answer

Purchase a new SAP license for AWS.

Question 4

A company is migrating its SAP system to AWS. The system uses a custom ABAP program that writes to a local file system. Which TWO AWS services can the company use to provide a shared file system accessible to multiple EC2 instances?

Accepted Answer

Amazon FSx for Lustre. Amazon FSx for Lustre (A) is correct because it is a fully managed, high-performance parallel file system that can be mounted simultaneously by multiple EC2 instances, making it suitable for shared file access in workloads like SAP custom ABAP programs. Amazon EFS (D) is also correct because it is a managed NFS file system designed for shared, concurrent access from many EC2 instances across Availability Zones, which satisfies the requirement for a shared local-like file system. Amazon RDS (B) is a managed relational database service, not a file system, so it cannot provide shared file storage. Amazon S3 (C) is object storage and is not natively mountable as a POSIX shared file system for multiple EC2 instances without additional gateway or caching layers. Amazon EBS (E) provides block storage volumes that are typically attached to a single EC2 instance at a time and do not natively offer a shared file system across multiple instances.

Answer

Amazon RDS

Answer

Amazon S3

Answer

Amazon EBS

Question 5

A company is migrating its SAP HANA database to AWS. The migration requires minimal downtime and data consistency. Which THREE steps should the company take to achieve this?

Accepted Answer

Use AWS DMS with change data capture (CDC) for ongoing replication.. To achieve minimal downtime and data consistency when migrating an SAP HANA database to AWS, the company should: Use AWS DMS with change data capture (CDC) for ongoing replication (B), create the target HANA database and schema in advance (C), and perform a full load of the data using AWS DMS before enabling CDC (D). A full backup and restore (A) would cause downtime, and disabling logging (E) is incorrect as it would compromise data consistency and recovery.

Answer

Take a full backup of the source database and restore it on the target.

Answer

Disable all logging on the source database to reduce overhead.

Question 6

A company is using AWS DMS to migrate an SAP database. The full load is complete, but the CDC latency is high. Which step should the company take to reduce latency?

Accepted Answer

Increase the compute capacity of the DMS replication instance.. Increasing the compute capacity of the DMS replication instance can reduce CDC latency by providing more CPU and memory resources to process changes more quickly. High CDC latency often indicates the replication instance is under-resourced.

Answer

Increase the size of the target database instance.

Answer

Restart the DMS replication task.

Answer

Disable change data capture (CDC) on the source database.

Question 7

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

Accepted Answer

AWS Database Migration Service (DMS). AWS Database Migration Service (DMS) is the correct choice because it is purpose-built to migrate databases to AWS with minimal downtime, supporting both the initial full data load and ongoing change data capture (CDC) replication from an on-premises Oracle source to Amazon RDS for Oracle. DMS uses a replication instance and endpoints to continuously apply changes, keeping the target in sync until cutover. AWS SCT only converts schema and code between engines, not data replication. AWS Snowball is for bulk physical data transfer and does not provide ongoing replication. AWS DataSync is for file/object data movement, not database replication.

Answer

AWS Schema Conversion Tool (SCT)

Answer

AWS Snowball

Answer

AWS DataSync

Question 8

A company is migrating an SAP S/4HANA system to AWS. The migration strategy involves using SAP HANA System Replication (HSR) to replicate the source HANA database to an EC2 instance running HANA. During the final cutover, the replication link breaks and the target database becomes inconsistent. What should the migration team do to recover?

Accepted Answer

Perform a full HSR initial snapshot from the source to the target. When SAP HANA System Replication (HSR) link breaks and the target database becomes inconsistent, the most reliable recovery is to perform a full HSR initial snapshot from the source to the target. This re-establishes the replication and ensures the target is consistent with the source. Delta snapshots are only possible if the replication link is intact and the target is not too far behind.

Answer

Restart HSR with a delta snapshot from the source

Answer

Restore the target database from an AWS Backup

Answer

Use AWS DMS to replicate remaining changes

Question 9

A company is planning to migrate its SAP environment to AWS. They have multiple SAP systems that are interconnected. Which migration approach is recommended to minimize dependency issues?

Accepted Answer

Migrate systems in logical groups that have dependencies on each other. Migrating SAP systems in logical groups that share dependencies minimizes issues because interdependent systems (e.g., ECC, BW, PI/PO) must be migrated together to maintain integration and data consistency. This approach ensures that cross-system interfaces, RFC connections, and batch jobs continue to function without disruption. It also allows for coordinated testing and cutover, reducing the risk of broken dependencies.

Answer

Migrate systems based on business process priority, ignoring technical dependencies

Answer

Migrate systems individually based on size, starting with the smallest

Answer

Migrate all systems at the same time in a big bang approach

Question 10

A company is migrating an SAP ERP system to AWS using an SAP-certified backup/restore method. After restoring the database to Amazon RDS for SAP ASE, the SAP application fails to start with an error 'database connection refused'. The security group allows inbound traffic from the application server. What is the most likely cause?

Accepted Answer

The SAP application is using the wrong database hostname or port. After restoring the database to Amazon RDS, the database endpoint (hostname and port) changes. The SAP application likely still uses the old connection parameters, leading to a 'connection refused' error. Option A is incorrect because, although a stopped RDS instance would also cause this error, after a restore the instance is automatically started and running; a stopped state is unlikely. Option B is incorrect because outbound traffic rules are not required for inbound connections; the inbound rule on the database security group is sufficient. Option D is incorrect because different VPCs would typically result in 'no route to host' or timeout errors, not 'connection refused'.

Answer

The RDS instance is in a 'stopped' state

Answer

The security group does not allow outbound traffic

Answer

The RDS instance is in a different VPC than the application server

Question 11

A company is migrating its SAP landscape to AWS. They need to choose a migration method for each system. Which TWO factors are most important to consider when selecting a migration method for SAP systems? (Choose TWO.)

Accepted Answer

Source and target platform (OS, DB). Option C is correct because the source and target platform (operating system and database) determines which migration techniques are technically feasible — for example, homogeneous migration (same OS/DB) allows SAP SWPM-based system copy or backup/restore, while heterogeneous migration (different OS/DB) requires SAP Migration Monitor with R3load export/import or tools like SUM/DMO. Option E is correct because the SAP release and database version dictate the supported migration tools and target options — for instance, SAP NetWeaver version affects whether DMO with SUM can be used, and the DB version determines compatibility with the target platform on AWS (e.g., SAP HANA, Oracle, SQL Server). Option A is not a primary selection factor because cost is a consequence of the chosen method, not a technical determinant of which method is viable. Option B is not decisive because backup frequency is an operational policy and does not determine the migration method itself. Option D is not a key factor because the number of SAP users affects sizing and performance, not the choice of migration method.

Answer

Total cost of migration

Answer

Frequency of database backups

Answer

Number of SAP users

Question 12

A company is migrating an SAP HANA database from on-premises to AWS using SAP HANA System Replication (HSR). They have set up the replication but the target database is not in sync. Which THREE configuration items should the migration team verify? (Choose THREE.)

Accepted Answer

The hostname resolution between source and target. Option A is correct because SAP HANA System Replication requires bidirectional hostname resolution between the primary and secondary hosts so that the replication services can register and communicate; mismatched or missing DNS/hosts entries will prevent the secondary from syncing. Option B is correct because HSR demands compatible SAP HANA versions and revision/build levels between source and target; incompatible builds can block replication or cause the secondary to fail to reach sync. Option D is correct because HSR uses specific TCP ports (e.g., 313, 317, 340, and 341 for the HSR channel) and the firewall/security groups must allow this traffic between the two systems. Option C is not required for replication sync, since licensing is a separate administrative concern and does not affect HSR data synchronization. Option E is not required because HSR does not mandate identical storage types; performance may vary, but SSD vs HDD does not prevent synchronization.

Answer

The SAP HANA license is activated on the target

Answer

The storage type (SSD vs HDD) is identical

Question 13

A company is migrating its SAP environment to AWS using AWS Launch Wizard for SAP. Which TWO pieces of information does Launch Wizard require to deploy an SAP system? (Choose TWO.)

Accepted Answer

SAP product version (e.g., SAP S/4HANA 2020). Option A is correct because AWS Launch Wizard for SAP requires you to specify the SAP product and version (for example, SAP S/4HANA 2020 or SAP NetWeaver) so it can select the appropriate deployment pattern, sizing, and supported operating system and database combinations. Option E is correct because the SAP system ID (SID), a three-character identifier such as S4H, is mandatory for defining the SAP system's naming, directories, and instance configuration during deployment. Option B is not required; Launch Wizard does not ask for the number of SAP users, since sizing is driven by the selected SAP product, deployment size, and instance type choices. Option C is not required because on-premises IP addresses are irrelevant to a new AWS deployment; Launch Wizard works with the target VPC, subnets, and CIDR ranges you specify in AWS. Option D is not required because the AWS account ID is implicitly known from the credentials used to run Launch Wizard and is not an input field for the deployment.

Answer

Number of SAP users

Answer

On-premises IP addresses

Answer

AWS account ID

Question 14

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

Accepted Answer

Increase the allocated storage for the target database tablespace.. The error explicitly states the target database tablespace is full, meaning the allocated storage for that tablespace is insufficient for the data being imported. The correct resolution is to increase the storage allocated to the target database tablespace, either by adding space to the existing datafile or enabling autoextend, so the import can complete. This directly addresses the root cause—insufficient space—without altering the migration method or data set.

Answer

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

Answer

Restart the import with a smaller package size.

Answer

Use SAP DMO instead of SWPM for the migration.

Question 15

A company is migrating an SAP system to AWS and wants to use AWS Launch Wizard for deployment. They have an existing VPC and subnets. Launch Wizard requires the selection of a subnet for each component. What is the best practice for selecting subnets for high availability?

Accepted Answer

Select subnets in different Availability Zones to ensure high availability.. For high availability, Launch Wizard deployments should select subnets in different Availability Zones so that SAP components (ASCS, PAS, database) are spread across physically isolated data centers. If one AZ fails, the system can fail over to the other. AWS Launch Wizard for SAP explicitly requires subnet selection per component and recommends multi-AZ placement for production HA.

Answer

Use only private subnets without public access.

Answer

Select a single subnet in one Availability Zone for simplicity.

Answer

Create a new VPC and subnets specifically for Launch Wizard.