PAS-C01 Migration Practice Test 4 — 15 Questions

Question 1

A media company is migrating its on-premises video processing infrastructure to AWS. The current infrastructure uses a custom application that splits video files into segments, transcodes them using FFmpeg, and assembles the final output. The application runs on a single server with 64 vCPUs and 256 GB RAM. The migration plan is to use AWS Batch with EC2 instances for the transcoding jobs. The video files are stored on an on-premises NAS and will be migrated to Amazon S3. The company needs to minimize latency for file access during migration and reduce the time to transfer initial data. The company has a 1 Gbps AWS Direct Connect connection. The total data volume is 500 TB. The migration window is 30 days. Which approach should the team use to transfer the initial data to S3 with the lowest latency and within the migration window?

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

Accepted Answer

Use multiple AWS Snowball Edge devices to transfer the data in parallel, then copy from the devices to S3 using the Snowball client.. AWS Snowball Edge devices provide a physical, high-bandwidth transfer method that bypasses network constraints entirely. With 500 TB of data and a 1 Gbps Direct Connect link, the theoretical maximum transfer over the network in 30 days is only ~324 TB (1 Gbps * 30 days * 86400 seconds/day / 8 bits per byte), which is insufficient. Multiple Snowball Edge devices in parallel can transfer the full 500 TB within the migration window without saturating the Direct Connect link, and the Snowball client efficiently copies data to S3 after the devices are returned.

Answer

Use AWS DataSync to transfer data over the Direct Connect connection in multiple concurrent tasks.

Answer

Use a single AWS Snowball Edge device and copy data incrementally.

Answer

Use S3 Transfer Acceleration to speed up transfers over the internet.

Question 2

A company is migrating its on-premises web application to AWS. The application consists of a stateless web tier and a stateful database tier running on a single server. The web tier uses session data stored in the local file system. The database tier runs on MySQL. The company wants to minimize changes to the application code during migration. They plan to use Amazon EC2 for the web server and Amazon RDS for MySQL for the database. After migrating the web server to an EC2 instance and the database to RDS, users report that they are being logged out of the application frequently. What is the most likely cause of this issue?

Accepted Answer

The web server's session data is stored locally and is lost when the EC2 instance is replaced or restarted.. The web tier stores session data in the local file system of the EC2 instance. When the instance is replaced or restarted (e.g., due to Auto Scaling, instance failure, or a maintenance event), that local session data is lost. Since the application code was not modified to use a shared session store (like ElastiCache or DynamoDB), users lose their sessions and are logged out. This is the most likely cause because the migration explicitly minimized code changes and did not address the stateless web tier requirement.

Answer

The RDS instance's backup window is causing database connections to drop.

Answer

The application's session timeout setting was reduced during migration.

Answer

The security group for the web server is blocking inbound session cookies.

Question 3

A company is migrating a legacy on-premises application to AWS. The application uses a MySQL database with a complex stored procedure that runs every hour and takes approximately 10 minutes to complete. The company wants to minimize downtime during migration. Which TWO approaches should the company use to migrate the database?

Accepted Answer

Use AWS Database Migration Service (DMS) with ongoing replication from the source MySQL database to an Amazon RDS for MySQL instance.. AWS DMS with ongoing replication allows continuous synchronization from the source MySQL database to Amazon RDS for MySQL, minimizing downtime during migration. The complex stored procedure that runs hourly and takes 10 minutes is handled seamlessly as DMS captures ongoing changes, enabling a controlled cutover with minimal disruption.

Answer

Use AWS DMS with a full load only, without ongoing replication, and schedule a cutover window.

Answer

Take a full database dump using mysqldump and import it into an Amazon RDS for MySQL instance during a planned maintenance window.

Answer

Create an Amazon RDS for MySQL read replica from the on-premises database.

Question 4

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

Accepted Answer

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

Answer

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

Answer

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

Answer

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

Question 5

A manufacturing company is planning to migrate a legacy inventory application from a data center to AWS. The application runs on Windows Server 2012 R2 and uses a SQL Server 2014 database. The application requires low-latency access to a shared file system for storing CAD drawings. The current on-premises environment uses a SAN-based storage array for the database and a Windows File Server for the CAD files. The company wants to minimize operational overhead and avoid refactoring the application. The migration must be completed within 3 months. The company has already established a Direct Connect connection between the data center and AWS. Which migration strategy should the company use?

Accepted Answer

