CCNA Management and Operations Questions

Option C is correct because RDS supports modifying allocated storage online with minimal downtime. Option A is wrong because creating a new instance and migrating involves downtime. Option B is wrong because increasing storage is not a backup.

Option D is wrong because deleting logs may cause issues.

Option C is correct because with automated backups and a retention period of 7 days, the latest restorable time is typically within the last 5 minutes, but the maximum point-in-time recovery window is 7 days. Option A is wrong because it is too short. Option B is wrong because it is the backup window, not recovery window.

Option D is wrong because it exceeds the retention period.

Option A is correct because 'ConsumedReadCapacityUnits' tracks the number of read capacity units consumed, and an alarm can be set on this metric. Option B is wrong because 'ProvisionedReadCapacityUnits' is only for provisioned mode. Option C is wrong because 'ReadThrottleEvents' indicates throttling, not request rate.

Option D is wrong because 'SuccessfulRequestLatency' measures latency, not request rate.

Option B is correct because increasing storage quickly avoids potential downtime and I/O throttling. Option A is wrong because switching to Provisioned IOPS addresses latency but not the storage shortage. Option C is wrong because adding a read replica does not increase storage on the primary.

Option D is wrong because modifying the instance class may not address storage space.

Option C is correct because the policy allows CreateDBSnapshot on resources matching 'mydb-*', but the snapshot name must match that pattern. Option A is wrong because DeleteDBInstance is denied. Option B is wrong because the user can create snapshots matching the pattern.

Option D is wrong because the user can describe instances.

Option B is correct because RDS Proxy manages connection pooling efficiently, reducing the number of connections to the database and lowering CPU overhead. Option A is wrong because increasing max_connections may lead to resource exhaustion. Option C is wrong because read replicas do not reduce write connection load.

Option D is wrong because switching to a smaller instance would worsen the problem.

Option B is correct because AWS DMS can perform continuous replication. Option C is correct because using a large instance reduces migration time. Option E is correct because disabling backups during migration reduces overhead.

Option A is wrong because AWS SCT is for schema conversion, not data migration. Option D is wrong because manual snapshot is for backup, not migration.

Options A and D are correct. Hot partitions (A) can cause throttling even with Auto Scaling because a single partition can exceed its limit. Throttling due to exceeding the maximum provisioned capacity (D) can also occur.

Option B is wrong because Global Tables replicate writes but do not cause throttling. Option C is wrong because Auto Scaling is disabled? (the question says enabled, so C is irrelevant). Option E is wrong because DAX is for reads.

Option A is correct. Adding a read replica (sharing read traffic) reduces CPU on the primary. Option B is wrong because increasing to a larger node type is more expensive than adding replicas.

Option C is wrong because increasing maxmemory-policy does not reduce CPU. Option D is wrong because enabling encryption adds overhead.

Option A is correct because increasing the size of the InnoDB redo log files reduces checkpoint frequency. Option B is wrong because decreasing would increase checkpoint frequency. Option C is wrong because innodb_flush_log_at_trx_commit controls durability, not checkpoint frequency.

Option D is wrong because innodb_buffer_pool_size affects memory, not directly checkpointing.

Switching to on-demand capacity handles unpredictable spikes automatically and reduces throttling. Using DynamoDB Accelerator (DAX) reduces read load by caching. Auto scaling adjusts capacity based on load, but on-demand is better for unpredictable spikes.

Reducing read capacity units would worsen throttling. Disabling auto scaling is counterproductive.

Option B is correct because upgrading to a larger instance class provides more CPU capacity. Option A is wrong because decreasing max connections may cause connection errors. Option C is wrong because increasing storage does not directly affect CPU.

Option D is wrong because switching to Provisioned IOPS improves I/O, but CPU is the bottleneck.

Options B and D are correct. Running VACUUM reclaims space and re-sorts data, improving performance. Analyzing tables updates statistics for the query optimizer.

Option A is incorrect because increasing the number of nodes improves performance but is not an optimization action; it's a scaling action. Option C is incorrect because disabling compression reduces performance. Option E is incorrect because enabling encryption does not directly affect query performance.

Option B is correct because enabling RDS Proxy reduces connection overhead and provides a connection pool, mitigating timeouts. Option A is incorrect because increasing connect_timeout only delays the timeout, not the root cause. Option C is incorrect because adding readers does not help with writer connection timeouts.

Option D is incorrect because the issue is not related to TLS.

Adding more reader instances distributes the read load. Using Aurora Auto Scaling automatically adjusts reader capacity. Enabling read replicas in different regions can offload read traffic locally.

Option B (increasing writer instance size) does not directly help reads; Option D (using ElastiCache) is for application-level caching, not database read scaling; Option E (using DynamoDB Accelerator) is irrelevant.

