hardmultiple choiceObjective-mapped

Exhibit

Emergency change request CHG-8841
Service: Customer portal login API
Reason: critical authentication bug causing lockouts

Pipeline status:
- Code review: pending
- Automated unit tests: skipped to save time
- Integration tests: failed once and were not rerun
- Rollback plan: not documented
- Approval: verbal yes from operations supervisor
- Deployment window: 21:30-22:00 tonight

Based on the exhibit, what is the best next step before the hotfix is released?

Question 1hardmultiple choice
Full question →

Based on the exhibit, what is the best next step before the hotfix is released?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Distractor review

Deploy immediately because the issue is customer-facing and urgent.

Urgency does not remove the need for basic change controls when the exhibit shows skipped tests and no rollback plan.

B

Distractor review

Close the ticket after deployment and create a postmortem if users complain.

A post-implementation review is useful, but it cannot replace required pre-release approvals, testing, and rollback planning.

C

Distractor review

Ask support to warn users that sign-in may fail during the next hour.

Customer communication may help operations, but it does not address the unsafe release process shown in the exhibit.

D

Best answer

Pause release until the change is formally approved, tested, and has a documented rollback path.

The exhibit shows multiple process gaps: skipped tests, unresolved integration test failure, no documented rollback plan, and only verbal approval. Even an emergency fix should follow an emergency change process with documented authorization and enough validation to reduce the chance of making the outage worse. The safest next step is to complete the required change controls before production deployment.

Common exam trap

Common exam trap: NAT rules depend on direction and matching traffic

NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.

Technical deep dive

How to think about this question

NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.

KKey Concepts to Remember

  • Static NAT maps one inside address to one outside address.
  • PAT allows many inside hosts to share one public address using ports.
  • Inside local and inside global describe the private and translated addresses.
  • NAT ACLs identify traffic for translation, not always security filtering.

TExam Day Tips

  • Identify inside and outside interfaces first.
  • Check whether the scenario needs static NAT, dynamic NAT or PAT.
  • Do not confuse NAT matching ACLs with normal packet-filtering intent.

Related practice questions

Related SY0-701 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this SY0-701 question test?

Static NAT maps one inside address to one outside address.

What is the correct answer to this question?

The correct answer is: Pause release until the change is formally approved, tested, and has a documented rollback path. — The hotfix should not be released yet. The change record shows missing code review, skipped unit tests, an unresolved integration-test failure, and no rollback plan, all of which create unnecessary operational risk. Even under an emergency timeline, the team needs formal approval, sufficient validation, and a documented way to revert if the fix causes new problems. Those controls are the foundation of safe change management. Why others are wrong: Immediate deployment ignores multiple red flags in the pipeline. A postmortem is useful after the fact but does not make the release safe. User notification may help service desk planning, but it does not reduce the technical risk of shipping unverified code. The right answer is to fix the process before release, not after.

What should I do if I get this SY0-701 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.