Use AWS Application Migration Service (AWS MGN) to replicate the on-premises Windows server to an EC2 instance. Migrate the SQL Server database using native backup and restore. Use Amazon FSx for Windows File Server to replace the on-premises file server, and mount the file share via SMB.. It uses AWS Application Migration Service (AWS MGN) to lift-and-shift the Windows Server 2012 R2 instance without refactoring, native backup/restore for SQL Server 2014 to minimize complexity, and Amazon FSx for Windows File Server to provide a fully managed SMB file share with low-latency access for CAD drawings. This approach meets the 3-month timeline, avoids application refactoring, and reduces operational overhead by replacing the SAN and Windows File Server with managed AWS services.

Answer

Use AWS App2Container to containerize the Windows application and deploy it on Amazon ECS. Migrate the database to Amazon RDS for SQL Server. Use Amazon EFS for the CAD file share.

Answer

Use AWS Database Migration Service (DMS) to migrate the SQL Server database to Amazon RDS for SQL Server. Use AWS Server Migration Service (SMS) to replicate the Windows server to an EC2 instance. Use AWS Storage Gateway file gateway to present the CAD files from Amazon S3.

Answer

Use AWS Application Migration Service (AWS MGN) to replicate the Windows server to an EC2 instance. Migrate the SQL Server database using native backup and restore. Use Amazon S3 with a VPC endpoint for the CAD file share, and mount S3 as a network drive using an S3 file gateway.

Question 6

Drag and drop the steps to configure an SAP S/4HANA high-availability cluster using AWS Resilience Hub into the correct order.

Accepted Answer

1. Define the application stack in Resilience Hub. 2. Associate a resilience policy and run an assessment. 3. Implement the recommended changes (e.g., configure HA cluster). 4. Validate the configuration with a test and monitor using Resilience Hub.. Resilience Hub helps assess and improve HA by defining stack, assessing policy, implementing changes, testing, and monitoring.

Answer

1. Define the application stack. 2. Implement recommended changes. 3. Associate a resilience policy and run an assessment. 4. Validate and monitor.

Answer

1. Associate a resilience policy and run an assessment. 2. Define the application stack. 3. Implement recommended changes. 4. Validate and monitor.

Answer

1. Define the application stack. 2. Associate a resilience policy and run an assessment. 3. Validate and monitor. 4. Implement recommended changes.

Question 7

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

Accepted Answer

Create the CloudFormation template, then upload it to Amazon S3, then launch the stack, then verify the SAP HANA installation.. CloudFormation automation involves template creation, upload, stack launch, provisioning, and verification.

Answer

Create the CloudFormation template, then launch the stack, then upload it to Amazon S3, then verify the SAP HANA installation.

Answer

Upload the template to Amazon S3, then create the CloudFormation template, then launch the stack, then verify the SAP HANA installation.

Answer

Create the CloudFormation template, then upload it to Amazon S3, then verify the SAP HANA installation, then launch the stack.

Question 8

Match the SAP HANA deployment option to its description.

Accepted Answer

Scale-up (Single Node): All SAP HANA resources are contained within a single large EC2 instance.. SAP HANA on AWS can be deployed as Scale-up (single large instance) or Scale-out (multiple smaller instances). High availability is achieved through HANA System Replication (HSR) to a standby, while backup uses cloud-native methods like EBS snapshots. Distractors swap definitions to test understanding.

Answer

Scale-up (Single Node): Multiple EC2 instances work together as a distributed system.

Answer

HANA System Replication (HSR): Using EBS snapshots for backup.

Question 9

Match the SAP transport type to its description.

Accepted Answer

Workbench transport: Contains repository objects like programs and function modules. Workbench transports carry repository objects (ABAP programs, dictionary objects), while Customizing transports carry client-specific configuration. Transport of Copies duplicates existing transport requests. Common confusions involve swapping these definitions.

Answer

Workbench transport: Contains configuration settings

Answer

Customizing transport: Contains ABAP development objects

Answer

Transport of Copies: Used for emergency corrections without a transport request

Question 10

During a migration of an SAP system to AWS, the SAP application team reports that batch jobs are failing with an error 'RFC connection refused'. The on-premises system and AWS are connected via a VPN. What is the MOST likely cause?

Accepted Answer

