Exam AWS-SysOps topic 1 question 652 discussion

D is correct. if there is more insert query going to aurora database it will spike the cpu utilization.

it say An Application performs read-heavy operations ....then How insertLatency matrix will help to find CPU usage

monitoring the DatabaseConnections and InsertLatency metrics (Option D) in addition to the CPUUtilization metric is recommended. These metrics can provide valuable insights into the number of connections and latency for insert queries, which can help diagnose the cause of the CPU surge.

According to chat GPT the Answer is A. To understand the CPU surge on an Amazon Aurora DB instance, in addition to monitoring the CPUUtilization CloudWatch metric, the SysOps Administrator should monitor the following: 1. Database Connections: 2. Disk Queue Depth: High Disk Queue Depth 3. SQL Statements: 4. Memory Usage: SysOps Administrator can monitor the "FreeableMemory"

D is the answer One should also look for DatabaseConnections and InsertLatency for the number of connections to the DB instance and latency to insert queries.

I believe having high CPU utilization will result in insert latency and that can arise from having high DB connections .. Memory seem irrelevant .. i would choose D over A

It's C. If an Aurora Replica runs out of CPU credits before the primary instance, the lag behind the primary instance results in the Aurora Replica frequently restarting. This result is common when an application has a heavy load of read operations distributed among Aurora Replicas in an Aurora MySQL DB cluster, at the same time that the primary instance has a minimal load of write operations. Ref: https://docs.amazonaws.cn/en_us/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html

D. DatabaseConnections and InsertLatency for the number of connections to the DB instance and latency for insert queries.

I'll go with D

I think it is saying the cpu of primary instance is high, not the replica. So replicalatecy is not the main point. However, insert is made on the primary instance. So I prefer D.

D should be right as your concern is to understand why the CPU has increased, so you may need to understand how many DML queries are ongoing and from each of the connections in addition to their latency IOP .. this is closer to just monitor the CPU and memory

Ans: A https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/MonitoringOverview.html Investigate consistent or trending variances from your baseline. The following metrics are often the source of performance issues: 1) High CPU or RAM consumption 2) Disk space consumption 3) Network traffic 4) Database connections 5) IOPS metrics

I will go with D due to this links https://pegacert.com/vendor/aws/soa-c01/application-performs-readheavy-operations-amazon-aurora-23806 https://www.freecram.com/question/Amazon.AWS-SysOps.v2019-09-03.q368/an-application-performs-read-heavy-operations-on-an-amazon-aurora-db-instance-the-sysops-administrator

performs read-heavy operations and not insert anything so D incorrect. The Answer is A

It's C. Because it is a Read heavy application. You can assume it has a Read Only setup. So you want know about the database connection and the replication lag.

performs read-heavy operations and not insert anything so D incorrect. The Answer is A

why not A? Because RAM has a direct influence on CPU utilization.i.e in many scenarios we upgrade to bigger instance when CPU utilisation is high, upgrading means higher RAM too ri8.???