10 realistic exam questions, graded as you go, with the exact rule or statute citation for every answer. Start free, no sign-up.
Timed mock exam
40 questions in 48 minutes, drawn from every topic. No answers shown until the end, then a full score breakdown, your weakest topics and a review of what you missed.
Prices are in US dollars, plus tax where it applies. Stripe, our payment processor, calculates tax at checkout.
All sales are final. If something is really wrong, such as a duplicate charge or a purchase that does not unlock what you bought, write to support@careerexampro.com and we will put it right.
One-time payment. Nothing renews.
You have an exam ticket for this practice test. Start the timed mock exam to use it.
A campus distribution switch interface is assigned the IPv4 address 172.24.139.210/20. Which combination correctly identifies the subnet's network address, broadcast address, and usable host range?
B. Network 172.24.128.0, broadcast 172.24.143.255, usable range 172.24.128.1 to 172.24.143.254 (4,094 hosts).
A /20 prefix corresponds to subnet mask 255.255.240.0, which yields a block size of 256 - 240 = 16 in the third octet. Multiples of 16 in the third octet are 0, 16, ..., 128, 144. Since 139 falls between 128 and 143, the network ID is 172.24.128.0, the broadcast address is 172.24.143.255, and the usable range is 172.24.128.1 to 172.24.143.254 (2^12 - 2 = 4,094 usable hosts).
A platform engineering team stores Terraform state in a shared Amazon S3 bucket without state locking configured. Two CI/CD pipelines simultaneously execute terraform apply against the same workspace after merging separate pull requests. What is the primary operational risk, and how should the team prevent it?
Terraform merges concurrent state diffs via S3 Object Versioning, so only S3 PUT costs rise.
The second pipeline fails with a syntax error; adding terraform init -reconfigure prevents this.
Concurrent writes can corrupt state or leave orphaned resources; enable remote state locking (S3 native/DynamoDB or HCP Terraform).
Concurrent applies safely serialize at the AWS API layer through IAM throttling, so enabling S3 Transfer Acceleration is the only required change.
Show the answer
C. Concurrent writes can corrupt state or leave orphaned resources; enable remote state locking (S3 native/DynamoDB or HCP Terraform).
Without remote state locking, two concurrent terraform apply runs read the same starting state and race to overwrite the remote state file, causing lost updates, corrupted state, or untracked/duplicated cloud resources. Enabling state locking—via an S3 backend with native S3 lockfiles (use_lockfile = true) or a DynamoDB lock table, or via HCP Terraform's managed remote execution and locking—ensures only one state-mutating operation runs at a time.
A Cisco router interface GigabitEthernet0/1 with burned-in MAC address 5C:26:0A:7B:19:F4 is enabled for IPv6 using ipv6 enable without a manually configured link-local address. What IPv6 link-local address does IOS derive via Modified EUI-64, and which Neighbor Discovery Protocol (NDP) message verifies its uniqueness on the link?
fe80::5e26:aff:fe7b:19f4, verified by Duplicate Address Detection using a Neighbor Solicitation.
fe80::5c26:aff:fe7b:19f4, verified by DAD using an ICMPv6 Router Solicitation.
fe80::5e26:0aff:fffe:7b19, verified by Duplicate Address Detection (DAD) using a multicast ARP Request to ff02::1.
fe80::5a26:aff:fe7b:19f4, verified by DAD using a Neighbor Advertisement.
Show the answer
A. fe80::5e26:aff:fe7b:19f4, verified by Duplicate Address Detection using a Neighbor Solicitation.
Modified EUI-64 splits 5C:26:0A:7B:19:F4 in half and inserts FF:FE in the middle (5C26:0AFF:FE7B:19F4), then inverts the 7th bit (Universal/Local bit, 0x02) of the first byte: 0x5C (0101 1100) XOR 0x02 = 0x5E (0101 1110), yielding 5e26:0aff:fe7b:19f4, compressed to fe80::5e26:aff:fe7b:19f4. Before assigning any IPv6 address, NDP performs Duplicate Address Detection (DAD) by sending an ICMPv6 Neighbor Solicitation (Type 135) with unspecified source :: to the solicited-node multicast group.
An engineering team manages an AWS Auto Scaling Group (ASG), a Launch Template attached to it, and a stateful production RDS cluster in Terraform. They must ensure: (1) replacing the Launch Template never leaves the ASG without a valid template, (2) accidental terraform destroy cannot delete the RDS cluster, and (3) Terraform ignores ASG desired_capacity changes made dynamically by scaling policies. Which lifecycle settings satisfy all three requirements?
prevent_destroy = true on the template, ignore_changes = all on RDS, and create_before_destroy on ASG.
create_before_destroy = true on the template, prevent_destroy = true on RDS, and ignore_changes = [desired_capacity] on the ASG.
replace_triggered_by on the Launch Template, read_only = true on the RDS cluster, and skip_refresh = true on the ASG desired capacity.
create_before_destroy = false on the template, protect_state = true on RDS, and ignore_changes = [launch_template].
Show the answer
B. create_before_destroy = true on the template, prevent_destroy = true on RDS, and ignore_changes = [desired_capacity] on the ASG.
Terraform's default replacement order is destroy-then-create; setting `create_before_destroy = true` on the Launch Template (or ACM cert / target group) provisions the replacement before removing the old dependency. Setting `prevent_destroy = true` on the stateful RDS cluster causes Terraform to reject any plan that would destroy it. Setting `ignore_changes = [desired_capacity]` on the ASG prevents Terraform from reverting runtime scaling adjustments made by AWS Auto Scaling.
Reference: HashiCorp Terraform Documentation (The `lifecycle` Meta-Argument)
Two Catalyst switches are connected via an 802.1Q trunk (Gi1/0/24). Switch A has switchport trunk native vlan 10, while Switch B has switchport trunk native vlan 20. Both VLANs are allowed on the trunk, and CDP logs %CDP-4-NATIVE_VLAN_MISMATCH. What happens to data traffic sent from a host in VLAN 10 on Switch A across the trunk, and what is the recommended security hardening?
Switch A drops all VLAN 10 frames on the trunk until CDP resolves the mismatch.
VLAN 10 frames cross untagged and land in VLAN 20 on Switch B; align native VLANs or enable vlan dot1q tag native.
Switch A tags VLAN 10 frames with an explicit 802.1Q header because of the CDP mismatch, so Switch B delivers them normally to VLAN 10.
Switch B places untagged frames into VLAN 1 and err-disables Gi1/0/24 unless DTP is disabled.
Show the answer
B. VLAN 10 frames cross untagged and land in VLAN 20 on Switch B; align native VLANs or enable vlan dot1q tag native.
On an 802.1Q trunk, frames belonging to the locally configured native VLAN are transmitted untagged (unless vlan dot1q tag native is enabled). Thus Switch A sends VLAN 10 frames untagged, and Switch B interprets all received untagged frames as belonging to its native VLAN (VLAN 20), causing silent cross-VLAN leaking and potential spanning-tree topology inconsistencies. Aligning the native VLAN to an unused dedicated VLAN on both ends—and optionally tagging native frames with vlan dot1q tag native—prevents VLAN hopping.