Option C is correct because AWS Systems Manager Patch Manager can automate patching of RDS instances. Option A is wrong because RDS Automated Backups are for backups, not patching. Option B is wrong because RDS Maintenance Windows handle minor engine versions but not OS patching.

Option D is wrong because AWS Config is for configuration compliance.

Option A is correct because the application should connect to the reader endpoint to distribute read queries across the read replicas. Option B is incorrect because the cluster endpoint points to the writer. Option C is incorrect because the instance endpoint is for a specific instance.

Option D is incorrect because a custom endpoint is used for specific reader groups, but the standard reader endpoint is simpler for general offloading.

Option D is correct because the BurstBalance at 0% indicates the gp2 volume exhausted its burst credits, leading to I/O throttling and increased latency, which likely caused the failover. Switching to Provisioned IOPS (io1/io2) provides consistent performance. Option A is wrong because increasing instance size does not directly address storage I/O performance.

Option B is wrong because increasing backup retention does not affect storage performance. Option C is wrong because additional read replicas do not improve write performance on the primary.

Option C is correct because using a CNAME that points to the RDS endpoint ensures that after failover, the DNS record updates automatically, reducing downtime. Option A is wrong because setting TTL too low may cause DNS propagation delays. Option B is wrong because the RDS endpoint already handles failover.

Option D is wrong because Connection pooling does not reduce failover time.

AWS DMS supports homogeneous and heterogeneous migrations with minimal downtime by replicating ongoing changes. RDS for Oracle does not support native Oracle Data Guard (B) across environments. AWS SCT (C) is for schema conversion, not full data migration.

AWS Database Migration Service (D) is the recommended service, but option A is AWS DMS which is correct.

Option B is correct because the EXPLAIN command shows the query execution plan, including join types, distribution styles, and sort keys, which helps identify bottlenecks. Option A is incorrect because STL_QUERY logs completed queries but does not provide the plan. Option C is incorrect because SVV_TABLE_INFO gives table statistics, not the query plan.

Option D is incorrect because WLM metrics show queue performance, not individual query plans.

Option D is correct because implementing exponential backoff with retries handles throttling errors gracefully without over-provisioning. Option A is incorrect because it is costly and inefficient to over-provision. Option B is incorrect because DynamoDB Accelerator (DAX) is a cache, but it does not increase write capacity; it can reduce read load but not write throttling.

Option C is incorrect because switching to on-demand may be more cost-effective for spiky traffic, but it is not the most cost-effective if traffic is predictable; the question asks for most cost-effective.

Option D is correct because Aurora MySQL does not rely on binlogs for PITR; it uses its own storage-based recovery. Disabling binlog altogether saves storage and reduces I/O. Option A is incorrect because reducing the retention period may not be sufficient if binlogs are still accumulating.

Option B is incorrect because binlog files are not stored on the DB instance but in the cluster volume; deleting them manually is not recommended. Option C is incorrect because using the Binary Log Export feature is for exporting logs, not reducing storage.

CloudWatch Logs capture connection logs. Lambda can query the database to terminate idle connections. Option A is correct.

Option B uses EC2 which is less automated. Option C uses RDS Event Notifications which do not include connection details. Option D lacks Lambda automation.

Option B is correct because the application's connection pool may have stale connections to the old primary, and the DNS TTL of 60 seconds delays the resolution to the new primary. Option A is wrong because RDS failover typically completes in 1-2 minutes. Option C is wrong because Multi-AZ DNS records are updated automatically.

Option D is wrong because a cold start would cause longer outage.

On-Demand capacity can handle spikes but has per-partition throughput limits. If a hot partition exists, writes to that partition may exceed its limit. Option A is correct because uneven partition keys cause throttling.

Option B is incorrect because On-Demand does not have table-level limits. Option C is not the primary cause. Option D is incorrect as GSI writes also consume write capacity.

Using a read replica for failover is not supported in RDS MySQL; Multi-AZ is the correct approach. Option D (Multi-AZ cluster) provides faster failover than Multi-AZ with a standby. Option A is correct because RDS Multi-AZ cluster uses a writer and two reader instances, reducing failover time.

Option B is not supported. Option C increases cost without performance benefit.

Option D is correct because enabling Multi-AZ with automatic failover ensures a replica in a different AZ is promoted, but the key is to pre-warm the cache or use a larger instance. However, among the options, using a cluster mode with shards distributes load and reduces impact. Option A is incorrect because disabling replica reads doesn't help.

Option B is incorrect because increasing replica count without cluster mode may not help. Option C is incorrect because automatic backup does not reduce latency after failover.

