ExamTopics Logo
Mail Us[email protected]
Menu
Amazon Discussions
exam questions

Exam AWS Certified SAP on AWS - Specialty PAS-C01 All Questions

View all questions & answers for the AWS Certified SAP on AWS - Specialty PAS-C01 exam
Go to Exam

Exam AWS Certified SAP on AWS - Specialty PAS-C01 topic 1 question 78 discussion

Exam question from Amazon's AWS Certified SAP on AWS - Specialty PAS-C01
Question #: 78
Topic #: 1
[All AWS Certified SAP on AWS - Specialty PAS-C01 Questions]

A global company is planning to migrate its SAP S/4HANA workloads and SAP BW/4HANA workloads to AWS. The company’s database will not grow more than 3 TB for the next 3 years. The company's production SAP HANA system has been designed for high availability (HA) and disaster recovery (DR) with the following configurations:

• HA: SAP HANA system replication configured with SYNC mode and LOGREPLAY operation mode across two Availability Zones with the same size SAP HANA node
• DR: SAP HANA system replication configured with ASYNC mode and LOGREPLAY operation mode across AWS Regions with the same size SAP HANA node

All the SAP HANA nodes in the current configuration are the same size. For HA, the company wants an RPO of 0 and an RTO of 5 minutes. For DR, the company wants an RPO of 0 and an RTO of 3 hours.

How should the company design this solution to meet the RPO and RTO requirements MOST cost-effectively?

  • A. Maintain HA with SAP HANA system replication configured with SYNC mode and table preload turned on across two Availability Zones. In each Availability Zone, use the same size SAP HANA node. Decrease the size of the DR node to at least 64 GiB of memory or the row store size plus 20 GiB, whichever is higher, with ASYNC mode and table preload turned on. Increase the size of the DR node during a DR event.
  • B. Maintain HA with SAP HANA system replication configured with SYNC mode and table preload turned on across two Availability Zones. In each Availability Zone, use the same size SAP HANA node. Decrease the size of the DR node to at least 64 GiB of memory or the row store size plus 20 GiB, whichever is higher, with ASYNC mode and table preload turned off. Increase the size of the DR node during a DR event.
  • C. Maintain HA with SAP HANA system replication across two Availability Zones. Decrease the size of the HA secondary node to at least 64 GiB of memory or the row store size plus 20 GiB, whichever is higher, with SYNC mode and table preload turned on. Increase the size of the HA secondary node during an HA event. Decrease the size of the DR node to at least 64 GiB of memory or the row store size plus 20 GiB, whichever is higher, with table preload turned on. Increase the size of the DR node during a DR event.
  • D. Maintain HA with SAP HANA system replication across two Availability Zones. Decrease the size of the HA secondary node to at least 64 GiB of memory or the row store size plus 20 GiB, whichever is higher, with SYNC mode and table preload turned on. Increase the size of the HA secondary node during an HA event. Decrease the size of the DR node to at least 64 GiB of memory or the row store size plus 20 GiB, whichever is higher, with table preload turned off. Increase the size of the DR node during a DR event.
Show Suggested Answer Hide Answer
Suggested Answer: B 🗳️
by [deleted] at July 14, 2023, 7:41 p.m.
Disclaimers:
  • - ExamTopics website is not related to, affiliated with, endorsed or authorized by Amazon.
  • - Trademarks, certification & product names are used for reference only and belong to Amazon.

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Submit Cancel
Demianwholovesjudo
1 year, 4 months ago
Selected Answer: B
BBBBB Cost optimized - https://docs.aws.amazon.com/sap/latest/sap-hana/hana-ops-ha-dr-hsr.html
upvoted 2 times
...
zzw890827
1 year, 8 months ago
Selected Answer: B
A is wrong sincer turn on the preload is not cost-effective.
upvoted 3 times
...
kaishin0527
1 year, 9 months ago
Selected Answer: A
A: Maintain HA with SAP HANA system replication configured with SYNC mode and table preload turned on across two Availability Zones. In each Availability Zone, use the same size SAP HANA node. Decrease the size of the DR node to at least 64 GiB of memory or the row store size plus 20 GiB, whichever is higher, with ASYNC mode and table preload turned on. Increase the size of the DR node during a DR event. For high availability (HA) scenarios, the SAP HANA system replication is typically configured in SYNC mode to ensure zero Recovery Point Objective (RPO). For optimal Recovery Time Objective (RTO), table preload can be turned on. For disaster recovery (DR), you can use smaller instance types, since they are only used during actual disaster recovery and not for serving normal production load. If you are using system replication for DR, you can use ASYNC mode. The "table preload" option can be turned on to minimize RTO.
upvoted 4 times
...
Frankong
1 year, 9 months ago
What's the difference between A and B?
upvoted 1 times
...
[Removed]
1 year, 9 months ago
Selected Answer: B
Option B is correct because it suggests using ASYNC mode for DR with table preload turned off which will meet the RPO requirement of 0 seconds and an RTO of 3 hours for DR Option A is incorrect because it suggests using SYNC mode for DR which is not cost-effective. Option C is incorrect because it suggests using SYNC mode for HA and preload turned on which may not cost-effective Option D is incorrect because it suggests using ASYNC mode for DR with table preload turned off which will not meet the RPO requirement of 0 seconds1.
upvoted 2 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago