SSO issues are often related to cached session data, cookies, or browser artifacts. The fact that the user can access the company portal but not one specific SaaS tool suggests a session or token problem. Using a private
/incognito browsing window allows a clean session to be initiated, which often resolves SSO conflicts.
A). Reenrolling MFA is not related unless access issues stem from failed multifactor authentication.
C). Bypassing SSO may not be possible depending on the SaaS tool and company policies.
D). Factory resetting a device is a last resort and unnecessary in this case.
Reference:
CompTIA A+ 220-1102 Objective 3.3: Troubleshoot common software, application, and OS security issues.
Study Guide Section: Troubleshooting login and authentication issues, especially with SSO services.

To allow Remote Desktop Protocol (RDP) access, the firewall must be configured to allow inbound connections on TCP port 3389. If the Windows Firewall blocks RDP, users will not be able to connect remotely even if the feature is enabled in system settings.
B). Computer Management allows configuration of services and local users, but not network access.
C). User Accounts is for account setup and control, but enabling remote access requires firewall configuration.
D). Ease of Access is unrelated to remote connectivity-it's for accessibility features.
Reference:
CompTIA A+ 220-1102 Objective 2.2: Compare and contrast security measures and firewall settings.
Study Guide Section: Enabling and securing RDP via firewall settings

3-D rendering is a graphics-intensive workload, and minimum hardware checks for this type of software commonly fail due to GPU capability (including dedicated vs. integrated GPU support) and VRAM requirements. Quentin Docter explains that application "Display" requirements can include "a graphics processing unit (GPU). A specific GPU may be required if the application will process video or graphics." He also notes that "VRAM requirements are typically related to applications that are graphic intensive, such as gaming," which aligns strongly with 3-D rendering workloads.
Mike Meyers' Lab Manual reinforces that "graphically demanding applications... state specific graphics requirements," and that CompTIA focuses on "dedicated graphics cards versus integrated ones," because integrated GPUs are often less capable for demanding graphics tasks. It also reminds that systems with integrated GPUs share RAM with graphics, which can matter when software checks VRAM.
Therefore, the first thing to verify is GPU requirements (B), not USB/NIC/PSU.

If uploading fails only offsite,mobile data limits or restrictionsare the likely cause. Data caps or network management can interfere with uploads.
FromTravis Everett - All-in-One Exam Guide:
"When mobile users experience network issues, always check if the device has reached a data cap or roaming restriction."

Explanation:
Issue: Limited network connectivity
Resolution: Refresh DHCP
Verify/Resolve: ipconfig
Issue (drop-down)
Limited network connectivity
Why this matches:
"Internet Down" most commonly indicates the workstation has lost valid Layer 3 connectivity (bad/expired DHCP lease, APIPA address, wrong gateway, etc.). In CompTIA A+ terms, this aligns best with limited connectivity symptoms (can't reach internet resources).
Resolution (drop-down)
Refresh DHCP
Why this is the most efficient fix:
If the client has:
an expired lease
an APIPA address (169.254.x.x) because DHCP failed
an incorrect IP/gateway from a bad lease
...then the fastest first remediation is to renew DHCP to obtain a correct IP address, default gateway, and DNS servers. This is a standard CompTIA A+ troubleshooting action (quick, low-risk, high-success).
Verify/Resolve (drop-down)
ipconfig
Why this is the correct verification tool:
ipconfig is the primary Windows CLI tool to:
check current IP settings (ipconfig /all)
release/renew DHCP (ipconfig /release and ipconfig /renew)
confirm you received a valid IP + gateway + DNS, which is required for internet access.
What you would do (mapped to those choices)
Using ipconfig to complete "Refresh DHCP" and confirm the fix:
Check current addressing
ipconfig /all
Look for:
Valid IPv4 (not 169.254.x.x)
Valid Default Gateway
DNS servers present
Refresh the DHCP lease
ipconfig /release
ipconfig /renew
Verify outcome
Run ipconfig again to confirm:
You now have a correct IP for the network
Default gateway is populated
If the gateway/DNS populate correctly, internet access typically returns.