Option C is correct because on-demand tables can throttle if you exceed the previous peak traffic by more than double in a short time, but since WriteThrottleEvents is zero, latency is likely due to hot partitions. Option A is wrong because throttling would show WriteThrottleEvents > 0. Option B is wrong because insufficient WCUs is not applicable for on-demand.

Option D is wrong because while DAX can reduce read latency, it does not affect write latency.

Option C is correct because enabling the Neptune Query Language (SPARQL or Gremlin) explain plan can show how queries are executed and whether indexes are used. Option A is incorrect because instance metrics show system health, not query execution details. Option B is incorrect because removing indexes would worsen performance.

Option D is incorrect because adding readers does not fix query optimization.

Option C is correct because read replicas offload read traffic from the primary, reducing CPU utilization. Option A is wrong because increasing instance size is more expensive and may not be optimal. Option B is wrong because vertical scaling is not the most cost-effective.

Option D is wrong because adding storage does not reduce CPU.

Option B is correct. Enhanced Monitoring provides OS-level metrics for RDS instances. Option A is wrong because Performance Insights provides database performance metrics, not OS metrics.

Option C is wrong because CloudWatch provides hypervisor-level metrics, not OS metrics. Option D is wrong because CloudTrail logs API calls.

RDS automated backups provide PITR within the retention period. The maximum retention period is 35 days. Enabling automated backups with 35-day retention meets the requirement with no additional cost beyond the backup storage.

Option B is correct. Option A (manual snapshots) does not provide PITR. Option C (cross-region) adds cost.

Option D (AWS Backup) adds complexity and cost.

Option A, Option D, and Option E are correct. Option A increases write capacity immediately. Option D implements exponential backoff to handle throttling.

Option E uses DynamoDB Auto Scaling to adjust capacity. Option B is wrong because DAX is for reads, not writes. Option C is wrong because switching to on-demand may cause higher costs and is not a quick fix for the spike.

Option A is correct because lowering the minimum to 200 RCUs ensures auto scaling does not scale below the actual usage, reducing provisioned capacity costs. Option B is wrong because decreasing the maximum could cause throttling during spikes. Option C is wrong because increasing the minimum would increase costs unnecessarily.

Option D is wrong because disabling auto scaling would require manual management and may lead to over-provisioning.

Option A is correct because lowering the minimum to 100 WCUs matches the actual usage, preventing over-provisioning. Option B is wrong because decreasing the maximum could cause throttling during spikes. Option C is wrong because increasing the minimum would increase costs.

Option D is wrong because disabling auto scaling would require manual management.

Option C is correct because Redshift Spectrum allows querying data directly in S3, offloading compute from the cluster. Option A is wrong because increasing WLM concurrency may actually slow down queries due to resource contention. Option B is wrong because adding more nodes can improve performance but may be overkill and more expensive.

Option D is wrong because compression is for storage, not query performance.

Correct answers are B and D. B: Create a CloudWatch alarm using the 'DatabaseConnections' metric. D: Set the alarm threshold to 80% of max_connections and the period to 1 minute for timely alerts.

A is wrong because RDS Performance Insights does not provide connection count metrics via CloudWatch. C is wrong because Enhanced Monitoring provides OS metrics, not DB connection counts. E is wrong because the max_connections parameter should be checked from the DB parameter group, not the alarm.

Option A is correct because using the Query API with ScanIndexForward set to false and Limit 1 will return the most recent item for a given partition key. Option B is wrong because ScanIndexForward=true returns items in ascending order, which would give the oldest item first. Option C is wrong because Scan operations scan the entire table and are inefficient.

Option D is wrong because GetItem requires both partition and sort key; the sort key value is not known in advance.

Options B and C are correct because using DynamoDB Auto Scaling for writes will adjust capacity based on demand, and reducing provisioned reads to actual usage will save costs. Option A is wrong because switching to on-demand may increase costs if the workload is predictable. Option D is wrong because reducing writes would cause throttling.

Option E is wrong because using DAX does not reduce write costs.

Option B is correct because using a consistent hashing algorithm ensures that keys are evenly distributed across nodes, reducing evictions and improving hit ratio. Option A is wrong because increasing TTL may cause stale data but does not directly improve hit ratio. Option C is wrong because Cluster Mode Off would limit scalability but not necessarily improve hit ratio.

Option D is wrong because random TTLs can lead to premature evictions and reduce hit ratio.

Option B is correct because point-in-time recovery is performed through the RDS console or API by specifying the time. Option A is wrong because it restores the latest backup. Option C is wrong because it restores a manual snapshot.

Option D is wrong because automated backups are used for point-in-time recovery.