The security group attached to the SAP instance does not allow inbound RFC traffic. Security groups act as a virtual firewall for EC2 instances, controlling inbound and outbound traffic. If the security group for the SAP instance does not allow inbound RFC traffic (e.g., on ports 3300 or 3200 for SAP RFC), connections will be refused. Option B (VPN bandwidth) would cause timeouts or slow transfers, not immediate connection refusal. Option C (network ACLs) operates at the subnet level and stateless; they could block RFC ports, but since the error is specifically 'RFC connection refused' and it's a common misconfiguration, security groups are more likely the culprit. Option D (route table) is for routing traffic between networks; if there were no route to on-premises, traffic would not reach AWS at all, rather than being refused.

Answer

The VPN bandwidth is insufficient causing timeouts

Answer

The network ACLs are blocking the RFC ports

Answer

The route table does not have a route to the on-premises network

Question 11

A company is migrating an SAP BusinessObjects environment to AWS. They need to ensure high availability for the web tier and have a requirement to use a single DNS name for end users. Which AWS service should they use to distribute traffic across multiple web servers?

Accepted Answer

Application Load Balancer. Application Load Balancer (ALB) operates at Layer 7 and can distribute HTTP/HTTPS traffic across multiple web servers, providing health checks and a single DNS name. Option A (Amazon CloudFront) is a content delivery network, not a load balancer. Option B (Network Load Balancer) operates at Layer 4 and is ideal for TCP/UDP traffic, not web application traffic. Option C (Amazon Route 53 weighted routing policy) distributes traffic based on weights but does not provide built-in health checks or load balancing features like connection draining and path-based routing.

Answer

Amazon CloudFront

Answer

Network Load Balancer

Answer

Amazon Route 53 weighted routing policy

Question 12

A company is migrating a large SAP HANA database to AWS. They plan to use AWS DMS for ongoing replication. The source database is Oracle. During the full load phase, DMS reports an error: 'Failed to add supplemental logging for table'. What is the MOST likely cause?

Accepted Answer

The source database does not have supplemental logging enabled. The error 'Failed to add supplemental logging' indicates that DMS cannot capture changes because supplemental logging is not enabled on the source Oracle database. Supplemental logging is required for DMS to track changes during ongoing replication. Option A correctly identifies this missing prerequisite. Option B (target storage insufficient) would cause target-side errors, not this specific error. Option C (network latency) would cause connectivity or timeout issues. Option D (source database memory) would cause performance issues, not a supplemental logging error.

Answer

The target database storage is insufficient

Answer

The network latency between source and target is too high

Answer

The source database does not have enough memory for DMS

Question 13

A company is migrating an SAP system to AWS and needs to retain the same hostname for the SAP application server after migration. Which configuration should the company use?

Accepted Answer

Create a private hosted zone in Amazon Route 53 with an A record. A private hosted zone in Amazon Route 53 allows you to create an A record that maps a custom hostname to the private IP address of an EC2 instance. This ensures that the SAP application server retains the same hostname after migration, as DNS resolution within the VPC will consistently return the instance's private IP, regardless of instance changes or restarts.

Answer

Assign an Elastic IP to the EC2 instance and update the /etc/hosts file

Answer

Create a CNAME record in a public hosted zone pointing to the EC2 instance

Answer

Use a public hosted zone in Route 53 with an A record

Question 14

A company is migrating an SAP system to AWS and wants to use AWS Systems Manager for patching. The SAP application server is running Windows. What is a prerequisite for Systems Manager to manage the instance?

Accepted Answer

Install the AWS Systems Manager Agent (SSM Agent) on the instance. AWS Systems Manager requires the SSM Agent to be installed and running on managed instances to perform patching and other management operations. The SSM Agent processes Systems Manager requests, executes run commands, and reports instance state back to the Systems Manager service. Without the agent, the instance cannot communicate with the Systems Manager endpoint or receive patching instructions.

Answer

Install the Amazon CloudWatch agent on the instance

Answer

Enable AWS Config on the instance

Answer

Assign a public IP address to the instance

Question 15

An organization is migrating an SAP system from on-premises to AWS. The SAP system uses a shared file system (NFS) for transport directories. The company wants a fully managed NFS solution on AWS. Which service should they use?

Accepted Answer

Amazon Elastic File System (EFS). Amazon EFS is a fully managed NFS file system that supports the NFSv4.1 and NFSv4.0 protocols, making it the ideal choice for SAP transport directories that require a shared POSIX-compliant file system. It provides high availability, automatic scaling, and eliminates the need to manage underlying storage infrastructure, directly matching the requirement for a fully managed NFS solution on AWS.

Answer

Amazon Elastic Block Store (EBS)

Answer

Amazon FSx for Windows File Server

Answer

Amazon S3