Question 1mediummultiple choice
Read the full Migration explanation →PAS-C01 Migration • Complete Question Bank
Complete PAS-C01 Migration question bank — all 0 questions with answers and detailed explanations.
Refer to the exhibit. Error from AWS DMS task: "Last Error: Failed to start change data capture for table 'sales.orders'. Details: The source database is not configured for full supplemental logging. To enable full supplemental logging, run: ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (ALL) COLUMNS;"
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag a concept onto its matching description — or click a concept then click the description.
Single large instance with more memory
Multiple nodes in a cluster for horizontal scaling
Certified hardware with flexible storage options
Fully managed cloud database service
Drag a concept onto its matching description — or click a concept then click the description.
For ABAP development objects
For configuration changes
Copies transport without original history
Moves objects between systems preserving change history
Refer to the exhibit.
```
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": "rds:*",
"Resource": "*"
},
{
"Effect": "Allow",
"Action": "ec2:Describe*",
"Resource": "*"
},
{
"Effect": "Deny",
"Action": "rds:DeleteDBInstance",
"Resource": "arn:aws:rds:us-east-1:123456789012:db:prod-sap-db"
}
]
}
```Refer to the exhibit.
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": "s3:PutObject",
"Resource": "arn:aws:s3:::migration-bucket/*"
}
]
}Refer to the exhibit.
{
"AWSTemplateFormatVersion": "2010-09-09",
"Resources": {
"MyEC2Instance": {
"Type": "AWS::EC2::Instance",
"Properties": {
"ImageId": "ami-12345678",
"InstanceType": "t2.micro"
}
}
}
}Refer to the exhibit.
```json
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"ec2:DescribeInstances",
"ec2:StartInstances",
"ec2:StopInstances",
"ec2:DescribeVolumes",
"ec2:AttachVolume",
"ec2:DetachVolume"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"s3:GetObject",
"s3:PutObject"
],
"Resource": "arn:aws:s3:::sap-migration-backup/*"
}
]
}
```Refer to the exhibit.
```
# AWS Launch Wizard for SAP - Deployment Parameters
{
"SAPSystemID": "PRD",
"SAPApplicationVersion": "SAP S/4HANA 2020",
"DatabaseType": "HANA",
"DatabaseInstanceClass": "r5.8xlarge",
"ApplicationInstanceClass": "r5.4xlarge",
"BackupRetentionDays": 30,
"HighAvailability": true
}
```Refer to the exhibit. The following is an AWS CLI command output:
{
"Replications": [
{
"ReplicationTaskIdentifier": "sap-migration-task",
"SourceEndpointArn": "arn:aws:dms:us-east-1:123456789012:endpoint:AAAA",
"TargetEndpointArn": "arn:aws:dms:us-east-1:123456789012:endpoint:BBBB",
"ReplicationTaskStats": {
"FullLoadProgressPercent": 100,
"TablesLoaded": 150,
"TablesLoading": 0,
"TablesQueued": 0,
"TablesErrored": 0,
"CdcLatencySource": 5000,
"CdcLatencyTarget": 5000
}
}
]
}Refer to the exhibit. The following is an IAM policy attached to an EC2 instance role:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"s3:GetObject",
"s3:PutObject",
"s3:DeleteObject"
],
"Resource": "arn:aws:s3:::sap-migration-bucket/*"
},
{
"Effect": "Allow",
"Action": [
"dms:CreateReplicationTask",
"dms:StartReplicationTask"
],
"Resource": "*"
}
]
}Refer to the exhibit. The following is a CloudFormation template snippet:
Parameters:
InstanceType:
Type: String
Default: r5.2xlarge
AllowedValues:
- r5.2xlarge
- r5.4xlarge
- x1e.2xlarge
DBInstanceClass:
Type: String
Default: db.r5.2xlarge
AllowedValues:
- db.r5.2xlarge
- db.r5.4xlarge
- db.x1e.2xlarge
Resources:
SAPEC2Instance:
Type: AWS::EC2::Instance
Properties:
InstanceType: !Ref InstanceType
ImageId: ami-0abcdef1234567890
SAPRDSInstance:
Type: AWS::RDS::DBInstance
Properties:
DBInstanceClass: !Ref DBInstanceClass
Engine: SAP HANA
MasterUsername: admin
MasterUserPassword: password
AllocatedStorage: 1000Refer to the exhibit.
```
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"ec2:DescribeInstances",
"ec2:CreateTags",
"ec2:StartInstances",
"ec2:StopInstances"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"dms:CreateReplicationTask",
"dms:StartReplicationTask",
"dms:DescribeReplicationTasks"
],
"Resource": "arn:aws:dms:us-east-1:123456789012:task:*"
}
]
}
```Refer to the exhibit.
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"ec2:DescribeInstances",
"ec2:StartInstances",
"ec2:StopInstances"
],
"Resource": "*"
}
]
}Refer to the exhibit.
Resources:
MySAPInstance:
Type: AWS::EC2::Instance
Properties:
InstanceType: r5.2xlarge
ImageId: ami-0abcdef1234567890
BlockDeviceMappings:
- DeviceName: /dev/sdf
Ebs:
VolumeSize: 100
VolumeType: gp3
Tags:
- Key: Name
Value: SAP-ASCSA global company is migrating its SAP ERP system to AWS. The system runs SAP ECC on IBM AIX with Oracle Database. The company plans to move to SAP S/4HANA on AWS. The source system is 5 TB in size. The network bandwidth between the on-premises data center and AWS is 100 Mbps. The migration must be completed within a 2-week window with minimal downtime. The company has a SAP license that allows running S/4HANA on certified hardware. They have already used AWS SCT to convert the database schema to SAP HANA-compatible format. They now need to execute the data migration. The team is considering the following options:
Option A: Use AWS DMS with ongoing replication from Oracle to HANA, then perform a final cutover. Option B: Use AWS Snowball Edge to transfer the Oracle backup files to AWS, then restore to HANA. Option C: Use AWS DataSync to copy the Oracle data files to Amazon EFS, then import into HANA. Option D: Use SAP HANA system replication from the source Oracle database to the target HANA database.
Which option is the most feasible and efficient for this migration?
A mid-size company is migrating its SAP Business One on SAP HANA to AWS. The current system runs on a single server with 256 GB RAM and uses a local disk for HANA data. The company wants to minimize capital expenditure and operational overhead. They have already sized the target EC2 instance as an x1e.2xlarge (122 GB RAM) but later realized that SAP HANA requires at least 256 GB RAM for their workload. The migration deadline is in one week. The company has a limited budget and cannot change the instance type to a larger one due to procurement delays. They have an 8 TB EBS gp2 volume attached for HANA data, but it is not meeting performance requirements. The team proposes the following actions:
Option A: Increase the EBS volume size to 16 TB to improve IOPS. Option B: Switch to EBS io2 volumes with provisioned IOPS to meet performance requirements, and use AWS DMS to migrate the data. Option C: Use an instance with instance store SSDs (e.g., i3en.2xlarge) to get high local I/O performance, and migrate using SAP HANA backup and restore. Option D: Use Amazon FSx for NetApp ONTAP as the storage backend for HANA, as it provides high performance and is certified for SAP HANA.
Which option is the best course of action considering the constraints?
Refer to the exhibit.
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"s3:GetObject",
"s3:PutObject",
"s3:DeleteObject"
],
"Resource": "arn:aws:s3:::migration-bucket/*"
},
{
"Effect": "Allow",
"Action": [
"ec2:DescribeInstances",
"ec2:StartInstances",
"ec2:StopInstances"
],
"Resource": "*"
}
]
}Refer to the exhibit. Error: "SAP HANA database migration failed: Incompatible character set. Source database uses 'UTF-8', target database uses 'ISO-8859-1'."
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"s3:GetObject",
"s3:PutObject",
"s3:DeleteObject"
],
"Resource": "arn:aws:s3:::example-bucket/*"
},
{
"Effect": "Allow",
"Action": [
"s3:ListBucket"
],
"Resource": "arn:aws:s3:::example-bucket"
}
]
}Refer to the exhibit.
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"ec2:DescribeInstances",
"ec2:StartInstances",
"ec2:StopInstances"
],
"Resource": "*"
}
]
}Refer to the exhibit. $ aws s3 cp s3://my-sap-backup/backup.hdb /mnt/restore/backup.hdb Error: An error occurred (AccessDenied) when calling the GetObject operation: Access Denied
Refer to the exhibit.
Exhibit:
```
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"dms:CreateReplicationTask",
"dms:StartReplicationTask",
"dms:DescribeReplicationTasks"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"s3:PutObject",
"s3:GetObject",
"s3:ListBucket"
],
"Resource": "arn:aws:s3:::migration-bucket/*"
}
]
}
```Refer to the exhibit.
Exhibit:
```
{
"AWSTemplateFormatVersion": "2010-09-09",
"Resources": {
"SAPApplicationServer": {
"Type": "AWS::EC2::Instance",
"Properties": {
"InstanceType": "r5.2xlarge",
"ImageId": "ami-0abcdef1234567890",
"BlockDeviceMappings": [
{
"DeviceName": "/dev/xvda",
"Ebs": {
"VolumeSize": 100,
"VolumeType": "gp3"
}
},
{
"DeviceName": "/dev/xvdb",
"Ebs": {
"VolumeSize": 200,
"VolumeType": "io1",
"Iops": 10000
}
}
]
}
}
}
}
```Refer to the exhibit.
```json
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"ec2:DescribeInstances",
"ec2:StartInstances",
"ec2:StopInstances"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"s3:PutObject",
"s3:GetObject"
],
"Resource": "arn:aws:s3:::my-bucket/*"
}
]
}
```Refer to the exhibit.
```json
{
"AWSTemplateFormatVersion": "2010-09-09",
"Description": "SAP HANA HA using Pacemaker",
"Resources": {
"ASCSInstance": {
"Type": "AWS::EC2::Instance",
"Properties": {
"InstanceType": "m5.large",
"ImageId": "ami-0abcdef1234567890",
"SubnetId": "subnet-12345678"
}
},
"ERSInstance": {
"Type": "AWS::EC2::Instance",
"Properties": {
"InstanceType": "m5.large",
"ImageId": "ami-0abcdef1234567890",
"SubnetId": "subnet-12345678"
}
}
}
}Refer to the exhibit.
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"dms:CreateReplicationTask",
"dms:StartReplicationTask",
"dms:DescribeReplicationTasks"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"s3:GetObject",
"s3:PutObject"
],
"Resource": "arn:aws:s3:::my-bucket/*"
},
{
"Effect": "Allow",
"Action": [
"ec2:DescribeVpcs",
"ec2:DescribeSubnets",
"ec2:DescribeSecurityGroups"
],
"Resource": "*"
}
]
}Refer to the exhibit.
{
"Resources": {
"SAPApplicationServer": {
"Type": "AWS::EC2::Instance",
"Properties": {
"InstanceType": "r5.2xlarge",
"ImageId": "ami-0abcdef1234567890",
"SecurityGroupIds": ["sg-12345678"],
"SubnetId": "subnet-12345678",
"BlockDeviceMappings": [
{
"DeviceName": "/dev/xvda",
"Ebs": {
"VolumeSize": 50,
"VolumeType": "gp2"
}
}
],
"Tags": [
{"Key": "Name", "Value": "SAP-AS"}
]
}
}
}
}Refer to the exhibit.
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"dms:CreateReplicationTask",
"dms:StartReplicationTask",
"dms:DescribeReplicationTasks"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"ec2:DescribeVpcs",
"ec2:DescribeSubnets",
"ec2:CreateSecurityGroup"
],
"Resource": "*"
}
]
}{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"dms:CreateReplicationTask",
"dms:StartReplicationTask",
"dms:DescribeReplicationTasks",
"rds:CreateDBInstance",
"rds:DescribeDBInstances",
"s3:GetObject",
"s3:PutObject"
],
"Resource": "*"
}
]
}{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"dms:CreateReplicationTask",
"dms:StartReplicationTask",
"dms:DescribeReplicationTasks",
"dms:StopReplicationTask"
],
"Resource": "*"
}
]
}{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"ec2:DescribeInstances",
"ec2:DescribeImages",
"ec2:DescribeSnapshots",
"ec2:CreateImage",
"ec2:RegisterImage",
"s3:PutObject",
"s3:GetObject",
"s3:ListBucket"
],
"Resource": "*"
}
]
}