Option D is correct because Amazon CloudWatch Contributor Insights can analyze DynamoDB logs and identify the most accessed partition keys, helping to pinpoint hot partitions. Option A is incorrect because CloudWatch Logs Insights requires enabling VPC Flow Logs, which is not specific to DynamoDB. Option B is incorrect because AWS X-Ray traces requests but does not provide partition-level metrics.

Option C is incorrect because DynamoDB Streams capture changes, not access patterns.

Option B is correct. The Performance Insights dashboard in Aurora provides SQL query metrics with low overhead and can publish logs to CloudWatch Logs. Option A is wrong because database audit logs are for security compliance, not performance analysis.

Option C is wrong because the general log is high overhead. Option D is wrong because slow query log only captures slow queries, not all queries.

Option C is correct because Amazon RDS for MySQL supports the 'wait_timeout' parameter, which automatically closes idle connections after the specified number of seconds. Reducing this value from the default 28800 seconds will terminate sleeping connections sooner. Option A is incorrect because manually killing connections is not automated.

Option B is incorrect because RDS Proxy does not terminate idle connections; it manages connection pooling. Option D is incorrect because modifying 'max_connections' does not affect idle connections.

Option A is correct because DynamoDB Auto Scaling can adjust capacity based on demand, and setting a target utilization of 70% allows headroom for spikes. Option B is wrong because on-demand capacity is simpler but can be more expensive for predictable workloads. Option C is wrong because increasing WCU to 8000 permanently would be costly.

Option D is wrong because SQS adds latency and does not solve the throttling issue in real-time.

Option C is correct because adding a random suffix to the partition key distributes writes across partitions, avoiding hot partitions. Option A is wrong because increasing WCU does not solve the partition hot spot, as the limit per partition is fixed. Option B is wrong because switching to on-demand still has per-partition limits.

Option D is wrong because a GSI does not change the base table's write distribution.

Option A is correct because Multi-AZ provides automatic failover within minutes, meeting the RTO. Option D is correct because a cross-region read replica with automatic backups allows replication with low RPO. Option B is wrong because manual snapshots have higher RPO.

Option C is wrong because a single-AZ instance with backups takes longer to restore. Option E is wrong because AWS DMS is for migration, not DR.

Option C is correct because changing the backup retention period takes effect immediately without reboot. Option A is incorrect because it requires a reboot. Option B is incorrect because it requires a reboot.

Option D is incorrect because it requires a reboot.

Option B is correct because AWS DMS with ongoing replication can minimize downtime by capturing changes. Option A is incorrect because native export/import requires downtime. Option C is incorrect because RMAN backup and restore requires downtime for restore.

Option D is incorrect because copying dump files also requires downtime.

Automated backups with a retention period of 35 days provide point-in-time recovery. Cross-region snapshots via AWS Backup provide additional protection. A read replica can be promoted quickly for failover.

Option A (daily manual snapshots) may not meet the 5-minute RPO. Option D (single-AZ) is not as resilient. The correct options are B, C, and E.

Options A, C, and D are correct. Implementing retry logic with exponential backoff handles throttling gracefully. Using DynamoDB Accelerator (DAX) reduces read load on the table, which can help with read throttling.

Designing the application to handle throttling by retrying ensures resilience. Option B is incorrect because switching to provisioned capacity may not be cost-effective and does not inherently reduce throttling. Option E is incorrect because enabling auto scaling is not applicable to on-demand mode.

Option A is correct. DynamoDB Accelerator (DAX) is a fully managed, highly available, in-memory cache that reduces read latency. Option B is wrong because auto scaling is for provisioned capacity, not on-demand.

Option C is wrong because read replicas are not a DynamoDB feature. Option D is wrong because DynamoDB Streams does not cache data.

Option A is correct because CPUUtilization is a default metric. Option B is correct because DatabaseConnections is a default metric. Option C is incorrect because it is a metric for DynamoDB.

Option D is incorrect because it is for Redshift. Option E is incorrect because it is not a default metric.

Option C is correct because on-demand tables can throttle if a GSI's write capacity is exceeded. Option A is incorrect because on-demand capacity scales automatically for the base table. Option B is incorrect because throttling is not due to read-heavy workloads on the base table.

Option D is incorrect because partition keys are automatically managed.

Option A is correct because RDS for PostgreSQL supports pgAudit extension. Option B is incorrect because it is not a feature. Option C is incorrect because it is for MySQL.

Option D is incorrect because it is for Oracle.

Option B is correct because 'modify-db-instance' with --multi-az is the correct AWS CLI command to enable Multi-AZ. Option A is wrong because 'create-db-instance' is for new instances, not modifying existing ones. Option C is wrong because 'reboot-db-instance' restarts the instance but does not change Multi-AZ.

Option D is wrong because 'create-db-cluster' is for Aurora, not for converting a single DB instance to Multi-AZ.